Sage 50: "You have changed the account's number, making its assigned account class invalid
Sage 50 is saying the account number you entered falls in a range that belongs to a different account class than the one assigned to that account.
The message “You have changed the account’s number, making its assigned account class invalid.” reads like an accusation of a bookkeeping mistake, but it is really a structural complaint. Sage 50 keeps the chart of accounts organized by account class: assets, liabilities, equity, income, expenses, and their subtypes. Each class is tied to a block of account numbers, and the exact blocks depend on the chart of accounts your company file was built from. When you renumber an account so its new number lands in a block belonging to a different class, the pairing of the new number with the account’s existing class stops making sense to the program, and it blocks the change until the mismatch is resolved.
Why it happens
The usual trigger is simple: you edited an account’s ID and typed a number that crosses a class boundary. The message also appears when accounts are renumbered in bulk, by an import, or by a conversion tool that remaps numbers without keeping the class aligned. Less often, customers report seeing it when they had not touched the number at all, which points to the chart of accounts structure being inconsistent or damaged rather than to anything the user did.
Put the old number back
If you were only tidying up the numbering, the safest fix is to cancel the change and re-enter the original number. Nothing else in the file has been altered at that point, so the message clears and no further cleanup is needed.
Create a new account instead of renumbering
If the goal is to move the account into a different block for good, adding a new account with the desired number and class is usually cleaner than renumbering the old one. The existing account keeps its history and its statements stay untouched; you simply post forward to the new account. Many accountants prefer this route precisely because it does not rewrite the past.
Change the account’s class to match the new number
The alternative is to keep the new number and change the account’s class to one that belongs in that block. Be aware this reclassifies the account everywhere it appears, including on statements covering periods already closed, since class drives how accounts are grouped when reports are built. Whether Sage 50 will let you change the class of an account that already carries transactions depends on the file and its history; if it refuses, the new-account route above is the way forward.
If it appears during an import or conversion
When the message surfaces while loading data from another system, the number-to-class mapping in the conversion is at fault: numbers were assigned into ranges that do not match the classes attached to them. Fixing it means correcting the mapping so the two stay aligned, or letting the conversion assign both together. If you are moving Sage 50 data into QuickBooks, our Sage 50 to QuickBooks conversion service handles number and class alignment as part of the move.
If you did not change any number
A message like this arriving unprompted, with no edit on your side, suggests the chart of accounts in the file is inconsistent, and that is a data problem rather than user error. Our engineers deal with this through Sage 50 and Simply Accounting database repair, and a free evaluation will tell you whether the file can be corrected in place.
Before you dismiss the message, note the account ID, the number you tried to assign, and the class currently attached to the account. That combination determines which fix applies, and it is the first thing we ask for when we look at a file.