Courses / Commodity Trading Operations & ERP
Bank reconciliation — when the statement, not the ledger, is wrong
A variance that looks like a posting error is often a gap or a defect in how bank statements reached the system at all.
Lesson 1 · free to read
A reconciliation can break even when the bank did nothing wrong
A bank reconciliation matches two independent records of the same cash: what the ERP posted from invoices and payment runs, and what the bank's own statements say happened. Most systems import one statement per account per period. If a period is simply never imported, the gap is invisible until someone goes looking.
Worked example (figures re-based). A multi-currency treasury's last successfully imported statement for an account closed at USD 1,000,000.00. The next statement imported for that account opened at USD 1,090,500.00, continuing correctly from the bank's own books. In between, two calendar days of statements were never uploaded. The ERP had already recorded a customer receipt of USD 142,000.00 and a supplier payment of USD 51,500.00 against those two dates, because finance posts from invoices and payment instructions, not from bank statements. With no statement lines imported for those two days, the matching engine had nothing to match those two postings against, and the account sat unreconciled by exactly USD 90,500.00 (142,000.00 − 51,500.00) — the net of the missing period — even though the bank's own records had no gap at all.
The giveaway. A variance that equals a plausible net cash movement for a short period is a different animal from a rounding difference or an FX-revaluation difference. Chasing it at the transaction level finds nothing, because the transactions are not wrong; the statement coverage is incomplete.
What a system must therefore do: track the date range each account has imported statements for as a first-class fact, and flag a gap in that coverage before running the matching engine, rather than only surfacing a currency-level variance after the fact and leaving someone to rediscover the gap by hand.
The rest of this module
- A parser that silently drops a line is worse than one that fails loudlyTwo statement-import defects in the same engagement both hid the same way: a plausible-looking statement that was quietly wrong.
- Why matching should prefer a reference over date and amountA matcher that only compares date and amount can swap two unrelated transactions that happen to coincide.
Carry on with the course
The other lessons and the quiz are in the course itself, where your progress is saved and counts towards the certificate: Commodity Trading Operations & ERP.
Next module: Implementing a trading system — requirements, go-live, and life afterwards