How to Set Up a Chart of Accounts for Your Business

Every financial report a business produces traces back to a single structural decision: how the chart of accounts is designed. A chart of accounts (COA) is the organized list of all financial accounts a company uses to record transactions in its general ledger, and its design sets the ceiling for financial analysis. If the COA doesn’t record a data point, it won’t appear in any report. Retroactive changes mean re-coding historical transactions, a process that grows more expensive with every passing quarter.

Getting COA design right at the outset, especially for travel and expense (T&E) categories, helps save accounting teams significant rework during month-end close and tax season alike. This guide covers what belongs in a chart of accounts, how to structure T&E categories for tax compliance, common mistakes to avoid, and how automation helps maintain accuracy as your business scales.

What a Chart of Accounts Does and Why Design Decisions Persist

A chart of accounts provides the structural blueprint for recording every financial transaction a business makes. It uses general ledger (GL) accounts to classify transactions into broad categories, such as assets, liabilities, equity, revenue, and expenses, and then into more specific subcategories, such as salaries, rent, or office supplies. The COA is typically organized in the order those categories appear on financial statements, with balance sheet accounts first and income statement accounts second.

What makes COA design consequential is its permanence. Adding new analytical distinctions after the fact requires re-coding each historical transaction, a cost that scales with transaction volume. A growing company that initially lumps all travel into a single account, for instance, may later need to revisit historical entries if it wants to separate domestic from international airfare. The architecture chosen at setup shapes what finance and accounting teams can analyze for years.

The Core Account Categories

Every COA is built on foundational categories, such as assets, liabilities, equity, revenue, and expenses, though Cost of Goods Sold is often broken out as a distinct range between revenue and operating expenses.

Many COAs use number ranges like these to group accounts:

In many COA structures, the leading digit helps staff quickly recognize the account category and helps reports sort consistently.

How Numbering Conventions Support Growth

Small and midsize businesses typically use relatively short account numbers, which can provide enough granularity without unnecessary complexity. Larger organizations and multi-entity companies may extend to longer structures, or multi-segment codes, to accommodate divisions, locations, and product lines.

Regardless of company size, leaving gaps in your numbering ranges makes future changes easier. Reserving unused numbers, such as assigning accounts at 6100, 6200, and 6300 rather than 6101, 6102, and 6103, gives you room to add new accounts later without renumbering the entire structure.

How to Structure Travel and Expense Accounts

T&E accounts typically reside in the expense range and represent one of the most complex areas of COA design. The fundamental question is whether to use a single parent account for all travel, separate top-level accounts per category, or a hybrid approach with sub-accounts. The right answer depends on how material T&E spending is to your business. If travel represents a significant cost driver, granular sub-accounts for airfare, lodging, ground transportation, and meals can justify the administrative overhead.

The structural decisions that carry the most tax, compliance, and scalability weight involve how you separate meal and entertainment accounts, whether you encode dimensions into account numbers, and how you handle corporate card clearing.

Separate Meals, Entertainment, and Travel for Tax Compliance

Tax rules create a meaningful split that directly affects COA design. Client entertainment, business meals, and travel expenses may receive different tax treatment. A combined “Meals & Entertainment” account, still common in many COAs, makes it harder to calculate the book-tax differences needed for reporting.

When a single invoice includes meals and entertainment, the costs should be allocated between the two. Your COA should reflect that separation at the account level. A recommended structure includes distinct accounts such as:

• Business meals — travel meals and meals with clients
• Entertainment — tickets, events, golf, sporting events
• Per diem — standard rate reimbursements

You may also want a dedicated account for employer-provided meals if that category matters to your business and tax reporting workflow.

Use Dimensions Instead of Multiplying Account Numbers

One of the most damaging COA design errors is encoding every reporting dimension, such as department, location, and project, directly into the account number. That approach quickly creates more account combinations than most teams want to manage. Using dimensional tracking in a modern ERP keeps the base COA simpler while still covering reporting needs.

Maintain one natural account per expense type and let cost center, department, and project segments carry the analytical splits as separate attributes. A single “Salaries & Wages” account (6100) can serve all departments when the cost center segment distinguishes Sales from Engineering from Finance.

This structure also simplifies integration when transactions flow into ERP systems such as NetSuite, QuickBooks, or Xero, because the natural account stays stable while dimensional fields carry the reporting detail.

Build a Clearing Account for Corporate Cards

