Payments Officer¶

You turn approved beneficiaries into a paid batch: generate it, check the accounts, get it signed off by two officers, send it to the bank, and reconcile what comes back. Your work happens under Payments in the left sidebar.

This role moves money

Every batch you approve becomes a real bank instruction. Payment guides mark the irreversible steps clearly — never approve a batch you have not reviewed.

What you can do¶

Task	Guide
Generate a batch and get it approved by two officers	Create and approve a payment batch
Hold a beneficiary out of one run, with a reason	Exclude a beneficiary — coming soon
Match the bank's response back to the batch	Reconcile a bank response — coming soon

%%{init: {'theme':'base','themeVariables':{'primaryColor':'#eef0f7','primaryTextColor':'#1a2e35','primaryBorderColor':'#3d4476','lineColor':'#6b7488','fontFamily':'inherit','fontSize':'15px'}}}%%
flowchart LR
    R(("Payments<br/>Officer"))
    R --> A["Build a batch"]
    A --> A1["Generate"]
    A --> A2["Validate accounts"]
    R --> B["Before approval"]
    B --> B1["Exclude with a reason"]
    R --> C["Approve"]
    C --> C1["First sign-off"]
    C --> C2["Second sign-off"]
    R --> D["After the bank"]
    D --> D1["Download instruction file"]
    D --> D2["Reconcile response"]
    classDef hub fill:#dfe3f2,stroke:#3d4476,stroke-width:2px,color:#1a2e35;
    classDef topic fill:#eef0f7,stroke:#3d4476,color:#1a2e35;
    classDef detail fill:#f4f6fb,stroke:#6b7488,color:#1a2e35;
    class R hub;
    class A,B,C,D topic;
    class A1,A2,B1,C1,C2,D1,D2 detail;

How a batch flows¶

%%{init: {'theme':'base','themeVariables':{'primaryColor':'#eef0f7','primaryTextColor':'#1a2e35','primaryBorderColor':'#3d4476','lineColor':'#6b7488','fontFamily':'inherit','fontSize':'15px'}}}%%
flowchart LR
    A[Create Batch] --> B[Queued]
    B --> C[Processing]
    C --> D[Complete]
    D --> E[First approval]
    E --> F[Second approval]
    F --> G[Approved 2/2]
    G --> H[Instruction file]
    H --> I([Bank]) --> J[Reconcile response]
    classDef good fill:#eef2ec,stroke:#657e6b,color:#1a2e35;
    classDef topic fill:#eef0f7,stroke:#3d4476,color:#1a2e35;
    class G good;
    class H topic;

The batch is generated once and then paid exactly as generated — the amounts and account details are frozen the moment it finishes building (the "approval snapshot"). Checking accounts and excluding people happens before approval; after the second sign-off the batch is locked.

Permissions you need¶

Create a batch — pym:ls:crt
First / second approval — pym:bc:ap:fr / pym:bc:ap:sd
Validate accounts — pym:bc:val; exclude a beneficiary — pym:exc:mg
Generate / download the instruction file — pym:ins:gn / pym:ins:dl
Upload / export reconciliation — pym:rcn:imp / pym:rcn:exp