This account cannot be deleted because it is used for Job Defaults
Sage 50 is blocking deletion of a GL account because it is referenced by the Job Defaults setup for jobs or projects.
When Sage 50 tells you “This account cannot be deleted because it is used for Job Defaults,” it means the general ledger account you are trying to remove is still wired into the default account assignments that Sage 50 uses whenever a new job or project is created. The account is not necessarily tied to a specific job that exists today; it is sitting in the template that feeds new jobs. Until you point that template elsewhere, Sage 50 will not let the account go.
What “Job Defaults” actually means
Job Defaults are the accounts Sage 50 pre-fills when someone sets up a new job, phase, or cost code. Think of them as the blueprint: every new job starts by inheriting these accounts, and only then do you override them individually. Because the blueprint still names your GL account, Sage 50 treats the account as in use, even if no live job is currently posting to it.
Remove the account from Job Defaults first
The safest fix is to change the default before attempting the deletion. In your Sage 50 company, open the Job Defaults or Default Job Cost settings (the exact location depends on your edition and whether you are on the US Peachtree product or the Canadian Simply Accounting product). Replace the account you want to delete with the correct alternative account, save, and then try deleting the account again from your chart of accounts. In most cases the deletion goes through cleanly once the reference is gone.
Check whether the account is also used on existing jobs
If Sage 50 still refuses after you clear the default, the account is likely assigned to one or more existing jobs, phases, or estimates. You will need to reassign those individually before the account can be removed. This is straightforward when only a handful of jobs are involved, but in a company with dozens or hundreds of jobs it can be tedious to track down every reference manually.
When the account will not release
Sometimes the account resists removal even after every visible reference has been updated. That can happen when the company file has lingering links in its internal job-cost tables, or when the file itself has structural damage that prevents a clean update. If you have cleared Job Defaults and checked existing jobs and the message still appears, the file likely needs professional attention rather than further trial and error.
Our engineers regularly work with Sage 50 (Peachtree and Simply Accounting) company files that have stuck or orphaned account references, and we can inspect the file, identify every place the account is linked, and clear those links safely. If you are also considering moving your Sage 50 data to QuickBooks, that conversion can sidestep the problem entirely by rebuilding the chart of accounts fresh in the destination file.
Send us the file for a free evaluation and we will tell you exactly what is holding the account in place and what it will take to release it.