Blog Summary
- A reconciliation that balances can still be wrong. Balancing is not the test.
- Run the pre-checks before opening the reconciliation screen — half of all discrepancies originate before you start.
- Any activity in the Reconciliation Discrepancy account means someone plugged a difference. Treat it as a finding.
- A closing date password is the control that prevents most beginning-balance failures.
- Never force a reconciliation to close. An unexplained difference is information, not an obstacle.
If you need the mechanics of reconciling inside QuickBooks Online, that's covered separately in our step-by-step reconciliation walkthrough. This post assumes you know how, and focuses on the controls that stop a clean-looking reconciliation from hiding a real problem.
Why does reconciliation go wrong even when it balances?
Because the reconciliation screen only checks one thing: that the transactions you selected sum to the difference between your beginning and ending balances.
It doesn't check whether those transactions are classified correctly. It doesn't check whether a duplicate got matched. It doesn't check whether someone edited a reconciled transaction from four months ago and silently invalidated your beginning balance. And it doesn't check whether last month's difference was resolved or simply plugged with a journal entry.
That's why firms that reconcile every month still end up in year-end cleanup. The reconciliation was completed. It just wasn't verified.
Stage 1 — Pre-reconciliation checks
Run these before you open the reconciliation screen. Finding a problem here saves you from reconciling around it.
- Statement obtained and legible — the actual bank statement, not a downloaded transaction list. You need the bank's own ending balance.
- Beginning balance matches last month's ending balance. If it doesn't, stop. Something was edited in a closed period, and reconciling now will bury the evidence.
- Closing date password is set. If it isn't, set it before you begin.
- All bank feed transactions reviewed and categorized — nothing sitting in the For Review tab.
- Undeposited Funds balance checked. A material balance means deposits weren't grouped, and the bank won't reconcile cleanly.
- Uncategorized Expense and Ask My Accountant at zero.
- Prior month's Reconciliation Discrepancy account reviewed — confirm last month's difference was actually resolved.
- Duplicate check run — expense report sorted by amount and date, scanning for repeated pairs.
Stage 2 — During reconciliation
- Ending balance entered from the statement, not accepted from QuickBooks' suggestion.
- Statement date matches the statement period. Off-by-one-month reconciliations look complete and leave a whole period unreconciled.
- Outstanding items reviewed, not ignored. Anything uncleared over 60 days needs an explanation — usually a duplicate, a payment that was never actually voided, or a check that will never clear.
- Every matched transaction has a real counterpart on the statement. Bank-feed auto-matching gets this wrong regularly.
- Bank fees, interest, and service charges recorded — small amounts, and the most common cause of a small persistent difference.
- No transaction dated outside the statement period has been cleared.
Stage 3 — Resolving a difference
This is where reconciliations get compromised. The rule is simple: do not close a reconciliation you can't explain.
| Difference amount | Most likely cause |
|---|---|
| Small, odd cents | Unrecorded bank fee or interest |
| Exactly twice a transaction amount | Duplicate entry, or a sign error |
| Exactly a transaction amount | Recorded once but cleared twice, or missing entirely |
| Round number | Manual entry typo, or a transposition |
| Changes month to month | Prior-period edit to a reconciled transaction |
Work it in this order — it resolves most cases within the first three steps:
- Run the Reconciliation Discrepancy report. Shows transactions changed after being reconciled — the most common cause of a beginning-balance failure.
- Check the Audit Log filtered to the account, for edits and deletions in closed periods.
- Compare transaction counts, statement versus QuickBooks. A count mismatch localizes the problem faster than a balance mismatch.
- Search for the exact difference amount as a transaction value. Frequently finds it immediately.
- Halve the difference and search that. Catches sign errors, where a transaction posted as the opposite type.
What not to do: book an adjusting journal entry to force the reconciliation closed. It makes the reconciliation look complete while the actual error stays in the file — and now it's harder to find, because the trail of the discrepancy has been overwritten.
If a difference genuinely cannot be resolved, document it: amount, date, what you checked, what you ruled out. An undocumented plug is invisible to the next person. A documented open item is a task.
Stage 4 — Sign-off checks
- Reconciliation report saved and filed to the client's workpapers
- Reconciliation Discrepancy account at zero, or any balance explained in writing
- Undeposited Funds at or near zero
- Closing date advanced to the reconciled period end
- Any uncleared items over 60 days documented with an explanation
- Reviewer initials and date recorded
How do you run this across 40 client files?
The checklist above takes fifteen to twenty minutes per file when nothing is wrong. Across forty clients that's most of a work week, every month — and it depends on each reviewer remembering every check.
Two things make it scale:
Standardize the sequence. Same order, every file, every month. Variation is where checks get skipped, and skipped checks are always the ones that would have caught the problem.
Automate the detection pass. The zero-balance and anomaly checks — Undeposited Funds, Uncategorized Expense, Reconciliation Discrepancy activity, duplicates, prior-period edits — are mechanical. They don't need judgment, only consistency, which makes them the right candidate to hand to software.
Xenett Pulse runs those checks across a QuickBooks file and returns a prioritized findings list, so your reviewer's time goes to resolving problems rather than hunting for them.
Run a free diagnostic on a client file →
