Chart of accounts cleanup: map the reports before changing live accounts
In this illustration, the current management report shows office costs of £6,600 against £4,800 last year, an apparent 37.5% increase. Most of that jump comes from coding. During a tidy-up, stationery lost its own account and is now coded to the combined office costs line, while last year's column still shows £1,200 of stationery separately. A chart of accounts cleanup needs a reporting map, and a clear view of what each software operation does to history, before anyone changes a live account.
Build the map before touching accounts
Start with the report lines you want, then map every existing account to one of them. We suggest recording, for each mapping, the old account, its type, the new reporting line, the reason, the effective date and who approved it. Similar names do not prove a shared purpose, and a zero balance does not show an account is unused or safe to remove, so check what has actually been posted to each one.
A reporting map is often enough on its own. Grouping old and new accounts under the same management report line can fix the comparison without changing any posted transaction.
Test the comparison
In this hypothetical example, the costs in all three accounts are assumed comparable. A map cannot fix a change in what was included.
Before and after any change, run the trial balance and a few prior and current period reports and compare them. Also check what routes transactions into each account, such as bank rules, recurring entries, products and services, and payroll mappings where used.
| Comparison | Prior year | Current year | Change |
|---|---|---|---|
| Office expenses alone against combined office costs | £4,800 | £6,600 | £1,800, or 37.5% |
| Office expenses and stationery mapped to office costs | £6,000 | £6,600 | £600, or 10% |
Rename, inactivate or merge
These operations do different things. Renaming changes an account's label and leaves its transactions where they are. Inactivation usually removes an account from routine future coding, and merging combines its history with another account. Intuit's US help for QuickBooks Online explains the risks of inactivating and merging in that product.
Making an account inactive keeps its transactions. For a balance sheet account with a non-zero balance, Intuit warns that QuickBooks creates an automatic entry moving the balance to Opening Balance Equity, which can affect balances and sales tax reports, and that reactivating the account does not reverse it. Products and services, recurring transactions and protected default accounts can also depend on an account. If a balance sheet account still holds a real balance, decide with the accountant where it belongs before inactivating anything. A plug entry to force it to zero only hides the problem.
Merging is permanent. Intuit says it moves past transactions into the account you keep and makes the duplicate inactive, and recommends it only for accounts created by mistake. Accounts connected to online banking or created by the system should not go through the ordinary merge. The merged-away account loses its reconciliation history, although its transactions stay reconciled, so Intuit advises keeping its reconciliation reports first. An export or backup is useful evidence and does not make a merge reversible.
Start with one pair
Pick one suspected duplicate pair. Document what each account contains, its balance and what routes transactions into it, build the comparative map, and let the accounting owner choose between a report mapping, an inactivation and a merge. Make that one change, check the reports against your before figures, then move to the next pair.