Equility hands you month-end already reconciled. Set it up on a laptop — enter your email and we’ll send you a link.

Email me a link Book a demo

Nov 14, 2026

Bank Close Controls: How to Do Bank Reconciliation in QuickBooks Online

Grayscale photo of a bunch of metal tools
  • Treat bank reconciliation as a close control, not a clerical task
  • Use a staged workflow: high-certainty matches, then exceptions
  • Require documentation: statement, report, and exception log
  • Control aging of outstanding items with defined escalation rules
  • Troubleshoot systematically: duplicates, missing items, transfers
  • Track KPIs like cycle time and items aged over 30 days

Bank reconciliation is one of the few close activities where a small process gap can cascade into misstated cash, inaccurate working capital, and avoidable audit friction. Yet many teams treat reconciliation as a clerical box-check, rather than a control that ties transactions, timing, and classification together. For CFOs and finance leaders, the goal is repeatability: a workflow that produces the same quality outcome every month—even as volume grows or staff changes.

This post breaks down how to do bank reconciliation in QuickBooks Online using a structured sequence: pre-close hygiene, disciplined matching in QBO, exception handling, and post-reconciliation controls. If you’re also standardizing your broader reconciliation program, align this workflow with how to reconcile efficiently in QuickBooks so your bank rec becomes a predictable part of a faster, cleaner close.

Control Objective

A bank reconciliation should answer three questions: (1) Do your books reflect every real cash movement that cleared the bank? (2) Are timing differences clearly explained (in transit, pending, outstanding)? (3) Is the ending book cash balance defensible to leadership, auditors, and lenders? When done well, reconciliation becomes a key detective control, catching duplicate entries, missing postings, and misclassifications before they hit reporting.

The practical objective is not simply to “match transactions,” but to tie the statement ending balance to the general ledger cash balance after considering reconciling items. In operational terms, that means defining ownership, cutoffs, documentation standards, and review thresholds. Example policy thresholds (tailor to company size, cash volume, and audit requirements): escalate any unreconciled difference over $50–$250 or over ~0.1%–0.5% of monthly cash activity (based on your materiality), and require that suspense-like items be resolved within 30–60 days unless documented and approved.

Close Prerequisites

Before you begin the formal reconciliation, make sure the accounting period is ready. Confirm the bank statement period dates (e.g., month-end) and verify that all relevant bank activity is in the system: deposits, disbursements, fees, interest, returns, and transfers. If you reconcile while transactions are still being posted—or if the bank feed is behind—you’ll create noise, chase false differences, and waste review time.

Adopt a simple pre-flight checklist: confirm the statement is final, ensure all bank accounts are mapped correctly, and validate that cash-related posting accounts aren’t being misused. A common vendor payment posting error isn’t that cash “isn’t reduced” (it usually is), but that the debit side is coded incorrectly—e.g., coding the debit to the wrong expense/category, posting directly to an expense and bypassing Accounts Payable when you intended an AP workflow, or misclassifying a payment as a transfer. Those errors can still allow the bank account to reconcile while the P&L, AP aging, or vendor balances are wrong. For finance teams building scalable close routines, you can also standardize reconciliation documentation alongside your broader financial review procedures to ensure every month has consistent evidence and sign-off.

Data Hygiene

Many reconciliation issues aren’t “recon problems”—they’re data hygiene problems. Common root causes include duplicate bank feed entries, missing transaction dates, inconsistent memo fields, or improperly recorded transfers that create cash movement without a matching other side. The fix is not to brute-force the recon; it’s to improve the inputs.

In QuickBooks Online, start with the Banking/Transactions area (often labeled Transactions > Bank transactions) to review bank feed items before they hit the ledger. If you see duplicates, use the platform’s options to Exclude items you don’t want posted, or Undo/Add carefully if something was added twice. Also review the For Review vs Categorized tabs to ensure items are being added once, to the correct account, and with consistent payee/category rules.

Set clear operational rules: all cash transactions must have a payee, date, and reference; transfers must use the correct transfer workflow rather than being entered as expenses or deposits; and bank fees/interest should be recorded in a consistent cadence (either via monthly journal entry or individual transactions, but not both). If you use reclassification workflows to correct coding after the fact, keep them controlled and documented via a standard reclassify process so your reconciliations don’t become a recurring clean-up exercise.

Workflow Steps

Here is a controlled sequence for bank reconciliation in QBO that prioritizes both speed and evidence. To start, go to Accounting > Reconcile (in some layouts, it may appear under Bookkeeping > Reconcile). Select the specific bank account you’re reconciling, then enter the statement ending date and ending balance exactly as shown on the bank statement. Confirm the beginning balance matches the prior period’s reconciled ending balance; if it doesn’t, stop and investigate before checking off transactions.

