Another user has changed this account class" Sage 50 error
This message means Sage 50 hit a data conflict or corruption in your company file, not that a coworker is really editing it.
You are trying to post or edit a transaction, and Sage 50 stops you with:
“The program could not process this transaction because another user has changed this account class.”
Despite the wording, this is rarely about another person. In plain terms, Sage 50 thinks the account class your transaction touches has been modified since your screen was loaded, so it refuses to save. On a single-user installation, where no one else could possibly have changed anything, the message almost always points to a damaged or inconsistent account class record inside the company file itself.
Why does Sage 50 show this message?
Sage 50 locks account class definitions while a transaction is being written. Before saving, it checks that the class is unchanged. If the check fails, the save is rejected to protect the data.
The check can fail for three reasons. Someone genuinely edited the account class while you had the transaction open. The file was not closed cleanly after a crash, power loss, or forced shutdown, leaving stale internal state. Or the account class record itself is damaged, so the comparison fails even with no other user involved.
What should you try first?
Close the transaction screen without saving, then close Sage 50 completely and reopen the company file. Have any other users log out first. In many cases the conflict was transient and the same transaction will post normally afterward.
If it recurs, make a fresh backup of the company file right now, before further attempts. Repeated failed saves can add to the confusion inside the file.
The message keeps coming back
If the error appears on the same account or the same transaction every time, and especially if you are the only user, the account class record is likely damaged. This is not something a setting change fixes. Our engineers see this pattern in files that survived an improper shutdown or that have grown unstable over time.
At that point the file needs professional attention, and we would say so plainly: continuing to retry, or rebuilding lists by hand, risks making the underlying damage worse.
How we can help
We repair damaged Sage 50 and Simply Accounting databases directly, and we can examine your file and tell you what is wrong before you commit to anything. The diagnosis is free, and cost and timing depend on what the examination finds. If the file is beyond economic repair, converting the data to QuickBooks is often a practical route out, and we handle that too.
Start with a free evaluation: send us the file through our Sage 50 database repair service page, or if you would rather leave Sage behind, see our Sage 50 to QuickBooks conversion service. Either way you will know within the evaluation what the file needs.