A messy Chart of Accounts builds up slowly, and rarely gets fixed before a system migration. Moving uncleaned data into new software just shifts the same problems onto a shinier platform. Clean and rationalise the Chart of Accounts first, then choose the system.
Most NFP and education finance leaders don't set out to build a messy Chart of Accounts. It happens slowly. A code gets added for one grant. A workaround gets bolted on for a funder's odd reporting quirk. A cost centre from a program that wrapped up years ago never quite gets retired. Ten or fifteen years on, the Chart of Accounts has quietly become a history of every reporting decision the organisation has ever made, rather than something anyone sat down and designed on purpose.
That's a completely normal way for it to happen. It's also exactly what turns a straightforward system migration into a very expensive one.
The mistake happens before the software is even chosen
When an organisation moves to a new accounting platform, all the attention goes to the software itself. Which vendor, which features, what it costs. The Chart of Accounts tends to just come along for the ride, exported from the old system, mapped as closely as anyone can manage, and dropped into the new one without much thought.
The result is predictable, even if it's rarely what anyone intended. The new system looks modern, but the data sitting inside it is exactly as tangled as it was before. Multi-funder reporting is still something someone reconciles by hand each month. Grant acquittal still means a spreadsheet living quietly outside the "official" system. The organisation has spent six figures on a migration and ended up with the same problem, just wearing a newer interface.
What clean actually looks like
A rationalised Chart of Accounts isn't about having fewer codes for the sake of tidiness. It's about the structure doing the reporting work on its own, rather than someone doing it manually every month. In practice, that usually means:
- Fund and grant structures that map cleanly to what each funder actually asks for, without someone cross-referencing by hand
- Consistent naming and coding across entities, so a consolidated report doesn't need translating first
- Old or merged codes that get properly retired, instead of piling up indefinitely
- A structure documented well enough that a new finance hire could make sense of it without a handover meeting
None of this is exciting work. But it's consistently the difference between a system implementation that actually changes how the finance team operates, and one that just shifts the same old problems onto a newer platform.
The sequencing matters more than the software
The organisations that get the most out of a new system are, almost without exception, the ones who treat data remediation as its own piece of work. Something finished, or well underway, before implementation even begins, rather than squeezed into the migration timeline as an afterthought.
It's a less exciting place to start than choosing new software. It's also the one that actually decides whether the investment was worth it.
If your Chart of Accounts has quietly become a history of every reporting decision your organisation has ever made, that's worth talking through before any vendor conversation starts.
Contact us