
Two Screens, Two Numbers, One Business
The short answer: the software is rarely broken. Timing, duplicates from bank feeds, processor fees netted out of deposits, and transfers counted as income explain most gaps. Run the reconciliation report, fix the cause rather than forcing the number, and reconcile weekly.
Your accounting software shows one cash figure. Your banking app shows another, and the difference is large enough that you stop trusting both.
The instinct is to assume the software is broken. It rarely is. In most small businesses the gap comes from timing, from a duplicate, or from a payment processor that deposits less than it collected.
The difference between a healthy gap and a real error is whether you can name every line inside it. That is the whole skill, and it takes minutes once you know the order to check things in.
This guide walks the causes from most to least common, then sets out a routine that keeps the two numbers close enough to be useful.
The Gap That Is Supposed to Be There
- ● Uncleared payments sit in your books first
- ● Deposits in transit arrive at the bank later
- ● Timing alone explains most differences
Your books record a transaction when it happens. Your bank records it when money actually moves, and those two moments are often days apart.
Write a supplier cheque on the thirtieth and your books drop by that amount immediately. The bank balance stays high until the supplier deposits it, which might be next month.
Customer payments run the same way in reverse. A deposit made on Friday afternoon may not clear until Monday, so your books show cash the bank has not yet acknowledged.
Card payments add a third delay. Funds authorised today typically settle over the following days, which is why a busy weekend leaves your books ahead of your account. Stripe, for example, lists a settlement timing of two business days for US accounts.
None of that is an error. It is called reconciliation for a reason, and the outstanding items are supposed to be listed rather than eliminated.
Nine Reasons the Numbers Drift Apart
- ● Duplicate imports from reconnected feeds
- ● Processor fees netted out of payouts
- ● Opening balances entered twice
Beyond timing, a handful of causes account for nearly every mismatch that small businesses report. The table below maps the symptom to the place worth checking first.
| What you see | Likely cause | Where to look | How to fix it |
|---|---|---|---|
| Books higher than bank by a round figure | Uncleared cheque or scheduled payment | Outstanding items on the reconciliation screen | Leave it and confirm it clears next period |
| Same expense appears twice | Bank feed imported an entry you also keyed | Transaction list sorted by amount | Delete the manual copy, keep the matched one |
| Deposit smaller than the invoices it covers | Processor fees netted out of the payout | Stripe, PayPal, or Square payout report | Record the fee as an expense on that deposit |
| Balance jumped after reconnecting the feed | Re-imported history overlapping old data | The week around the reconnection date | Review duplicates before accepting the sync |
| Books never matched from day one | Opening balance entered twice or wrongly | Opening balance equity account | Correct the opening entry, not the current one |
| Transfer between accounts shows as income | Both sides categorised separately | Transfers report or uncategorised list | Match the pair as one transfer |
| Refund recorded as a new sale | Credit note posted as a positive amount | Customer account history | Reverse and re-enter as a credit |
| Bank fees missing from the books | Small charges nobody categorised | Uncategorised or suspense account | Categorise monthly rather than at year end |
| Balance drifts a little every month | Rounding or foreign exchange differences | Currency gain and loss account | Post the difference to the correct account |
Three rows cause the most confusion in practice. Duplicates from reconnected feeds, netted processor payouts, and transfers counted as income together explain a large share of the panic emails bookkeepers receive.
Notice that only one row is a genuine software problem. The rest are data and workflow issues that follow you to any platform you migrate to.
The Payout Problem Nobody Warns You About
If customers pay by card, your revenue and your deposits are different numbers by design. A processor collects the full amount, subtracts its fee, then deposits the remainder on its own schedule.
Stripe’s standard fee for domestic cards is 2.9% plus 30 cents per successful transaction, as of November 2026. On a $100 sale that is a $3.20 fee, so $96.80 reaches the bank. International cards add another 1.5%, which widens the gap further.
That single payout may cover several invoices at once. Matching it to one invoice leaves the others open and your income understated by the fee.
The correct treatment records the gross sale, the fee as an expense, and the net deposit that reaches your account. Most platforms support this through a clearing account that behaves like a holding pen for money in transit.
Refunds and chargebacks complicate the same flow. A refund issued in one period against a sale from another moves the mismatch across months, which is why processors are worth reconciling on their own before you reconcile the bank.
A Routine That Keeps Them Close
Reconcile on a fixed schedule rather than when something looks wrong. Weekly works well for freelancers, and monthly is the practical floor for anyone with staff.
Always start from the bank statement, not from the software. The statement is the record you did not create, so it makes a better reference point than your own entries.
Categorise everything before you compare totals. Uncategorised items sit outside the balance you are checking and quietly create differences that look mysterious.
Check the reconciliation report for outstanding items at the end. That list is your explanation of the gap, and if an item stays outstanding for two periods it needs investigation.
Our month-end close checklist sets out the wider sequence this fits into, including the steps that catch errors before they reach a tax return.
When a Forced Adjustment Becomes a Problem
Every major platform offers a way to force agreement. QuickBooks Online, Xero, Wave, FreshBooks, and Zoho Books all provide an adjustment entry when a reconciliation refuses to close.
Using it feels efficient. What it actually does is move an unexplained difference into an account with a name like reconciliation discrepancy, where nothing prompts you to look again.
Those balances accumulate. An accountant reviewing the year finds a suspense account full of small forced entries, and the cleanup costs more than finding the original transactions would have.
There is one honest use for the tool. Rounding differences of a few units, or a bank correction you have documented, belong in an adjustment with a note explaining the cause.
If forcing agreement has become routine, the workload has outgrown the setup. Our comparison of a bookkeeper and accounting software for a one-person business covers where that line usually sits.
Which Fix Fits Your Situation
- ● Freelancers reconcile weekly in minutes
- ● Product sellers watch processor payouts
- ● Growing teams need review separation
You are a freelancer with one account and a handful of clients: reconcile weekly and expect the gap to be uncleared invoices. Ten minutes on a Friday keeps the difference small enough to explain from memory.
You sell products and take card payments: reconcile the processor before the bank. Payout netting is the single biggest source of mismatches in this pattern, and fixing it fixes most of the noise.
You just switched platforms: suspect the opening balance before anything else. A migration that duplicates or omits the starting figure produces a gap that never closes, no matter how carefully you code new transactions.
You have staff entering transactions: separate entry from review. The person who created a duplicate is the least likely to see it, so a second pair of eyes finds errors that the software rates as matched.
Your feed keeps disconnecting: check for duplicates each time it returns. Reconnections re-import history, and the resulting pairs are the most common cause of a balance that jumps overnight.
You are still choosing a platform: weigh reconciliation tools above invoice design. Our roundup of accounting software for small business covers where the main options differ on matching and bank feeds.
You run a very simple business and want the cheapest route: compare the free and paid options honestly. Our head-to-head on QuickBooks and Wave for freelancers sets out what the free tier gives up.
What Higher Tiers Actually Improve
Paid plans in this category tend to add multi-currency handling, class or project tracking, more users, and stronger rules for automatic categorisation. The last of those genuinely reduces mismatches over time.
What no tier buys is a clean opening balance or a correctly recorded payout. Automation applies your rules faster, including the wrong ones, so the setup work stays yours.
Bank feed reliability varies by institution rather than by plan. Before committing, check that your specific bank connects well, since a feed that drops weekly creates duplicate work at every level.
Pricing and packaging in this market shift often, so confirm the current terms on the official site, and check what happens to your data if you leave. Several vendors limit historical access once a subscription ends, as of 2026.
The Bottom Line
A difference between your books and your bank is normal until you cannot explain it. The reconciliation report turns that difference into a list, and a list is something you can act on.
Most gaps trace to four causes. Timing, duplicates from bank feeds, processor fees netted out of deposits, and transfers counted as income cover the large majority of cases.
Fix the cause rather than the number. A forced adjustment closes the screen and leaves the error inside your accounts, where it distorts every report built on top of it.
Then keep the interval short. Reconciling weekly turns an investigation into a glance, and the business decisions you make from those numbers get better as a result.
FAQ
Should the two balances ever match exactly?
Only for a moment, and usually at the end of a reconciled period. Between those moments, uncleared payments and deposits in transit keep the two numbers apart on purpose. The goal is a gap you can explain line by line, not a gap of zero.
Why did my balance change after I connected the bank feed again?
Reconnecting often re-imports a stretch of history, and anything that was already entered manually now exists twice. Most tools flag possible duplicates, but they miss pairs with different dates or descriptions. Check the days around the reconnection before accepting the new balance.
My Stripe payout is smaller than the invoices it covers. Is that an error?
No, and it is one of the most common mismatches in small business books. Payment processors deposit revenue after subtracting their fees, so one payout can cover several invoices minus a deduction. Record the fee as an expense so the invoice totals and the deposit both stay true.
Can I just adjust the balance to match the bank?
You can, and it hides the cause rather than fixing it. A forced adjustment moves the difference into an account nobody reviews, where it distorts profit and confuses next month's close. Find the transaction first, and reserve adjustments for genuine rounding.
How often should a one-person business reconcile?
Monthly is enough for most, and weekly is easier in practice. Short intervals mean fewer transactions to search when something does not line up, and recent memory still works. Waiting until tax season turns a ten-minute check into a weekend.
Sources
- Manage your business | U.S. Small Business Administration — checked 2026-10-01
- Stripe: Pricing and fees — checked 2026-11-07
- Stripe Docs: Receive payouts — checked 2026-11-07
Some links may be affiliate links. We may earn a commission at no extra cost to you.
How this article was made: it was drafted with AI assistance from the official sources listed above, and its figures were checked against those pages on the dates shown. It is not based on personal hands-on testing.
Comments
Post a Comment