The chart of accounts (COA) is the foundation of your entire financial reporting system. Every transaction is categorised by it. Every P&L, balance sheet, and management report is built from it. Get it right and financial reporting is clean, fast, and useful. Get it wrong and the consequences compound — bad data, poor reports, and a remediation project every time someone wants a different view of the business.
Most SMBs inherit a COA from whatever their accountant set up initially or from a default template in their accounting software. Those defaults are designed for compliance, not management reporting. This post explains the principles of a well-designed COA and what to change if yours isn't serving the business.
What a Chart of Accounts Is (and Isn't)
A chart of accounts is a structured list of all the financial account codes used to classify transactions. Every income, cost, asset, liability, and equity movement in the business flows into one of these codes.
The COA determines:
- How your P&L is structured and which cost lines you can see separately
- Whether you can report by department, product line, or project
- Whether your management accounts match the structure your team actually thinks in
- How easy it is to produce the reports investors, banks, or boards expect
It is not the same as the management reporting structure — you can present financial information in management reports that groups or reframes COA categories differently. But the COA is the underlying data structure, and the quality of your management reporting is constrained by its quality.
Principle 1: Structure Should Mirror How You Manage the Business
The most common COA design error is letting it be driven by tax or statutory reporting requirements. Statutory accounts need to be prepared, but they're not the primary user of your COA.
The primary user is your management team. Structure the COA around the questions your management team actually asks:
- How much are we spending on sales and marketing as a defined category?
- What is the direct cost of delivering each service or product line?
- How does the engineering team's budget compare to plan?
- What is the gross margin on each revenue stream separately?
If your COA lumps "sales salaries" and "marketing spend" into a single "selling expenses" code, you can't answer those questions from your accounting system. If your direct costs and overheads are mixed together without cost centre or department coding, you can't separate them.
Principle 2: Revenue Should Be Split at the Level You Actually Manage
Revenue is the most important line, and it should be coded at the level of granularity that reflects your business model and reporting needs.
Minimum recommended split:
For a services business: By service line or type of engagement — retainer revenue, project revenue, training/event revenue, licence revenue. Each of these has different margin characteristics and different growth trajectories.
For a SaaS or subscription business: By product tier, by customer segment, or by revenue type (subscription vs professional services vs one-time). The distinction between recurring and non-recurring revenue is typically important enough to require separate codes.
For a product or e-commerce business: By product category or brand, and by channel (direct, marketplace, wholesale).
The principle: if you would ever want to report on a revenue stream separately, give it its own code. If you're combining things in your management accounts that need to be separated for analysis, the COA isn't granular enough.
Principle 3: Cost of Revenue vs Operating Expenses Must Be Clearly Separated
This is the most common structural failure in SMB charts of accounts — the line between direct costs (those that vary directly with revenue) and overhead (those that are relatively fixed regardless of revenue) is blurred or non-existent.
Direct costs (COGS / cost of revenue) should include:
- The cost of goods or materials in a product business
- Direct staff costs for fee-earners in a services business
- Hosting and infrastructure costs directly driven by revenue in a SaaS business
- Third-party fulfilment costs, delivery costs, and payment processing fees
Operating expenses (overhead) should include:
- Management and back-office salaries
- Rent, premises, utilities
- Marketing and advertising spend
- G&A: legal, accounting, insurance, software subscriptions
- Sales salaries and commissions (these are above the gross margin line, below the revenue line)
When these are mixed together, gross margin is meaningless — which means you can't benchmark it, model it, or manage it effectively.
Principle 4: Use Cost Centres or Departments for Overhead Allocation
Even once direct costs and overhead are cleanly separated, a single "G&A" or "Operations" bucket for all overhead costs is usually insufficient for managing a business with multiple teams or product lines.
Most modern accounting systems (Xero, QuickBooks, NetSuite) support cost centre, department, or class coding as a dimension on top of the COA. This allows you to code each expense to both a nominal code (what type of expense) and a cost centre (which part of the business incurred it).
This gives you:
- Departmental P&Ls (what did the sales team cost vs the engineering team vs the back office?)
- Product-line profitability (how much overhead can be attributed to each revenue stream?)
- Budget vs actual analysis by team
Set up the cost centre structure before you need the analysis — retrospectively recoding transactions is painful.
Principle 5: Consistency Over Time Matters More Than Perfection at Inception
A COA that changes category definitions significantly year-over-year makes trend analysis impossible. If "marketing spend" included agency fees in year one and excluded them in year two, your marketing cost trend is meaningless.
Establish your COA structure, document what belongs in each code, and then change it rarely and deliberately. When you do change it, restate prior periods if the change is significant, or at minimum document the change clearly so that anyone reviewing historical trends understands it.
Principle 6: Keep It Clean — Remove or Merge Codes That Aren't Used
Most accounting systems accumulate codes over time — codes set up for a specific purpose that then never get used, or codes that duplicate each other. A COA with 200+ codes that are partially used is harder to maintain consistently than one with 60–80 well-defined codes that are used correctly every time.
Conduct a COA audit annually: identify codes with no transactions in the last 12 months, identify codes where the category definition is unclear or overlapping, and rationalise.
A Practical Structure for a €2M–€10M Business
Revenue accounts (by revenue stream × 3–6 codes) COGS / cost of revenue (by major direct cost type × 3–8 codes) Gross profit line
Sales and marketing expenses (4–6 codes) Research and development / product (3–5 codes) General and administrative (6–10 codes) Total operating expenses
EBITDA Depreciation and amortisation EBIT Finance income/expense Tax Net income
On the balance sheet: current assets (cash, receivables, inventory, prepayments), fixed assets, current liabilities (payables, deferred revenue, accruals, short-term debt), long-term liabilities, equity.
Total codes: typically 60–100 for a business of this size. More granular if there are multiple distinct revenue streams or departments to manage.
Frequently Asked Questions
Can I restructure my COA once the business is running? Yes, but it requires recoding historical transactions to maintain comparability, or accepting a break in the trend data at the point of restructure. The earlier you do it, the less historical data needs to be restated.
Does my accountant need to be involved? Yes — particularly to ensure the new structure remains compliant for tax and statutory purposes. The design of the management-facing COA should be led by finance or a fractional CFO, with the accountant validating the statutory compliance dimensions.
What's the difference between a COA and a budget template? The COA defines how transactions are classified in your accounting system. The budget template is a planning tool that may use the same structure or group COA codes differently for management purposes. Ideally they align closely to avoid reconciliation complexity.
BB Financial Services Kft frequently begins new client engagements, including our accounting and monthly close work, with a COA review and restructure — it's one of the highest-leverage improvements available to growing businesses. Get in touch if your financial reporting isn't giving you the view of the business you need.
<!-- ============================================================== -->