Bank and cash reconciliation: matching the statement to your books

It is 6:40 p.m. on the fifth of the month. The person who keeps the books has pulled March's bank statement, matched 198 of its 212 lines against the ledger, and is now staring at the fourteen that refuse to close. Three are incoming transfers whose only description is a customer's surname, two are bank charges nobody can trace to a transaction, one is a rent payment that was entered twice, and the last eight are end-of-day cash deposits that never made it into the cash book at all. The variance line at the bottom of the screen reads $4,180 — every figure in this article is an illustration. The real question is not the size of that number: who closes it, on the strength of which document, and what exactly has been proven once it is closed?

What follows treats reconciliation not as an exercise in making two numbers agree, but as a chain of evidence. We start with what reconciliation actually proves, then look at the fields where a statement line and a ledger line meet, the four things to settle before matching begins, and the criteria for accepting or rejecting an automatic match suggestion. After that: the order in which to hunt a variance, why cash is harder than bank, how foreign-currency accounts and payment providers change the picture, and how the whole thing becomes a monthly routine. Wherever a tax or reporting rule is involved, the boundary is the same — read the process here, confirm the treatment with your accountant.

What does reconciliation actually prove?

A bank statement is a record you did not write. It comes from the bank's own books, it is indifferent to your intentions, and that independence is precisely what gives it evidential weight. Your ledger entry, by contrast, is a claim: on this date, this amount landed in the account against this customer's balance. Reconciliation is the act of testing that claim against independent evidence. When the two sides meet, what has been proven is not that the balance is correct — it is that every movement has something behind it, and that nothing without a basis is sitting in your books.

The distinction matters in practice, because there are easy and wrong ways to make a balance agree. Closing a leftover variance with a single line called "bank charges" makes the arithmetic work without building any evidence; next month the same gap returns wearing a different name. By the same logic, confirming a balance with a customer is a separate exercise altogether, and the steps of a customer account reconciliation should not be confused with bank reconciliation. One proves that money moved; the other proves that two parties read the same debt. Neither substitutes for the other.

Which fields does a statement line share with a ledger line?

A match is built from four fields agreeing: date, amount, direction and identity. Date is less simple than it looks. Statements carry a transaction date and a value date in separate columns, while your entry usually carries a third one — the document date. That is why matching allows a tolerance on dates, typically a few days. But the wider the tolerance, the greater the chance that two same-value movements swap places. Setting a tolerance broader than you need raises the error rate, not the match rate.

Amount and direction are absolute: a $12,400 credit does not match a $12,400 debit, no matter how close the dates are. Identity is the weak link. Statement descriptions differ from bank to bank; sometimes you get a payer name, sometimes a free-text reference somebody typed at a branch counter. The logic behind automatic statement matching is essentially an attempt to read that field. Rocketly's pre-accounting module starts in the same place with Bank Statement Import: the CSV you upload is parsed, the parsed rows are shown as a preview before they become cash movements, and rows already imported are skipped — so re-uploading the same file by mistake does not create duplicate entries.

Which four things should you settle before matching starts?

First, the cut-off date. Reconciliation closes a period, so decide up front which side late entries belong to; otherwise you chase the same movement across two months. Second, the opening balance. If last period's closing balance is not identical to the brought-forward line on the statement, do not start matching at all — the variance you are looking for is already there, and working through the new month's lines will only bury it.

Third, clearing the drafts. A receipt with missing information should wait in a separate queue rather than being dropped into the ledger, which is exactly what the Financial Drafts feature is for: receipts and payments sit as drafts without touching the customer balance, and turn into real financial movements in a single action once the missing detail arrives. Fourth, the completeness of your account list. Every bank account, every cash drawer and every card terminal needs to exist as its own account.

These four look like overhead and are in fact the thing that shortens reconciliation. They also determine the ground your period-end reporting stands on: the balance sheet and income statement you read at month end can be assembled perfectly and still show a misleading picture if the accounts underneath were never closed.

When should you accept an automatic match, and when reject it?

An automatic match is a candidate, not a decision. The Bank & Cash Reconciliation screen brings bank and cash movements forward with matching suggestions; you approve them and close the remainder by hand. Your acceptance test should not be "it looks green" but "which signal is this suggestion resting on". The table below summarises the usual suggestion types, the signal behind each, and the call to make.

