Sage 50 "one or more accounts have already been linked" error explained
Sage 50 is refusing a transaction because an account in it is already tied to another linked account elsewhere in the file.
You were probably entering or posting a transaction, and Sage 50 stopped you with:
The program could not process this transaction because one or more accounts have already been linked.
In plain language, this is not a complaint about the transaction itself. Sage 50 is telling you that one of the accounts involved is already connected to something else, and that existing connection blocks the new one you are trying to create. The wording is vague on purpose, because the software cannot tell you which account or which link is in the way.
What “linked” means here
In Sage 50, accounts get linked to other parts of the system. A bank account can be linked to a module, an account can be set as a default for a particular transaction type, and accounts can be linked to each other for things like clearing or control purposes. Once a link exists, Sage 50 protects it. It will not let a second, conflicting link be created through a transaction.
So the message usually means the transaction would implicitly reassign an account that is already spoken for. The software declines rather than silently change your setup.
Why it happens
A few situations produce this message regularly. One is a data conversion or import, where accounts arrive with links already attached and a transaction then tries to establish the same link again. Another is a change in account structure, such as merging or renumbering accounts, after which old links were never cleared. A third is genuine file damage, where the link tables inside the company file are inconsistent and the software sees links that should not exist.
Which of these applies to you depends on the history of your file. If the message appeared right after a conversion, import, or restore, that history is the likely cause.
What to check first
Start with the account itself. Open the account in your chart of accounts and review its settings and any linked-transaction configuration. If you can identify the conflicting link and you do not need it, removing it may let the transaction post. Make a fresh backup before changing account links, because these settings affect many transactions at once.
If the transaction involves a default or linked account for a module, try the transaction with a different, unlinked account. If it goes through, you have found the account causing the conflict.
When the file itself is the problem
If the message appears on ordinary transactions, on accounts you have verified are not linked anywhere, or across many different entries, the link data inside the file is probably inconsistent. That is not something you can fix from the screens. It means the internal link tables disagree with what the program shows you, and forcing entries around it risks making the bookkeeping wrong.
In that case the file needs professional attention. Our engineers repair damaged Sage 50 and Simply Accounting databases, including exactly this kind of broken internal linking, and we can also convert Sage 50 data to QuickBooks if you would rather move off the file entirely.
A useful next step
Stop entering transactions against the affected account and make a backup of the company file as it stands now. Then send us the file for a free evaluation. We will tell you which link is conflicting, whether the file is damaged, and what the repair involves, with no obligation.