Resources

SaaS accounting

SaaS Chart of Accounts Template

A practical SaaS-ready chart of accounts structure for organizing revenue, COGS, payroll, cloud costs, sales, marketing, R&D, G&A, and AI compute costs.

In this article

Direct answer: A SaaS chart of accounts should organize transactions so founders can understand revenue, gross margin, payroll, cloud costs, sales efficiency, R&D spend, runway, and investor reporting. It is usually the first step toward a cleaner SaaS accounting foundation.

Who this template is for

This template is for SaaS and AI founders who have outgrown a generic bookkeeping setup and need their accounting structure to support real operating decisions.

  • You cannot easily separate recurring revenue from services, setup fees, or usage revenue
  • Hosting, cloud, support, or implementation costs are buried in generic expense accounts
  • Your gross margin is hard to calculate or explain
  • Your board or investors are asking for cleaner reporting
  • You are preparing for fundraising or diligence
  • You are hiring a controller, fractional CFO, or new accounting provider
  • Your AI or compute costs are becoming material and need better visibility

SaaS chart of accounts template

Use this as a starting structure. The exact account names and numbering will depend on your accounting system, revenue model, and stage, but the goal is to make revenue, gross margin, operating expenses, runway, and investor reporting easier to understand.

4000 to 4999

Revenue

  • Subscription revenue
  • Usage-based revenue
  • Implementation or setup fees
  • Professional services revenue
  • Other revenue

Why it matters: Separates recurring ARR/MRR revenue from non-recurring or services revenue.

4900 to 4999

Contra-revenue

  • Discounts
  • Credits
  • Refunds
  • Service credits

Why it matters: Helps show true net revenue and explains the gap between list price, billings, and recognized revenue.

2000 to 2999

Deferred revenue and liabilities

  • Deferred subscription revenue
  • Deferred setup fees
  • Sales tax payable
  • Payroll liabilities
  • Loan or credit facility balances

Why it matters: Supports accrual accounting, clean balance sheet reporting, and investor diligence.

5000 to 5999

COGS

  • Cloud hosting
  • Infrastructure
  • Customer support
  • Implementation delivery
  • Payment processing fees
  • Third-party software used to deliver the product

Why it matters: Makes SaaS gross margin visible and separates cost of delivery from operating expenses.

5100 to 5199

AI and compute costs, if applicable

  • Model API costs
  • Inference costs
  • Training costs
  • GPU or specialized cloud compute
  • Vector database costs
  • AI infrastructure tooling

Why it matters: Helps AI companies understand usage-driven costs, margin pressure, and scalability.

6000 to 6999

Sales and marketing

  • Sales salaries
  • Sales commissions
  • Paid ads
  • Marketing tools
  • Events
  • Content and demand generation
  • Partnerships

Why it matters: Supports CAC, sales efficiency, payback analysis, and growth investment decisions.

7000 to 7999

R&D and product

  • Engineering payroll
  • Product payroll
  • Product design
  • Developer tools
  • Product contractors
  • Capitalized development, if applicable
  • Research and experimentation

Why it matters: Shows product investment clearly and supports R&D tracking, budgeting, and investor reporting.

8000 to 8999

G&A

  • Finance and accounting
  • Legal
  • Insurance
  • HR and recruiting
  • Admin software
  • Office costs
  • Professional fees

Why it matters: Keeps overhead visible and separates operating support costs from growth and product spend.

9000+

Other income and expenses

  • Interest income
  • Interest expense
  • Foreign exchange gains and losses
  • One-time expenses
  • Non-operating income or expense

Why it matters: Keeps unusual or non-operating items from distorting core operating performance.

SaaS-specific accounts generic templates often miss

A generic small-business chart of accounts may be fine at the beginning, but it usually breaks down when SaaS reporting becomes more important.

  • Subscription revenue
  • Usage-based revenue
  • Implementation or setup fees
  • Deferred revenue
  • Customer credits and refunds
  • Cloud hosting and infrastructure
  • Customer support and success costs
  • Implementation delivery costs
  • Sales commissions
  • Payment processing fees
  • R&D and product development costs
  • Capitalized development, if applicable
  • AI compute, inference, training, and model API costs

Weak setup vs SaaS-ready setup

Weak setup

  • All revenue booked into one account
  • Services, setup fees, and usage revenue mixed with subscription revenue
  • Hosting costs buried in software expenses
  • Support and implementation costs mixed into payroll
  • No deferred revenue tracking
  • No separation between sales, marketing, R&D, and G&A
  • AI compute costs hidden inside generic cloud costs
  • Board reporting requires manual cleanup every month

SaaS-ready setup

  • Recurring, usage, services, and setup revenue separated
  • Deferred revenue tracked clearly
  • COGS separated from operating expenses
  • Hosting, support, implementation, and payment processing visible
  • Sales and marketing spend supports CAC analysis
  • R&D and product spend are tracked clearly
  • AI compute costs are visible where relevant
  • Reporting supports gross margin, runway, board reporting, and diligence

When to change your chart of accounts

You do not need a complex accounting structure on day one. But the chart of accounts should evolve before reporting becomes painful.

  • You are preparing for a fundraise
  • You cannot calculate SaaS gross margin cleanly
  • ARR, MRR, and accounting revenue are hard to reconcile
  • Your board is asking for better reporting
  • You are switching accountants or accounting systems
  • You are hiring a controller or fractional CFO
  • Hosting, support, or AI compute costs are becoming material
  • Month-end close requires too many manual adjustments
  • Investor diligence would require last-minute cleanup

Need a cleaner SaaS accounting foundation?

Offset Partners helps SaaS and AI founders turn messy books into a finance structure that supports revenue reporting, gross margin, runway, board reporting, and investor diligence.

Book a SaaS finance diagnostic

Why it matters

If the chart of accounts is too generic, founders cannot easily connect the books to operating decisions. Revenue quality, gross margin, CAC, R&D investment, cloud costs, AI compute costs, burn, and runway become harder to explain.

The goal is not more categories for the sake of complexity. The goal is better decision-making, cleaner monthly reporting, and a finance foundation that can support board updates, fundraising, and diligence.

If your chart of accounts is already messy, controller services for SaaS companies can help turn the template into a repeatable monthly close process instead of a one-time cleanup.

FAQs

Why does a SaaS company need a specific chart of accounts?

A SaaS company needs a chart of accounts that separates recurring revenue, usage revenue, services, COGS, hosting, support, sales, marketing, R&D, G&A, and other key categories. Without that structure, gross margin, CAC, runway, and board reporting become harder to explain.

Can a SaaS company use a generic bookkeeping chart of accounts?

It can at the earliest stage, but a generic setup usually becomes limiting once the company needs SaaS metrics, board reporting, fundraising support, or investor diligence.

Should hosting costs be included in COGS?

For most SaaS companies, hosting and cloud infrastructure costs should be tracked in COGS because they are part of delivering the product. This helps management understand gross margin.

Where should customer success costs go?

It depends on the role. Support or implementation work directly tied to service delivery may belong in COGS, while account management, renewals, expansion, and commercial customer success may be tracked in sales and marketing. The important point is to define the treatment consistently.

Should AI compute costs be tracked separately?

Yes, if they are material. AI compute, inference, training, model API, and specialized cloud costs can materially affect gross margin and should not be hidden in a generic software or hosting account.

When should we rebuild our chart of accounts?

Rebuild it before a fundraise, before switching accounting providers, before hiring a controller, or when gross margin, ARR, runway, or board reporting become difficult to explain from the current books.