Suggestion type	Signal behind it	Call
Exact match	Same amount, same direction, 0-2 days apart, reference matches the entry	Approve; no need to open each one
Amount matches, no reference	Only amount and date line up	Confirm the customer; never approve blind if two open invoices share the amount
Partial payment	Statement amount is smaller than the invoice	Leave the remainder open; do not close the invoice
Batched deposit	One statement line, several open invoices	Confirm the split against a document, then allocate
Near amount, small gap	Difference equals a fee or transfer charge	Post the gap as its own expense line; do not bury it in the match

That last row is where most teams slip. Burying a $37 gap inside the match reduces the number of entries but makes a real cost invisible. In a business running a few hundred transfers a year, those small gaps add up to a number worth knowing and appear in no report at all. Keeping fees and charges on their own lines is the only way to read that cost later.

In what order should you hunt down a variance?

Do not start at random — the variance itself tells you where to look. First, search for a difference equal to exactly one transaction amount. That is usually a single missing or duplicated entry, and it is the fastest search to finish. If half the variance equals a transaction amount, a direction error is likely: a movement that should have been a credit was entered as a debit, so the gap comes out at twice the transaction value.

The second place to look is digit-order errors. If the variance divides evenly by nine, two digits may have been transposed; writing 1,530 as 1,350 produces a gap that is always a multiple of nine. Third is a decimal shift: if the variance is exactly nine times a transaction amount, the decimal point probably moved one place. These three checks take minutes and belong before any line-by-line comparison.

If none of them holds, the variance is most likely a timing difference: a cheque written on the last day of the month has not cleared, or a transfer sent on Friday reached the other side on Monday. A timing difference is not an error. You do not close it — you list it and confirm in the following period that it cleared. On the cash side, most variances come from record-keeping discipline instead, and the methods for tracking cash movements accurately are not the same checklist you use on the bank side.

Why is cash reconciliation harder than bank reconciliation?

With a bank there is an independent record on the other side. With cash there is not. The cash drawer's "statement" is a physical count, and a count carries no evidential weight unless it becomes a signed record. So in cash-heavy businesses, reconciliation begins with turning the end-of-day count into a document. Having the person who counts differ from the person who posts the entry is the cheapest control available, and it is workable even in a team of three.

The second difficulty is petty spending: taxis, couriers, stationery, the amounts an employee pays out of pocket and later claims back. The Employee Out-of-Pocket Expenses record moves those amounts onto an employee statement showing who is owed what, so an unreimbursed expense does not read as a shortfall in the drawer. Advances paid to staff, meanwhile, must not be mixed into wage accounts. The fundamentals of payroll and social contributions run in a separate ledger, and how an advance is settled there is a question to put to your accountant.

Third comes the retail day close. The Z Reports screen takes the terminal close with its cash, card and other-tender breakdown, its tax split and its cash-over-short figure, and it refuses to confirm the entry unless the tender breakdown reconciles to total sales. The preview creates no financial record at all; you post the close to the drawer with a separate approval, and the same terminal and report number is only accepted again with identical content. The point of that design is not to hide the day's discrepancy but to keep it in its own field. A visible gap gets discussed; a buried one accumulates.

What do you reconcile in a foreign-currency account?

A foreign-currency account carries two separate reconciliations, and confusing them is one of the most common mistakes. The first is quantity: if the account holds €12,500, the ledger must hold €12,500. The second is valuation: at what rate is that €12,500 carried in your reporting currency, and at what rate is it revalued at period end?

When the quantity agrees but the reporting-currency balance does not, the difference is not a matching error — it is an exchange difference, and there is no line to correct. On the Rocketly side, the Multi-currency with Central Bank Rates behaviour stores the rate in force when the invoice was issued and converts the amount into the base currency, so which rate a movement sits at is never reopened later. In the cash-flow projection, entries in foreign currency with no rate captured are excluded and the screen says so explicitly, which means missing data is never quietly rounded away.

