The bank reconciliation that takes 12 minutes

Bank reconciliation compares a bank statement with the books for the same account and date, accounting for outstanding checks, deposits in transit, fees, and errors. The IRS recommends reconciling business checking accounts monthly. This fictional example uses a twelve-minute routine to explain the steps; actual time depends on the number of transactions and unresolved differences.

The setup: two numbers that should agree

Pick one account and one month. The July statement says checking closed at $18,406.22. Your books say the same account ended July at $18,641.65. The difference is $235.43 — books higher than bank. That number isn’t a verdict on your bookkeeping. It’s a search warrant: something specific, adding up to exactly $235.43, is recorded in one place and not the other. Your whole job is to find it.

One rule before you start: never “plug” the difference with an adjustment to make the numbers agree. A forced match doesn’t fix the error — it hides it, and it will come back bigger. The difference is information. Spend it.

Minutes 1–4: what does the bank have that you don’t?

Start on the statement side and scan for anything your books never saw. The usual finds are small and boring: service charges, wire fees, interest earned. Sure enough, near the bottom of the statement sit two lines that never made it into the books — a $15.44 monthly service charge and a $30.00 outgoing wire fee. That’s $45.44 of bank charges. Record them, and the unexplained difference drops to $189.99 — a suspiciously specific number, which is exactly the kind you want.

Minutes 5–9: the suspiciously specific remainder

A difference like $189.99 doesn’t look like an accumulation of small stuff — it looks like one transaction. Search the books for that amount and there it is, twice: a customer payment recorded by hand on the day the check was deposited, and the same deposit imported again from the bank feed three days later. Classic double-record — it happens whenever manual entry and imports mix. Merge the duplicate (don’t delete history; mark it as the same money) and the difference reads $0.00.

Check the math: $45.44 in missed bank charges plus a $189.99 duplicated deposit is $235.43. The books were “wrong” in two mundane ways, and both took minutes to find because the amount told you what to look for.

Minutes 10–12: tick, tie, and lock it

Mark the month reconciled. This step matters more than it feels like it does: a reconciled month is a trusted base, which means next month’s search space is one month wide instead of six. Businesses that reconcile monthly chase differences measured in minutes. Businesses that reconcile at tax time chase a year of compounded ones.

The three usual suspects

Nearly every reconciliation difference is one of three things:

• Bank activity your books missed — fees, interest, and the occasional returned payment. The bank never forgets to charge you; you sometimes forget to record it.
• Duplicates from mixed entry — a transaction typed in by hand and then imported again by feed or CSV. The tell is a difference that exactly equals one transaction.
• Timing — a check you wrote on the 29th that cleared on the 2nd. It belongs in your books now and on next month’s statement. List it, don’t “fix” it.

And two old tricks for when nothing jumps out. A difference divisible by nine is often a transposition — record $270 as $720 and the $450 gap divides cleanly by nine. A difference that’s exactly double one transaction usually means something was entered backwards: a deposit recorded as a withdrawal moves the balance twice its amount. Neither trick finds the error for you, but both tell you what kind of error to hunt.

Why twelve minutes and not three hours

Regular recordkeeping can make reconciliation easier because there is less history to investigate. Review the transactions and reconciling items as well as the totals: offsetting errors can leave equal balances. The twelve-minute schedule is a teaching example, not a completion-time guarantee or proof that every accounting entry is correct.