Payments Training Hub

FLOW-04: Reconcile Payments Across Messages, Statements, and Ledger

Flow. Payment reconciliation

Every payment leaves a trail in several places: the payment message, the nostro statement, the clearing record, the settlement record, and the ledger. When those records agree, the bank can close the day with confidence. When they disagree, the difference is a break that must be found, explained, and fixed before it affects a customer or a financial report. You will also learn how to prove that every payment was accounted for, even when the source systems disagree about the amount, the date, or the reference. In this lab you act as the business analyst for the full reconciliation flow. You will define the matching rules, the tolerances for fees and foreign exchange, and the handling of missing, duplicate, and partial matches. You will design the break workflow, the ageing and escalation rules, and the reports that finance and operations use each day. By the end you will have a complete pack that finance, operations, treasury, audit, and technology can use to run daily reconciliation with confidence.

0 of 6 steps done. Tick each step as you finish it, your progress is saved in this browser.

  1. Interview the finance manager, the operations manager, and the audit lead to agree what reconciliation must prove each day. Record the pain: breaks that sit for weeks, manual spreadsheets, and month end surprises. Define the accounts, the payment types, and the sources in scope, including clearing files, nostro statements, settlement records, and the ledger. Set measurable objectives, for example 98 percent auto match, no break older than five business days, and a balanced daily report. Get the sponsor to confirm the objectives before you write any requirement.

  2. List every stakeholder, from finance and operations to treasury, audit, compliance, technology, and each correspondent bank. Build a RACI for the key decisions, naming who is responsible, accountable, consulted, and informed. Walk the current reconciliation process with the team and draw the as-is diagram, showing every step, system, handoff, and wait. Record the break volumes by type, the average age of a break, and the time spent on manual matching, so the redesign is based on evidence.

  3. Define the matching keys for each payment type, using the transaction reference, the amount, the currency, and the value date. State the tolerance for fee differences and foreign exchange differences, and the rule for each tolerance, including who approves a match outside tolerance. Define the rules for partial matches, duplicate records, and missing records, with a clear outcome for each case. Walk the rules through with finance using three real examples, one clean match, one fee difference, and one missing record, and correct any rule the examples prove wrong.

  4. Define how a break is created, who owns it, and the steps to investigate it, from checking the source file to contacting the correspondent bank. Set the ageing rules: a break is investigated within one business day, escalated after three days, and reported to management after five days. Define the suspense accounting rule for unmatched funds and the write off rule, including the approval level for each amount band. Agree the workflow and the ageing rules with finance and audit, so no break sits without an owner or a deadline.

  5. Write the functional requirements as testable statements, each with a unique identifier, a priority, and an acceptance test in mind. Cover file ingestion, validation, matching, break creation, manual matching, write off, reporting, and audit trails. Then write the non-functional requirements: processing of the full daily volume within two hours, 99.5 percent availability, data retention for seven years, audit logging of every change, and data protection. Review the full set with finance and the test lead, and trace every requirement to a business objective.

  6. Define the daily, weekly, and monthly reports, including the match rate, the break count by age and type, and the suspense balance. Define the defect analysis that groups breaks by root cause, such as missing references, fee differences, and late files, with a fix owner and a prevention action for each cause. Define the controls: a four eyes check for write offs above 5,000 pounds, a full audit trail, and a daily sign off by finance. Present the full pack to finance, operations, treasury, and audit for sign off.

Artefacts you produce.

Worked example. Falconbridge Bank, a fictional bank in Birmingham, reconciles its payments every morning. On 12 May 2026 the team receives a clearing file with 4,200 records, a nostro statement from its correspondent, and the ledger extract for the previous day. The matching engine auto matches 4,110 records, a rate of 97.9 percent. One break is a 10,000 dollar SWIFT payment with reference FAL-2026-5520 that appears in the ledger but not in the clearing file. The analyst checks the settlement record and finds the clearing file arrived late, so the record will match the next day and the break is marked as timing, not error. A second break is a 500 euro SEPA payment where the ledger shows 498.50 euros after a 1.50 euro fee, while the clearing record shows 500 euros. The difference is within the agreed 2 euro tolerance, so the system matches it and records the fee separately. A third break is a duplicate 2,000 pound Faster Payments record that appears twice in the file. The analyst confirms the duplicate, removes one record, and logs the root cause as a file generation error. The team reports the match rate, the 90 breaks by age and type, and the suspense balance to finance, and the daily report is signed off before 10:00.