Corporate card transactions need a path from statement import to final GL classification. A clearing account, sometimes called a suspense account, holds unallocated card charges until an employee’s expense report assigns each transaction to the correct expense account. The payment method, corporate card versus out-of-pocket, can change which GL account certain components of an expense (such as sales tax) ultimately post to, depending on an organization’s accounting setup. The expense type drives the GL account; the payment method is tracked at the liability level.

A typical flow works like this:

• Card statement imports hit the clearing account.
• Expense reports move charges from clearing to specific expense accounts, such as airfare, meals, and lodging.
• The clearing account balance returns to zero.

Any remaining balance at period end signals unreconciled charges that need attention.

Mistakes That Erode COA Accuracy Over Time

Even a well-designed COA can deteriorate without active maintenance. The most common problems share a root cause: treating the chart of accounts as a static artifact rather than an actively governed structure.

Letting the Account List Grow Without Constraints

Account proliferation is the most predictable COA problem. Teams add accounts reactively, for new projects, vendor types, or one-off cost categories, without a governing framework. The remedy is periodic consolidation: review existing accounts, merge duplicates, and inactivate (but don’t delete) dormant accounts to preserve historical records while preventing future postings.

In addition to a name, each account should also have a written definition that specifies what belongs in it and what doesn’t. When definitions are vague, staff make different judgment calls about where to code the same type of transaction, and month-over-month variance analysis becomes unreliable. The more manual the process, the bigger the risk is of inconsistent coding. And according to The State of Corporate Travel and Expense 2026, a report from Skift and Navan, 29% of the travel and finance professionals surveyed say their companies still process expenses manually — up from 23% two years ago.

Importing a Legacy COA Into a New ERP Without Redesigning It

ERP migrations present the best opportunity to fix a broken COA and the most common moment to waste it. Organizations frequently “lift and shift” their existing account structure into a new system without redesigning it for the ERP’s native capabilities. Flat account structures that worked in a legacy system don’t take advantage of the dimensional reporting built into modern platforms.

The fix:

• Redesign the COA from scratch using the ERP’s best practices.
• Produce a complete crosswalk document mapping old accounts to new.
• Schedule go-live dates well before the final week of a fiscal quarter.

A poor COA structure in the ERP can influence reporting long after implementation.

Skipping Multi-Entity Standardization

When subsidiaries build their own COAs independently, account numbers and names drift apart over time, and consolidation becomes a manual, error-prone process. Standardizing account numbers across the company helps support more accurate reporting — and requiring subsidiaries to adhere to a master COA, while more effort upfront, often makes the close checklist substantially easier than maintaining separate mapping tables.

How Expense Automation Supports a Clean COA

Automated expense platforms sit between employee-submitted data and the ERP’s GL structure. The goal is a clean handoff. But employees typically select expense types during submission, and few understand the accounting implications. Many finance teams resort to manual workarounds to fix coding errors before uploading to the ERP. The Skift and Navan report found that 71% of travel and finance professionals surveyed spend more than 30 minutes on each expense report.

Platforms that apply GL codes at the point of transaction can help ease this burden. Navan Expense, for example, captures 130-plus data points per transaction and applies GL codes based on the company’s chart of accounts. Its Expense Agent reads individual receipt line items to classify purchases by account — useful when the same merchant could mean software, office supplies, or reference materials. A Forrester Consulting Total Economic Impact study commissioned by Navan and based on a composite organization found Navan customers saved 40% in auditing time.

Fewer misclassified transactions often means fewer reclassifying journal entries at close. Direct ERP connections further support that workflow by moving transactions from swipe to general ledger in systems such as NetSuite, QuickBooks, and Xero. But no platform eliminates the initial setup step — the expense type-to-GL account mapping is always a manual configuration task. What automation changes is what happens after that configuration.

Design Your Chart of Accounts for the Business You’re Becoming

A chart of accounts isn’t a document you set up once and forget: It’s financial infrastructure that shapes every report, every close, and every spending decision your team makes. The choices you make now about account granularity, T&E separation, numbering conventions, and dimensional structure will either support or constrain your finance team for years.

Start with the core account categories, then build your T&E sub-accounts to reflect current tax requirements — especially the separation of meals, entertainment, and travel when different treatment applies. Use your ERP’s dimension and cost center features rather than encoding departments into account numbers, and assign formal ownership of the COA to your controller or accounting manager with a documented change request process and at least annual reviews.

The companies that close their books fastest aren’t the ones with the most accounts. They’re the ones whose accounts are well-defined, consistently coded, and supported by systems that capture the right data at the point of transaction. That’s a foundation worth building deliberately.