QuickBooks won't reconcile: the discrepancy checklist, in order
Your QuickBooks reconciliation is off and the difference won't clear. The five causes, ranked by how often they're the real one, and the order to check them in.
The statement says one number. QuickBooks says another. The difference is $1,847.32 and it corresponds to nothing you can find.
Reconciliation discrepancies feel random. They are not — they come from a short list of causes, and they have a reliable order of likelihood. Working that order saves the afternoon that gets lost to scrolling a register looking for a number.
Check this first: did the beginning balance change?
Before hunting for the difference, confirm the starting point is still where you left it.
QuickBooks does not store your beginning balance as a fixed value. It derives it from the transactions currently marked as reconciled. So if anyone edits, deletes, voids, moves or un-reconciles a transaction that was part of a closed period, the beginning balance of your next reconciliation silently changes — and you start the month already out by that amount, chasing a difference that has nothing to do with this month’s activity.
Open the Reconciliation Discrepancy report before you open the register. It lists exactly which previously-reconciled transactions have been altered and when. If the difference you are chasing appears there, you have found it in thirty seconds instead of an hour.
Two related traps:
- An incorrect opening balance from account setup. If the account was created in QuickBooks with the wrong opening balance, every reconciliation since has been carrying that error. It never resolves itself and it never gets smaller.
- A reconciled transaction moved to a different account. It leaves the reconciled set without being deleted, so it does not appear as a deletion anywhere obvious.
The five causes, in order of likelihood
1 · Duplicates from the bank feed
The most common cause, by a distance. Someone enters a payment manually. The bank feed imports the same payment two days later. QuickBooks now has two records for one event, and the account is off by exactly that amount.
Finding them: sort the register by amount, not date. Duplicates share an exact amount and sit days apart — trivially visible by amount, nearly invisible by date.
Fixing them: use Exclude on the banking screen for the imported copy rather than deleting the manually-entered one. The manual entry usually carries the categorisation, the class, the customer link and the attachment. The feed copy carries none of that. Delete the wrong one and you lose work.
This gets worse, not better, with volume — which is why it is the first thing to break when a business grows past the point where one person recognises every transaction.
2 · Sign errors
A deposit entered as a payment, or a payment entered as a deposit.
The signature of this one is unmistakable: the difference is exactly twice a real transaction on the statement. A $450 item in the wrong direction produces a $900 discrepancy — you are missing $450 you should have and carrying $450 you should not.
Halve the difference. Look for that number on the statement. If it is there, you have found it.
3 · Timing differences
Not errors at all. A cheque written on the 29th and presented on the 3rd belongs in your books this month and on the bank’s statement next month. A deposit made after the bank’s cut-off lands the following business day.
These resolve themselves and should not be adjusted. The problem is that they are indistinguishable from real errors until you check the date, which is why “the difference is a cheque that hasn’t cleared” is worth confirming before assuming something is broken. If your uncleared list is long and old, though, that is its own signal — cheques that have sat uncleared for months are usually lost, void, or were never sent.
4 · Date-range errors
The reconciliation end date does not match the statement end date. Off by one day at a month boundary and every transaction on that day is on the wrong side of the line.
Equally common: a transaction dated outside the period it belongs to — a payment recorded on the 1st that the bank processed on the 31st. It exists in QuickBooks and does not appear in this reconciliation, so it reads as missing when it is merely misdated.
5 · Unrecorded bank-side items
Bank fees, interest, FX charges, chargebacks, returned-item fees. The bank knows about them. Your books do not, because nobody entered them.
Processor fees are the version of this that scales badly. If a payment processor deposits net of its fees but your invoices are recorded gross, then every single deposit is a discrepancy — and the total for the month is your entire processing cost. That is not a reconciliation error to hunt down one by one; it is a structural mismatch between how money arrives and how it is recorded, and it needs a rule, not a search.
The order to work
- Open the Reconciliation Discrepancy report. Did the beginning balance move?
- Halve the difference. Does that number appear on the statement? → sign error.
- Sort the register by amount. Any pair of identical amounts days apart? → duplicate.
- Check the end date against the statement end date. Off by one?
- Scan the statement for items with no counterpart in QuickBooks — fees, interest, returns.
- Only now, go transaction by transaction.
Most discrepancies die at step 1, 2 or 3. The reason reconciliation feels like an all-afternoon job is that people start at step 6.
Why this keeps happening
Every cause above has the same root: the bank’s record and your record are built by different processes and only compared once a month. The bank records what moved. QuickBooks records what someone said moved. A month of small divergences accumulates, and reconciliation is the ritual where you discover them all at once, with the least context and the most time pressure.
Nothing about that ritual is inevitable. The comparison could happen continuously — each transaction matched when it arrives, while the person who authorised it still remembers what it was for, and while the invoice it settles is still open. Month-end would then be a confirmation rather than an investigation.
That is the entire argument for automating reconciliation: not that matching is hard, but that matching thirty days late and in bulk is hard. The same work done on the day is nearly free. See also reconciling payments to Xero for the same problem in the other ledger, and what to actually do about QuickBooks Desktop going away if you are still on the desktop edition.
Where Fynex fits
Fynex sits between the money and the ledger. Every payment that moves carries its own context — which invoice it settles, which fees were deducted, which payout it arrived in — and that context is written to the accounting system as the payment happens, not reconstructed from a bank statement four weeks later.
Gross-versus-net stops being a monthly discrepancy because the fee is recorded as a fee at the moment it is charged. Duplicates stop appearing because the payment record has one source rather than two. And when something genuinely does not match — a short payment, an unexpected deduction, a reference that resolves to nothing — it surfaces the same day as an exception with the underlying detail attached.
Reconciliation stops being an event. It becomes a state that is either true or has a specific, named reason why it isn’t.