← The journalFINANCE / HOW-TO

Bank reconciliation without the Friday-night spreadsheet

Reconciliation is painful when it is done monthly and by hand. Import daily, match by rule, and keep only real exceptions for people.

Heather landscape with directional camera-motion blur.FINANCE / SUNDIAL
Photography: Doncoombez / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

Reconcile a little every day, let rules match the obvious items, and spend human attention only on the lines that genuinely do not match.

Why reconciliation piles up

Bank reconciliation is the act of confirming that every transaction on the bank statement is recorded in the books, and every bank transaction in the books appears on the statement. It is simple in principle. It becomes painful because it is usually done once a month, after hundreds of lines have accumulated, by someone matching a downloaded statement against a ledger export.

At that volume, the hard items hide among the easy ones. A customer payment that covers three invoices, a bank charge nobody recorded, a check that has not cleared: each one takes minutes to understand, and they arrive all at once.

Import statements daily

The first change is frequency. Import the bank statement every business day, or as often as your bank allows. Twenty lines a day is a five-minute task while the details are fresh. Who sent that payment and what it was for is easy to remember on Tuesday and hard to remember three weeks later.

Use the bank's statement file rather than retyping. Retyping introduces errors into the one process meant to catch errors.

Assign one owner per bank account and a backup. Daily work that belongs to everyone tends to belong to no one by the second week.

Match by rule

Most bank lines match something already in the system: a payment entry for the same amount, a customer receipt with the invoice number in the reference, a supplier payment on the expected date. Matching should start with exact matches on amount and reference, then amount and date within a short window, then amount and party.

For recurring items such as bank charges, interest and card fees, set up rules that create the accounting entry automatically when the line arrives. These items should never need a human again.

Handle the exceptions properly

What is left after matching is the real work. A customer paid one amount against several invoices: allocate it across them. A customer paid less than invoiced: record the payment, then decide whether the difference is a deduction, a dispute or a discount. A payment arrived from an unknown party: park it in a suspense account with a note, and chase it the same day.

Never force a match to make the numbers agree. A wrong match is worse than an unmatched line, because it hides the problem and spreads it into customer balances.

Keep references clean at the source

Matching is only as good as the information on each bank line. Ask customers to quote the invoice number when they pay, and put that request, with your bank details, on every invoice. When you pay suppliers, include their bill number in the payment reference so their reconciliation is easy too; it shortens the conversation when they ask what a payment was for.

Use one bank account per purpose where you can. Collections, supplier payments and payroll running through separate accounts make each statement shorter and the patterns easier to match.

Record checks and post-dated payments when they are issued, with the expected clearing date. An uncleared check is not an error; it is a timing difference, and it should appear on the reconciliation as one until the bank clears it. Review anything that stays uncleared for longer than usual, because a lost check is easier to replace in the first week than the first quarter.

What a clean reconciliation proves

When the bank is reconciled daily, the cash figure in the books can be trusted every day, not just at month end. That trust flows outward: customer balances are right because receipts are applied correctly, supplier balances are right because payments are recorded against the right bills, and the month-end close loses one of its longest tasks.

It also gives you an early warning. An unexpected debit, a duplicate payment or a missing receipt is visible within a day.

How it works in Sundial

In Sundial, bank transactions, payment entries and invoices are part of the same Finance and Accounting module. A bank line matched to a payment is matched to the invoices that payment settled, so reconciliation and receivables stay in step automatically. Agents that propose matches for review are part of what Sundial is designed for and building toward; the person reconciling still decides.