This is the core workflow for how to do bank reconciliation in QuickBooks Online in a way that holds up to review: (1) verify statement header fields (account, ending date, ending balance), (2) match transactions in structured passes, (3) document exceptions and aging, and (4) retain the reconciliation output.

Second, work in disciplined passes rather than random clicking. Start with high-certainty matches: bank fees, interest, known recurring payments, and payroll-related transactions (if applicable). Then move to deposits and customer receipts, followed by vendor payments and other disbursements. Finally, address transfers and exceptions. This staged approach reduces rework and helps reviewers validate completeness (e.g., “all deposits cleared except those dated the last two business days”).

QBO-specific tips while you’re in the Reconcile screen:

- Use the search box to find transactions by amount, payee, or reference when you’re investigating a specific statement line.
- Sort by date or amount to spot duplicates (two identical amounts on the same date) and cutoff issues (items dated just before/after the statement end).
- If the list is long, use the filter controls (where available) to narrow to payments vs deposits, or focus on uncleared items around the statement end date.

Controls Checklist

Controls are what transform a reconciliation into a defensible close artifact. At a minimum, require: preparer sign-off, independent review sign-off, and a retained reconciliation package (PDF statement, reconciliation report, and exception notes). If you want to justify stronger language internally, be specific about what “close-ready” means: a named preparer and reviewer, a dated sign-off, an exception log with owners and due dates, and evidence that aging and unusual-item checks were performed.

Many teams also set materiality thresholds, but these should be tailored. Example policy thresholds (adjust for company size, cash velocity, and audit expectations): differences over 0.5% of monthly cash disbursements (or a fixed dollar cap such as $500–$2,500) require controller review, while smaller items can be reviewed by a senior accountant. Similarly, define what “large” means for your business rather than relying on a universal number.

Operationally, add three high-value checks: (1) aging of outstanding items (example policy: anything over 30–60 days must be explained and approved), (2) review of large or unusual transactions versus prior months (example policy: payments exceeding ~2x the vendor’s typical run rate, or above a defined dollar threshold tied to spend materiality), and (3) validation that transfers net to zero across accounts (no orphan transfer legs). If you’re building a more automated reconciliation environment later, it helps to understand the control tradeoffs in auto reconciliation in accounting before you redesign workflows.

Method Comparison

MethodTime per closeError riskBest for
Manual tick and tie3-6 hoursHighLow volume
Rules and templates1-3 hoursMediumGrowing teams
Standardized workflow45-90 minsLowMonthly close
Automation plus review15-45 minsLowestHigh volume

These time ranges should be treated as illustrative examples, not guarantees. Actual timing depends on transaction volume, number of reconciling items, bank feed reliability, staffing experience, and whether you’re reconciling multiple accounts (operating, payroll, merchant, trust). If you’re setting internal SLAs, calibrate them to your close calendar and audit requirements.

Timing Differences

Timing differences are normal—especially around month-end, holidays, and weekends. The key is to distinguish timing from true errors. Deposits in transit and outstanding checks should be explainable, documented, and expected to clear in the next cycle. A healthy reconciliation has reconciling items that are recent and reversing, not old and compounding.

Use practical rules to reduce noise: cut off cash receipts and disbursements by statement date, but track late-posting bank items (like card settlement delays). Document every reconciling item with a reason and an expected clearing timeframe. For example: “Deposit dated 3/30, bank credited 4/1; expected to clear next statement.” If you see the same explanation repeating for the same payee or process step, that’s a process improvement signal—not just a recon note.

In QBO, keep your documentation consistent. Some teams add notes in the Memo/Description field on the underlying transaction (where appropriate), while others maintain an external exception log (spreadsheet or ticketing system) that references the QBO transaction ID, amount, date, and owner. Either approach can work; the key is that your evidence is retained and reviewable.

Common Exceptions

When the reconciliation doesn’t balance, resist the temptation to “plug” the difference. Instead, isolate the category of issue. The most frequent drivers are: duplicate transactions (often from bank feeds), missing transactions (not posted or posted to the wrong account), mis-entered amounts (digit or decimal errors), or misclassified transfers (entered as an expense/deposit rather than a transfer).

A practical troubleshooting flow: (1) re-verify statement ending balance and date, (2) confirm you’re reconciling the correct bank account, (3) scan for duplicates by amount/date, (4) filter for uncleared transactions around the statement end date, and (5) validate transfers by searching for the matching other side in the destination account.

