The chart of accounts decides what the books can tell you. A generic small-business chart lumps hosting with office software and puts every salary in one line, which makes SaaS gross margin and departmental spend a manual exercise every month. A chart built for SaaS produces those numbers straight from the ledger.
Two dimensions, not one
| Dimension | Answers | Examples |
|---|---|---|
| Account | What was bought or earned | Salaries, hosting, software, subscription revenue |
| Department (class or tracking category) | Which function it serves | Cost of revenue, R&D, sales, marketing, G&A |
Salaries is one account; the department tells you whether a salary belongs in cost of revenue (support, customer success onboarding, DevOps running production) or operating expense.
Revenue accounts
- 4000 Subscription revenue
- 4100 Usage and overage revenue
- 4200 Implementation and professional services revenue
- 4900 Discounts and credits (contra-revenue)
Split by stream so subscription gross margin and services margin can be reported separately.
Cost of revenue
- 5000 Hosting and infrastructure (production only)
- 5100 Third-party software embedded in the product
- 5200 Payment processing fees (if treated as cost of revenue by policy)
- 5300 Salaries and benefits, coded to the cost of revenue department
Staging and development environments belong in R&D, not cost of revenue. The split needs a written policy so it does not drift.
Operating expense
Keep the account list by nature (salaries, payroll taxes, benefits, contractors, software, travel, marketing programs, rent, professional fees) and let the department dimension assign function.
Balance sheet accounts SaaS companies need
| Account | Why |
|---|---|
| Deferred revenue, current and long-term | Annual and multi-year prepayments |
| Unbilled receivables or contract assets | Revenue recognized before invoicing |
| Capitalized commissions, current and long-term | ASC 340-40 |
| Capitalized software | ASC 350-40, if the policy applies |
| Accrued payroll and bonuses | Monthly accruals |
| Clearing accounts for each payment processor | Stripe and similar payouts reconcile through them |
| SAFE or convertible notes | Until conversion |
Map once, report forever
Build a mapping from accounts and departments to the board's P&L lines: revenue by stream, cost of revenue, gross profit, R&D, S&M, G&A, operating income. The same mapping feeds the operating model so budget and actuals line up account for account.
A migration checklist
- Agree on the target P&L and the metrics it must produce.
- Draft the account list and department list.
- Map old accounts to new; reclassify the current year's history so comparisons work.
- Lock the chart; new accounts need finance approval.
- Document coding rules for the common gray areas.
We design the chart around your board reporting, move the history onto it, and keep the coding consistent at every close.
Sources
- IRS, Publication 583, Starting a Business and Keeping Records
- IRS, Recordkeeping for businesses
- FASB Accounting Standards Codification (Topics 606, 340-40, 350-40)
Questions founders ask
Should departments be accounts or classes?
Use departments, classes or tracking categories for function (R&D, sales, marketing, G&A, cost of revenue) and keep the account list for the nature of the expense. That keeps the chart short and every report sliceable.
How many accounts is too many?
If people regularly code to the wrong account, there are too many. Most SaaS companies run well on a list of 80 to 150 accounts with departments doing the rest.
