How Do I Do a Bank Reconciliation
Wondering how do i do a bank reconciliation? Our 2026 guide covers steps, handling discrepancies, and using automation to simplify your accounting.
Your bank account says one thing. QuickBooks or Xero says another. Stripe paid out yesterday, PayPal is holding part of a transfer, and one client payment landed net of fees instead of at the invoice amount. That's usually the moment a business owner asks, how do I do a bank reconciliation without turning it into a full-day detective job?
The short answer is this: you reconcile by matching your bank activity to your books, identifying anything that appears on one side but not the other, and adjusting for timing differences, fees, interest, and errors until the adjusted balances agree. The practical answer is a little messier, especially if you collect money through more than one channel and need visibility before month-end.
A good reconciliation process doesn't just clean up bookkeeping. It tells you whether your cash number is real.
Table of Contents
- What Is a Bank Reconciliation and Why It Matters
- Gathering Your Documents for Reconciliation
- The Bank Reconciliation Process Step by Step
- A Worked Example of a Bank Reconciliation
- Troubleshooting Common Reconciliation Discrepancies
- How to Make Future Reconciliations Easier
What Is a Bank Reconciliation and Why It Matters
A bank reconciliation is the process of comparing the cash balance in your accounting records with the balance on your bank statement, then explaining every difference until both sides agree after adjustments.
That sounds technical, but in practice it answers a simple question. Do your books reflect the cash you have?
When they don't, the problem usually comes from one of three places: timing, missing transactions, or mistakes. A deposit may be in your ledger but not yet on the statement. A bank fee may have hit the bank but never reached your books. Or someone entered the wrong amount and nobody noticed.
This matters for every business, not just large finance teams. Bank reconciliation is a foundational accounting control process mandated by the Sarbanes-Oxley Act of 2002 for public companies in the United States, and both IFRS and GAAP require cash balances on the balance sheet to match adjusted bank statement balances according to QuickBooks on bank reconciliation. The same source notes that failure to reconcile monthly results in an average of 17 undetected errors per business annually, with 68% of small businesses experiencing cash flow misstatements due to unreconciled accounts.
Practical rule: If you're making decisions from an unreconciled cash balance, you're guessing. Sometimes you guess right. Sometimes you pay a vendor too early, miss a fraud signal, or think a customer paid when they didn't.
For a small business owner, reconciliation is less about compliance language and more about control. You catch duplicate payments. You spot withdrawals you didn't authorize. You see whether a processor payout is short because of fees, holds, or a posting error.
What reconciliation does for you day to day
- Confirms real cash: You can trust the number you're using to pay payroll, vendors, and taxes.
- Catches missing items: Fees, interest, chargebacks, and old checks don't stay buried.
- Improves close quality: Month-end financials stop swinging because cash was wrong.
- Creates a review trail: If your accountant, lender, or auditor asks questions, you have support.
If you use one checking account and deposit checks once a week, bank reconciliation is straightforward. If you use Stripe, PayPal, Square, wires, and international payments, the principle stays the same. The workflow just needs to be tighter and more frequent.
Gathering Your Documents for Reconciliation
Most reconciliation problems start before the matching begins. People jump in with half the records, the wrong date range, or a bank feed that hasn't fully synced. Then they spend an hour chasing differences that aren't real.
Get your materials together first. It saves time and keeps you from fixing the wrong problem.
What to pull before you start
You need the records for the same period on both sides. If you're reconciling June, use the June bank statement and the June general ledger cash activity. Don't mix a bank statement through the 30th with books that include transactions posted on the 1st of the next month.
Use this checklist:
- Bank statement: The official statement for the account and period you're reconciling.
- General ledger cash detail: The transaction list from QuickBooks, Xero, or your ledger system for that same account and period.
- Prior reconciliation: This shows old outstanding checks or deposits in transit that may still need clearing.
- Deposit support: Deposit slips, batch reports, or processor payout reports if the deposit amount combines multiple customer payments.
- Disbursement support: Check register, bill payments, ACH details, debit card activity, and bank transfer support.
For businesses using Stripe, PayPal, or Square
Many reconciliations encounter difficulties when matching bank statements to accounting records. The bank statement only shows the net payout. Your accounting system may show the gross customer payment. The difference is often a fee, reserve movement, refund, or timing lag.
Pull the processor reports that explain:
- gross payments received
- fees withheld
- refunds or disputes
- net payouts sent to the bank
- payout dates versus customer payment dates
If you skip processor reports, you'll keep trying to match a net bank deposit to a gross invoice amount. That never reconciles cleanly.
If your books are clean and your documents line up, the actual reconciliation tends to move fast. If the records are scattered across inboxes, apps, and someone's spreadsheet, the process turns into reconstruction instead of reconciliation.
The Bank Reconciliation Process Step by Step
A solid reconciliation follows a disciplined order. The version I trust is an eight-step protocol: obtain the bank statement, retrieve the General Ledger cash balance, match transactions, identify unmatched items, investigate discrepancies, record adjusting entries, verify adjusted balances agree, and document the reconciliation as described by Eagle Rock CFO's bank reconciliation guide.
That framework works whether you reconcile in Excel, QuickBooks, Xero, or a close tool.
Start with the right period and opening balance
First, confirm you're reconciling the correct account and statement period. Then check the opening book balance against the prior month's ending reconciled balance. If that opening number is wrong, everything after it will be noisy.
This is also where you decide your level of detail. In a low-volume account, line-by-line matching is manageable. In a high-volume account, especially one fed by processors, you may reconcile grouped payouts to clearing accounts rather than trying to match every customer payment directly to the bank.
Match cleared activity first
Match what appears in both places without overthinking it. Check off deposits, ACH payments, wires, checks that cleared, card transactions, and transfers that appear in the ledger and on the statement.
If you use software, let the system suggest matches, but review the logic. Auto-match works well on direct one-to-one items. It works less well when dates shift, descriptions vary, or one bank deposit includes many underlying transactions.
A practical order that works:
- Match obvious one-to-one items first: wires, rent payments, loan payments, payroll withdrawals.
- Then clear checks and ACH: these often match by amount and approximate date.
- Handle deposits after that: they're more likely to bundle multiple items or arrive net of fees.
Investigate what does not match
After the easy matches, the unmatched list points to where the essential work is.
Common legitimate differences include:
- deposits recorded in the books but not yet shown by the bank
- checks issued but not yet cleared
- transfers initiated near period-end
- processor payouts that hit after the customer payment date
Unmatched items can also point to bad data. An amount may be transposed. A transaction may have hit the wrong account. A fee may have posted to the bank and never been entered in the ledger.
For businesses with Stripe or PayPal, keep one principle in mind: reconcile the processor balance before expecting the bank deposit to make sense. A customer can pay today, the processor can deduct fees, hold part of the funds, and send the payout later. If you only look at the bank account, it looks like the books are wrong when incomplete processor accounting is the issue.
Here's a short visual walkthrough if you want to see the flow in practice:
Adjust the books and document the result
Once you've identified the differences, post the entries that belong in your books. Typical examples include bank service fees, interest income, debit memos, corrections for entry errors, and sometimes reclasses when something posted to the wrong cash account.
Do not post entries for timing differences that will clear naturally. An outstanding check is not a bookkeeping error. A deposit in transit is not a bookkeeping error either. Those belong on the reconciliation, not as new journal entries.
Reconciliation is not about forcing a match. It's about explaining the difference correctly.
Finish by proving this equation:
| Reconciliation check | Result |
|---|---|
| Bank statement ending balance plus or minus bank-side reconciling items | Adjusted bank balance |
| General ledger ending balance plus or minus book-side adjustments | Adjusted book balance |
If those two adjusted balances are equal, the account is reconciled.
For higher-risk or higher-volume accounts, don't rely on software blindly. Run the automated reconciliation and compare it to a manual workpaper for the current month. If both produce the same matched items and exceptions, that's when automation earns trust.
A Worked Example of a Bank Reconciliation
A simple example makes this easier than abstract rules.
A simple monthly example
Assume a small creative agency is reconciling its operating account for month-end. The bank statement shows an ending balance of $24,800. The general ledger shows $25,100.
The accountant reviews the detail and finds four items:
- a client deposit recorded in the books at month-end that hasn't appeared on the bank statement yet
- a check to a contractor that hasn't cleared
- a monthly bank fee on the statement that wasn't entered in the books
- a small interest credit on the statement that also wasn't entered in the books
The reconciliation looks like this.
Sample Bank Reconciliation Worksheet
| Bank Balance Side | Amount | Book Balance Side | Amount |
|---|---|---|---|
| Ending bank balance | $24,800 | Ending book balance | $25,100 |
| Add deposit in transit | $900 | Less bank fee | $(50) |
| Less outstanding check | $(600) | Add interest credit | $50 |
| Adjusted bank balance | $25,100 | Adjusted book balance | $25,100 |
That's a clean reconciliation because each difference has a clear home. The deposit in transit and outstanding check belong on the bank side because the business already recorded them. The bank fee and interest credit belong on the book side because the bank recorded them first.
This is also why cash application matters. If a client payment is sitting in accounts receivable with no clean trail to the deposit, the bank rec gets harder than it should be. Using a structured invoice tracker template can make it much easier to trace which invoices were paid and when cash should have shown up.
A modern twist on this example is processor payouts. If the agency received card payments through Stripe, the bank may not show the full customer amounts. It may show a bundled net payout. In that case, the worksheet still works, but you first need a processor clearing account that separates gross receipts, fees, refunds, and transfers to the bank.
Troubleshooting Common Reconciliation Discrepancies
The hard part of reconciliation isn't usually the matching. It's getting stuck with a difference you can't explain.
The fastest way through that problem is to sort discrepancies into two buckets: timing issues and errors.
According to the Florida SouthWestern State College reconciliation guide, the most frequent reconciliation pitfalls involve timing differences and unrecorded bank-side items. Deposits in transit must be added to the bank balance, while outstanding checks must be deducted. Bank fees, interest credits, and debit memos often require journal entry adjustments, and data entry errors are the primary cause of persistent mismatches.
Timing issues that are normal
These differences are frustrating, but they usually aren't signs that anything is wrong.
- Deposit in transit: You recorded the receipt, but the bank hasn't posted it yet. Add it on the bank side.
- Outstanding check: You issued and recorded the check, but it hasn't cleared. Deduct it on the bank side.
- Processor payout lag: The customer paid, but the processor hasn't transferred funds to the bank yet. Keep the activity in the processor clearing flow until payout occurs.
If you manage receivables closely, an aging report can help you separate a true unpaid invoice from a payment that was received but hasn't landed where you expected in the books.
Errors that need correction
These require action, not just explanation.
| If you see this | Usually means | What to do |
|---|---|---|
| Same amount off in multiple places | Duplicate entry or duplicate import | Remove the duplicate and recheck prior reconciliations |
| Small odd difference | Transposed digits or typo | Search for near-match amounts and review source documents |
| Bank statement has a fee or credit missing from books | Unrecorded bank-side item | Post the journal entry to the general ledger |
| One transaction posted to wrong cash account | Misclassification | Reclass the entry to the correct account |
| Old outstanding item never clears | Stale check, unresolved deposit, or posting issue | Investigate support and decide whether to void, reissue, or correct |
Don't chase every discrepancy in date order. Start with the largest items and anything that affects cash availability today.
One more practical point. If your statement period and your accounting close period don't line up exactly, stop and fix that first. Partial-month reconciliations create fake differences and waste time. The same goes for manual bank downloads saved from the wrong day. If your bank feed is reliable, use it. If it isn't, verify imports against the official statement before you start checking boxes.
How to Make Future Reconciliations Easier
A painful reconciliation usually tells you something about your process, not just your bookkeeping. If each month feels like a reset, the underlying cash workflow needs tightening.
Change the cadence for modern cash flow
Monthly reconciliation is the minimum most businesses think about. For a business with card payments, recurring billing, contractor payouts, or tight cash timing, monthly is often too slow.
A better pattern is:
- review bank and processor activity during the week
- clear obvious matches continuously in QuickBooks or Xero
- leave month-end for true exceptions, not first-time discovery
That approach matters even more if you use several payment channels. Existing guidance often treats reconciliation like a single-bank monthly task, but modern businesses commonly juggle multiple processors and payout lags. Zone & Co notes that many businesses now use several payment processors while most reconciliation guides still center on simpler single-account models in its discussion of improving the bank reconciliation process.
Treat payment processors as separate reconciliation streams
Stripe, PayPal, and Square should not be treated like ordinary bank deposits. Each one can create timing gaps between customer payment, processor fee deduction, reserve movement, refund, and actual bank payout.
What works:
- set up a clearing account for each processor
- record gross customer receipts into that clearing account
- record processor fees separately
- match actual payouts from the processor clearing account to the bank
What doesn't work:
- posting net deposits straight to revenue
- trying to match grouped payouts directly to invoice totals
- ignoring refunds and disputes until month-end
Use automation where volume makes manual work break down
Manual tick-and-tie still works for a simple business. It breaks down when you have recurring billing, many small transactions, or frequent exceptions that need routing to the right person.
For contractors and staffing firms, this matters a lot. AI-powered reconciliation tools can reduce discrepancy resolution time by 74% for high-volume, low-value transaction businesses by auto-matching transactions from payment reminders and exception routing, based on the 2025 claim cited in this YouTube discussion on AI-powered reconciliation.
That doesn't mean you should automate everything blindly. Good automation does three things well:
- pulls transaction data from the systems you already use
- matches routine items consistently
- leaves a clear exception queue for human review
If you're evaluating workflow improvements, it's worth looking at how accounting software integrations handle sync quality, status updates, and exception visibility. The more context your systems preserve between invoice, payment, processor activity, and bank deposit, the easier reconciliation becomes.
The goal isn't to remove humans from the process. It's to stop using skilled finance time on predictable matches that software can handle reliably.
A good bank reconciliation should feel boring. When it's boring, your controls are working.
If you want fewer mystery deposits, cleaner invoice follow-up, and better visibility into what's been collected before month-end, Payment Reminder is worth a look. It connects with your accounting software, sends contextual payment reminders, routes exceptions, and gives you a weekly AR summary so cash collection is easier to track before you start reconciling.