QBO-specific exception handling that reduces “mystery differences”:

- Bank feed duplicates: in Transactions > Bank transactions, identify duplicates and Exclude the extra item (or Undo if it was added incorrectly). If duplicates already posted to the ledger, you may need to delete one entry or void it, depending on whether it was used downstream (e.g., linked to a bill payment).
- Uncleared transactions: in the register (Accounting > Chart of accounts > View register), you can sort/filter and look for items without a cleared/reconciled status around the cutoff window.
- Transfers: confirm both sides exist and were recorded as a transfer between the correct accounts; mis-entered transfers are a common source of orphan activity.

If your organization also reconciles corporate cards, keep processes consistent using your credit card playbook from how to reconcile credit card in QuickBooks for finance professionals.

Troubleshooting Playbook

If you’re teaching your team bank reconciliation in QBO, equip them with a repeatable playbook for the hard cases. Start by pinpointing whether the issue is completeness (a missing transaction) or accuracy (wrong amount/date/account). Encourage staff to work from the bank statement outward: for any statement line without a matching book entry, create or correct the book entry; for any book entry without a statement line, determine whether it’s outstanding, duplicated, or misposted.

For stubborn differences, use targeted tests. Perform a “top five” scan for the largest uncleared deposits and payments—large-dollar items usually reveal the root cause quickly. Then do a “range test” for transactions posted on the last two statement days and the first two days after statement close; many errors hide in the cutoff window. (Treat “two days” as an example; widen or narrow based on your bank’s posting behavior and your cash volume.) Finally, check whether prior-period reconciliations were finalized; an incorrect beginning balance often traces back to an unreconciled prior month or a back-dated entry.

Also confirm you didn’t reconcile the wrong statement month. In QBO’s Reconcile screen, the statement ending date drives what “should” be cleared. A mismatch between the bank’s statement period and what you entered can create a difference that looks like missing transactions.

High-Volume Scaling

As transaction volume increases, reconciling line-by-line without structure becomes expensive and risky. A practical scaling strategy is to segment: reconcile high-volume categories (like customer receipts) using consistent grouping rules, while reserving detailed review for exceptions and large-dollar items. This reduces time-to-close without weakening controls—provided you have clear policies and retained evidence.

Scale also requires role clarity. Define who prepares, who reviews, and who resolves exceptions with operations (for example, missing remittance details or unidentified deposits). If leadership is evaluating broader finance systems for scalability, align your reconciliation requirements—controls, audit trails, approvals—with your systems roadmap. For related context on enterprise-scale finance operations, see features of QuickBooks Enterprise Online for modern CFOs.

In QBO, scaling often comes down to disciplined bank feed governance: consistent bank rules (where appropriate), tight control over who can add/categorize transactions, and a clear policy for handling unmatched items (e.g., “no uncategorized bank feed items older than X days,” where X is set based on your close cadence and audit needs).

Review And Audit

A reconciliation that can’t be reviewed efficiently is a hidden liability. Make your reconciliation package review-ready: include the bank statement, the reconciliation report, and an exception log that documents every open item with owner, root cause, and expected resolution date. In audit terms, you want to demonstrate three things: completeness of cash, appropriateness of reconciling items, and evidence of review.

QuickBooks Online-specific documentation steps:

- After you finish and click Finish now, save or export the reconciliation output. You can typically find reports under Reports (search “Reconciliation Reports”) or via the reconcile history for the account, depending on your QBO version.
- Save the Reconciliation Report PDF along with the bank statement PDF for the same period. If you maintain an exception log outside QBO, store it in the same close folder and reference the report period and account name.

Institute a monthly variance review tied to cash activity. For example, compare total deposits and withdrawals per the statement to the totals recorded in the general ledger for the period, and investigate variances above a defined threshold. Example thresholds (tailor to materiality and audit expectations): $100–$500 or ~0.1% of monthly cash activity, whichever is greater. This provides a second layer of assurance and often catches miscodings that still “reconcile” but distort operating expense or revenue classification.

Best Practices

Standardization is what makes reconciliation resilient. Use consistent naming conventions, a cutover checklist, and a clear schedule (e.g., reconcile within two business days of statement availability—adjust this SLA based on statement timing, staffing, and close deadlines). Consider creating a recurring close calendar and holding a brief exceptions review meeting for aging items—15 minutes weekly can prevent 90-minute month-end hunts (time estimates are illustrative and will vary with volume and issue complexity).

