← All posts

What Is a Chart of Accounts? (And Why It Matters for Migration)

September 23, 2026 · LedgerSwitch Team

If you've ever searched for a transaction in your accounting software and couldn't remember whether you categorized it as "office supplies" or "general expenses," you've felt the downstream effect of chart of accounts design. A chart of accounts (COA) is the complete list of categories your business uses to organize every dollar that flows in and out—every invoice, bill, payroll run, and bank transfer. It's the organizational backbone of your books, and every accounting software platform you'll ever use is built around it.

Think of it as your business's financial filing cabinet. Just as you wouldn't throw every document into a single drawer labeled "stuff," you need categories that make sense for how you run your business, how you report to stakeholders, and how you file taxes. The chart of accounts delivers that structure, and when you switch accounting software, it's one of the most critical—and most overlooked—pieces of data you'll migrate.

Key Takeaways

What a Chart of Accounts Actually Contains

Every chart of accounts follows the same fundamental architecture, built around five core account types mandated by double-entry accounting. These aren't arbitrary—they're the categories that make your balance sheet and income statement mathematically balance.

Assets are what your business owns: cash in the bank, accounts receivable (money customers owe you), inventory, equipment, vehicles, and prepaid expenses. Each gets its own line in your COA.

Liabilities are what you owe: accounts payable (money you owe vendors), credit cards, loans, accrued payroll, sales tax collected but not yet remitted. These accounts have a credit balance, the opposite of assets.

Equity represents ownership in the business: owner's capital, retained earnings, draws or distributions. For corporations, this includes common stock and additional paid-in capital.

Revenue (or income) accounts track every way money comes into the business: product sales, service revenue, interest income, shipping charges you collect. These accounts reset to zero each year.

Expenses track every cost of running the business: rent, payroll, software subscriptions, marketing, cost of goods sold, professional fees. Like revenue, these reset annually.

Each account in your COA gets a unique number (typically three to five digits) and a name. The numbering convention isn't just for organization—it's how your accounting software, your bookkeeper, and your tax preparer quickly identify account types. Most businesses use a structure like this:

Within each range, you create sub-accounts that reflect your actual business operations. A retail business will have detailed inventory asset accounts and COGS accounts. A service business will have more granular expense categories for billable and non-billable labor. A SaaS company will track deferred revenue as a liability. The universal framework adapts to your reality.

Why Chart of Accounts Structure Actually Matters

The COA you build today becomes the lens through which you'll view your business for years. Choose poorly, and you'll spend hours every month trying to pull useful reports out of a system that wasn't designed to answer your questions.

A well-structured chart of accounts lets you answer questions quickly. How much did we spend on Facebook ads versus Google ads last quarter? What's our gross margin by product line? How do our office expenses compare year over year? If those answers require exporting to Excel and manually re-categorizing transactions, your COA isn't serving you.

Tax time becomes dramatically easier with intentional account structure. Your CPA needs to see expenses broken out by tax category—meals and entertainment, auto expenses, travel, home office, depreciation. If everything lives in a catch-all "general expenses" account, someone has to manually comb through hundreds of transactions to reclassify them for Schedule C or your corporate return. That's billable time you're paying for repeatedly, every single year.

The structure also impacts who can use the system effectively. If you hire a bookkeeper or bring on a part-time controller, they need to categorize transactions without asking you questions every day. Intuitive account names and logical groupings make delegation possible. Cryptic account names or overlapping categories turn bookkeeping into a bottleneck that only you can handle.

Perhaps most importantly, your chart of accounts shapes the decisions you make. If you can't easily see which marketing channels drive revenue or which service lines are profitable, you're navigating by gut feel instead of data. The businesses that outgrow their competitors are almost always the ones with financial visibility, and that visibility starts with account structure.

How Many Accounts Do You Actually Need

There's a sweet spot for chart of accounts complexity, and most small businesses miss it in one direction or the other. Too few accounts, and you lose visibility into where money is actually going. Too many, and you create a maintenance burden that slows down bookkeeping and makes reports unreadable.

A solo consultant or simple service business can often operate effectively withundefinedtoundefinedaccounts. You need enough granularity to track major expense categories for taxes and decisions, but not so much that you're debating which of three similar accounts to use for every transaction.

