QuickBooks Desktop Beginning Balance Does Not Match the Previous Reconciliation
QuickBooks Desktop warns your beginning balance no longer matches the last reconciliation. Fix it without undoing months of reconciled work.
You open the Begin Reconciliation window and QuickBooks Desktop warns that the beginning balance does not match the ending balance from the previous reconciliation. The warning is honest. Something in the register changed after you reconciled, usually a cleared transaction that was edited, deleted, or re-entered. Our engineers trace this routinely, and the report that finds the change takes a few minutes to run.
Why does the beginning balance change after a reconciliation?
QuickBooks does not store the beginning balance as a fixed number. It adds up the cleared items in the register each time you reconcile. When a reconciled transaction is later changed or removed, that running total shifts. Common causes include an edited amount on a reconciled payment, a deleted reconciled deposit, a payment unlinked from its deposit, or a backdated journal entry. A bank feed that re-matches an old item can do it too.
Before you touch the register
- Back the file up first. Choose File > Back Up Company > Create Backup and keep the backup somewhere local. You are about to edit cleared data.
- Switch to single-user mode under File > Switch to Single-user Mode so nobody else saves a change mid-repair.
- Keep the last bank statement at hand. You need its ending balance and statement date to confirm the result.
The Reconciliation Discrepancy report shows what changed
- Open Reports > Banking > Reconciliation Discrepancy.
- Select the affected account when QuickBooks asks.
- Set the date range to cover everything since the last reconciliation you trust. Widen it if you are unsure.
- Read the rows. Each line names the transaction, its date, the amount of the change, and the user who made it, wherever the audit trail captured the change.
The report lists three kinds of trouble: modified reconciled transactions, deleted ones, and new items dated inside an already reconciled period. Deleted items show their original details, which is exactly what you need for the repair.
Put each item back the way the bank saw it
An edited amount. Open the transaction and restore the amount shown on the statement. If the edit was a legitimate correction, leave it in place. The difference then belongs to this month's reconciliation, where you account for it rather than force it away.
A deleted transaction. Re-enter it exactly as the bank recorded it. Then open the account's register from the Chart of Accounts, find the row, and click in the checkmark column until the status reads R. That marks it reconciled again and returns the beginning balance without dragging the item onto the current statement.
An unlinked payment and deposit. Open the deposit and reattach the payment in the payments pane at the bottom of the window.
A backdated journal entry. Check whether the date was a mistake and correct it if so. Either way, the amount still has to clear during the current month.
Now reopen Banking > Reconcile and select the account. The beginning balance should equal the ending balance on last month's statement before you enter anything else.
What if the report comes back empty?
The discrepancy report reads the audit trail. If a condense cleared that trail, or the change falls outside the range you set, the report shows nothing while the mismatch stays. Run Reports > Accountant > Audit Trail and filter for the account name to catch older edits. If both reports come back clean and the balance still disagrees, the reconciliation flags inside the file are likely damaged. That is a company-file problem rather than a bookkeeping one, and it is where our professional QuickBooks Desktop file repair service applies.
Signs the fix worked
The Begin Reconciliation window opens without the warning, and the beginning balance equals the ending balance on the last statement. The Previous Reconciliation report, under Reports > Banking, still produces output for past months, which proves nothing was undone. The current reconciliation clears to a zero difference using only items that appear on this month's statement.
If the mismatch runs deeper than edits
A mismatch that first appeared after a condense, a rebuild, a file conversion, or a restore from backup is rarely caused by an edit. The stored reconciliation state itself can be broken. Undoing months of reconciliations one at a time will eventually force the balance, but it destroys the record you most want to keep. A targeted repair can rebuild the reconciliation flags while leaving cleared transactions and their history untouched, and that is work our engineers do on the file directly.