Suggested: SaaS finance leader reviewing bookings, billings, and revenue dashboards on a laptop.
–>
SaaS Insight
Bookings, Billings, Revenue, and Cash Are Not the Same
Why SaaS finance leaders need to define, track, and reconcile all four — and what happens when two get treated as interchangeable
Bookings, billings, revenue, and cash measure four different things in a SaaS business, each on its own timeline. Treating any two as interchangeable — most often billings-as-revenue or cash-as-runway — overstates momentum, understates risk, and produces cash surprises that surface only once they’re expensive to fix.
A $120,000 annual contract, signed and paid upfront, can be described four ways in the same week: a $120,000 booking, a $120,000 billing, $10,000 of recognized revenue, and $120,000 of cash in the bank. All four numbers are correct — none is a substitute for the others.
The confusion is easy to fall into because all four numbers trace back to the same contract and often move in the same direction. That’s exactly what makes it dangerous: a board deck, an investor update, or an internal forecast can look internally consistent while actually blending four different measurements into one misleading story.
1. What Each Term Actually Measures
Four numbers, four different questions:
- Bookings — the total value of a contract when it’s signed. Answers “how much did we sell,” and can span multiple years in one number.
- Billings — the value of invoices actually sent to the customer. Answers “how much have we asked to be paid.”
- Revenue — the amount earned under ASC 606, recognized ratably as the service is delivered. Answers “how much have we actually earned so far.”
- Cash — what’s actually in the bank. Answers “what can we spend right now” — and says nothing on its own about what’s already been promised to customers or owed to deliver.
2. Why Bookings Overstate Momentum
A multi-year contract signed today is real and worth celebrating — but it isn’t revenue today, and it isn’t even cash today unless it was paid upfront. Bookings reflect intent and commitment, not delivery.
A sales team that hits its bookings target with mostly three-year deals has produced a very different result than one with mostly one-year deals — even if the headline number looks identical.
3. Why Billings Aren’t Revenue
This is the mismatch that trips up the most SaaS companies, because ASC 606 requires revenue to be recognized ratably over the service period, not when the invoice is sent or paid:
- The invoice isn’t the earning event. Billing a customer $120,000 for a one-year subscription doesn’t create $120,000 of revenue that day.
- Revenue is recognized as the service is delivered. That $120,000 contract produces roughly $10,000 of recognized revenue per month across the year — not a lump sum.
- The unearned portion becomes a liability. Cash collected for service not yet delivered sits in deferred revenue on the balance sheet until it’s earned.
A $120,000 annual subscription collected in January produces about $10,000 per month of recognized revenue under ASC 606 — not $120,000 of Q1 revenue. Booking it as a lump sum is one of the most common mistakes that trigger restatements and audit findings.
4. Why Cash Isn’t Runway
Cash from annual prepayments makes a company look more liquid than it actually is, and the gap only shows up once growth slows:
- Deferred revenue inflates the cash picture. Cash lands before the revenue is recognized, so the balance sheet looks stronger than the income statement suggests.
- The illusion depends on continued growth. As long as new annual contracts keep signing, fresh cash keeps replacing what’s unwinding into recognized revenue.
- The unwind is the risk. Once new bookings slow, deferred revenue starts converting to recognized revenue faster than new cash replaces it — and the cash position that looked healthy starts shrinking.
A large deferred revenue balance improves liquidity today, but it doesn’t reduce the operating costs still owed on those contracts. Runway based on cash-in-bank alone, without netting out what’s owed customers, overstates available time.
5. What Happens When You Conflate Them
The consequences aren’t abstract — they show up in specific, expensive ways:
- Audit findings and restatements. Recognizing billed or booked amounts as revenue before it’s earned is one of the most common issues auditors flag in SaaS financials.
- Fundraising delays. Investors doing diligence will recompute revenue from the contract terms; a mismatch between reported and recomputed revenue slows or kills a round.
- Runway miscalculation. Treating cash-in-bank as available runway, without netting out deferred revenue obligations, leads to spending plans the business can’t actually sustain.
- Board and investor confusion. Different numbers presented as if they answer the same question erode confidence in the finance function generally, not just in that one metric.
- Compounding errors at scale. A definitional mismatch that’s manageable at $1M in bookings becomes a much larger reconciliation problem once a company is signing hundreds of contracts a year.
The Four Metrics at a Glance
| Metric | What It Measures | Recognized When | Risk If Mistaken for Another |
|---|---|---|---|
| Bookings | Total contract value signed | At signature | Overstates near-term growth |
| Billings | Invoices sent to customer | When invoiced | Overstates earned revenue |
| Revenue | Value earned under ASC 606 | As service is delivered | Misstates financial performance |
| Cash | What’s actually in the bank | When received | Overstates available runway |
Bottom Line
None of these four numbers is wrong — they just answer different questions. Bookings show sales momentum, billings show what’s been asked for, revenue shows what’s been earned, and cash shows what’s spendable right now.
Tracking and reconciling all four — not picking whichever looks best in a board deck — is what keeps growth numbers, financial statements, and runway estimates honest.
How PNJ Can Help
PNJ helps SaaS companies build the revenue recognition discipline, deferred revenue tracking, and reporting structure that keeps bookings, billings, revenue, and cash distinct — and reconciled — from the first annual contract through an audit or a raise.
Sources and Professional Notes
- Wall Street Prep, “Bookings vs. Billings | SaaS Formula + Calculator.”
- NetSuite, “What Are Bookings, Billings and Revenue? SaaS Revenue Recognition Models.”
- Beancount.io, “ASC 606 for SaaS Startups: The Five-Step Model, Deferred Revenue, and the Mistakes That Sink Audits,” 2026.
- G Squared CFO, “Deferred Revenue and Cash Flow: Understanding the Timing Gap in SaaS.”
- Fiscallion, “Deferred revenue in SaaS: accounting, cash flow, and FP&A implications explained.”
Disclaimer
This material is for general informational purposes only and does not constitute accounting, tax, or legal advice. Revenue recognition treatment under ASC 606 depends on an entity’s specific contracts and facts. This article is a general summary and is not a substitute for reviewing ASC 606 directly or obtaining advice based on specific circumstances. Consult qualified advisers before changing revenue recognition or reporting practices.