You cannot change settings because there are pending or failed transactions
Sage 50 is blocking a settings change because transactions are still waiting to post or have failed to post.
The message “You cannot change settings because there are pending or failed transactions” means Sage 50 has work queued up that has not finished posting, and it refuses to let you change company-level settings until that queue is cleared. It is not usually a sign of damage. Most often it is a batch, an electronic payment, or a bank feed transaction that is stuck halfway through, and the software will not risk changing settings while the books are in that in-between state.
What is actually blocking you?
The message covers two different situations, and the wording does not tell you which one you are in.
Pending means something is saved but not yet posted. A batch of invoices held for approval, a scheduled payment waiting to go out, or a downloaded bank transaction sitting unaccepted all count. Nothing is wrong; the software just wants the queue emptied first.
Failed means something tried to post and did not complete. An interrupted posting session, a dropped connection during an electronic transaction, or a workstation that lost power mid-save can leave a transaction flagged as failed. These need attention, not just patience.
Clear the pending items first
Start with the safe option. Reopen the area where you were last working and look for anything saved but not posted: an unposted invoice batch, a held payment run, or bank feed lines waiting to be accepted. Post or delete each one. In a multi-user setup, check whether someone else has a transaction open on their workstation; an entry left open on another machine can hold the whole queue. Once nothing is waiting, close and reopen the company, then try the settings change again.
Deal with a failed transaction
If an entry is marked as failed, do not simply delete it and move on without understanding what it was. First, note the date, amount, and account involved so you can verify the books afterwards. Then attempt to post it again, or void it if it is a duplicate or an error. If the failure repeats, the transaction record itself may be damaged, and forcing it through repeatedly can make things worse. Stop and take a backup at that point.
When the queue will not clear
Sometimes nothing shows as pending or failed, yet the message still appears. That usually means the posting queue itself is out of step with the data: the software believes something is outstanding even though the visible transactions say otherwise. This can happen after a crash, an interrupted backup, or an unexpected shutdown while posting.
Do not keep retrying the settings change. Make a fresh backup of the company file while it is in this state, because that backup preserves the evidence our engineers would need. If the built-in maintenance options in your installation do not clear it, the file likely needs professional attention, and we would rather say that plainly than have you guess at repairs.
A useful next step
If the queue refuses to clear, send us the file for a free evaluation. Our engineers will identify the stuck or failed transaction, tell you what it was trying to do, and quote repairing the database before any work starts. If you have been considering moving off Sage 50 entirely, a stuck file is often a reasonable moment to look at a Sage 50 to QuickBooks conversion instead, since the conversion reads the underlying data directly and does not depend on the settings screen cooperating. Either way, the evaluation costs nothing and gives you a definite answer rather than another retry.