Pending or failed transactions" blocks starting a new year in Sage 50
The message means Sage 50 will not roll the year forward until unfinished or rejected transactions are cleared from the data.
The message on screen reads:
You cannot start new year because there are pending or failed transactions.
Despite the wording, this is usually not about the calendar year at all. Sage 50 runs a year-end close as a batch process. Before it commits the close, it checks that every transaction in the batch is complete and posted. If even one entry is stuck in a pending state, or failed to post cleanly, the whole close is refused. The software is protecting your balances: it will not roll forward while the underlying data is inconsistent.
What “pending” and “failed” actually mean here
A pending transaction is one that was saved but never fully posted. Common causes include a workstation that lost its network connection mid-posting, a user closing the program at the wrong moment, or a transaction waiting in a queue such as an unprocessed online banking or payroll batch. A failed transaction is one that tried to post and was rejected, often because of damage inside the company data itself.
The frustrating part is that Sage 50 often does not tell you which transaction is the problem. The message is a gate, not a report.
Start with the safest checks
First, make a fresh backup of your company data before changing anything. Then have every other user log out of the company completely. Pending states can persist simply because another session still holds the transaction open.
Next, look through your unposted queues: unreleased or unposted invoices, receipts, payments, and any banking or payroll batches awaiting processing. Release or post anything waiting, and void or delete anything you no longer want. In multi-user setups, check whether any remote or queued entries from another workstation never made it in.
If you use online banking or integrated services, a stuck download is a frequent culprit. Re-running the import, or clearing the stuck batch, often resolves the block without touching your history.
When the block is data damage
Sometimes there is no visible pending transaction because the “pending” flag lives in a damaged part of the data. The transaction may have half-posted during a crash or power loss, leaving the file internally inconsistent. In that case no amount of clearing queues will help, and the year-end close will keep failing on the same hidden entry.
Our engineers see this pattern often after an interruption during posting. It is a data-integrity problem, not a workflow problem, and it needs the file itself examined. If you have reached this point, stop retrying the close. Each attempt writes to the file, and you want a clean backup preserved from before those attempts.
We repair damaged Sage 50 and Simply Accounting databases directly, clearing stuck transaction states so the year-end close can run. You can read about our Sage 50 database repair service or send us the file for a free evaluation and quote.
A useful next step
Restore your most recent backup from before the problem appeared into a test location, and try the year-end close there. If it succeeds, the fault is in the live file’s data rather than in your books, and that tells you the file needs professional attention. We can confirm this quickly from a copy, at no cost, before you commit to anything.