How to Redesign Your Chart of Accounts for a New ERP in 2026: A Government Guide
Chart of accounts redesign for a government ERP in 2026: define fund, department, object and project segments, meet state rules, and map old accounts to new.
On this page
- Key takeaways
- What is a chart of accounts redesign (and why a new ERP is the moment to do it)?
- The segments of a government chart of accounts
- Check your state’s uniform chart of accounts rules first
- How to redesign your chart of accounts for a new ERP in 2026: 7 steps
- Mapping old accounts to the new chart of accounts (crosswalk)
- Common chart of accounts redesign mistakes to avoid
- Chart of accounts redesign sign-off checklist
- FAQ
- Conclusion: build the chart for the next 15 years, not the last 15
Chart of accounts redesign for a new ERP means rebuilding your government chart of accounts and its account string around a few strictly defined segments (fund, department, program, object and project) based on how your government is actually organized and what it must report. Then, and only then, you map every old account to the new structure before data conversion. GFOA’s chart of account guidelines for ERP implementations recommend using the implementation to develop a new chart unless strict requirements dictate a specific structure.
Key takeaways
Start from your reporting needs and org structure, not from the old chart. GFOA’s guidance says to start over.
Define each segment strictly and in writing: fund, department, program, object and project.
Check state rules before the first workshop. Michigan mandates a uniform chart, Washington prescribes minimum BARS coding, and Tennessee requires cities to crosswalk audited data.
Push detail into subledgers (project ledger, pay codes, work orders) instead of creating new funds or object codes.
Build the crosswalk after the design, and freeze the chart before the first full mock conversion (KCT rule of thumb).
Get written sign-off from finance, budget, your external auditor and the operating departments.
Every budget, report, interface and security role in your new ERP sits on the chart of accounts. Yet it often gets rushed because it feels abstract. Rushing it is one of the Tyler Munis implementation mistakes KCT sees most often, and the same pattern shows up on every platform.
KCT works on both sides of these projects, as an ERP advisor and as an implementer. On engagements like the City of Oxnard’s ERP program, our team leads data conversion directly, so we see exactly where a weak chart breaks.
Most guidance online is written for universities or corporations, so this guide focuses on fund accounting, state uniform chart rules and real mapping for a city or county.
What is a chart of accounts redesign (and why a new ERP is the moment to do it)?
Chart of accounts redesign is the process of rebuilding the account structure your government uses to record every transaction, so it reflects your current organization, funds, programs and reporting obligations. For most cities and counties, the right moment is during an ERP implementation, because conversion, training and process change are already happening together.
GFOA puts it plainly. Its chart of account guidelines say that “unless there are strict requirements that a specific chart of account structure be used, GFOA recommends that organizations take the opportunity of the ERP system implementation to develop a new chart of accounts.”
Why fix the old chart? GFOA observes that many cities created extra funds and object codes to track projects and grants because the legacy system lacked flexibility.
The stakes are also unusual. In a February 2026 article, consulting firm Plante Moran describes chart of accounts restructuring as, for many finance teams, “a once-in-a-career effort.”
Your move: decide early whether you’re redesigning or just re-mapping. If your state prescribes the structure, you’re designing within it, which is still a redesign, just with guardrails.
The segments of a government chart of accounts
Government chart of accounts segments usually come down to five components: fund, organizational unit (department and division), program or activity, object and project. GFOA lists these as the common structure, but it explicitly does not recommend using every possible segment. Use only the segments you need, and smaller organizations should keep the chart simple.
Swipe to see all columns →
| Segment | What it answers | Example values | Common mistake |
|---|---|---|---|
| Fund | Which self-balancing set of accounts pays for or receives this? | General Fund, Water Utility Fund | Creating a fund to track a single project or grant |
| Department and division | Who is responsible? | 10 Finance, 1010 Accounting, 20 Police, 2020 Patrol (GFOA example) | Coding that breaks every time there’s a reorg |
| Program or function | What public purpose does this serve? | General government, public safety, transportation, recreation | Making programs a 1:1 copy of departments |
| Object | What was bought, earned, owned or owed? | Salaries, overtime, contracted services, property tax revenue | Creating object codes for specific projects or grants |
| Project or grant | Which time-bound effort is this part of? | A capital project, a federal grant, a disaster cleanup | Storing grant detail in the GL string instead of the project ledger |
Real governments publish these codes for staff. The City of Madison, Wisconsin’s ERP page lists two-digit agency numbers (15 for Finance, 30 for Fire, 31 for Police) alongside materials from a December 2024 session on its 2025 chart changes.
Fund
A fund is a self-balancing set of accounts. Your funds should exist because external reporting requires them, not because a manager wanted a separate report. GFOA recommends clear written criteria for what counts as a fund, documented and reviewed periodically.
GASB standards and state rules shape those criteria. Washington’s State Auditor’s BARS manual (GAAP), updated January 2024, notes that while GASB Statement 54 sets no numeric threshold for a “substantial portion” of inflows, at least 20 percent has been recommended as a reasonable limit for reporting a special revenue fund. It also prescribes fund numbering by first digit: 000 to 099 for the General Fund, 100 to 199 for special revenue, 200 to 299 for debt service, 300 to 399 for capital projects, 400 to 499 for enterprise and 500 to 599 for internal service funds.
Department and division
Your department segment should mirror the org chart, with numbering that shows hierarchy. GFOA’s example uses prefix numbers: Finance is 10 and its divisions run 1010 to 1040, while Police is 20 with divisions 2010 to 2040. GFOA adds that for smaller organizations, one segment (department only) is likely enough.
Design so that a reorg is a change to segment values and roll-ups, not a structural change to the string (KCT rule of thumb).
Program or function
Programs cut across departments, so don’t copy the org chart. In GFOA’s example, not all police programs are focused on public safety, and police isn’t the only department that contributes to public safety.
Tie this segment to the functions your annual report and state filings use. In Washington’s BARS structure, the second and third digits of revenue and expenditure codes identify functions and activities.
Object (account)
The object segment records what was bought or earned, along with assets, liabilities and fund balance. Start with major categories and add detail only where someone will actually use it.
GFOA’s example uses ranges such as 10000 for assets, 20000 for liabilities, 30000 for fund balance, 40000 for revenue and 50000 to 70000 for expenses. It warns that object codes suffer the same problem as funds: they get created to track projects, grants and programs.
Project and grant tracking
Use a project segment, backed by the ERP’s project ledger, for anything with a start and end date: capital projects, grants and events like disaster cleanup. GFOA recommends keeping the detail in the project ledger rather than the account string.
Federal grants raise the bar. Under 2 CFR 200.302, your financial management system must identify every federal award received and expended.
As applicable, that includes the Assistance Listings title and number, the Federal award identification number, the year the award was issued and the name of the federal agency or pass-through entity. The system must also compare expenditures with budget amounts for each award.
Store those attributes on the grant or project record, not inside the GL string.
Your move: list every report you must produce (budget book, annual comprehensive financial report, state filing, grant reimbursements, department dashboards) and tag which segment feeds each one.
Check your state’s uniform chart of accounts rules first
Some states prescribe the chart itself, some prescribe minimum reporting codes, and some only require you to crosswalk your data into a standard format. Find out which applies to you before workshop one, because it changes what you’re allowed to design.
Michigan: mandatory uniform chart. Michigan Treasury’s November 2020 release memo states that compliance “is mandatory for all local units of government in the state of Michigan,” with the chart’s history dating to at least 1968.
As of the 2020 edition of the chart, cited here only for its structure, the account number is built from three sets of three digits (fund, activity and account), and a more complex local chart with extra digits is allowed as long as it stays consistent with the uniform one.
Design against the current edition, not the 2020 one. Treasury’s January 2023 bulletin asked local units to update to the January 2023 edition, said Treasury had begun revising the chart annually and said past editions should be discarded. Get the current Uniform Chart of Accounts edition from Michigan Treasury’s local government accounting resources before workshop one.
Washington: prescribed BARS coding. The BARS manual says the structure requires a ten-digit capability, with seven digits reserved for the account code and three for the fund. The annual report requires seven digits for all account codes.
If you use unassigned digits locally, the manual warns those digits “may be prescribed in the future” and the new prescription overrides your local use.
Tennessee: mandatory crosswalk. A January 2023 Comptroller memo requires incorporated municipalities, beginning with the audit year ending June 30, 2023, to convert audited data into a standard format and submit it to the Comptroller, using an Excel crosswalk that the city’s external auditor applies or verifies.
Cities aren’t required to adopt the municipal chart, but the memo notes adopting it would simplify the crosswalk. Tennessee counties have used a uniform chart since the mid-1980s.
Swipe to see all columns →
| State | Who it applies to | What’s required | Design implication |
|---|---|---|---|
| Michigan | All local units of government | Use the uniform chart (fund, activity, account) | Your string must stay consistent with the state chart; extra digits are allowed |
| Washington | Cities, counties and special purpose districts using BARS | Prescribed fund ranges and seven-digit account codes for the annual report | Keep BARS codes as a segment or a reliable attribute; avoid local use of unassigned digits |
| Tennessee | Incorporated municipalities | Crosswalk audited data to a standard format | Your chart can differ, but every account needs a clean crosswalk value |
Your move: call your state auditor, treasury or comptroller’s local government office and ask what applies. Ask your external auditor too. School districts should check their state education agency’s accounting manual separately, since K-12 rules usually differ from city and county rules.
How to redesign your chart of accounts for a new ERP in 2026: 7 steps
A chart of accounts redesign follows seven steps, from reporting requirements to long-term governance:
Inventory the reports and requirements the chart must serve.
Form a cross-functional design team.
Define each segment and its rules in writing.
Build the new structure from scratch, then compare it to the old one.
Push transaction detail into subledgers.
Build the old-to-new crosswalk.
Validate, freeze and govern the chart.
1. Inventory the reports and requirements the chart must serve
Start with outputs, not codes. Plante Moran’s process begins with a vision of what the chart must produce, naming the annual comprehensive financial report, budget-to-actual reporting and federal compliance reports.
Add your budget book, state filings, grant reimbursements and department reports. The output is a requirements matrix: each report in a row, each segment it needs in a column.
2. Form a cross-functional design team
A chart designed only by accounting will miss how budget, payroll and operations use it. Include finance, budget, accounting, grants, HR and payroll, IT and at least two operating departments, and consult your external auditor.
Ohio University’s June 2026 progress update describes a similar design team spanning finance, budget, accounting, research administration, HR and IT, plus implementation partners.
3. Define each chart of accounts segment and its rules in writing
Every segment needs a strict definition that everyone agrees on. GFOA says each segment should be defined strictly, with the definition communicated and enforced, and no exceptions.
Write a segment dictionary. For each segment, capture:
Its definition and length
Its owner
Who can request new values
Which combinations with other segments are valid
4. Build the new structure from scratch, then compare
Design from your current organization and operations first, and only then look back at the old chart. GFOA’s “start over” recommendation says the new chart should not concern itself initially with mapping back to the old one.
Work within what your ERP supports. Platforms handle segments differently, so confirm your vendor’s documented capabilities in a design workshop.
5. Push detail into subledgers
Your GL string doesn’t need to hold every detail. GFOA’s guidelines note that most organizations keep the chart relatively simple and use other system components, such as the project ledger, AR charge codes, salary pay codes and work order detail, to carry the specifics.
6. Build the old-to-new crosswalk
Once the design is approved, map every legacy account to its new segment values. Plante Moran places the crosswalk in the develop step, alongside cleaning up existing accounts for conversion readiness. The full mechanics are in the mapping section below.
7. Validate, freeze and govern
Test the new chart with real transactions and real reports before you lock it. A useful bar comes from Washington’s statewide ERP program: its One Washington draft chart of accounts model for state agencies (July 2020) aimed for a structure that is “simple, expandable and flexible for the life of the system.”
Then freeze it before the first full mock conversion, because every later change forces a re-map of budgets, history and interfaces. Assign an owner for new values and review requests quarterly. (Both are KCT rules of thumb.)
Plan the time honestly. KCT’s ERP implementation timeline guide shows where this work sits in design and configuration. The redesign alone can take 2 to 3 months (KCT rule of thumb).
Chart of accounts decisions ripple into conversion, budget loads, interfaces, security roles and reports, usually while your staff still run daily operations. KCT’s Full-spectrum ERP Implementation team runs the chart workshops, builds the crosswalk and reconciles every mock conversion alongside your finance team.
Mapping old accounts to the new chart of accounts (crosswalk)
A chart of accounts crosswalk is a table that maps every legacy account string to its new segment values. Build it after the design is approved, not before. Mapping first just recreates your old chart under new numbers.
Here’s an illustrative example (not from a real client) of one legacy string splitting across the new segments, using GFOA’s example numbering.
Swipe to see all columns →
| Legacy string | Fund | Department | Program | Object | Project |
|---|---|---|---|---|---|
| 101-4210-5310 “Police patrol overtime, grant” | General Fund | 2020 Patrol | Public Safety | 51300 Premium Pay (overtime) | Grant project record (award details live here) |
The grant, once buried in a description, now sits on a project record that can carry the award attributes 2 CFR 200.302 requires.
One-to-one, one-to-many and many-to-one mappings
Chart of accounts conversion: balances, history and budgets
Decide how many years of history to convert, and whether to convert it in detail or at summary level. Opening balances must convert by fund and tie out exactly.
Budgets must load in the new structure, and every interface (utility billing, payroll, cashiering) must post to new strings. Unlike Tennessee’s summary-level state crosswalk, your ERP conversion needs an account-level one.
Test the crosswalk in mock conversions and parallel
Tie the legacy trial balance to the converted trial balance, fund by fund, in every mock conversion. Then prove the mapping holds under live conditions in your ERP parallel test before go-live.
Splits and merges you missed will surface at your first month-end close on the new ERP, so plan for it.
At Oxnard, KCT leads data conversion and integrations across deliberately split go-lives (Finance, then HCM, then EPL), with each cutover rehearsed before the next began.
Common chart of accounts redesign mistakes to avoid
The most common chart of accounts redesign mistakes are carrying old habits into the new structure and leaving the chart without an owner.
Chart of accounts redesign sign-off checklist
A chart of accounts redesign is ready for configuration only when each item below has a named owner and a documented artifact.
Segment dictionary approved (owner: finance director).
Reports-to-segments matrix complete (owner: budget and accounting).
State compliance confirmed in writing (owner: accounting manager): uniform chart, BARS or crosswalk requirements checked with the state office.
External auditor review (owner: finance director).
Grant and project attributes defined (owner: grants lead): award fields required under 2 CFR 200.302 built into the project record.
Crosswalk complete (owner: conversion lead): every legacy account mapped, every split rule documented.
Budget load tested (owner: budget office).
Interface mapping signed (owner: IT): every inbound system posting to valid new strings.
Security by segment defined (owner: IT and finance): who can see and post to which funds and departments.
Governance policy adopted (owner: finance director): who approves new values and how often requests are reviewed.
Written sign-off from finance, budget and the operating departments on the design team.
FAQ
These answers cover the questions finance teams ask most often about chart of accounts redesign.
When should you redesign your chart of accounts?
Your chart of accounts redesign should happen during an ERP implementation, before system configuration begins. GFOA’s guidelines recommend using the implementation to develop a new chart unless strict requirements dictate a structure.
How long does a chart of accounts redesign take?
A chart of accounts redesign typically takes 2 to 3 months within the design and configuration phase (KCT rule of thumb), depending on segments, departments, state rules and legacy workarounds.
What are the segments of a government chart of accounts?
The segments of a government chart of accounts are usually fund, organizational unit (department and division), program or activity, object and project. GFOA recommends using only the segments you actually need.
Should you map your old chart of accounts to the new one?
Yes, mapping is required for conversion, but only after the new design is approved. GFOA advises that a new chart should not concern itself initially with mapping back to the old one.
Do states require a uniform chart of accounts for local governments?
Some do. Michigan mandates a uniform chart, Washington prescribes BARS coding and Tennessee requires municipalities to crosswalk audited data, so check with your state auditor, treasury or comptroller first.
How many segments should a chart of accounts have?
A chart of accounts should have only as many segments as your reporting requires. GFOA does not recommend using every possible segment. Most governments land between three and five, with extra detail carried in subledgers such as the project ledger, pay codes and work orders (KCT rule of thumb).
Who should be involved in a chart of accounts redesign?
A chart of accounts redesign team should include finance, budget, accounting, grants, HR and payroll, IT and at least two operating departments, with your external auditor consulted on the design.
Conclusion: build the chart for the next 15 years, not the last 15
A successful chart of accounts redesign starts from reporting needs, not old codes. Build it from what you must report and what your state requires, define every segment strictly, push detail into subledgers and only then map the old chart across.
Start the requirements matrix and the state check this month, before your vendor’s design workshops begin.
If you’d like experienced hands running the workshops, the crosswalk and the mock conversion reconciliations, KCT’s Full-spectrum ERP Implementation team can help at any point in the project.
Not sure your current design will hold up? Start with an ERP Health Check. The scope of support depends on your modules, departments and stakeholders, so it begins with an assessment.