A currency payment can reach its destination while the institution that sent it still reports an unsettled obligation. Reconciliation is the process of matching expected cash movements against bank statements, payment confirmations and internal settlement records. When those sources disagree, the issue may be missing information rather than missing money.
For an fx trade, reconciliation usually involves two currency legs, potentially different banks and distinct payment identifiers. The five causes below explain why an apparently completed exchange can remain unresolved long after execution.
Payment References Do Not Match the Trade Record
An operations system may expect a deal number in the incoming payment narrative, while the correspondent bank transmits only a shortened reference. Automated matching then fails even when the amount, currency and beneficiary are correct.
The difficulty grows when one payment covers several transactions or when a bank replaces the original reference with its own tracking code. Reliable reconciliation requires a maintained link between trade identifiers, payment instructions and bank transaction references. Guessing a match solely from an amount can assign cash to the wrong obligation.
Intermediary Charges Create Unexpected Net Receipts
Cross-border payments can pass through intermediary institutions that deduct charges, depending on the payment route and fee arrangement. The beneficiary may receive less than the amount expected by its ledger, creating an exception that resembles a short payment.
Imagine a hypothetical company selling SGD 500,000 against Japanese yen through a bank and expecting the full SGD amount in its designated account. The payment instruction specifies SGD 500,000, but a correspondent deducts SGD 45 in charges, leaving SGD 499,955 credited. An automated matcher requiring exact equality rejects the receipt. The SGD 45 difference is not a currency-market loss; it is a payment charge requiring investigation and the correct accounting treatment. The operations team must also confirm whether the agreed fee arrangement permitted that deduction.
Settlement Dates Differ From Bank Posting Dates
A payment’s contractual value date, the date its bank processes the instruction and the date it appears on an account statement need not be identical. Local holidays, correspondent cutoffs and delayed statement delivery can put a valid payment into the next reporting period.
A reconciliation rule that compares only calendar dates may incorrectly flag the cash as overdue. Matching should distinguish contractual settlement from statement posting and retain the relevant time zone. Otherwise, teams may escalate a timing exception as a genuine failure to pay.
Split Payments Defeat One-to-One Matching Rules
Large settlements may arrive in installments because of operational limits, repair procedures or separate funding sources. A system expecting one receipt for one fx trade can leave every installment unmatched until someone recognizes their combined total.
For example, three receipts of SGD 200,000, SGD 175,000 and SGD 125,000 equal a SGD 500,000 obligation. Yet combining amounts is safe only when currency, beneficiary, value date and traceable references support the relationship. Overly permissive matching can hide a duplicate payment or misallocate funds from another transaction.
Internal Settlement Statuses Are Updated Out of Sequence
A payment instruction marked ‘sent’ is not necessarily proof of final receipt. Messaging acknowledgments, bank debit confirmations and beneficiary credits represent different stages, and interfaces may deliver their updates in an unexpected order.
The resulting mismatch can persist even after the cash is available. Operations teams should reconcile against authoritative bank evidence and preserve an audit trail of reversals, repairs and final confirmations rather than treating the latest status message as definitive.
Before opening a currency CFD position alongside a physically settled hedge, verify which account funds the position, which currency payments are expected and how unmatched receipts are escalated. Confirm that a reconciliation exception will not be mistaken for available collateral or an unpaid hedge when assessing the combined exposure.