Sage 50 error "This account can not be moved because it has been used in a transaction
Sage 50 blocks moving a chart of accounts entry that has posted transactions or serves as a linked account, to protect your history.
If Sage 50 has just told you “This account can not be moved because it has been used in a transaction or is a linked account”, it is refusing to relocate an entry in your chart of accounts, and the refusal is protective rather than a sign of damage. The account either has transaction history attached to it, or the program is using it automatically somewhere in your setup. Nothing is broken; the move you asked for is one Sage 50 simply will not make. The same message appears in the products sold as Peachtree in the US and Simply Accounting in Canada.
What “moved” means here
The message typically appears when you try to reposition an account inside the chart of accounts: changing where it sits in the list, its indent level, or the heading or segment group it falls under. Sage 50 treats an account’s position and identifier as part of its identity. Once transactions point at the account, or a module setting depends on it, the program locks the position so those references stay intact.
Why one account can move and another cannot
The message describes two different locks, and they have different fixes. The first is transaction history: any account with posted activity, even a single entry, is anchored in place. The second is the linked account: certain accounts are wired into the program’s automatic posting, for example accounts used for receivables, payables, inventory, sales tax, or payroll. Exactly which accounts are linked in your company depends on the modules and settings you use. Linked accounts are blocked even with no transactions on them, because settings elsewhere point at them.
Start with the changes that are allowed
Often the goal behind a move is cosmetic: a clearer label or better grouping. You can generally edit an account’s description without moving it, and reports will show the new wording while history stays put. If the account number itself is the problem, renumbering is a different operation from moving, and whether it is permitted depends on the file and how the account is used. Test any change on a backup copy first.
If the account is linked, repoint the link
When the block comes from the linked side, the account can sometimes be freed by pointing the relevant module setting at a different account, then moving the original. Where that setting lives depends on your version and edition, so we will not guess a path here. Two cautions: make the switch at a period boundary if you can, and expect new transactions to post to the new account while existing history stays where it originally posted.
The safe workaround: a new account and a journal entry
When an account with history truly must sit elsewhere, the standard route is to create a new account in the desired position, post a journal entry that moves the balance across, then make the old account inactive so it drops from day-to-day lists. Prior-period reports continue to show the old account, which is precisely why this route is safe: nothing already posted is rewritten.
When the whole chart needs restructuring
If this message keeps appearing because you are renumbering or regrouping the entire chart of accounts, the account-by-account workaround becomes slow and error-prone. Our engineers can restructure the chart in a copy of your data with history preserved; what is possible depends on the file, so we start with a free evaluation and a quote. If the reorganization is preparation for leaving Sage 50, the chart can instead be reshaped as part of a Sage 50 to QuickBooks conversion.
Take a fresh backup, then write down the accounts you need moved and why. With that list in hand, either the journal-entry route or a free evaluation of your file gives you a concrete starting point rather than a trial-and-error session against this message.