SaaS Bookkeeping: Chart of Accounts, MRR Tracking, and Financial Reporting

A generic small-business chart of accounts breaks down the moment a SaaS company tries to use it for anything other than filing a tax return. It has one revenue account, one expense category for software, and no way to answer the two questions every SaaS founder gets asked in a board meeting: what’s the gross margin, and how many months of runway is left. Fixing that takes a chart of accounts built around three separations: subscription revenue from services revenue, cost of revenue from operating expenses, and cash received from revenue earned.

What does a SaaS chart of accounts need beyond generic?

The core problem with a stock QuickBooks or Xero chart of accounts is that it treats “revenue” as one number and “expenses” as a flat list. Neither tells you what a SaaS investor, board member, or your own CPA needs to see. The fix is a chart built around five groupings.

• Subscription revenue, split by plan tier if the product has more than one (Starter, Growth, Enterprise), so the P&L can show which tier is actually growing.
• Professional services revenue, kept entirely separate from subscription revenue. Implementation fees, custom integrations, and training are one-time or project-based, they carry a different margin profile, and mixing them into subscription revenue distorts every SaaS metric that depends on recurring revenue being actually recurring.
• Deferred revenue, a balance sheet liability, not a revenue account. Cash collected for a service not yet delivered is a liability until the service period passes, under ASC 606 revenue recognition rules. A SaaS company that books an annual prepay as revenue on the day it hits the bank account is overstating income and will eventually have to explain the correction to an investor doing diligence.
• Cost of revenue (COGS), isolated from operating expenses. This is the section most SaaS bookkeeping gets wrong, covered in detail below.
• Capitalized software costs, tracked separately from R&D expense. Costs of building internal-use software during the application development stage are capitalized under ASC 350-40 for books; the tax treatment is different again and is covered in the R&D section below.

A chart built this way answers “what’s our gross margin” and “what’s our runway” directly from the trial balance, instead of requiring someone to reconstruct both numbers in a spreadsheet every month.

How do you track MRR and ARR against the books?

Monthly recurring revenue and annual recurring revenue are metrics, not GAAP revenue, and they live in a metrics layer (a billing system like Stripe or Chargebee, or a dedicated tool like ChartMogul or Baremetrics) rather than in the general ledger itself. MRR counts a subscription’s normalized monthly value the moment the deal closes; GAAP revenue only recognizes revenue as the service is delivered over the contract term. An annual contract signed on day one shows up in MRR immediately at its full monthly-equivalent value, while the same contract’s recognized subscription revenue trickles in over twelve months from the deferred revenue account.

The two numbers are supposed to diverge, but they still need to reconcile to each other every month, and this is the step that gets skipped most often. The reconciliation has three parts:

• New, expansion, contraction, and churned MRR for the month should tie to new contracts signed, upsells, downgrades, and cancellations in the billing system.
• Ending MRR times twelve should be in the same neighborhood as the annualized run rate implied by the subscription revenue account, adjusted for the timing lag between signing and recognition.
• Deferred revenue rollforward (beginning balance, plus cash collected, minus revenue recognized, equals ending balance) should match the billing system’s own record of what’s been invoiced but not yet earned.

When these don’t tie out, the usual cause is a subscription that was upgraded or downgraded mid-term without a corresponding journal entry to the deferred revenue schedule, or a customer who paid annually but was set up in the accounting system on a monthly recognition schedule that doesn’t match the actual contract terms.

How do you separate COGS from operating expenses?

Cost of revenue for a SaaS company is every cost directly tied to delivering the product to a paying customer, not every cost related to the business existing. Getting this split right is what makes the gross margin number mean anything.

• Hosting and infrastructure. AWS, Azure, Google Cloud, and any third-party API or data provider the product depends on to function for customers. This is almost always the largest COGS line and the one worth tracking by customer cohort if usage-based pricing is part of the model.
• Payment processing fees. Stripe, Braintree, or bank processing fees on subscription charges are a direct cost of collecting revenue and belong in COGS, not in G&A.
• Customer success and support. Salaries for the team that onboards and supports paying customers are a cost of serving those customers, and belong in COGS. This is the line most commonly misclassified, usually because support sits organizationally under the same VP as sales and gets lumped into a general “people costs” bucket in the chart of accounts.
• Third-party software embedded in the product. A license fee for a component the product resells or depends on to function (an embedded analytics engine, a mapping API, an SMS provider) is COGS. A license fee for internal tools the team uses to build the product (project management software, an IDE license) is an operating expense.

