ASC 606 SaaS Revenue Recognition
What is ASC 606 for SaaS?
ASC 606 is the US GAAP standard governing how revenue is recognized. It applies across industries, and it applies to SaaS in a way that has two specific consequences worth understanding together, because they are usually taught apart.
On the revenue side: subscription revenue is recognized as the service is delivered, not when the contract is signed and not when the cash arrives. A customer who pays $120,000 upfront for a twelve-month subscription does not produce $120,000 of revenue in month one. They produce $10,000 a month for twelve months, and the rest sits as deferred revenue.
On the cost side: the commission paid to win that contract is a cost to obtain a contract, and it generally has to be capitalized and amortized rather than expensed at signature.
Those two rules are the same idea applied to both halves of the transaction: recognize the revenue as you deliver it, and recognize the cost of getting it across the same window. Match the cost to the revenue it produced.
The five-step model
ASC 606 prescribes a five-step approach to recognizing revenue. Applied to a typical SaaS contract:
StepWhat it meansIn SaaS1. Identify the contractEstablish there is an enforceable agreement.The signed subscription order form.2. Identify performance obligationsWork out what distinct things you promised.The subscription itself; implementation and support may or may not be distinct.3. Determine the transaction priceEstablish what you expect to be entitled to.Complicated by discounts, ramps, usage tiers, and variable fees.4. Allocate the price to the obligationsSplit the price across what you promised.A bundled implementation fee may need allocating out of the subscription.5. Recognize revenue as obligations are satisfiedRecognize as you deliver, not as you invoice.Ratably across the subscription term, in most cases.
Step two is where SaaS gets genuinely difficult. If implementation is a distinct performance obligation, its revenue is recognized separately as it is delivered. If it is not distinct, it is bundled into the subscription and recognized across the term. That single judgment can move a large amount of revenue between periods, and reasonable people disagree about it.
Why it matters for commission
The connection that most SaaS finance teams meet the hard way: ASC 606 is a revenue standard that ended up reshaping commission accounting.
If revenue on a three-year contract is recognized across three years, then expensing the entire commission at signature would put the full cost of acquisition into a period carrying only a fraction of the revenue. That is the opposite of matching. So the commission is capitalized and amortized across the expected benefit period instead, and the two lines move together.
This is why a standard about revenue recognition ends up dictating the granularity of your commission data. To amortize commission per contract, you must know commission per contract. See commission expense recognition.
What this means?
For a SaaS CFO, ASC 606 is the reason bookings, revenue, and cash are three different numbers that are all correct at the same time. A $120,000 annual contract signed in January is $120,000 of bookings, possibly $120,000 of cash, and $10,000 of revenue in that month. Explaining that distinction to a board, and to a sales team, is a recurring task.
It also has a direct comp-design implication that is worth surfacing: bookings versus collections determines when a rep gets paid, and ASC 606 determines when the company recognizes both the revenue and the commission cost. Those are three separate clocks on the same deal, and a plan that has not thought about how they interact will produce surprises in all three.
This page explains general accounting concepts and is not accounting or tax advice. Treatment depends on your facts, your jurisdiction, and your auditor. Confirm with a qualified professional.
How Visdum fits
Visdum does not recognize revenue; that is your accounting system's job. What it supplies is the commission data that ASC 606 compliance depends on.
Commission is calculated per deal, so the amount attributable to a specific contract can be capitalized and amortized against that contract rather than allocated from a payroll total. Plans can be modeled on bookings or on collections, so what triggers a rep's payment is a deliberate design choice rather than an accident. And because every figure traces back through the audit trail to the deals behind it, the commission side of a 606 position rests on evidence rather than estimate.
Take a self-guided product tour to see this in action, or read the complete commission close playbook.
Related terms
ASC 606 · ASC 605 vs ASC 606 · Capitalized Commissions · Revenue Recognition · Bookings vs Collections
Calculate your OTE in 30 seconds
Frequently asked questions
What is ASC 606 for SaaS companies?
ASC 606 is the US GAAP standard governing revenue recognition. For SaaS it means subscription revenue is recognized as the service is delivered rather than when the contract is signed or the cash arrives. It also requires commission paid to win the contract to be capitalized and amortized rather than expensed at signature.
What are the five steps of ASC 606?
Identify the contract, identify the distinct performance obligations, determine the transaction price, allocate that price across the obligations, and recognize revenue as each obligation is satisfied. Step two is the hardest in SaaS, because whether implementation is a distinct obligation can move a large amount of revenue between periods.
How does ASC 606 affect sales commission?
It requires commission that is an incremental cost of obtaining a contract to be capitalized and amortized over the expected benefit period, rather than expensed when paid. If revenue on a three-year contract is spread over three years, expensing the whole commission at signature would break the matching the standard exists to enforce.
When is SaaS revenue recognized under ASC 606?
As the service is delivered, rather than when the contract is signed or the cash arrives. A customer paying $120,000 upfront for a twelve-month subscription does not generate $120,000 of revenue in month one. They generate roughly $10,000 a month across the term, with the remainder sitting as deferred revenue until it is earned.
Why are bookings, revenue, and cash all different numbers?
Because they measure different things and ASC 606 keeps them apart. A $120,000 annual contract signed in January is $120,000 of bookings, potentially $120,000 of cash, and only a month's worth of recognized revenue. All three figures can be correct simultaneously, which is a recurring explanation for any SaaS finance team.
Does ASC 606 change when reps get paid?
Not directly. When a rep is paid is set by the comp plan, typically on bookings or on collections. ASC 606 governs when the company recognizes the revenue and the commission cost. Those are three separate clocks on the same deal, and a plan that ignores how they interact will produce surprises in all three.