Reconciliation Matching Hierarchies and Suspense Account Management

Reconciliation compares the internal ledger with the external statement, and it starts with exact matching on the reference, the amount and the value date. When the correspondent statement shows USD 120,000 with the same end to end identification and the same value date as the internal record, the item matches exactly and is closed without human touch. Exact matching handles the large majority of payments, because straight through processing produces clean references and clean amounts, and it is the fastest and safest level. The matching engine runs every morning on the previous day activity, and it reports the matched rate as a key measure of operational health. Testing exact matching means sending a payment with a clean reference and confirming it matches and closes automatically, with no manual intervention and no break record created. When exact matching fails, the engine tries amount and value date matching, and then fuzzy matching on close but not identical names, references and amounts. A payment of USD 120,000 that arrives with a value date one day late, or with a reference that differs by one character, can still be matched if amount and beneficiary agree and the difference is clear. Fuzzy matching uses rules and scores, and it proposes a match for an operator to confirm rather than closing the item automatically, because a wrong match can hide real errors. In the worked example, the USD 120,000 payment matches on amount and value date despite a shortened reference on the statement, and an operator confirms it after checking the UETR. Testing fuzzy matching means creating a one character reference difference and confirming the engine proposes the match, and creating a wrong amount and confirming it proposes nothing. Items that do not match at any level go to a break queue, where an operator investigates the difference and decides how to resolve it. The break record shows the internal ledger entry, the external statement entry, the difference in amount or date, and the age of the break, so the operator can see the whole problem at a glance. Common breaks are missing statements, value date differences, correspondent charges, and payments that arrived but were never booked. In the worked example, a USD 120 charge deducted by the correspondent creates a break on the USD 120,000 payment, because the statement shows USD 119,880 while the ledger shows USD 120,000, and the operator books the charge to a charges account and closes the break. Testing the break queue means creating a charge difference, confirming the break appears with the right amount, and confirming the resolution is recorded. A suspense account holds money that cannot yet be matched to a payment, and it must never become a hiding place for unexplained funds. When a payment arrives without a clear reference, or a break cannot be resolved on the day, the amount is posted to suspense with the full detail attached, and operations works the balance every day. Ageing rules escalate suspense items, for example to a supervisor after five days and to senior management after thirty days, and write off needs dual approval and a documented investigation. In the worked example, the USD 120,000 payment never touches suspense because it matches the next morning, but a USD 4,500 receipt without a reference sits in suspense for three days until the sender is found. Testing suspense control means ageing an item past each threshold and confirming escalation fires and a write off without dual approval is refused.