Sage 50 message: "Cannot use this account here because it is a total account
Sage 50 blocks the entry because the account is a statistical total that cannot hold its own transactions.
You are trying to post a transaction to an account, and Sage 50 refuses it with:
Cannot use this account here because it is a total account.
Despite the wording, nothing is wrong with your data. Sage 50 is telling you that the account you picked is a summary-level account. It exists only to roll up the balances of the accounts beneath it. It cannot accept a transaction of its own, so the program stops you at the point of entry.
What a total account is
In the Sage 50 chart of accounts, some accounts are posting accounts and some are total accounts. A posting account is where transactions actually land: an expense line on a bill, a payment, a journal entry. A total account sits above other accounts in the hierarchy and adds up their balances for reporting.
Think of it as a subtotal on a report. A subtotal is calculated, not typed in. If you try to type a number into a subtotal, the report has nowhere to put it. Sage 50 enforces the same rule in your ledger: totals are computed from their children, so they are closed to direct posting.
Why it happens
The usual cause is simply picking the wrong line in the account list. Total accounts and posting accounts often sit near each other and can have similar IDs or names, so it is easy to grab the parent instead of the child.
It can also happen after a conversion or a chart-of-accounts restructure. When data is moved between systems, or between Sage 50 and QuickBooks, account types and hierarchy levels do not always map cleanly. An account that was postable in the old system may arrive as a total account in the new one. If you inherited the file, the structure may have been set up this years ago by someone else.
How to fix it yourself
First, check whether a posting account already exists beneath the total account. Open your chart of accounts and look at the accounts indented under the one that was rejected. In most cases the correct choice is one of those children, and re-selecting it resolves the message immediately.
If no suitable child account exists, create one. Set it up as a posting account under the total account, then use it on your transaction. The total account keeps summarizing as before.
If the account genuinely should be postable, its type or level in the hierarchy may need to change. How you do that depends on your Sage 50 edition and how the chart was built, so review the account’s properties before editing, and back up your company file first.
When the structure itself is the problem
Sometimes the issue is not one transaction but a chart of accounts that came out of a conversion with the wrong levels throughout. Fixing that by hand, account by account, is slow and risky. The same applies if you are mid-way through moving data from Sage 50 (or Peachtree, or Simply Accounting) into QuickBooks and the hierarchy is fighting you at every step.
Our engineers handle both situations: repairing or restructuring Sage 50 data, and converting Sage 50 to QuickBooks with the account hierarchy mapped correctly. If the message keeps appearing across many accounts, send us the file for a free evaluation and we will tell you what is involved before you commit to anything.