Also, measure it. Track reconciliation cycle time, count of open reconciling items, and the aging profile of outstanding items. A meaningful KPI is “aged items over 30 days as a percent of total reconciling items,” with a target under 10% for stable processes. Treat both “30 days” and “10%” as example targets; calibrate them to your transaction cycle, bank posting patterns, and audit requirements. If that metric rises, treat it as an operational signal that upstream processes (billing, collections, AP, or cash application) need attention.

FAQ

Bank Reconciliation FAQs

What if the beginning balance is wrong?
A wrong beginning balance typically indicates a prior period wasn’t fully reconciled or a back-dated transaction was entered after the prior month was closed. Locate any edits dated in the prior statement period and confirm the prior reconciliation was completed and not undone. In QBO, also check reconcile history for the account to see whether a prior reconciliation was changed or whether transactions were edited after the fact.

Should we reconcile daily, weekly, or monthly?
For most mid-sized organizations, monthly is the minimum. If cash is tight or transaction volume is high, weekly (or even daily for receipts) reduces surprises and speeds month-end close by shrinking the exception set. Set the cadence based on cash risk, volume, and reporting deadlines.

Can a reconciliation “match” but still be wrong?
Yes. If transactions are misclassified (for example, a cash outflow posted to the wrong expense account), the account can reconcile while the P&L is misstated. That’s why reconciliations should include reasonableness checks and variance review, not just matching.

How do we handle bank fees and interest consistently?
Pick one method and standardize it: record monthly totals via journal entry based on the statement, or record individual items as they occur. Mixing approaches often causes duplicates and recurring reconciliation headaches.

Conclusion

A bank reconciliation is a monthly proof of cash—not merely an accounting task. When you standardize how to do bank reconciliation in QuickBooks Online around controls, exception handling, and review evidence, you reduce close risk, speed up reporting, and create confidence in liquidity numbers that leaders rely on.

If your team is still relying on ad hoc matching, use this workflow to formalize ownership, thresholds, and documentation. Over time, these habits turn reconciling bank accounts in QBO from a recurring fire drill into a dependable, finance-led control that scales with the business—and a repeatable answer to how to do bank reconciliation in QuickBooks Online month after month.

Share :
Michael Nieto

Michael Nieto

As the owner of the financial consulting firm, Lanyap Financial, Michael helped businesses and lending institutions who needed help improving their financial operations and identifying areas of financial weakness.

Michael has since leveraged this experience to found the software startup, Equility, which is focused on providing businesses with a real-time, unbiased assessment of their accounting accuracy, at a fraction of the cost of hiring an external auditor.

Connect with Michael on LinkedIn.

Related Blogs

See All Blogs
Mastering the Process: How to Reconcile Efficiently in QuickBooks

Mastering the Process: How to Reconcile Efficiently in QuickBooks

Reconciliation is one of those finance disciplines that appears routine—until it fails. When it fails, it rarely does so quietly: unexplained variances cascade into month-end delays, audit friction, and decision-making based on incomplete data. For CFOs and controllers, the question 'how to reconcile in QuickBooks' is less about a button sequence and more about designing a reliable process that scales with transaction volume, payment rails, and team complexity.

12 Jan, 2026
A Comprehensive Guide: How to Reconcile Credit Card in QuickBooks for Finance Professionals

A Comprehensive Guide: How to Reconcile Credit Card in QuickBooks for Finance Professionals

Finance teams often view credit card reconciliation as routine bookkeeping, but it’s a significant area where errors can infiltrate spend analytics, accruals, and month-end close. When card activity is high-volume, spread across departments, and charged in multiple currencies or tax treatments, small misclassifications can quickly accumulate—particularly if reconciliation is delayed beyond the statement date. This guide is crafted for CFOs and accounting leaders who require a repeatable, controlled process, not just a “match transactions” exercise.

05 Mar, 2026
Exploring the Features of QuickBooks Enterprise Online for Modern CFOs

Exploring the Features of QuickBooks Enterprise Online for Modern CFOs

Modern finance leaders are expected to deliver faster closes, cleaner data, tighter controls, and better forecasting—all while supporting growth. That makes accounting platform decisions less about “software preferences” and more about operating model design: who does what, when, with which approvals, and under which audit trail. If you’re evaluating QuickBooks Enterprise Online, the most useful lens is to map features to CFO outcomes: visibility, control, velocity, and scalability.

13 Mar, 2026
Analytics and Reporting

Your Next Close Is Already Counting Down

Every hour your team spends on manual reconciliations is an hour they're not doing higher-value work. Equility handles the matching, the checks, and the errors — so your close takes hours, not days.