Small-Business Bank Reconciliation: The Daily Process That Separates Balance From Available Cash

Daily bank reconciliation is the pass that turns a bank balance into a number you are allowed to spend. The balance includes money you have already committed and excludes money you have already earned. The process names every difference - an uncleared cheque, an unsettled card batch, a Masav file leaving tonight - instead of smoothing it into an "other" row.

The four numbers, and only one of them is the bank balance

A small business actually operates against four separate figures, and none substitutes for another:

• Bank balance. What the account shows now, after debits and credits that have actually settled.
• Ledger balance. What your own system recorded: invoices, receipts, cheques written, expenses captured. It is almost always different from the bank balance, and that is correct.
• Available cash. Bank balance minus obligations already authorised but not yet debited - a Masav file already sent, cheques sitting in suppliers' hands, standing orders debiting tonight.
• Forward position. Available cash plus dated inflows and minus dated outflows over the next two weeks.

"Can we pay this supplier" is answered by the third number. The accountant's question is answered by the second. The bank's screen shows the first. Confusing the three is the most common reason a profitable business bounces a payment.

Why does the bank balance disagree with your books every single morning?

Because the bank and your ledger record the same event on two different dates. These are timing differences, not mistakes, and each has an expected closing date:

The last two rows are the only ones where the bank knows something you do not. Everything else is information you already hold that has simply not reached the account yet. Where the movements come from in the first place - a manual export, a licensed financial information provider, acquirer reports or a payment provider's interface - is a separate decision covered in the routes for pulling bank and card transactions. This article is about what you do with the data once it is in.

The morning pass, in order

1. Pull yesterday's movements with four fields per row: bank reference, value date, description and amount.
2. Run automatic matching on the reference, and where there is none, on an exact amount inside a three-business-day window.
3. Work the unmatched list top down by amount. The five largest rows usually explain most of the gap.
4. Age the suspense queue. Anything sitting there for more than three business days gets an owner and a written note, not a push to tomorrow.
5. Recompute available cash: balance minus authorised obligations that have not yet debited.
6. Freeze the day. Rows matched yesterday become read-only, and a correction is recorded as today's dated adjustment.

Step six is the one people skip, and it is the only one that lets you answer, two months later, why Monday's number changed.

A worked Tuesday: 84,300 in the app, 30,600 you can actually spend

A nine-person studio, 08:20, banking app showing 84,300 shekels:

The 5,600 transfer is the whole point. It is already inside the 84,300, but until it is identified it closes no customer's debt, so it does not reduce receivables and is not counted as a receipt. Until then it is cash that exists and is unexplained - exactly the condition that produces a receipt recorded twice against the same customer. Those lines feed the same queue as open balances and the collection workflow.

What do you do with a line that matches nothing?

You do not delete it and you do not "tidy" it. The line moves through four defined states, each with an owner:

• Unmatched - arrived from the bank, no corresponding document. A temporary state only.
• Suspense - has an owner, an age in days and a note. Unreferenced transfers live here.
• Identified - the document or customer has been found, waiting to be posted.
• Posted - matched to a document and locked against editing.

Disputed is a separate fifth state: a charge you are contesting with the bank or a supplier. It stays visible until it is resolved rather than entering suspense, otherwise it disappears into the rest of the noise.

What actually breaks

• Matching on amount alone. Two payments of 1,200 on the same day attach to each other's invoices, and the report still looks correct.
• Value date versus posting date. Matching on the wrong one creates a fixed gap that reappears at every month end.
• Fees captured as an odd transaction. Dozens of small unrecognised rows that add up to a real number by December.
• Editing yesterday. Somebody changes an already-matched row, and the month stops balancing with no way to show what moved.
• Files sent but not recorded. A Masav file goes out and nobody records the obligation, so available cash reads high on exactly the day it matters most.
• Leading zeros. Account and branch numbers stored as numbers rather than text lose a digit the first time they pass through a spreadsheet.

What to have ready before you start

• A stable transaction source with a unique reference per row.
• A decision on who owns the suspense queue and what happens when it goes untouched for three days.
• A flag showing that a payment file was sent, so available cash reduces itself.
• A locking rule: from what moment a day is closed to edits.

Sources

• Bank of Israel
• Masav - Banks' Clearing House