Home / Resources / Accounting
Accounting

What a chart of accounts really is (and how to structure one)

7 min read · Keepsync Systems

The chart of accounts is the most important list in any set of books, and the one most often built badly. It’s simply the master list of every account a business uses to categorise money — but its structure quietly decides whether your reports are useful or a mess.

The five buckets

Every account belongs to one of five types, always in the same order, because that order is the financial statements:

  • Assets — what the business owns.
  • Liabilities — what it owes.
  • Equity — the owners’ stake.
  • Income — what it earns.
  • Expenses — what it spends.

Assets, liabilities and equity form the balance sheet; income and expenses form the profit-and-loss.

Numbers and structure

Most charts use a numbering scheme (assets in the 1000s, income in the 4000s) so accounts sort logically, with subaccounts nesting detail under a parent so you can report at either level.

The mistake: too much detail

The most common chart-of-accounts error is granularity. A separate account for every tiny thing produces a chart hundreds of lines long that nobody can navigate. The goal is the least detail that still answers the questions the business asks — you can always drill into a transaction, but you can’t easily un-clutter a bloated chart later.

Why the account type is sacred

More than the name or number, the account’s type drives everything — where it lands on the statements, how it behaves. A type set wrong distorts every report while looking fine on the surface. It’s also the field that most often breaks in a migration: importing a chart of accounts cleanly is mostly about getting every type right.

A good chart is small, logically numbered, correctly typed, and built around the handful of things the owner needs to see. Everything else is drilling down.
Keepsync Data Prep

Clean data, done right

Data Prep maps, validates and reconciles accounting data before it’s written to QuickBooks — translating each system’s structure into the destination’s, and catching problems before they land.

See Data Prep