Bank reconciliation, one of the most-used workflows in the accounting glossary, is the process of matching your book balance (what QBO says is in the account) to the bank statement balance, line by line. Done right, the difference comes out to zero and every transaction in the bank account ties to a transaction in the books. Done sloppy or skipped entirely, errors compound silently and fraud goes undetected for months.
The bank statement balance is what the bank says you have at month-end. The book balance is what QBO says you have based on the transactions posted to that account. The two rarely match exactly on any given day. There are always timing differences (outstanding checks, deposits in transit), but at month-end, after accounting for those timing differences, the two numbers should reconcile.
Reconciliation is the formal proof: here's the bank balance, here are the timing differences, here's the adjusted book balance, and they tie. The output is a reconciliation report you save to the client's records.
Two timing items show up almost every month:
Both are normal. They appear on the reconciliation as adjustments and clear out of the report once the bank catches up.
Monthly bank reconciliation is the single best internal control a small business has. It catches transposition errors before they compound, missing transactions before the bank feed gap stretches across months, unauthorized charges before they grow into a recurring drain, and fraud patterns before they cost real money.
Stretch the cadence to quarterly or annual and you give errors three to twelve months to compound. By the time someone reconciles, the trail is cold and the cleanup is hours instead of minutes.
Bank statement ending balance: $48,200. QBO book balance: $44,800. Difference: $3,400.
Outstanding checks (issued but not cashed): $4,100. Deposits in transit (recorded but not yet credited by bank): $700. Adjusted bank balance: $48,200 - $4,100 + $700 = $44,800.
Adjusted bank balance ($44,800) ties to book balance ($44,800). Difference: $0. Reconciliation complete.
That's the whole game. Every month, every account.
Most small business fraud isn't elaborate. It's a recurring small charge that nobody questions because nobody's looking. Bank rec is the only thing that consistently looks.
Reconciliation forces a line-by-line read of the bank statement. Every charge has to map to something in the books. An unauthorized debit doesn't have a match. It shows up as an unmatched item that has to be researched. If the bookkeeper is doing the rec correctly, they catch the unmatched line and ask "what's this?" within thirty days.
Without reconciliation, a $300 monthly unauthorized debit can run for two years before anyone notices. With reconciliation, it gets flagged month one.
ACH fraud is one of the more common patterns: someone uses your account and routing numbers to pull a small ACH ($25, $50, $200). The pattern is small enough not to trigger alerts but recurring enough to add up. Bank rec catches it because the ACH appears on the statement and has no matching invoice, bill, or transfer in the books.
Internal embezzlement often hides as a recurring vendor payment to a phantom vendor. The "vendor" has the same name as a real one, with one letter changed. The payment is a round number, monthly, similar in size to other vendors. Bank rec catches it when the vendor name on the statement doesn't match anything in the AP subledger or the accounts payable workflow.
A small services firm had a $750 monthly ACH going to "Velocity Marketing LLC." Real vendor was "Vector Marketing." Owner approved the original setup; bookkeeper was processing the recurring payment without questioning. Three months in, a new bookkeeper running her first reconciliation flagged that the ACH didn't match any active vendor in the system. The "vendor" was an account set up by a former employee. Total before catch: $2,250. Without reconciliation, the same pattern would've gone fifteen to twenty months easily.
The point of bank rec isn't the report; it's the discipline of looking at every transaction in the bank account and verifying it has a legitimate match in the books. The report is the byproduct. The discipline is the control.
QBO's Reconcile feature is the standard tool. It walks the bookkeeper through the matching step by step.
The path is "Settings (gear icon) → Reconcile." Pick the account being reconciled (checking, savings, credit card; each has its own rec), then enter the statement details from the bank statement.
QBO asks for the statement ending balance and the statement ending date. Pull both from the actual bank statement, not from QBO's calculated numbers. The whole point of reconciliation is to compare an external source (statement) to an internal source (books).
QBO presents every uncleared transaction in the account. The bookkeeper marks each transaction as cleared if it appears on the bank statement. As transactions clear, the running difference at the bottom of the screen updates.
The goal is "Difference: $0.00" at the end. If the difference isn't zero, something's wrong: a transaction is missing from the books, a transaction is duplicated, or an amount is off.
At $0 difference, QBO lets you finalize the reconciliation. It generates a reconciliation report (save it as a PDF in the client's records) and locks the cleared transactions. Future edits to a reconciled transaction prompt a warning.
If the difference isn't zero, work through the troubleshooting steps:
Most small differences resolve to one of those five. The mathematical shortcuts below speed it up.
QBO saves the reconciliation report automatically, and it's accessible from "Reports → For My Accountant → Reconciliation Reports." Save a PDF copy in the client's monthly close folder anyway: paper trail for the year-end close and for any future audit.
Two timing items account for almost every legitimate book-vs-bank difference.
A check you wrote and recorded in QBO ($1,200 to a vendor on March 28) might not clear the bank until April 4 if the vendor is slow to deposit. On the March reconciliation, that $1,200 is an outstanding check: recorded in the books, not yet on the bank statement. It shows up as a positive adjustment in the rec.
A deposit you recorded in QBO on March 31 might not appear on the bank statement until April 1 (cutoff timing). On the March rec, it's a deposit in transit: recorded in books, not yet in bank. It shows up as the opposite adjustment.
Outstanding checks and deposits in transit are normal. They aren't errors and they don't need to be "fixed." They clear naturally on the next month's reconciliation as the bank catches up. The reconciliation report records them as adjustments and the math comes out to zero.
An outstanding check that hasn't cleared after 90 days is a red flag. Either the check was lost, the vendor never received it, or the vendor isn't depositing it for some reason. Stale-dated checks (typically 6+ months) may not be honored by the bank.
The cleanup options: contact the vendor to confirm receipt, void and reissue if necessary, or write off the check if the vendor has gone out of business. Don't let stale outstanding checks accumulate in the rec; they make every month's reconciliation noisier.
When the difference isn't zero, the cause is usually one of four things.
A transposition error is when digits are swapped: $4,500 entered as $5,400, $1,234 entered as $2,134. The mathematical signature: the difference between the right number and the wrong number is always a multiple of 9. ($5,400 - $4,500 = $900, divisible by 9. $2,134 - $1,234 = $900, divisible by 9.)
The shortcut: if the rec difference is divisible by 9, look for a transposition. Find the transaction whose two-digit difference matches.
Duplicate transactions usually come from bank-feed mismatches: the bookkeeper enters the transaction manually, then the bank feed pulls it in too. The duplicate inflates the book balance. Cleanup: delete one copy (usually the manual entry, since the bank-feed version has the correct date and bank metadata).
Bank feeds occasionally drop transactions, especially during connection refreshes or after bank password changes. A transaction on the statement with no match in the books is the signature. Pull the transaction in manually or refresh the bank feed for that date range.
Sometimes the transaction is in the books with the right amount but the wrong date: recorded as April 1 instead of March 31, putting it in the wrong reconciliation period. Or the amount is right in QBO but recorded as $487.50 when the bank shows $478.50.
The fix is to edit the transaction in QBO to match the bank statement, then re-run the reconciliation. The TB won't change because the transaction still posts the same accounts; only the period or amount changes.
The single most useful reconciliation diagnostic: take the rec difference and divide by 9. If it's a clean integer, you have a transposition somewhere, and the digits that got swapped have a difference equal to the quotient. ($900/9 = $100, meaning the swap was between digits whose place values differ by 100.) This catches a huge fraction of single-error reconciliations.
When a bank feed has gapped, the cleanup workflow is:
QBO's bank feed reliability is generally good but not perfect. Plan on one gap repair per client per year as a reasonable baseline.
Most reconciliations are routine. A small fraction reveal something serious.
A monthly $40 charge from a name you don't recognize, repeated. Often a subscription that was set up by someone with access (former employee, fraudulent merchant). The recurring pattern is the giveaway. Single charges get noticed; recurring ones don't until reconciliation forces a look.
ACH or check payments to a vendor name that doesn't appear in the AP subledger. The bookkeeper checks the vendor list, doesn't find a match, escalates. Phantom vendor fraud requires internal access to set up; it's typically an inside job.
A check is "washed" (the payee or amount is altered after issuance) and the altered version clears the bank. The bank statement shows a payment that doesn't match the original check in the books. The bookkeeper catches the mismatch during reconciliation, the client contacts the bank, and the bank reverses (and investigates).
Check washing is rarer than ACH fraud but more devastating per incident; typically four-figure or five-figure checks are targeted.
The fraud-response sequence:
Don't just "fix" the books to remove the fraudulent transactions. The bank investigation may need the original transaction history. The proper bookkeeping treatment depends on the bank's resolution: dispute reversal goes through one set of journal entries; written-off loss goes through another. Cross-check against the general ledger at every step.
The reconciliation is the moment fraud surfaces. Bookkeepers who do monthly recs catch fraud at month one. Bookkeepers who skip recs catch fraud at month twelve, with five figures of damage.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Accounting & Bookkeeping Glossary, Trial Balance: What It Is, How to Read It, and What to Do When It's Off, General Ledger (GL): The Backbone of Your Accounting System
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
Undeposited Funds is the QBO holding account where customer payments sit between receipt and bank deposit. It exists so a single bank statement deposit can match multiple customer payments. Here's how to use it correctly and clear stuck balances.
Uncategorized Expense is QuickBooks Online's catchall for transactions imported but never assigned to a real category. A clean book has $0 in this account. Here's how to recategorize what's there and prevent new ones from landing.
The trial balance lists every GL account with its debit or credit balance, proving total debits equal total credits. Here's how to read it, and the troubleshooting framework for when it doesn't balance.