Most established small businesses with employees, inventory, or multiple revenue streams operate best withundefinedtoundefinedaccounts. This gives you room to track different income sources separately, break out major expense categories into useful sub-accounts (advertising by channel, contractor costs by department, travel versus meals), and maintain the asset and liability detail your balance sheet needs.

Once you reach mid-sized operations—multiple locations, departments, or business units—you might maintainundefinedtoundefinedaccounts. At this scale, you're often adding dimensions (location codes, department codes, class tracking) rather than just multiplying base accounts, but the COA itself grows to accommodate the complexity.

The right number for your business depends on how you need to report. If you have investors who want to see SG&A broken out from R&D, you need that structure. If you operate in multiple states and need to track revenue by jurisdiction for tax nexus, you need those accounts. If you're a single-location retail shop with one product category, you don't.

A useful rule: if you haven't posted a transaction to an account in over a year and don't expect to going forward, make it inactive. If you find yourself creating accounts that differ only by subtle naming variations, consolidate them. Your chart of accounts should evolve as your business does, but evolution means pruning as much as it means adding.

Common Chart of Accounts Mistakes That Create Long-Term Pain

The most expensive COA mistake is the catch-all account. "Miscellaneous expenses," "general operating costs," "other income"—these become dumping grounds that obscure what's actually happening in your business. Every accounting system lets you create these, and you should almost never use them. If a transaction doesn't fit your existing structure, that's a signal to create a properly named account, not to hide it in miscellaneous.

Duplicate or overlapping accounts create confusion that multiplies over time. If you have both "advertising" and "marketing expense" and no clear rule about what goes where, every transaction becomes a judgment call. Different people (or the same person on different days) will categorize the same type of expense inconsistently. Your reports become meaningless because the data isn't clean.

Overly specific accounts often backfire. Creating separate expense accounts for every individual software subscription might seem logical, but when you haveundefinedSaaS tools and each gets its own line, your P&L becomes unreadable. A better structure: one "software and subscriptions" expense account, with vendor names visible in transaction detail if you need to drill down.

Many businesses inherit their chart of accounts from their accountant or from the default template in their software, then never revisit it. That template was built for a generic business, not yours. The account names might not match how you think about your operations. The structure might lump together things you need to see separately, or split apart things you view as a unit.

And perhaps the most damaging long-term mistake: using account names that made sense when you were smaller but no longer reflect reality. That "contract labor" account you created when you hired your first freelancer might now represent six figures of annual spend across multiple functions. Breaking it into meaningful categories (contract software development, contract design, contract administrative support) transforms it from a black box into actionable data.

What Happens to Your Chart of Accounts During Software Migration

When you switch accounting software, your chart of accounts doesn't just copy over unchanged. The new platform has its own required accounts, its own numbering conventions, its own way of handling sub-accounts and account types. Your migration becomes an exercise in translation—mapping every account from the old structure to the new one.

Some mappings are straightforward. Your old "checking account" asset becomes the new system's checking account. Your revenue accounts transfer with minimal adjustment. But complexity emerges quickly. If your old system let you create unlimited sub-account layers and your new one only supports two levels, you'll need to flatten or restructure. If the old system treated certain items as account types and the new one treats them as classes or tags, you'll need to redesign how you track that dimension.

The mapping process also surfaces every structural problem in your existing COA. Those duplicate accounts? You'll need to decide which one survives. That miscellaneous bucket with three years of unclassified transactions? You'll either bring that mess forward or spend time reclassifying before migration. Inactive accounts clutter the migration checklist. Poorly named accounts force you to interpret your own historical decisions.

The most dangerous migration scenario is one-to-many or many-to-one mappings. If transactions from three old accounts need to split across five new accounts based on transaction attributes, you're introducing logic that must be executed correctly for every historical transaction. Get it wrong, and your opening balances won't tie out. Your historical reports won't match what you filed on tax returns. You've created a data integrity problem that takes months to unwind.

This is exactly why planning your chart of accounts structure before migration—not during or after—is so valuable. If you're going to redesign your COA, do it deliberately when you can review the new structure in full, not reactively as you encounter each mapping issue.

LedgerSwitch handles this complexity by letting you review and approve account mappings before any data moves, flagging structural mismatches and many-to-many scenarios that need human decisions. You can restructure as part of the migration or preserve your existing organization exactly, but either way, the mappings are explicit and verifiable. Learn more about how it works for accounting data migration.

