SaaS Chart of Accounts: Numbering, COGS Split and Dimensions

Use ranges that group accounts by financial statement section, and leave gaps so you can add accounts later. A workable outline:

1. 1000 to 1999, assets: cash, accounts receivable, prepaid expenses, capitalized software and equipment.
2. 2000 to 2999, liabilities: accounts payable, accrued expenses, deferred revenue, payroll liabilities, sales tax payable and debt.
3. In a common numbering scheme, 3000 to 3999 is equity: common and preferred stock, additional paid-in capital, retained earnings.
4. 4000 to 4999, revenue: subscription, usage-based, professional services and other.
5. 5000 to 5999, cost of revenue: hosting, support, delivery and payment processing.
6. 6000 to 7999, operating expenses: payroll and other costs, grouped by nature.
7. 8000 to 8999, other income and expense: interest, foreign exchange, gains and losses.

Keep accounts by what the money was spent on, and use a department field for who spent it. That means one salaries account, not separate sales, marketing and engineering salary accounts that must be recreated every time you reorganize.

Cost of revenue should include the costs required to deliver the service to customers. Typical inclusions are production hosting and infrastructure, third-party software embedded in the product, customer support, onboarding and implementation staff, payment processing fees and amortization of capitalized software, where it applies. Development and testing environments generally belong in R&D, and sales and marketing costs stay out.

The margin you calculate then matches how outsiders read it. Median gross margin for B2B SaaS was 81 percent on subscription revenue and 30 percent on services¹, so keeping services revenue and costs in separate accounts prevents a low-margin service line from hiding a healthy subscription margin. Median hosting spending runs 5 percent of ARR², which is a helpful reference when you review your production infrastructure costs.

Decide on the gray areas once, write the policy down and apply it consistently. Common gray areas are customer success, shared engineering on-call and data costs used by both product and internal analytics. If you split a cost, use a documented allocation such as headcount or usage.

Create a revenue account for each way you earn money that you want to measure: subscription, usage or overage, implementation and training, and other services. Do not create an account per customer or per product unless you truly report on them at that level, and use tags for those.

On the liability side, a deferred revenue account holds billings you have collected or invoiced for service not yet delivered. Add a contract asset or unbilled receivable account if you recognize revenue before you invoice. That is common with multi-year contracts and usage true-ups.

The mechanics of how amounts move between these accounts follow the revenue recognition standard, ASC 606, so ask your accountant to confirm the schedule before you build the accounts. If your chart of accounts also feeds a driver-based forecast, a SaaS financial model will map more easily when revenue lines match how you report.

Use dimensions to answer questions that would otherwise require new accounts:

• Department: sales, marketing, engineering, support, finance and administration. This turns one salaries account into a functional expense view.
• Product or business line: separates revenue and costs for distinct offerings.
• Location or entity: needed once you have subsidiaries or regional reporting.
• Project or customer: only where you need to track profitability or capitalized development.

The rule is to add a dimension when you need a repeating view, and an account when the statement line itself differs. A larger ledger handles many dimensions cleanly, while entry-level tools may limit them. The accounting system comparison and a guide to accounting systems for B2B SaaS can help you pick.

Restructure when the chart no longer answers basic questions: gross margin is unreliable, departments cannot be reported without manual work, or an audit or diligence request exposes inconsistent mapping. Doing it before a financing or audit is easier than during one.

Follow a safe process:

1. Draft the new chart and map every old account to a new one.
2. Do not delete accounts with history. Mark them inactive after mapping.
3. Restate prior periods in your reporting to the new structure so trends remain comparable.
4. Test the new mapping on one closed month before switching.
5. Update recurring entries, integrations and payroll mappings.
6. Document the change and the date.

Close software helps keep reconciliations aligned to account ranges, and the close software comparison covers options.