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.
- Neobank Backend
- Features
- Bank reconciliation
Bank reconciliation
Compare provider movements and balance snapshots with confirmed instructions.
OverviewUnmatched Bank Movements×
Neobank Backend · Bank reconciliation
New
Unmatched Bank Movements
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched instruction | |
|---|---|---|---|---|---|---|
| PEI-335 | 23 Oct | 950 | Unmatched | FA-150 | BI-98066 | |
| PEI-927 | 05 Oct | 850 | Exception | FA-110 | BI-21110 | |
| PEI-574 | 19 Oct | 710 | Unmatched | FA-140 | BI-69578 | |
| PEI-258 | 22 Oct | 240 | Exception | FA-130 | BI-59453 | |
| PEI-799 | 09 Oct | 350 | Unmatched | FA-150 | BI-30048 |
6 of 6 records
PEI-335Reconciliation items · RI-36042
UnmatchedOccurred at23 Oct
Amount USD950
AccountFA-150
Matched instructionBI-98066
What you can do
Run the work
A provider movement arrives against a financial account. The reviewer traces it to the provider event, checks its amount and occurrence date, and looks for a confirmed instruction linked to that same account. The movement is matched only when those facts agree. Each provider movement carries an event identifier, occurrence date, amount and financial account. The reviewer compares it with a confirmed instruction linked to that account. Matching requires the same account, exact amount and exact confirmed occurrence date. A difference remains unmatched or becomes an exception; the team retains the provider event so the discrepancy can be investigated without forcing a match.
How the work is organized
- Identify the account. Use the provider account identifier and financial account reference for the movement.
- Compare the instruction. Check the confirmed instruction’s account lines, amount and occurrence date.
- Retain differences. Leave a mismatch unmatched or exceptional and keep its source event visible.
What to agree during setup
Choose the provider feeds that supply dated account snapshots and source-identified movements. Agree on the account code and external account identifier mapping. Define who investigates an unmatched movement and when an exception is escalated, while keeping the original provider event visible. Map the provider account reference to its financial account before bringing in movements. Test a matching event and separate amount, date and account discrepancies. Keep unmatched events visible for investigation.
Check the handoff on an actual case
Use one provider movement with the same amount and occurrence date as a confirmed instruction on the linked account. Then vary the amount, date and account in separate cases. The first can match; the others remain unmatched or become exceptions. Compare the latest ledger and available snapshots as context. Ask the next person to find the parent case and explain its status from the linked records. If a receipt is unclear, compare its claimed effects with persisted records before closing the investigation. Keep the dated account snapshot available as balance context, but do not use a matching balance alone to change a movement to Matched. The movement still needs a confirmed instruction with the exact account, amount and date.
What your team sees
- Unmatched Bank Movements — Compare source movements with confirmed instructions on the linked account.
- Reconciliation Exceptions — Investigate amounts, dates or accounts that differ.
Follow the work through
Work through bank reconciliation. Provider outcome explains the confirmed instruction that a movement can match.
What it keeps track of
Data model- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Financial accounts
- Provider-held financial accounts owned by a counterparty.
- Bank instructions
- Typed banking instructions moving through authorization, submission and confirmation.
- Instruction accounts
- Debit and credit account scopes that make an instruction balanced.
Who uses it
Permissions- Independent Treasury Approver
- Owns this decision.
- Treasury Preparer
- Assembles the case.
- Independent Treasury Approver
- Makes independent decisions.
- Auditor
- Reviews the resulting evidence in assigned scope.
- App Administrator
- Maintains organization membership and configuration.
Set up Neobank Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.