Everything else splits into the standard operating expense categories: sales and marketing (including sales commissions, discussed in a companion article below), general and administrative (rent, legal, accounting, executive salaries), and research and development (engineering salaries not capitalized under the internal-use software rules, plus the tax treatment discussed next).

What gross margin is healthy for a SaaS company?

Gross margin	What it typically signals
80%+	Strong for a pure software product with low support burden; typical of self-serve, low-touch SaaS
70-80%	The general benchmark range for a healthy SaaS company at scale
60-70%	Common for earlier-stage or high-touch enterprise SaaS with heavier customer success costs
Below 60%	Usually a sign that support, hosting, or implementation costs are under-recovered by pricing, or that costs are misclassified into COGS that shouldn’t be there

These bands are industry benchmarks reported by SaaS-focused investors and research firms (Bessemer’s annual State of the Cloud reports and similar sources), not a legal or accounting standard, and they shift by business model. A usage-heavy product with expensive compute costs per customer (AI inference, video processing) will run lower even when healthy. The number is only useful once the COGS split above is done correctly; a company reporting 90% gross margin because support salaries are sitting in G&A isn’t actually more efficient, it’s just measuring the wrong thing.

How do you calculate burn rate and runway from the books?

Burn rate comes from the cash flow statement, not the income statement, because a company can be profitable on paper (deferred revenue collected in cash, recognized over time) while still burning cash, or unprofitable on paper while sitting on a large cash balance from a prepay-heavy customer base.

• Gross burn is total cash spent on operating expenses in a month, full stop, regardless of revenue.
• Net burn is gross burn minus cash collected from customers in the same month. Net burn is the number that determines runway.
• Runway is cash balance divided by average monthly net burn over a trailing period (typically the last three months, to smooth out lumpy annual-prepay collections).

Runway should be recalculated monthly, using trailing-average collections rather than the current month’s number alone, precisely because SaaS collections are lumpy: annual contracts, multi-year prepays, and one-time services invoices all create months that look artificially strong or weak.

What does a SaaS monthly close checklist look like?

A close that only reconciles the bank account and calls it done will miss the items that actually drive SaaS-specific reporting errors. A complete monthly close includes:

1. Bank and credit card reconciliations, standard for any business.
2. Deferred revenue rollforward, tied to the billing system’s record of invoiced-but-unearned amounts.
3. MRR movement reconciliation (new, expansion, contraction, churn) against contracts signed and cancelled in the period.
4. Sales commission accrual, matched to the revenue or bookings that triggered them under the company’s commission plan.
5. Review of capitalized software costs for the month, confirming costs booked to the capitalized asset account are actually application-development-stage costs under ASC 350-40, not preliminary-stage or post-implementation costs that should be expensed.
6. COGS allocation review, confirming hosting invoices and support payroll were coded to cost of revenue rather than operating expense accounts.
7. Gross margin and burn rate calculation, reviewed against the prior month and the annual plan.
8. Cap table and outstanding option pool review if a financing event, exercise, or new grant occurred in the period.

What should I do next?

If your chart of accounts doesn’t separate subscription revenue from services revenue, or COGS from operating expenses, that’s the first fix, and it’s a one-time setup project rather than an ongoing burden. If deferred revenue on the books doesn’t reconcile to the billing system, that gap compounds every month it goes unaddressed and it’s the item most likely to surface as a correction during a financing round’s diligence process.

• SaaS stock options and 409A valuations, how ISO and NSO grants are taxed and why a private SaaS company needs an independent valuation before issuing options
• SaaS multi-state tax nexus, where a SaaS company owes income tax once it has customers or remote employees in multiple states
• SaaS startup costs and burn rate before revenue, how pre-revenue costs are treated under IRC 195 and how to track burn before the first paying customer
• SaaS customer acquisition cost tax treatment, the book-tax difference between capitalized sales commissions and currently deductible marketing spend
• Franchise startup costs and the IRC 195 election, a parallel walkthrough of the startup-cost amortization mechanics for a different industry

This guide is general information, not tax advice for your specific situation. Which points apply, and how, depends on your facts.