How to Review Your Chart of Accounts Before a Software Switch

Start by exporting your current chart of accounts to a spreadsheet. Every accounting platform lets you do this. You want to see account numbers, names, types, and ideally activity—which accounts had transactions in the pastundefinedmonths.

Review every active account and ask: do I need this going forward? Is the name clear enough that a new bookkeeper would know what belongs here? Does this account give me information I actually use for decisions, taxes, or reporting, or is it just historical artifact?

Look for consolidation opportunities. If you have five expense accounts that collectively represent less than 2% of annual expenses, consider whether one or two broader accounts would serve you equally well with less maintenance burden.

Identify accounts you need to split.

Check your account numbering for gaps and logic. If your numbering scheme is inconsistent or you've exhausted a range and started reusing numbers, now is the time to renumber everything logically. Most platforms let you renumber accounts during migration far more easily than after you're live.

Compare your current structure to the default chart of accounts in your new software. The new platform will have required accounts (often things like opening balance equity, uncategorized income, uncategorized expense) that you might not have explicitly maintained. Understand where those fit and how the new system wants to structure account hierarchies.

Document any custom reporting you run today and verify your new structure will support it. If you have a monthly report that breaks out expenses by department or a quarterly view of revenue by service line, make sure your new COA (and the new software's features) can deliver that same view.

This review typically takes two to four hours for a small business COA, longer if you're restructuring significantly. It's some of the highest-value time you'll spend in the entire migration process, because decisions made here affect every month of bookkeeping going forward.

Setting Up a Chart of Accounts in New Software

Most accounting platforms offer a default chart of accounts based on your industry when you first set up. These templates are decent starting points but rarely optimal for your specific business. You'll want to customize from day one rather than accepting defaults and trying to retrofit later.

Start with the five core account types and build out from there. Create your primary asset accounts: bank accounts, accounts receivable, any significant fixed assets. Set up liability accounts for credit cards, loans, and accounts payable. Equity accounts are often auto-generated but verify they match your business structure (sole proprietor, partnership, S-corp, C-corp).

For revenue, create an account for each distinct income stream you need to track. If you sell products and services and need to see them separately, use separate accounts. If you operate in multiple states and need revenue by jurisdiction, structure for that. If everything is functionally the same and you have no reason to split it, a single revenue account is fine.

Expense accounts require the most thought. Start with mandatory tax categories: meals and entertainment, vehicle expenses, home office, depreciation if applicable. Add operational necessities: payroll, payroll taxes, rent, utilities, insurance. Then layer in the categories that matter for your decisions: marketing by channel, software by function, contractor costs by type.

Use account numbering that leaves room to grow. Number in increments ofundefined(4000, 4010, 4020) so you can insert accounts later without renumbering everything. Group related accounts numerically—put all marketing accounts in the 6100s, all technology in the 6200s, all facilities costs in the 6300s.

Most modern platforms support sub-accounts, which let you create hierarchies. This is useful for situations like breaking "advertising expense" into "advertising: Google," "advertising: Facebook," and "advertising: print," where you want detail in transaction entry but can roll up to a single line on summary reports. Just don't nest more than two levels deep—complexity compounds quickly.

Set up your COA completely before you begin entering transactions or migrating data. Changing account structure after you have transaction history is possible but messy, requiring historical reclassification or data that doesn't match your current categories.

The Relationship Between Your Chart of Accounts and Other Accounting Dimensions

Your chart of accounts isn't the only way to categorize transactions. Modern accounting software offers additional dimensions—classes, locations, departments, projects, tags—that let you track information orthogonal to account structure.

A construction company might use accounts to track expense types (labor, materials, equipment, permits) and classes to track job sites. Every transaction has an account and a class, which lets you see both "what we spent money on" and "which job it was for" without creating a separate account for every expense-by-job combination.

A multi-location retail business might use accounts for expense categories and locations to track which store incurred the cost. You can then run reports by location, by expense type, or by both.

These dimensions are powerful, but they create migration complexity. If your old software supported features your new one doesn't (or vice versa), you need to decide how to preserve that information. Sometimes it means incorporating that dimension into account names (turning class into account sub-structure). Sometimes it means accepting that historical data won't have the same dimensional richness as future data.

The key decision: what must live in your chart of accounts because it's fundamental to how you structure finances, and what can live in other dimensions? Revenue by product line might be an account-level distinction if it's core to how you run the business. Department attribution might be better handled as a class if it's a layer of analysis you run sometimes but not always.

Frequently Asked Questions

What is the difference between a chart of accounts and a general ledger?

The chart of accounts is the list of categories or buckets you use to organize transactions, while the general ledger is the actual record of every transaction posted to those accounts. Think of the COA as the filing cabinet's drawer labels, and the general ledger as all the documents filed inside those drawers. You design your chart of accounts once and refine it occasionally, but your general ledger grows with every transaction your business records.

Can I change my chart of accounts after I have been using accounting software?

Yes, you can add, edit, merge, or make accounts inactive at any time, but changes affect historical reporting in ways you need to understand. If you merge two accounts, historical transactions from both will appear combined in reports, which might obscure trends you were tracking separately. If you make an account inactive, past transactions remain but you can't post new ones, which is the right move for accounts you no longer need. Most platforms won't let you delete accounts with transaction history, which protects data integrity but means you'll carry inactive accounts indefinitely.

Do I need different charts of accounts for different business entities?

Yes, each legal entity should maintain its own chart of accounts, even if you run them together operationally. If you operate an S-corp and an LLC, they file separate tax returns and need separate books. You can design the two COAs to mirror each other for easy consolidated reporting, but the underlying data must remain separated by entity. Many accounting platforms let you switch between entities in one system, each with its own COA, which is far cleaner than trying to track multiple entities in a single set of books using classes or other workarounds.

Should my chart of accounts match my tax return categories exactly?

Your COA should support your tax return, but it doesn't need to match line-by-line. Tax forms group expenses broadly (advertising, office expenses, legal and professional fees), while your COA can be more granular. Your accountant will map multiple detailed accounts to single tax lines when preparing returns, which gives you operational detail during the year and correct tax categorization at year-end. The critical requirement is that your expense accounts are categorized in a way that makes tax mapping straightforward and consistent, which is why having clear, unambiguous account names matters.

What is a COA mapping and why does it matter for migration?

A COA mapping is the translation table that defines how each account from your old accounting software corresponds to accounts in your new software. For example, old accountundefinednamed "product revenue" might map to new accountundefinednamed "sales revenue." This mapping controls where every historical transaction lands in your new system, which means it determines whether your migrated data makes sense and whether opening balances are correct. An incorrect mapping might send three years of advertising expenses into your cost of goods sold, destroying the integrity of historical reports. Reviewing and approving mappings before data migration is not optional—it's the difference between clean books and a mess that takes months to untangle.

How does industry affect chart of accounts structure?

Industry determines which accounts you'll use heavily and which you won't need at all. A retail business needs robust inventory asset accounts and COGS accounts to track product costs, while a consulting firm might have minimal assets beyond receivables and virtually no COGS. A restaurant needs granular food and beverage cost accounts and tip tracking, while a SaaS company needs deferred revenue liability accounts to handle annual subscriptions. The five core account types remain universal, but the specific accounts you create within each type should reflect how your industry operates, how you're taxed, and what information stakeholders expect to see in your financial statements.

Building Your Chart of Accounts as a Strategic Tool

The businesses that grow sustainably and make confident decisions are almost always the ones with financial systems they trust. That trust starts with structure—a chart of accounts designed to give you visibility into what actually matters, maintained cleanly enough that your reports answer questions instead of creating new ones.

Treating your COA as a strategic tool rather than a technical detail changes how you approach accounting software migration. Instead of simply moving data from one system to another, you're taking the opportunity to build the financial infrastructure your next stage of growth requires. That might mean consolidating years of account bloat, breaking out categories you've always wanted to track separately, or aligning your structure to how you've evolved as a business.

The work you put into chart of accounts design before migration pays dividends in every month of bookkeeping afterward. Cleaner categorization, faster closes, reports you can actually use, and tax preparation that doesn't require reconstructing your entire year. Your books become a tool that serves your business instead of a compliance obligation you resent, and that shift starts with the structure you choose today. For detailed guidance on the migration process itself, visit our pricing page to see how LedgerSwitch handles COA mapping and data validation as part of a complete switchover.