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.
- Core Banking System
- Features
- Evidence and reconciliation
Evidence and reconciliation
Match provider movements against confirmed instructions and preserve exceptions.
OverviewReconciliation Exceptions×
Core Banking System · Evidence and reconciliation
New
Reconciliation Exceptions
Reconciliation items
| Provider event ID | Occurred at | Amount USD | State | Account | Matched instruction | |
|---|---|---|---|---|---|---|
| PEI-969 | 16 Oct | 290 | Unmatched | FA-140 | BI-50178 | |
| PEI-571 | 15 Oct | 830 | Exception | FA-150 | BI-92985 | |
| PEI-257 | 06 Oct | 180 | Unmatched | FA-110 | BI-40565 | |
| PEI-358 | 20 Oct | 40 | Exception | FA-130 | BI-90177 | |
| PEI-343 | 17 Oct | 890 | Unmatched | FA-120 | BI-65777 |
6 of 6 records
PEI-969Reconciliation items · RI-97277
UnmatchedOccurred at16 Oct
Amount USD290
AccountFA-140
Matched instructionBI-50178
What you can do
Treat provider evidence as an observed result
Bank evidence records provider statements, confirmations, settlement notices and corrections against an instruction. The provider event identifier, occurrence date, amount and verification state let the team distinguish received material from evidence that has been checked. A submitted instruction is not confirmed merely because it has a provider reference. The provider outcome workflow waits for verified confirmation or settlement evidence before the instruction is marked confirmed.
Account snapshots record the provider ledger and available balances for a specific account and date. Reconciliation items identify individual provider movements. Together, these records let the team investigate whether a confirmed instruction explains a movement and whether the account’s dated balance is consistent with the confirmed activity. The reconciliation workflow reads the account and the provider’s event identity before assigning a match.
How the work is organized
- Evidence intake. Provider statements and notices retain their event identity, type and verification state.
- Movement matching. Reconciliation items remain unmatched until the linked instruction, amount, date and account agree.
- Exception review. Differing dates or amounts stay open for investigation; no forced match clears them.
What to agree during setup
Set the provider event source and the time zone used when an occurrence date is compared with a confirmed instruction. Decide who verifies a confirmation or settlement notice, who investigates an exception and where provider corrections are received. Maintain the account identifiers used on both instructions and provider movements. Agree how a statement or correction is attached without overwriting the evidence that supported an earlier decision.
Suppose a provider statement shows a movement with the expected amount, but the occurrence date is one day later than the confirmed instruction. The team should leave that movement unmatched or classify it as an exception. A matching total does not justify changing the confirmed date. Investigate the source event, time zone and account, then reconcile only after the provider evidence and the instruction agree under the established rule. Preserve the original provider event identifier through that work.
Check the handoff on an actual case
Use one confirmed instruction and three provider movements: a complete match, an amount difference and a date difference. Confirm that only the first becomes matched. Test a movement assigned to another financial account even when its amount and date happen to coincide; it should remain open. Compare the opening provider ledger amount with signed confirmed movements and the closing snapshot for the same account. If a discrepancy appears, leave the item visible for review and retain the provider statement that explains the investigation.
What your team sees
- Reconciliation Exceptions — Work unmatched and exception movements with their account and provider event identity.
- Unverified Bank Evidence — Find provider notices that still need a verification decision.
- Confirmed Instructions — Check the instruction outcome behind a proposed match.
Follow the work through
Read provider outcome and bank reconciliation.
What it keeps track of
Data model- Bank evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
- Account snapshots
- Dated provider balance snapshots for a financial account.
- Reconciliation items
- Source-identified provider movements matched against banking instructions.
- 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
- Reconciles operational evidence.
- Treasury Preparer
- Follows provider responses and supplies context.
- Auditor
- Reads the retained events and exception history.
Set up Core Banking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.