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.
- Mobile Banking App Backend
- Features
- Bank reconciliation
Bank reconciliation
Compare provider movements and account snapshots with confirmed instructions.
OverviewOpen Reconciliation Items×
Mobile Banking App Backend · Bank reconciliation
New
Open Reconciliation Items
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched instruction | |
|---|---|---|---|---|---|---|
| PEI-374 | 24 Oct | 40 | Unmatched | FA-110 | BI-61722 | |
| PEI-967 | 21 Oct | 470 | Exception | FA-120 | BI-35487 | |
| PEI-212 | 23 Oct | 110 | Unmatched | FA-110 | BI-52391 | |
| PEI-339 | 27 Oct | 790 | Exception | FA-140 | BI-41213 | |
| PEI-713 | 04 Oct | 620 | Unmatched | FA-120 | BI-52145 |
6 of 6 records
PEI-374Reconciliation items · RI-35000
UnmatchedOccurred at24 Oct
Amount USD40
AccountFA-110
Matched instructionBI-61722
What you can do
Reconcile the observed movement
A provider movement enters reconciliation with its own event identity, account, occurrence date and amount. The reconciliation analyst compares it with a confirmed instruction linked to the same account. A match needs the exact amount and confirmed occurrence date. A similar amount on a different date, or the right date on another account, remains open for investigation.
Account snapshots provide dated ledger and available balances for the account. Bank evidence explains the provider’s confirmation or settlement event behind a particular instruction. Together these records give the team a way to trace an apparent movement from account observation back to the authorized request and its provider evidence.
How the work is organized
- Source movement. A reconciliation item retains the provider event identity so a repeated import can be recognized.
- Match decision. Matched items point to the bank instruction; unmatched and exception items stay visible.
- Balance observation. Snapshots preserve the as-of date and provider snapshot identity for comparison over time.
The analyst should inspect both the account scope and the confirmed instruction before accepting a match. A matching amount alone is insufficient, since unrelated instructions can carry equal amounts. Differences need a named owner and a documented next action rather than a forced match to clear a queue.
What to agree during setup
Decide which provider feeds supply movement and snapshot records, how event identities are retained and who investigates discrepancies. Agree how to interpret provider dates across time zones. The team should know whether a given movement is a debit or credit account effect before comparing a signed balance change with an instruction scope.
Define the escalation path for a missing provider event, a date difference and an amount difference. The reconciliation analyst can examine the item and attach the relevant instruction, while a treasury owner contacts the provider if more evidence is required. Keep audit access read-only so an investigation does not alter the original provider observation.
Check the handoff on an actual case
A confirmed instruction moves an amount on a provider account. A reconciliation item arrives with the same account, amount and occurrence date. The analyst checks the linked account and confirmation evidence, then matches the movement to the instruction. The next account snapshot provides a dated balance observation for the period under review.
Run a second case where the provider amount differs by a small amount. Leave the movement unmatched or mark it as an exception; do not round it into a match. Run a third case with the correct amount on the wrong date. The result should again remain open until the provider record or instruction evidence explains it.
What your team sees
- Open Reconciliation Items — Provider movements that need matching or exception review.
- Confirmed Instructions — Instructions with provider outcome evidence available for comparison.
Follow the work through
Use account reconciliation and completion review.
What it keeps track of
Data model- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Bank evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Instruction accounts
- Debit and credit account scopes that make an instruction balanced.
Who uses it
Permissions- Reconciliation Analyst
- Investigates movements and snapshots.
- Treasury Preparer
- Supplies instruction context and contacts the provider.
- Auditor
- Reviews the match and original evidence without changing them.
Set up Mobile Banking App Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.