Payments
4 events
One high value
Message status
Pending
Confirmation needed
Impact
ETB 180m
Liquidity action
Owner
Payments Ops
Action due
Operator Workbench
The screen starts with the bank decision, owner, blocker, and next handoff.
Route/intraday-liquidity/payments
Payments ops / Treasury operations
Primary decisionWhich payments affect liquidity and need escalation?
Owner: Payments Operations
Current blockerOne high-value ETB payment is pending without confirmation.
Approvals and evidence control the next step.
Next actionOpen payment impact and confirm settlement status.
View Payment Impact
Payment Event Stream
Payment events show liquidity impact and ownership.
| Time | Message type | Amount | Currency | Status | Counterparty | Impact |
|---|---|---|---|---|---|---|
| 09:42 | MT / camt placeholder | 180,000,000 | ETB | Pending | Bank C | High-value liquidity impact |
| 10:15 | MT / camt placeholder | 42,000,000 | ETB | Settled | Corporate customer | Normal |
| 11:05 | MT / camt placeholder | 1,200,000 | USD | Queued | Foreign bank | Nostro impact |
Payment Detail Drawer
Configuration and approval controls stay visible beside the workpaper flow.
| Field | Value | Evidence / action |
|---|---|---|
| Message type | camt placeholder | Review |
| Counterparty | Bank C | Required |
| Impact | ETB 180m | Treasury review |
Required Inputs
Bank-provided inputs needed before this workspace can support official calculation evidence.
| Data requirement | Configuration status | Owner | Next action |
|---|---|---|---|
| Payment event feed | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Payment time | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Message type | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Amount | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Currency | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Status | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Counterparty | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Impact | Evidence needed | Bank data owner | Provide source extract or policy reference |
Operational States
The same screen accounts for empty, loading, blocked, validation, and approval states.
Loading stateSource checks runningLarge extracts stay in review until hash, row count, and schema validation finish.
Empty stateNo approved source rowsThe workspace shows required inputs and owner handoff instead of empty charts.
Blocked stateEvidence or approval missingOfficial output stays unavailable until the blocker is cleared by the owner.