← hr.manpower.host

Open Payroll & payments in your workspace

Automated payment workflow — preview

ILLUSTRATIVE PREVIEW · Visible to public documentation viewers (illustrative); operational access remains role-gated inside Payroll. Isolated from live dispatch.

These rows are fictional demonstration data. They are not operational payroll, not exported into reports, and do not transfer funds. No payment API is called. Operational payroll preparation remains on the other Payroll tabs.

Proposed payroll and transfer stages. A future finance release would require an authorized operations administrator. Existing payroll approval and external payment reconciliation remain separate steps.

  1. 1
    Attendance and tax inputs locked into a draft run.
  2. 2
    Totals, beneficiary readiness and dual-control checks.
  3. 3
    A different operations administrator approves the run.
  4. 4
    Finance authorises release for provider submission (ops role today).
  5. 5
    Batch submitted to the payment provider — not connected in Production.
  6. 6
    Accepted / settled / failed / unknown outcomes reconciled.
  7. 7
    Close settled payments; unresolved items remain open until resolved.

Stage 1 of 7: Prepare payroll. Attendance and tax inputs locked into a draft run. This walkthrough changes fictional display data only.

Illustrative scenarios

All transfers confirmed settled

Illustrative instructions at the prepare payroll stage. Choose a later stage to explore the selected provider outcome.

ILLUSTRATIVE ONLY — fictional QC batch · PREVIEW-BATCH-2026-10-DEMO · Demo HR Firm (fictional) · period 2026-10

Employees (demo)3
Net BDT (demo)87,150
Settled0
Failed0
Unknown0
Per-employee illustrative transfer status
Employee (demo)Net BDTStateProvider refNote
A. Rahman (demo)
DEMO-E-001		28,500Not submittedNot assignedIllustrative only; no payment submitted from this page.
S. Akter (demo)
DEMO-E-002		31,200Not submittedNot assignedIllustrative only; no payment submitted from this page.
K. Hossain (demo)
DEMO-E-003		27,450Not submittedNot assignedIllustrative only; no payment submitted from this page.

States remain distinct: approved → submitted → accepted → settled, with failed and unknown never shown as settled.

Payment provider capabilities awaiting official documentation
  • Official shurjoPay (or successor) payout / disbursement API contract and sandbox credentials
  • Beneficiary registration and account-validation callbacks
  • Delivery / settlement webhooks with idempotent Message or Transfer IDs
  • Confirmed failure taxonomy distinct from timeout/unknown
  • Resubmission rules that never silently retry unknown outcomes
  • Written go-live approving LIVE automated disbursement (separate from this preview)

Until those documents and a written go-live exist, this workspace stays on external payment evidence + independent reconciliation only. Automated payout remains disconnected.