Sage 50 was unable to reconcile those transactions
Sage 50 is rejecting a reconciliation attempt because one or more transactions are damaged, locked, or internally inconsistent.
When Sage 50 displays “Sage 50 was unable to reconcile those transactions,” it means the program tried to mark a batch of entries as cleared during a bank or credit card reconciliation and one or more of those entries refused to accept the cleared flag. Despite the wording, the problem is rarely about matching totals — it is usually a structural problem with a specific transaction inside the file.
What is actually happening
During reconciliation, Sage 50 writes a cleared-status marker onto each transaction you check off. If a transaction is internally damaged — missing a required link, carrying a corrupted amount field, or stuck in a partially posted state — the write fails and Sage 50 aborts the entire batch rather than leaving the reconciliation half-finished. The message you see is the generic catch-all for that abort.
Check for a prior-year lock first
The safest thing to rule out is a locked accounting period. In Sage 50, go to Maintain > Company Information and check whether the transaction date of the entries you are reconciling falls before the “Close Date” or prior-year cutoff shown there. If it does, entries in that period cannot be edited or marked cleared until the period is reopened. Reopening a closed period can have audit and reporting consequences, so confirm with your accountant before doing so.
Identify the specific transaction
Reconciliation failures are usually caused by one or two problem entries, not the whole batch. Try clearing transactions in small groups — ten or so at a time — instead of selecting all of them at once. When the error reappears, you have narrowed it to the last group. Repeat with progressively smaller groups until you isolate the single transaction that triggers the message. Note its journal reference and date.
Attempt a backup and re-entry
Once you have identified the problem transaction, make a verified backup through File > Back Up. Then delete the damaged entry if Sage 50 will allow it, and re-enter it manually with the same reference, date, and amount. In many cases the re-entered transaction will reconcile cleanly because it has a fresh, internally consistent record structure.
When the transaction will not delete or the error persists
If Sage 50 refuses to delete the transaction, throws a second error when you try, or the reconciliation still fails after re-entry, the underlying database has structural damage that the built-in tools cannot reach. Sage 50 does not ship with a Verify/Rebuild utility comparable to what QuickBooks offers, so there is no in-product repair path beyond what you have already tried. Continuing to force the reconciliation can propagate the corruption further into the file.
At that point the file needs professional attention. Our engineers can examine the damaged database directly, repair or rebuild the affected transaction records, and return a clean file that reconciles normally. If you are also considering moving away from Sage 50, the same damage can often be repaired as part of a Sage 50 to QuickBooks conversion. Either way, start with a free evaluation and quote — cost and turnaround depend entirely on what is inside your file.