Which period an exchange difference belongs to, which account it lands in and which rate values it are accounting-policy decisions. How exchange differences arise on a foreign-currency invoice explains the mechanics; the valuation method and the period-end treatment are for your accountant to confirm. The boundary of this article is process, not interpretation of the rules.

How do you close out card and payment-provider settlements?

Card acquirers and payment providers create three behaviours that break naive reconciliation: they settle the net amount after fees rather than gross sales, they batch many orders into one payout, and they hold the money for a few days first. Put together, a single $84,317 line on the statement gives no clue which orders it represents.

The answer is a clearing account. When an order is captured, the amount is posted not to the bank but to a transit account held in the provider's name. When the payout lands, the transit account clears, the fee becomes its own expense line, and only the net figure enters the bank. Money in transit at the provider stays visible at all times, you notice immediately when a hold period stretches, and you are never left splitting one statement line across five invoices at month end.

The settlement report the provider sends is the evidence for that flow: keep it alongside the bank advice, since it shows which transactions sit behind each payout. The tax side of the arrangement is a separate study — what an online seller owes and reports can vary by channel and jurisdiction, and which document is issued when is a rules question rather than a process one.

Recording the fee invoices falls on the same side of that boundary. The fee amount is readable from the statement while the document arrives separately; confirming that document and amount agree is reconciliation's job, whereas the deductible treatment is something to raise with your accountant alongside the basic mechanics of VAT. In Rocketly, the flow that turns inbound e-invoices into draft expenses imports each document once against its unique identifier, so the same fee invoice is not booked twice.

How do you turn reconciliation into a monthly routine?

The first rule of the routine is separation of duties: where possible, the person entering records should not be the one approving the reconciliation. In small teams that is not always achievable, in which case at least have someone else review the approval and record the date of that review. The second rule is a calendar: the day the statement is pulled, the day variances are closed and the day the period is locked are all fixed in advance. As long as reconciliation is something done "when there is time", it never finishes.

The third rule is documentation. Every manually closed variance needs something behind it — a bank advice, a count sheet, a provider report, or a note recording who made the adjustment and why. In the Contacts, Accounts and Ledger Entries screens the ledger keeps debits and credits in separate columns, and downloading a statement as PDF to share with the counterparty is part of the same chain. Because bulk import and export jobs leave their status in Job History and Downloads, what was done to a period's data, and when, stays traceable.

The fourth rule is connecting reconciliation to your filing calendar. No return built on an unclosed period is trustworthy: the logic behind periodic purchase and sales listings such as the Ba-Bs forms rests on purchase and sales totals being consistent, and that consistency cannot be verified before reconciliation is done.

The same holds for periodic tax computations. How income tax and advance tax work is its own subject, but if the revenue and expense figures feeding the computation come from accounts that were never reconciled, the result is contestable too. What matters is being able to defend not the number but the record the number rests on — and past that point, the ground belongs to your accountant.

If you want to try reconciling bank and cash movements from matching suggestions, holding incomplete receipts as drafts, and importing statements in one place, you can open a free Rocketly account.

FAQ

How often should reconciliation be done?

Monthly is the minimum for a bank account and weekly is healthier; the more movements you have, the shorter the interval should be. For cash, an end-of-day count is ideal and a weekly count is the floor. The rule is simple: the gap between two reconciliations should never exceed the period over which you could still trace an error backwards.

Is it wrong to round off and close a small variance?

The problem is not closing a small variance — it is closing it without a reason. If there is a known cause such as a rounding difference, a transfer charge or a counting discrepancy, post it under that name. Closing an unexplained gap as an "adjustment" guarantees the same error repeats next month, because nothing was learned from it.

If I import the same statement twice, do entries duplicate?

In Rocketly's Bank Statement Import flow the uploaded rows are parsed and shown as a preview first, and rows already imported are skipped, so re-uploading the same file does not create duplicate entries. Even so, checking the row count and the date range before confirming the preview is a good habit.

How should I hand reconciliation variances to my accountant?

Send the closed period's variance list with a reason and a supporting document for each line; "the balance agreed" is not a handover. Which account a difference is posted to, how it is valued at period end and how it flows into a return are your accountant's decisions. The scope of this article ends at finding the variance and documenting it.