Fix a Sage 50 bank reconciliation difference

Identify the failure before applying a fix

The matched balance and statement balance do not agree, or Sage reports a reconciliation difference caused by a changed historical transaction.

Record the complete message, affected organisation or company, user, date range, and last successful action. A precise symptom is more useful than trying several broad repairs at once.

Checks before changing data

• Confirm the statement end balance and date exactly match the bank statement.
• Check the last reconciled balance against the statement opening balance.
• Print or export the difference list before editing anything.

Resolution path

1. Review the statement summary. Verify the bank account, statement dates, end balance, and previous reconciled balance.
   • Check credit-card sign conventions.
   • Make sure you did not skip or overlap a statement.
2. Trace missing, duplicate, and grouped items. Compare matched transactions with the bank, including bank charges, interest, transfers, and grouped deposits.
   • Check amounts and dates, not descriptions alone.
   • Look for transactions downloaded and entered manually.
3. Use the Reconciliation Difference window. If a previously reconciled transaction changed, inspect the listed transaction and correct the specific cause.
   • Re-enter a deleted legitimate transaction when documented.
   • Clear an incorrect reconciliation flag only after confirming the transaction.
4. Restart the reconciliation if evidence is unclear. Cancel and start the reconciliation again with the corrected statement information rather than forcing a zero.
   • Post a temporary adjustment only with accountant approval.
   • Retain the reports supporting the correction.

Verify the result

A disappearing error is not enough. Confirm the accounting and workflow outcome:

• Matched and statement balances agree.
• Every correction ties to a bank record or documented accounting decision.
• The prior reconciliation history remains explainable.

What to avoid

• Posting an unexplained suspense adjustment.
• Deleting a transaction included in a filed VAT return.
• Clearing multiple reconciliation flags without a transaction-by-transaction review.

When to involve product support, IT, or your accountant

Stop making changes and escalate when any of these conditions applies:

• A submitted VAT return or closed period is affected.
• The last reconciled balance changed for an unknown reason.
• A material difference cannot be tied to source documents.

Bring the exact error, screenshots, affected record IDs, timestamps, product version or region, and a description of every change already attempted. That evidence shortens the support path and reduces repeated or conflicting fixes.