What Good Looks Like: Chart of Accounts

The chart of accounts (COA) is rarely the most exciting part of an ERP implementation, but it is one of the most important.

When organizations begin a system implementation, the conversation tends to gravitate towards the visible outputs: reporting, dashboards, workflows, integrations, automation, and more. Yet the quality of every one of those outputs is determined by the foundation beneath them. Get the chart of accounts right, and reporting becomes flexible, scalable, and meaningful. Get COA wrong, and you inherit years of workarounds, duplicate accounts, and manual processes that quietly persist long after go-live.

The Most Common Chart of Accounts Mistake

One of the approaches we see most often is organizations recreating the chart of accounts from their previous platform. It is understandable. After all, users are familiar with the old system. The reports already exist, and teams know where to find what they need. The problem is that a structure designed around the constraints of an old system is rarely the right structure for a modern one.

A good COA should reflect how the business operates today and how it intends to operate tomorrow — not how a system you are leaving behind happened to work. Before creating a single account, it is worth asking how you want to report, what dimensions of analysis you need, what operational structures exist now, and what growth or change you expect. The answers should drive the design.

The COA is Far More Than a List of GL Accounts

Many organizations think of the chart of accounts as simply a list of general ledger codes. In Yardi, the reality is more involved. A COA is the combination of account codes, cash account structures, account trees, reporting requirements, governance standards, and the operational processes that determine how financial information is captured and consumed. Understanding how these elements interact matters, because a decision made early in the design process can shape reporting flexibility for years.

Let the Property Structure Do the Heavy Lifting

For organizations moving from traditional ERP platforms, Yardi requires a genuine mindset shift,  though not the one people often expect. Voyager is, at its core, a property-centric ledger: each property operates as its own accounting entity, so much of the dimensionality you might once have built into a long, segmented account string is already handled by the property and entity hierarchy. This is why the instinct to proliferate accounts for every business dimension is usually the wrong one in Yardi. 

Segments do exist and have their place for finer breakdowns, such as department or cost center, but should be introduced deliberately. Every segment adds complexity to data entry, reporting, integration, and governance. The objective is not to capture as many dimensions as possible, but the right ones, in the right place. Good design balances reporting requirements against operational simplicity.

33Floors Insight:

The biggest COA problems rarely come from having too few accounts—they come from trying to make the Chart of Accounts solve reporting problems that should be solved with Account Trees, segments, or reporting hierarchies.

A Clear Coding Convention Pays Off for Years

A chart of accounts should be more than functional; it should be logical, consistent, and easy to understand. That starts with a well-defined coding convention. Historically, numbering has often evolved organically, leaving inconsistent ranges, duplicated logic, and codes that no longer carry meaning. Strong conventions reserve ranges for specific account types, leave room for expansion, and stay consistent across entities and portfolios — assets in the 1000s, liabilities in the 2000s, and so on.

Naming deserves the same discipline as numbering. Consistent, predictable account descriptions make the ledger easier to read, search, and report on, and they prevent the near-duplicates that quietly accumulate when conventions are loose. A simple structured approach keeps related accounts grouped and unambiguous wherever they appear. The exact structure matters less than consistency and governance.

It is also worth designing with external standards in mind. For example, in UK commercial real estate, the RICS’ “Service Charges In Commercial Property” sets clear expectations for how costs are categorized and allocated. The “Functional Accounting Guide and Chart of Accounts” by BOMA (Building Owners and Managers Association International) is one US benchmarking equivalent. Aligning account structures to these standards from the outset simplifies reporting, improves transparency, and removes the need for manual mapping later.

Account Trees Are Where Reporting Flexibility Lives

One of the most powerful and most underused parts of Yardi’s general ledger is the account tree. Many teams assume every new reporting requirement needs new GL accounts. In practice, that only inflates the chart of accounts and makes it harder to govern.

An account tree determines how accounts aggregate within financial statements and management reports. Think of it as the reporting framework that sits on top of the ledger. Rather than duplicating accounts to satisfy different audiences, you can present the same underlying data in different ways. A property owner may want operating expenses grouped one way; an asset manager may need an entirely different view of the same numbers. Well-designed account trees deliver both without touching the underlying accounts, giving you a cleaner GL, simpler maintenance and far greater flexibility. It is worth spending as much time on reporting structures as on the accounts themselves.

Don’t Overlook Cash Accounts

Cash account design is another area that causes problems, particularly for teams arriving from other platforms. The relationships between bank accounts, cash accounts, entities, and properties do not always translate directly, and their configuration influences cash reporting, property operations, fund accounting, and intercompany transactions. Time invested here upfront prevents operational headaches later.

Good Design Is Only Half the Job

A chart of accounts should support not only today’s reporting but tomorrow’s growth. A well-designed structure absorbs future business changes without a fundamental redesign every few years. But getting the structure right before go-live is only half the job. A COA that launches in excellent shape stays that way only if the controls around it are equally strong, with clear ownership, a defined approval process for creating or amending accounts, and naming and coding standards that everyone actually follows. Without that governance, even the best-designed chart drifts. Duplicate accounts creep in, conventions slip, and a few years later you are back where you started. With governance, a chart that is excellent at launch is likely to remain excellent years later.

What Good Looks Like in Charts of Accounts

A strong chart of accounts tends to share several characteristics. Use these as a quick check on your own COA:

• Built around your operating model, not old habits. Design from how the business reports and runs today, not from how your previous system happened to work.
• Property structure first, segments second. Let Voyager’s property-centric ledger carry the dimensionality. Reach for segments only where they add something the property structure can’t.
• Account trees do the reporting work. Use them to give each audience the view it needs, rather than proliferating GL accounts to satisfy every report.
• Consistent coding and naming. Reserve ranges by account type and apply the same discipline to descriptions — Cash – Operating, Cash – Reserves — so the ledger stays readable and free of near-duplicates.
• Designed for what’s coming. Leave room for new entities, funds and regions so growth doesn’t trigger a redesign.
• Governed, with clear ownership. Put an approval process and a named owner behind every change, so the COA is as strong years on as it was at go-live.
• Understood by finance and operations alike. If only one team can navigate it, it isn’t finished.

Above all, a good chart of accounts lets the business scale without continually re-engineering its financial foundation.

Key Takeaways in Charts of Accounts

We have seen organizations spend months refining reports and dashboards after go-live, only to find the real constraint sits in the Chart of Accounts beneath them. It is complex, it takes time, and it rewards careful thought. But if there is one area worth investing in during a Yardi implementation, it’s this one. Because long after the project closes, the quality of your Chart of Accounts will continue to shape every financial decision you make.

Want to learn more about setting your ERP implementation up for success? Read Your Guide to a Successful Yardi Implementation or check out our in-depth Implementation Series.