How far should a CPA firm standardize the chart of accounts across CAS clients?
To the structure rather than every account: fix the numbering ranges, top-level groupings and naming convention, then allow client-specific detail inside them. For an existing client, map the current accounts to that structure rather than rebuilding the ledger, which protects period-on-period comparability.
A firm with twenty recurring clients and twenty bespoke charts of accounts has twenty structures to relearn, and the cost lands almost entirely on the people with the least spare time. Every transaction without an obvious home becomes a judgment, every judgment is a possible review finding, and the same judgment gets made again next month because nobody recorded the answer.
The instinct is to impose one chart of accounts on everything. That usually fails for a reason worth understanding before starting. This sits under CAS production support; for one client’s setup at the start of an engagement, see CAS client onboarding.
Standardize the structure, not every account
The part worth making uniform is the frame: numbering ranges, top-level groupings, and the naming convention. Inside those ranges, let clients have the detail accounts their operations actually need. A reviewer then knows where to look in any ledger in the book, while a manufacturer and a professional services firm keep the accounts that make their own reports meaningful.
Pushing standardization down to individual accounts produces the opposite of the intended effect — a tidy ledger that nobody can run a useful report from, and a client who stops recognising their own numbers.
What has to stay client-specific
- Revenue categories that match how the business is actually managed
- Cost accounts a lender, franchisor or funder expects to see
- Departments, locations or entities reported on separately
- Accounts a prior adviser set up for a reason that still holds
That last one deserves a question before it is removed. An account that looks redundant is sometimes the only place a recurring obligation is visible.
Map an existing ledger; do not rebuild it
For a client already running, restructuring the chart of accounts breaks period-on-period comparability, invalidates saved reports and can disturb prior-year figures. Mapping achieves most of the benefit without any of that: the accounts stay where they are, and each is recorded against the standard grouping it belongs to, so reporting and review use the common structure while the client’s history stays intact.
Mapping is reversible. Restructuring is not, which is why it belongs to onboarding or to a cleanup already being done for another reason — and why the decision is the firm’s either way. Where the incoming records need correcting first, ledger hygiene covers that work.
The rule that prevents duplicate accounts
Most duplicates are created by a preparer making a reasonable guess. The convention that stops it is simple and has to exist in advance: a preparer may code to an existing account and must raise anything that appears to need a new one. Account creation is a decision, not a step.
And when two existing accounts could both plausibly take the same transaction, the account names are the problem rather than the preparer. A good name describes the nature of the cost, not a vendor or a project — vendors change and projects end, while the category persists.
Keep the convention where the work happens
A chart-of-accounts standard documented separately from the close process is a document that was agreed once and never opened again. Keeping it alongside the checklist the preparer already consults each period is what makes it operative. For how the periods themselves are sequenced across a book, see the CAS close calendar, and for what the firm checks before release, quality review.