Reconciliation

A provider movement enters the reconciliation register with its source event identifier, occurrence date, amount and financial account. It can be Unmatched, Matched or Exception. A matched item points to the vault transfer that explains it. The match must use the same account, the exact amount and the confirmed occurrence date; a similar amount or nearby date is a question for review, not a substitute for evidence.

Account snapshots add dated ledger and available balances. They provide the provider’s observed position at a point in time. The Credit Reviewer can compare opening and closing positions with the signed confirmed movements and isolate a difference. Assessment evidence supplies the event trail for the transfer, and the operation receipt helps explain whether an attempted action persisted its claimed effects.

• Source movement. Keep the provider event identifier, date, amount and account together.
• Exact match. Link a movement to a confirmed transfer only when amount, date and account agree.
• Exception. Keep mismatches visible with snapshots and transfer evidence for investigation.

Agree how provider snapshots and movement identifiers arrive, who checks their source, and how often the branch reconciles each account. The team should use one date convention for provider occurrences and transfer confirmations. Decide who owns an Exception and how the explanation is recorded when the provider corrects an event. A correction should preserve the earlier evidence rather than making the original record disappear.

Define a review path for operation receipts marked needs review. The reviewer should inspect actual effect references and the linked transfer before considering the operation complete. The process should not issue a second provider instruction to solve a local uncertainty about the first one.

Take a Confirmed transfer with a verified settlement event. Load the provider movement for the same financial account, amount and occurrence date. Check that it becomes Matched and points to that transfer. Then try a movement with a different date and another with a different amount. Keep those Unmatched or mark them Exception for review. Use snapshots before and after the period to explain the ledger movement and identify any residual difference.

Ask an Auditor to inspect a selected Exception. They should see the provider event identifier, account, amount and date, then navigate to the proposed transfer and its confirmation evidence. An unmatched movement is still an observed provider event; the team should not force it to a transfer just to clear the queue.

• Reconciliation exceptions — Provider movements whose account, amount or date need explanation.
• Unmatched movements — Source events waiting for an exact confirmed transfer match.
• Receipts needing review — Operations whose claimed effects need verification.

Follow account reconciliation and completion verification.