A missing bank charge
In this fictional example, Cedar Parts starts the period with 1,000 in both its bank statement and its bank account ledger. A customer receipt adds 400. The bank then deducts a charge of 15, so the statement closes at 1,385. The ledger still shows 1,400 because nobody recorded the charge.
Match the receipt to its ledger entry using the reference and amount. Then investigate the remaining 15. Once you confirm the bank charge, record the missing bank transaction against the appropriate expense account and match it. The ledger and statement can now reconcile at 1,385.
Changing the statement ending balance to 1,400 would conceal the missing charge.
Matching and timing
An entry may be correct but appear on a later statement. Keep that timing difference separate from an omitted entry. The task is to explain each outstanding transaction, not force every number into the current statement.
In Business Central, the bank reconciliation workflow compares statement lines with bank account ledger entries. A direct posting to a bank’s general ledger control account doesn’t create the bank account entry needed by that workflow. Check which ledger contains the transaction before trying to match it.
Practice sequence
Start with the Dynamics 365 course. Practice identifying a statement reference, investigating a bank charge and completing a reconciliation on original fictional data. The course’s local records don’t connect to a bank or send payments.
For the debit and credit behind the missing charge, review Accounting. For the wider product and exam boundary, use the certification guide.