These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Treasury Operations
- Features
- Bank reconciliation
Bank reconciliation
Match provider entries and balance snapshots to confirmed instructions, raise every difference as an exception and reconcile operation receipts.
OverviewReconciliation Exceptions×
Treasury Operations · Bank reconciliation
New
Reconciliation Exceptions
Reconciliation items
| Account | Provider event ID | Occurred at | Amount USD | Matched instruction | State | |
|---|---|---|---|---|---|---|
| FA-130 | PEI-331 | 23 Oct | 890 | BI-87156 | Unmatched | |
| FA-120 | PEI-904 | 14 Oct | 590 | BI-83012 | Exception | |
| FA-110 | PEI-688 | 26 Oct | 650 | BI-55290 | Unmatched | |
| FA-110 | PEI-397 | 16 Oct | 710 | BI-21000 | Exception | |
| FA-110 | PEI-454 | 23 Oct | 780 | BI-35978 | Unmatched |
6 of 6 records
PEI-331Reconciliation items · RI-80006
UnmatchedAccountFA-130
Occurred at23 Oct
Amount USD890
Matched instructionBI-87156
What you can do
Make every bank balance explainable
The bank’s view of each account arrives as balance snapshots and entries. A snapshot records the account, the as-of date, the ledger balance, the available balance and the provider’s snapshot identifier. Each provider entry records the provider’s event identifier, the date and the amount against the account. The Reconciliation Analyst matches each entry to the instruction it settles.
Matching is exact: the provider identity, amount and date must agree. A match marks the entry Matched with the instruction it belongs to. Anything else stays Unmatched or becomes an Exception with the difference visible. Nothing is forced to fit. For each account, the opening ledger balance plus confirmed movements must equal the closing snapshot.
Every controlled action on an instruction leaves an operation receipt. Receipts that are Pending or Failed are reconciled against the effects they name: a receipt is Completed only when the recorded effect is found, and moves to needs review when it is not.
How the work is organized
- Snapshot and entries per account. Each import carries the provider’s identifiers, so repeating an import does not duplicate it.
- Exact matching. An entry with a different amount or date stays an exception for the analyst to explain.
- Receipts closed on evidence. Pending and failed receipts are checked against the records they claim to have changed.
What to agree during setup
Agree the import schedule for each bank, such as an intraday and an end-of-day statement. Agree how opening balances are set for the pilot month. Agree who explains exceptions and by when, and who may close one. Agree how bank fees and interest, which have no instruction, are handled in your ledger.
Check the handoff on an actual case
The end-of-day statement for the RB-LON deposit account shows two entries: a credit of 25,000,000 with event RB-88412 and a fee of 35. The analyst matches the credit to the confirmed deposit instruction by event identifier, amount and value date. The fee has no instruction and becomes an Exception for the ledger team.
The closing snapshot shows a ledger balance of 24,999,965. Opening balance zero plus the confirmed deposit, less the fee exception, explains the balance in full. The analyst then opens Receipt Exceptions and finds the morning’s needs review submission receipt. The instruction is now confirmed with its evidence, so the receipt is marked Completed.
What your team sees
- Reconciliation Exceptions — Unmatched and exception entries by account, with event identifier, date and amount.
- Account Snapshots by Date — Ledger and available balances per account by as-of date.
- Receipt Exceptions — Pending, failed and needs-review receipts with expected revision, effects and failure reason.
Follow the work through
- Statement to reconciled account: Import, match and explain each account.
Connect your bank statements before the pilot month.
What it keeps track of
Data model- Account snapshots
- Timestamped provider balance snapshots imported for reconciliation.
- Reconciliation items
- Source-identified provider entries matched against instructions and evidence.
- Operation receipts
- Idempotent execution receipts for every guarded treasury operation.
- Financial accounts
- Provider-held treasury accounts and their external identities.
- Bank instructions
- Typed banking instructions raised by the treasury desk.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- Reconciliation Analyst
- Imports snapshots and entries, matches them and reconciles receipts.
- Settlement Officer
- Helps explain exceptions on recent instructions.
- Treasury Manager
- Reviews open exceptions.
- Admin
- Corrects access.
Set up Treasury Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.