Redesigning your chart of accounts before an ERP replacement

Reference article · 5 min read

An ERP replacement is the only practical chance most agencies get to rebuild the chart of accounts. Conversion moves whatever structure exists today into a system that will hold it for the next fifteen or twenty years, including the fund created for a single grant in the 1990s, the object codes that duplicate each other, and the department numbers that no longer match the org chart. If nobody redesigns the structure before configuration begins, the new system inherits all of it and the cleanup becomes a separate project later, paid for twice.

The redesign is finance work, not IT work. The controller, budget office, grants staff, and capital program staff decide what the segments mean; the implementation team configures what they decide. Starting the other way around produces a structure shaped by the software's defaults rather than by the agency's reporting obligations.

Give each segment exactly one job

Segment sprawl almost always comes from overlap, where two segments partly answer the same question and staff guess which one to use. Before touching code values, write one sentence describing what each segment answers.

• Fund. The legal and fiscal accountability structure used for external reporting under governmental accounting standards. Funds exist because of legal restrictions and reporting requirements, not because someone wants a subtotal.
• Department or organization. Who is accountable for the budget. This should track the organization chart and carry a hierarchy for divisions and cost centers.
• Program or activity. What service is delivered, independent of who delivers it. This is how you report cost of service across departments.
• Project and grant. Time-limited work with inception-to-date accounting that crosses fiscal years.
• Object or natural account. The nature of the revenue or expenditure. Keep it natural, so salaries are salaries whether they are charged to a grant or the general fund.

If two segments can both answer a question, one of them is a reporting attribute, not a segment.

How many segments is too many

The honest test is not a number, it is ownership. For every proposed segment, name the recurring report that requires it and the person responsible for maintaining its values. Segments that fail that test become optional fields, then inconsistently populated fields, then unusable data.

• Most general purpose government structures work with fund, department, object, and a small number of additional dimensions such as program, project or grant, and sometimes location or funding source.
• Avoid smart coding inside a segment, where digits carry hidden meaning such as the first character indicating governmental versus proprietary. Use the system's hierarchies, roll-up trees, and attributes instead, because those can be restructured without renumbering.
• Every added segment multiplies the number of valid combinations that must be built, validated, and secured. Ask how combination edits and account generation rules work before adding one.
• Leave numbering room for growth, but not so much that the scheme becomes unreadable.

Keep grants and capital projects out of the fund segment

The most common inherited problem is a fund created for every grant award and every capital appropriation. Fund counts grow into the hundreds, annual financial report preparation gets harder, and the fund structure stops describing legal restrictions and starts describing history.

Track awards in a grant or project segment with inception-to-date balances, and hold award attributes on the grant record rather than in the account code: awarding agency, pass-through entity, assistance listing number, award and budget periods, match requirements, and indirect cost treatment. Federal award reporting requirements, including schedule of expenditures of federal awards preparation and single audit obligations, change over time, so confirm current requirements with the applicable federal guidance and your auditor before fixing the design.

Capital projects follow the same pattern. Use a project segment with phases and multiple funding sources so a single project can draw on bonds, grants, and pay-as-you-go money without inventing a fund for each.

Build a crosswalk the auditors can follow

The crosswalk is a permanent record, not a conversion worksheet. Build it as one row per legacy code combination with the new combination, the mapping rule, the effective date, and who approved it.

1. Map at the level you will actually convert. Decide early how many years of history come over and whether history converts as detail or summary balances.
2. Document every many-to-one mapping, because detail collapsed during conversion cannot be recovered later from the new system.
3. Reconcile converted balances by fund to the last audited financial statements, and keep the reconciliation with the crosswalk.
4. Re-create a full prior year from mapped data, including the budget book and fund-level statements, before signing off.
5. Store the authoritative crosswalk under finance's control with version history, not in an unowned spreadsheet on a shared drive.

What to ask vendors and put in the contract

• Ask how many segments the system supports, maximum segment length, how many alternate hierarchies a segment can carry, and whether hierarchies can be restated for prior years after a reorganization.
• Ask how combination edits, default account generation, and inactivation of old codes work, and whether inactivated codes still report in history.
• Ask what the conversion tooling does with mapping files, error handling, and reruns.
• Require design signoff and the crosswalk as named contract deliverables owned by the agency, in an exportable format.
• Require at least two mock conversions with reconciliation reports, and tie the conversion payment milestone to balances that tie, not to data being loaded.
• Require that agency staff can create and restructure hierarchies and code values after go-live without vendor change orders.

HQT works with state and local agencies on enterprise system planning and data conversion, including chart of accounts design and crosswalk documentation.

Frequently asked questions