Honest, practitioner-built guide to SaaS accounting. ASC 606, deferred revenue, COA, metrics, and software comparison for bookkeepers, CPA firms, and founders.
A $4,127 annual SaaS contract gets signed on a Tuesday. The Stripe deposit hits the bank on Thursday for $3,847.92. Twelve months later, the P&L shows $4,127 of recognized revenue. But no single month shows the same number as the deposit. None of that is a mistake. It is what SaaS accounting looks like when you do it right. The mismatch is the timing gap between cash received and revenue earned. It is the thing that breaks naive SaaS bookkeeping inside the first year.
This hub is a practitioner's map for the people doing those books. It was written by a CPA firm partner who runs SaaS books on Growthy. He sees the same five mistakes on every cleanup engagement. The hub walks the parts that matter for three readers: a SaaS startup picking its first general ledger, an early-stage bookkeeper picking up a SaaS client, and a CPA firm staffer asked to review revenue recognition for the first time. Each section below covers the operator version of one big idea. Then it links forward to a deeper spoke when you need the full mechanics, journal entries, and edge cases.
Subscriptions break the cash-equals-revenue assumption every bookkeeper learns first. When a customer pays $1,200 in January for an annual subscription, only $100 is revenue that month. The other $1,100 sits on the balance sheet as a liability called deferred revenue. It moves to revenue one month at a time as the service is delivered. The default QBO setup treats that $1,200 deposit as January sales. That produces a P&L that looks great in month one and wrong every month after.
The mechanics matter because SaaS contracts come in three shapes. Each needs different handling. Month-to-month contracts recognize as billed. That is the simple case. Annual prepay contracts need a signing journal entry that parks the cash in deferred revenue. Then a monthly recognition entry moves $100 at a time. Multi-year prepay contracts add a current-versus-non-current split. The obligation beyond 12 months sits in a different balance-sheet line than the obligation inside the next year.
Five common breakages show up on almost every SaaS cleanup. Stripe deposits posted as gross revenue when the processor fee is sitting underneath. Mid-term upgrades treated as new sales when they are contract modifications. Downgrades with credit handled as refunds when they are forward credits. Free trials recognized as revenue at signup when there was no consideration received. Refunds netted into the wrong period. Each is fixable. None is obvious. The SaaS-ready chart of accounts is where most of these fixes get installed.
ASC 606 is the standard that tells SaaS companies when to recognize revenue. It is principle-based, not prescriptive. The standard is short. The application is everything. The principle is one sentence: recognize revenue when the customer gets the value, in the amount the company expects to receive for it. Everything else is how to apply that principle to a specific contract.
The five steps walk through every contract. Step one is identifying the contract. Under ASC 606, this includes click-through terms of service for most online SaaS. Step two is identifying the performance obligations. For a typical subscription, that is the continuous service itself. Sometimes it splits out for distinct implementation work. Step three is determining the transaction price. This includes variable consideration like usage charges and rebates. Step four is allocating that price across the performance obligations using standalone selling prices. Step five is recognizing as each obligation is satisfied. For SaaS subscriptions, that almost always means ratable monthly recognition.
Most operator mistakes happen at step five, not step one. Treating billings as revenue. Treating annual prepay as cash-day recognition. Missing the performance-obligation split when implementation services are bundled with the subscription. The ASC 606 five-step model spoke walks each step with a single B2B SaaS contract as the running example. It includes the journal entries from signing through month twelve. Bobby is a CPA firm partner, not a CPA. So the spoke uses plain-language interpretation, not GAAP citation.
Deferred revenue is the workhorse of a SaaS balance sheet. It is the obligation the company owes a customer who has paid for service not yet delivered. Under ASC 606, the technical name is contract liability. On a typical SaaS balance sheet it shows up in two lines. First, deferred revenue current, for obligations expected to be recognized within twelve months. Second, deferred revenue non-current, for everything beyond.
The signing journal entry moves cash into the liability. For an annual prepay contract, the entry is debit cash $1,200, credit deferred revenue current $1,200. For a three-year prepay, the entry splits: debit cash $30,000, credit deferred revenue current $10,000, credit deferred revenue non-current $20,000. The monthly recognition entry then moves the right amount each month: debit deferred revenue current $1,000, credit revenue $1,000. Same pattern every month, for every contract, for as long as the contract runs.
Contract assets are the mirror image. They are used when work is delivered before billing. Most SaaS companies do not see them until they sign their first contract with milestone billing or annual-pay-after-quarterly-delivery terms. The reconciliation that matters is the deferred-revenue rollforward. It ties beginning balance plus new bookings minus recognized revenue plus adjustments to the ending balance. When the rollforward does not tie, the gap is almost always a missed cancellation, a misclassified upgrade, or a processor-fee netting error. The deferred revenue spoke walks the JE patterns and the rollforward in full.
The default QBO chart of accounts is not wrong for SaaS. It is incomplete. A generic small-business COA has about fifty accounts. They cover cash, AR, AP, owner's equity, sales, and ordinary expenses. None of them capture the contract liabilities and capitalized costs that ASC 606 and ASC 340-40 require. Most SaaS startups outgrow the default setup inside the first year. Usually it happens when the first annual prepay contract signs.
The required additions are deferred revenue current, deferred revenue non-current, contract assets, and customer credit liability. Revenue should split into at least four sub-accounts: subscription revenue, professional services revenue, expansion revenue, and usage-based revenue. The split matters because expansion revenue is what feeds net revenue retention. Bundling it with new subscription revenue blinds the founder to where growth is actually coming from. COGS needs its own sub-accounts for hosting, payment processing, customer support, and third-party data fees. Each is a direct cost that scales with usage or revenue. Rolling them into general expenses produces a gross margin number that does not mean what most founders think it means.
Capitalized software development under ASC 350-40 is the line most founders blur with R&D expense. The standard says salaries during the application-development stage of software built for internal use can be capitalized. Pre-feasibility R&D plus post-implementation maintenance gets expensed. Capitalized commissions under ASC 340-40 add another account when sales commissions get amortized over the expected customer life. The SaaS chart of accounts spoke ships a 20-account starting template plus the additions to make at $500K and $5M ARR. The cross-cluster chart of accounts hub covers the general COA mechanics underneath.
Founders ask about MRR. Bookkeepers handle revenue. Both numbers are correct. They answer different questions. They do not tie to each other on the P&L. MRR is monthly recurring revenue, a forward-looking run-rate calculated from active subscription contracts. ARR is MRR times twelve, the same number annualized. Recognized revenue on the P&L is the GAAP number, ratable monthly recognition of what was actually delivered. They are three separate audiences with three separate measurement frames.
Bookings is the total contract value signed in a period. It can run far ahead of revenue when annual prepay contracts are common. Billings is the invoiced amount in a period. It can run ahead or behind revenue depending on billing cadence. A SaaS startup that signs a $12,000 annual contract in January has $12,000 of bookings, $12,000 of billings, $1,000 of MRR, and $1,000 of recognized revenue for the month. All four numbers are right. None tie to each other.
The bookkeeper question is always how to produce the metrics view from QBO or Xero without buying a separate revrec tool. The answer is contract-level tracking. Usually it is a spreadsheet sub-ledger that lives alongside the GL. MRR comes from the active-contracts list. Bookings comes from the contract sign-date field. Billings comes from invoice dates. Net revenue retention is the metric that hides churn behind expansion in a single number. It needs cohort tracking that is hard to do well in a spreadsheet at scale. The SaaS metrics spoke walks the math. It also shows the one-page metrics view bookkeepers use to answer founder questions without confusing the issue.
General-ledger software handles SaaS bookkeeping fine for a while. QuickBooks Online and Xero can produce a correct SaaS P&L through manual journal entries, a clearing-account method for Stripe, and a spreadsheet sub-ledger for contract tracking. The pressure point is usually between $500K and $1M ARR. That is when monthly close drags past five days, contract types diversify, and the founder asks the same MRR question every week. QBO Plus runs about $115 a month in 2026. Xero is in the $55 to $90 range.
Revenue-recognition layers sit on top of the general ledger when contract complexity exceeds what manual JEs can handle. Maxio, formerly SaaSOptics, is bookkeeper-shaped. It connects directly to QBO, Xero, or NetSuite. Chargebee bundles billing infrastructure with an ASC 606 module. It fits founders who want billing and recognition in one place. RecVue handles enterprise complexity, multi-currency, and audit-grade reporting. Stripe Billing Revenue Recognition is the native option for Stripe-billing-only setups. The limit is that it does not cover non-Stripe revenue or multi-currency consolidation. NetSuite is the graduation point for Series B and beyond. Total cost usually runs $30K to $100K per year.
Growthy sits in the matrix as a categorization layer plus a Mode 2 standalone GL. Today the product handles Stripe deposit reconciliation, processor-fee categorization, and multi-revenue-stream COGS at 85% accuracy on first import. ASC 606 multi-step automated recognition is on the roadmap, not in the product. SaaS books on Growthy use manual recognition JEs the same way QBO and Xero do. The dual-mode framing matters here. A SaaS founder picking a first GL can start on Growthy as the system of record. That skips the QBO-to-something-else migration that lands on most growing SaaS books inside three years. A bookkeeper or CPA firm with existing QBO clients can run Growthy in Mode 1 on top of the QBO data. They get the categorization lift without forcing a client migration. The honest comparison spoke walks all seven options with a decision matrix by ARR stage. The SaaS bookkeeping for founders spoke covers the year-one decision in more depth.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Chart of Accounts, AI Bookkeeping, Stripe Bookkeeping, Payment Reconciliation, 1099 Filing.
Free during alpha. Read-only access. You review every sync.
Request Early AccessTrace Stripe charges from gateway through bank deposit to recognized revenue. Clearing-account JEs, Stripe Billing RevRec vs GL-side recognition, and when to graduate to a dedicated tool.
Translate SaaS founder vocabulary (MRR, ARR, bookings, billings, NRR) into GAAP-shaped numbers. Why they don't tie to the P&L, and how to produce the metrics view from QBO or Xero.
Day-1 through end-of-year SaaS bookkeeping setup for founders. Chart of accounts, deferred revenue, Stripe, 1099s, and ASC 606 awareness without overengineering.
Practitioner comparison of 7 SaaS accounting options. QBO, Xero, Maxio, Chargebee, RecVue, Stripe Billing, and Growthy mapped to ARR stage and contract complexity.
Where deferred revenue lives on the SaaS balance sheet, the JE pattern on signing vs cash vs recognition, the monthly roll-forward, and what changes the balance in real-world contract churn.
SaaS chart of accounts template covering deferred revenue, capitalized commissions, COGS sub-accounts, and ASC 606/340-40/350-40 integration. 20-account starting point with $500K and $5M ARR additions.
ASC 606 revenue recognition for SaaS, explained in plain language. Walk the five-step model with a B2B contract, sample journal entries, and common mistakes.
Six SaaS contract patterns walked through with ASC 606 analysis, journal entries, and statement impacts. Monthly, annual prepay, multi-year, upgrades, downgrades.