Settlement reconciliation

A provider movement can arrive after the instruction was submitted, perhaps after the requested value date. The movement record keeps its provider event identifier, receipt date, amount, account and matched instruction. The settlement team uses these references to decide whether the movement belongs to an existing instruction. Matching by amount alone would be weak when several instructions have similar values.

The operation receipt is the other half of the check. It records what the operation claimed to do, the expected revision and the references to actual effects. The Independent Credit Approver reads the persisted instruction, decision, evidence and movement before marking an open receipt completed. If an effect is missing or points to a different case, the receipt goes to needs review with the discrepancy rather than triggering another provider action.

• Movement queue. Separate unmatched and exceptional provider events from movements linked to an instruction.
• Effect verification. Compare receipt claims with the local records they cite before closing the operation.
• Account snapshots. Keep dated provider balance snapshots with the account to support follow-up on amounts due.

Choose who imports or records provider events and how duplicate event identifiers are handled. Decide which source record is authoritative for a posted movement. Record each movement with its provider account and candidate instruction, then check the source before marking it matched. An exception should say what disagrees: event identity, account, amount, timing or missing instruction. The team should not conceal uncertainty by forcing a match.

The dated account snapshots show principal and interest due from the provider. Agree the snapshot source and refresh cadence before relying on a report. These records are useful for checking account-level balances; they do not replace the provider’s underlying transaction evidence. Keep the snapshot identifier so a later correction can be traced to the right imported source.

Import a provider event for a known account and instruction. Compare its provider identity, amount and receipt date with the instruction and verified evidence. Confirm its instruction link only when the source supports the association, then move it to matched. Try a second event with the same amount but a different provider identifier; it should stay in the unmatched or exception queue until investigated.

Open the operation receipt for the instruction and follow each effect reference. A completed receipt should point to persisted evidence or movement records, not just a successful request message. If a referenced effect is absent, record the concrete failure reason and leave it for review. Ask the Auditor to retrace the instruction from owner and decision through provider evidence, movement and receipt without changing any record.

• Movements needing match — Unmatched and exceptional provider movements with account and instruction references.
• Operation exceptions — Receipts whose effects failed or require investigation.
• Confirmed instructions — Instructions with verified provider outcome for comparison with settlement evidence.

See settlement reconciliation for the matching and receipt checks, and provider outcome for the preceding external response.