Sage 50: You cannot start a new fiscal year until the chart of accounts is correct
Sage 50 blocks the new fiscal year because one or more account records failed its check, usually due to data damage rather than a bookkeeping error.
“You cannot start a new fiscal year until the chart of accounts is correct.” When Sage 50 closes one fiscal year and opens the next, it re-validates every account in your chart before it will touch the balances. This message means that validation failed on at least one account. Despite the wording, it usually has nothing to do with your bookkeeping being wrong: the typical cause is one or more account records inside the company file that are incomplete, duplicated, or damaged.
Why Sage 50 shows it
The year-end process is one of the few times Sage 50 checks the entire chart of accounts in a single pass, so problems that sat quietly all year surface here. Common triggers include a crash, power loss, or network drop while the file was open; an import, conversion, or update that was interrupted partway; a duplicate or incomplete account record, such as one missing its account type; and an account the close depends on, such as the retained earnings account, being unusable. The message does not name the offending account, which is the frustrating part.
Take a backup first
Before changing anything, make a fresh backup of the company file. Every step below is safe on a good backup and risky on a file that is already damaged.
Look for visible problems in the chart
Open your account list and scan for duplicates, blank or garbled names, accounts with no type, and any account that throws an error when you open or edit it. Fix what you can see, then retry the year-end. If the list looks clean, the fault is below the surface and visual inspection will not find it.
Run data verification
Sage 50 includes a data verification tool that checks the company file, chart of accounts included, and reports what it finds; exactly where it lives depends on the version you run. Run it, let it repair what it can, then attempt the new fiscal year again. Two outcomes matter: if verification reports errors it cannot fix, the file is damaged; if it reports a clean file yet the message persists, the damage sits somewhere verification does not reach. Either way, stop retrying the year-end, because repeated attempts on a damaged file rarely help.
Consider an older backup
If you have a backup from before the message first appeared, restoring it is the most reliable do-it-yourself fix. The cost is re-entering everything recorded since, so weigh that against the alternative before you commit.
When the file needs professional repair
If verification cannot clear the fault and restoring an older backup would cost too much re-entry, the account data itself needs repair at the data level, and no setting inside Sage 50 will change that. Our engineers repair damaged Sage 50 company files, including charts of accounts that fail year-end validation, for both the US product (formerly Peachtree) and the Canadian one (formerly Simply Accounting). Details are on our Sage 50 database repair page; the evaluation is free and you receive a quote before any work starts, since cost and timing depend on the file.
Next step
Write down three things now, while they are fresh: the date the message first appeared, what happened immediately before it (a crash, an import, an update, an earlier year-end attempt), and whether data verification reported errors. Those three answers are what an engineer asks for first, and having them ready makes the free evaluation faster.