ASC 606: The Essential SaaS Revenue Recognition Guide for Founders

ASC 606 is the account­ing stan­dard that decides when the cash a cus­tomer pays you actu­al­ly becomes rev­enue on your income state­ment — and for a SaaS com­pa­ny, the answer is almost nev­er “when the mon­ey hits the bank.” A cus­tomer can wire you $120,000 today for a year of soft­ware, and under ASC 606 you have earned exact­ly $0 of rev­enue at that moment. You earn it at rough­ly $10,000 a month as you deliv­er the ser­vice. Most founders at $5M to $15M ARR have a vague sense this is true and have nev­er been walked through why, how, or what it costs them when they get it wrong. This guide fix­es that.

I am writ­ing this for the tech­ni­cal founder build­ing toward an exit, not for an accoun­tant. You do not need to do ASC 606 — your con­troller or out­side CPA does that. You need to under­stand it well enough that it nev­er sur­pris­es you: when a board mem­ber asks why rec­og­nized rev­enue is half your book­ings, when a deferred-rev­enue bal­ance shows up as a lia­bil­i­ty on your bal­ance sheet, and — the moment it mat­ters most — when a buy­er’s accoun­tants tear into your rev­enue dur­ing due dili­gence and decide whether your report­ed growth is real. ASC 606 is where “we signed $2M in new deals this quar­ter” and “we rec­og­nized $600K of rev­enue this quar­ter” stop being a con­tra­dic­tion and start being two dif­fer­ent, both-cor­rect num­bers. If that gap has ever con­fused you, this is the arti­cle that clos­es it.

This is edu­ca­tion­al, not account­ing or legal advice. I am explain­ing how ASC 606 works so you can have an informed con­ver­sa­tion with your finance team and your buy­er’s, not so you can apply it your­self. ASC 606 (for­mal­ly FASB Account­ing Stan­dards Cod­i­fi­ca­tion Top­ic 606, Rev­enue from Con­tracts with Cus­tomers) is a reg­u­lat­ed stan­dard, and the cor­rect treat­ment depends entire­ly on the spe­cif­ic lan­guage in your con­tracts and your com­pa­ny’s cir­cum­stances. Engage a qual­i­fied CPA or audi­tor for your actu­al num­bers, and run any­thing mate­r­i­al past them before you act on it.

What ASC 606 Actually Is — and Where It Came From

Start with the name, because it tells you the scope. ASC stands for Account­ing Stan­dards Cod­i­fi­ca­tion — the orga­nized rule­book of U.S. Gen­er­al­ly Accept­ed Account­ing Prin­ci­ples (GAAP), the stan­dard account­ing lan­guage every audit­ed U.S. com­pa­ny speaks. 606 is the spe­cif­ic top­ic num­ber inside that rule­book that gov­erns rev­enue. Its full title is Rev­enue from Con­tracts with Cus­tomers, and that phrase is the whole idea in five words: rev­enue comes from deliv­er­ing on a con­tract, so the account­ing fol­lows the deliv­ery, not the pay­ment.

ASC 606 was issued by the Finan­cial Account­ing Stan­dards Board (FASB) — the inde­pen­dent body that writes U.S. account­ing rules — through Account­ing Stan­dards Update (ASU) 2014-09, released in May 2014. It was a joint project with the inter­na­tion­al stan­dard-set­ter, so there is a near-iden­ti­cal glob­al twin called IFRS 15 (Inter­na­tion­al Finan­cial Report­ing Stan­dards, stan­dard 15) that com­pa­nies out­side the U.S. use. If you ever sell to or merge with a com­pa­ny on inter­na­tion­al books, the two stan­dards share the same five-step back­bone, which is the point — they were built togeth­er so rev­enue means the same thing every­where.

The time­line mat­ters for one prac­ti­cal rea­son: ASC 606 is not option­al and not new. Pub­lic com­pa­nies adopt­ed it for fis­cal years start­ing after Decem­ber 15, 2017. Pri­vate com­pa­nies — which is you — were required to adopt it for annu­al report­ing peri­ods begin­ning after Decem­ber 15, 2018 (the dead­line was lat­er pushed one year, to peri­ods begin­ning after Decem­ber 15, 2019, for com­pa­nies that had not yet adopt­ed, under a sep­a­rate update). Either way, if your books are audit­ed or you are head­ing toward a sale, your finan­cials are expect­ed to be on ASC 606 already (the SEC’s Finan­cial Report­ing Man­u­al lays out these adop­tion dates and the IFRS 15 align­ment). A buy­er will assume it. If your rev­enue is still rec­og­nized the old way — or worse, rec­og­nized when cash arrives — that is a find­ing, and find­ings cost you.

Before ASC 606, rev­enue rules were a patch­work of indus­try-spe­cif­ic guid­ance (the pri­or stan­dard was ASC 605). The whole rea­son FASB replaced it was to cre­ate one prin­ci­ple-based mod­el that works the same for a soft­ware com­pa­ny, a man­u­fac­tur­er, and a con­struc­tion firm. For SaaS, that sin­gle mod­el is the five-step process this guide is built around.

Why ASC 606 Matters to You Specifically: The Exit Lens

Here is the fram­ing no gener­ic account­ing arti­cle will give you, and the rea­son this mat­ters more for you than for a CFO who just wants clean books. When you sell your com­pa­ny, the buy­er does not pay you for the cash that came in the door. They pay a mul­ti­ple of your recur­ring, rec­og­nized rev­enue — and ASC 606 is the stan­dard that defines what counts as rec­og­nized rev­enue and how pre­dictable it is.

Three things a buy­er cares about run straight through ASC 606:

1. Rev­enue qual­i­ty. A buy­er pays the high­est mul­ti­ples for rev­enue that is con­trac­tu­al, recur­ring, and rec­og­nized rat­ably (smooth­ly, over the ser­vice peri­od) rather than lumpy or front-loaded. ASC 606 is what forces the smooth­ing. A com­pa­ny that books a $1.2M three-year deal and cor­rect­ly rec­og­nizes it over 36 months looks like a steady, durable rev­enue stream. A com­pa­ny that rec­og­nized the whole $1.2M upfront looks like it had one good quar­ter and noth­ing since. Same con­tract, very dif­fer­ent sto­ry to a buy­er — and only one of them is ASC 606-com­pli­ant.
2. The book­ings-to-rev­enue bridge. Dur­ing dili­gence, a buy­er rec­on­ciles what you sold (book­ings) to what you rec­og­nized (rev­enue) to what you col­lect­ed (cash). If those three do not tie out clean­ly under ASC 606, every num­ber you have report­ed is sus­pect, and sus­pi­cion is what com­press­es a mul­ti­ple. Clean ASC 606 account­ing is part of what makes a com­pa­ny easy to buy.
3. Deferred rev­enue as an assumed oblig­a­tion. That $120,000 annu­al pre­pay­ment sits on your bal­ance sheet as deferred rev­enue — a lia­bil­i­ty, because you owe the cus­tomer a year of ser­vice they already paid for. When a buy­er acquires you, they inher­it that oblig­a­tion: they have to deliv­er the ser­vice with­out col­lect­ing the cash, because you already spent it. Buy­ers know this and adjust the deal for it. If you do not under­stand your deferred rev­enue, you will be blind­sided at the nego­ti­at­ing table.

The through-line of how the best founders think is that you are not sell­ing the busi­ness you have today — you are sell­ing a pre­dictable, low-risk engine the buy­er can run for years. Risk is the gap between your Excel mod­el and real­i­ty, and slop­py rev­enue recog­ni­tion is one of the most com­mon places that gap hides. ASC 606 done right is a qui­et form of de-risk­ing. Done wrong, it is a land­mine you step on at the worst pos­si­ble moment. This is exact­ly the kind of finan­cial hygiene that belongs in any seri­ous SaaS exit strat­e­gy, and it is square­ly the job of a SaaS CFO — if you do not have one yet, ASC 606 com­plex­i­ty is one of the sig­nals you are close to need­ing one.

Bookings vs. Billings vs. Recognized Revenue vs. ARR

You can­not under­stand ASC 606 until four words stop blur­ring togeth­er. Founders use these inter­change­ably in board meet­ings and then won­der why their finance lead winces. Each mea­sures a dif­fer­ent thing, at a dif­fer­ent moment, and ASC 606 gov­erns only one of them. Here is the crisp ver­sion.

Term	What it measures	When it is counted	Where it lives	Governed by ASC 606?
Bookings	The total value a customer has committed to in a signed contract	When the contract is signed	A sales metric — not on the financial statements	No
Billings	The amount you have invoiced the customer so far	When you send the invoice	Drives accounts receivable and cash	No (billing terms are a business choice)
Recognized Revenue	The portion of the service you have actually delivered	Ratably, as you deliver the service	The income statement (P&L)	Yes — this is what ASC 606 governs
ARR	Your annualized recurring revenue run-rate at a point in time	A snapshot, anytime	An operating metric, not a GAAP figure	No (but built from recognized recurring revenue)

Walk through one deal to see all four at once. A cus­tomer signs a 2‑year con­tract for your soft­ware at $60,000 per year, paid annu­al­ly in advance.

• Book­ings the day they sign: $120,000 — the full two-year com­mit­ted val­ue (this is also the Total Con­tract Val­ue, or TCV). If you want the deep­er dis­tinc­tion here, see the dif­fer­ence between book­ings and rev­enue and what TCV is.
• Billings in year one: $60,000 — you invoice the first annu­al peri­od now; you will invoice the sec­ond $60,000 a year from now.
• Rec­og­nized rev­enue in the first month: $5,000 — one month of a $60,000 annu­al ser­vice ($60,000 / 12). ASC 606 says you have earned exact­ly that much by deliv­er­ing one month.
• ARR the day they sign: $60,000 — the annu­al­ized recur­ring run-rate from this cus­tomer.

Four dif­fer­ent num­bers — $120,000, $60,000, $5,000, $60,000 — all from the same sin­gle deal, all cor­rect, all answer­ing dif­fer­ent ques­tions. Founders get con­fused because they reach for “book­ings” when a buy­er or board wants “rec­og­nized rev­enue,” and on a mul­ti-year deal the two diverge sharply — here, $120,000 of book­ings ver­sus $60,000 of rec­og­nized rev­enue in the first year, a 2x gap that widens with the con­tract length. ASC 606 is the rule­book that pins down the $5,000-a-month num­ber specif­i­cal­ly. Every­thing else in this guide is about how that num­ber gets cal­cu­lat­ed when the con­tract is more com­pli­cat­ed than one clean sub­scrip­tion. The rela­tion­ship between the run-rate and the GAAP fig­ure is worth under­stand­ing on its own; I have writ­ten the full break­down of ARR vs. rev­enue and how annu­al recur­ring rev­enue dif­fers from rev­enue.

A note on a com­mon trap: ARR is an oper­at­ing met­ric, not a GAAP num­ber, and ASC 606 does not define it. That is not a loop­hole — it means you have to be dis­ci­plined about what you put in your ARR. Count­ing a one-time set­up fee or a can­cellable pilot as “ARR” inflates a num­ber a buy­er will recom­pute and dis­count. Keep ARR to gen­uine­ly recur­ring, con­tract­ed rev­enue; the mean­ing of ARR vs. rev­enue and what ARR actu­al­ly is are worth get­ting pre­cise about before a dili­gence process, not dur­ing one.

The ASC 606 Five-Step Model

The entire stan­dard reduces to a five-step deci­sion process the stan­dard calls the five-step mod­el. Your accoun­tant runs every cus­tomer con­tract through these five steps to decide how much rev­enue to rec­og­nize and when. You should under­stand each step well enough to know where the judg­ment calls — and the audit risk — live.

Here is each step in plain Eng­lish, with the SaaS-spe­cif­ic judg­ment calls flagged.

Step 1: Identify the Contract

A con­tract is an agree­ment that cre­ates enforce­able rights and oblig­a­tions. Under ASC 606 it does not have to be a signed paper doc­u­ment — it can be a click-through, an oral agree­ment, or one implied by your nor­mal busi­ness prac­tice — but it does have to clear a bar: both par­ties have approved it and are com­mit­ted, the rights and pay­ment terms are iden­ti­fi­able, it has com­mer­cial sub­stance, and it is prob­a­ble you will actu­al­ly col­lect what you are owed.

That last con­di­tion — the col­lectibil­i­ty thresh­old — is the SaaS gotcha. If a cus­tomer’s abil­i­ty to pay is gen­uine­ly shaky, you may not have a con­tract for account­ing pur­pos­es yet, even though sales is cel­e­brat­ing the win. The oth­er trap is the can­cellable con­tract: if your “annu­al” deal lets the cus­tomer walk after 30 days with no penal­ty, the enforce­able term for account­ing is clos­er to that 30-day out than the year on the order form. That dis­tinc­tion qui­et­ly shrinks how much you can treat as com­mit­ted — and it is exact­ly the kind of thing a buy­er’s dili­gence team checks line by line.

Step 2: Identify the Performance Obligations

A per­for­mance oblig­a­tion is a dis­tinct promise inside the con­tract — a spe­cif­ic thing you have com­mit­ted to deliv­er. The ques­tion ASC 606 forces is: how many sep­a­rate promis­es did you actu­al­ly make? Each dis­tinct one gets account­ed for on its own.

For a pure-sub­scrip­tion prod­uct, this is easy: the promise is “access to the soft­ware for the term,” one per­for­mance oblig­a­tion, rec­og­nized smooth­ly over time. It gets inter­est­ing when you bun­dle. Sell a SaaS sub­scrip­tion plus a one-time onboarding/implementation ser­vice plus pre­mi­um sup­port, and you may have three per­for­mance oblig­a­tions — each poten­tial­ly rec­og­nized on its own sched­ule. A promise is “dis­tinct” if the cus­tomer can ben­e­fit from it on its own and it is sep­a­rate­ly iden­ti­fi­able from the oth­er promis­es. Get­ting this count right is the hinge the next two steps swing on, and it is where com­pa­nies most often need an out­side accoun­tant to make a defen­si­ble call.

Step 3: Determine the Transaction Price

The trans­ac­tion price is the total con­sid­er­a­tion you expect to be enti­tled to for deliv­er­ing every­thing in the con­tract — the real eco­nom­ic price, not nec­es­sar­i­ly the list price. For a clean sub­scrip­tion it is just the con­tract val­ue. The com­pli­ca­tions, all com­mon in SaaS, are:

• Vari­able con­sid­er­a­tion — amounts that are not fixed, like usage-based over­age fees, tiered pric­ing, or per­for­mance bonus­es. ASC 606 makes you esti­mate this vari­able amount up front (using either the most-like­ly-out­come or a prob­a­bil­i­ty-weight­ed expect­ed val­ue) and only include it to the extent it is high­ly prob­a­ble it will not reverse lat­er.
• Dis­counts and cred­its — a pro­mo dis­count or ser­vice cred­its reduce the trans­ac­tion price.
• Refunds and mon­ey-back guar­an­tees — expect­ed refunds come out of the trans­ac­tion price.

Note what is not in here: the cus­tomer’s cred­it­wor­thi­ness was already han­dled in Step 1, and sales tax you col­lect on the gov­ern­men­t’s behalf is exclud­ed. The trans­ac­tion price is what you get to keep for what you deliv­er.

Step 4: Allocate the Transaction Price

If you iden­ti­fied more than one per­for­mance oblig­a­tion in Step 2, Step 4 splits the total trans­ac­tion price among them — and the rule is that you allo­cate based on each oblig­a­tion’s stand­alone sell­ing price (SSP): what you would charge for that item if you sold it by itself.

This is where bundling and dis­count­ing col­lide. Say you sell a bun­dle for $100,000 that includes a sub­scrip­tion with an SSP of $90,000 and an imple­men­ta­tion ser­vice with an SSP of $30,000. The stand­alone prices total $120,000, but the cus­tomer paid $100,000 — a $20,000 bun­dle dis­count. ASC 606 makes you spread that dis­count pro­por­tion­al­ly across both oblig­a­tions based on their rel­a­tive SSPs, not dump it all on whichev­er one is con­ve­nient. So the sub­scrip­tion is allo­cat­ed 90/120 of the $100,000 and imple­men­ta­tion gets 30/120. When you do not have a clean stand­alone price for some­thing (com­mon for a bespoke imple­men­ta­tion), the stan­dard lets you esti­mate the SSP — but the esti­mate has to be defen­si­ble, which again is where your accoun­tant earns their fee.

Step 5: Recognize Revenue as Obligations Are Satisfied

Final­ly, you rec­og­nize rev­enue for each per­for­mance oblig­a­tion as you sat­is­fy it — as con­trol of the ser­vice trans­fers to the cus­tomer. ASC 606 splits this into two pat­terns:

• Over time — when the cus­tomer con­sumes the ben­e­fit con­tin­u­ous­ly, which is the typ­i­cal SaaS sub­scrip­tion. You rec­og­nize rat­ably across the ser­vice peri­od (usu­al­ly even­ly, month by month).
• At a point in time — when con­trol trans­fers at a sin­gle moment, like a one-time set­up task that is done and deliv­ered, or a per­pet­u­al license hand­ed over.

For most of your recur­ring rev­enue, Step 5 means “spread it even­ly over the term,” which is why a $60,000 annu­al sub­scrip­tion becomes $5,000 of rec­og­nized rev­enue each month. The set­up fee or the one-time piece may land dif­fer­ent­ly, which is the whole rea­son the pre­vi­ous four steps exist. This idea — that the nature of the rev­enue deter­mines how and when it hits the P&L — is the foun­da­tion of the entire SaaS rev­enue mod­el and what sep­a­rates durable SaaS rev­enue from one-time sales dressed up to look recur­ring.

A Full Worked Example: A $1.35M Multi-Element Deal

Abstract steps do not stick. Here is a real­is­tic deal for a com­pa­ny in your range, run all the way through ASC 606 so you can see the num­bers move.

A mid-mar­ket cus­tomer signs a 2‑year con­tract with three ele­ments. Here are the con­tract prices and the stand­alone sell­ing prices for each:

Element	What it is	Contract price	Standalone selling price (SSP)
Software subscription (2 years)	Recurring access to the platform	$1,200,000	$1,300,000
Implementation (one-time)	Onboarding, data migration, configuration	$100,000	$150,000
Premium support (2 years)	Dedicated support tier	$50,000	$50,000
Total		$1,350,000	$1,500,000

The cus­tomer com­mit­ted to $1,350,000 in book­ings (TCV). Their stand­alone prices would have totaled $1,500,000, so they received a $150,000 bun­dle dis­count. Now run the five steps.

Step 1 — Con­tract. Approved, com­mit­ted, pay­ment terms set, col­lectibil­i­ty prob­a­ble, non-can­cellable for the two years. It is a valid con­tract.

Step 2 — Per­for­mance oblig­a­tions. Three dis­tinct promis­es — sub­scrip­tion, imple­men­ta­tion, sup­port — because the cus­tomer ben­e­fits from each and they are sep­a­rate­ly iden­ti­fi­able. (In prac­tice you must test whether imple­men­ta­tion is tru­ly dis­tinct or so inter­twined with the sub­scrip­tion that it is not sep­a­ra­ble; here we treat it as dis­tinct.)

Step 3 — Trans­ac­tion price. $1,350,000 total. No vari­able con­sid­er­a­tion in this ver­sion, no expect­ed refunds.

Step 4 — Allo­cate by rel­a­tive SSP. Spread the $1,350,000 across the three oblig­a­tions in pro­por­tion to their $1,500,000 of stand­alone prices. The allo­ca­tion ratio is $1,350,000 / $1,500,000 = 0.90, so each oblig­a­tion is rec­og­nized at 90% of its SSP:

Element	SSP	Allocation ratio	Allocated transaction price
Subscription	$1,300,000	0.90	$1,170,000
Implementation	$150,000	0.90	$135,000
Premium support	$50,000	0.90	$45,000
Total	$1,500,000		$1,350,000

Step 5 — Rec­og­nize as sat­is­fied.

• Sub­scrip­tion ($1,170,000) rec­og­nized over time, even­ly across 24 months = $48,750 per month.
• Pre­mi­um sup­port ($45,000) rec­og­nized over time, even­ly across 24 months = $1,875 per month.
• Imple­men­ta­tion ($135,000) rec­og­nized when that one-time oblig­a­tion is sat­is­fied. Assume it is deliv­ered over the first 3 months of onboard­ing, rec­og­nized even­ly = $45,000 per month for months 1 through 3, then $0.

So your rec­og­nized rev­enue in month 1 is $48,750 + $1,875 + $45,000 = $95,625. In month 4, once imple­men­ta­tion is done, it drops to $48,750 + $1,875 = $50,625 per month for the remain­der of the term. Notice the shape: rev­enue is high­er in the first three months because the imple­men­ta­tion oblig­a­tion is being sat­is­fied, then set­tles into the steady recur­ring run-rate.

Now con­trast that with the cash. If the cus­tomer pre­paid year one — $600,000 of sub­scrip­tion plus $100,000 of imple­men­ta­tion plus $25,000 of sup­port = $725,000 invoiced upfront, depend­ing on billing terms — you col­lect­ed far more in month 1 than you rec­og­nized. The dif­fer­ence becomes deferred rev­enue, a lia­bil­i­ty, and it releas­es into rec­og­nized rev­enue as you deliv­er. That gap between cash-in and rev­enue-earned is the sin­gle most impor­tant thing ASC 606 cre­ates, and it is the sub­ject of the next sec­tion.

Deferred Revenue: The Liability That Confuses Every First-Time Founder

When a cus­tomer pays you before you have deliv­ered the ser­vice, you have col­lect­ed cash you have not earned. ASC 606 (work­ing with the broad­er bal­ance-sheet rules) says that unearned cash is a lia­bil­i­ty called deferred rev­enue (some­times “unearned rev­enue” or a “con­tract lia­bil­i­ty”). It is a lia­bil­i­ty because you owe the cus­tomer some­thing — the ser­vice they paid for — and if you went out of busi­ness tomor­row you would the­o­ret­i­cal­ly have to refund the unde­liv­ered por­tion.

This feels back­wards to founders the first time they see it. You have more cash and your bal­ance sheet shows a big­ger lia­bil­i­ty. But that is exact­ly right, and it is one of the health­i­est lia­bil­i­ties a busi­ness can have: it is an inter­est-free pre­pay­ment from cus­tomers that funds your oper­a­tions. Strong SaaS com­pa­nies often car­ry large deferred-rev­enue bal­ances pre­cise­ly because cus­tomers are hap­py to pay annu­al­ly upfront.

Here is the mechan­ic, using the annu­al-pre­paid sub­scrip­tion from ear­li­er ($600,000/year, billed upfront):

Month	Cash collected	Revenue recognized	Deferred revenue remaining (end of month)
Month 0 (invoice paid)	$600,000	$0	$600,000
Month 1	$0	$50,000	$550,000
Month 2	$0	$50,000	$500,000
Month 3	$0	$50,000	$450,000
Months 4 through 11	$0	$50,000 each	declining by $50,000 each
Month 12	$0	$50,000	$0

Each month, $50,000 ($600,000 / 12) moves off the bal­ance sheet (deferred rev­enue shrinks) and onto the income state­ment (rec­og­nized rev­enue grows). The cash came in once; the rev­enue is earned over twelve months. By month 12 the lia­bil­i­ty is ful­ly burned down to zero and you have rec­og­nized the entire $600,000.

Why you care at exit: deferred rev­enue is a real oblig­a­tion a buy­er inher­its. They take on the duty to deliv­er the ser­vice, but you already spent the cash. In most deals this gets account­ed for explic­it­ly in the pur­chase price (the buy­er is effec­tive­ly com­pen­sat­ed for fund­ing the oblig­a­tion they are assum­ing). A large, well-doc­u­ment­ed deferred-rev­enue bal­ance is also pos­i­tive evi­dence — it proves cus­tomers pay you upfront, which sig­nals con­fi­dence and improves cash dynam­ics. But it must be clean and rec­on­cil­able. A deferred-rev­enue bal­ance that does not tie to your con­tracts and billing is a dili­gence red flag. This is core to the broad­er SaaS finan­cial mod­el and shows up direct­ly in any SaaS rev­enue fore­cast­ing mod­el you build.

The SaaS-Specific Issues ASC 606 Forces You to Get Right

The clean exam­ples above are the easy case. Real SaaS con­tracts have wrin­kles, and each one changes the recog­ni­tion pat­tern. Here are the ones that mat­ter most for a com­pa­ny at your stage.

Upfront, Setup, and Implementation Fees

A one-time set­up fee (also called an imple­men­ta­tion or onboard­ing fee — a charge to get the cus­tomer live) is the clas­sic ASC 606 trap. Your instinct is to rec­og­nize it imme­di­ate­ly because you did the work upfront and col­lect­ed the cash. ASC 606 often dis­agrees. The ques­tion is whether that set­up activ­i­ty is a dis­tinct per­for­mance oblig­a­tion (some­thing the cus­tomer sep­a­rate­ly val­ues and could ben­e­fit from on its own) or mere­ly a set­up activ­i­ty that is part of giv­ing them access to the sub­scrip­tion.

If the set­up work is not dis­tinct — if it is just the cost of switch­ing the cus­tomer on, with no stand­alone val­ue — then ASC 606 says you can­not rec­og­nize it upfront. Instead you spread that fee over the peri­od the cus­tomer ben­e­fits, which is the expect­ed life of the rela­tion­ship, not just the con­tract term. A $30,000 set­up fee on a cus­tomer you expect to keep for three years might be rec­og­nized at rough­ly $833/month over 36 months, not booked as $30,000 of rev­enue on day one. That sin­gle rule has sunk more than one star­tup’s “great quar­ter.”

Multi-Year Prepaid Contracts

A cus­tomer who pre­pays two or three years upfront hands you a pile of cash and a large deferred-rev­enue lia­bil­i­ty. The recog­ni­tion is straight­for­ward — spread even­ly over the ser­vice term — but two things bite. First, the cash-vs-rev­enue gap is huge in year one (you col­lect­ed three years, rec­og­nized one), which makes your bank bal­ance look far health­i­er than your P&L. Sec­ond, if there is a mate­r­i­al financ­ing com­po­nent — mean­ing the mul­ti-year pre­pay­ment is large enough that it effec­tive­ly includes you receiv­ing a loan from the cus­tomer — ASC 606 can require you to account for an implied inter­est ele­ment. For most SaaS deals of a cou­ple of years or less this is ignored as imma­te­r­i­al, but on long, large pre­pay­ments it is a real con­sid­er­a­tion your accoun­tant will flag.

Usage-Based and Consumption Pricing

Usage-based pric­ing (billing for what the cus­tomer actu­al­ly con­sumes — API calls, stor­age, seats used, mes­sages sent) is vari­able con­sid­er­a­tion, and it is rec­og­nized dif­fer­ent­ly from a flat sub­scrip­tion. The gen­er­al prin­ci­ple: you rec­og­nize usage rev­enue as the usage occurs, in the peri­od the cus­tomer con­sumes it, because that is when you sat­is­fy the oblig­a­tion. A cus­tomer who runs 2 mil­lion API calls in March gen­er­ates March rev­enue, not rev­enue smoothed across the year. Where it gets com­plex is tiered pric­ing, min­i­mum com­mit­ments, and pre­paid usage cred­its — each requires esti­mat­ing vari­able con­sid­er­a­tion and con­strain­ing it to amounts that will not reverse. If usage is a mean­ing­ful slice of your rev­enue, this is one of the first places a buy­er’s accoun­tants will dig, because it is the eas­i­est place to acci­den­tal­ly over­state rev­enue.

Contract Modifications, Upgrades, and Downgrades

Cus­tomers upgrade, down­grade, add seats, and renew ear­ly — a con­tract mod­i­fi­ca­tion is any change to the scope or price of an exist­ing con­tract. ASC 606 has spe­cif­ic rules for whether a mod­i­fi­ca­tion is treat­ed as (a) a sep­a­rate new con­tract, (b) a ter­mi­na­tion of the old con­tract and cre­ation of a new one, or © a change blend­ed into the exist­ing con­tract and caught up. Which path applies depends on whether the added goods or ser­vices are dis­tinct and priced at their stand­alone val­ue:

• Add a clear­ly dis­tinct ser­vice at its stand­alone price, and it is usu­al­ly a sep­a­rate con­tract, account­ed for on its own.
• Upgrade to a more expen­sive tier mid-term, and it is often a mod­i­fi­ca­tion of the exist­ing con­tract, with rev­enue prospec­tive­ly re-spread over the remain­ing term.
• A mid-term down­grade or par­tial can­cel­la­tion means you adjust rec­og­nized rev­enue and the remain­ing sched­ule accord­ing­ly.

For a fast-grow­ing SaaS com­pa­ny where expan­sion rev­enue is the engine of net rev­enue reten­tion, mod­i­fi­ca­tions are not an edge case — they are con­stant. Get­ting the treat­ment con­sis­tent is what keeps your report­ed expan­sion rev­enue trust­wor­thy, which direct­ly sup­ports the rev­enue reten­tion sto­ry you will tell a buy­er.

Commission Capitalization Under ASC 340–40

Here is the com­pan­ion rule most founders have nev­er heard of, and it sur­pris­es peo­ple because it is about costs, not rev­enue. ASC 340–40 is the cost-side guid­ance that ships along­side ASC 606, and it gov­erns the incre­men­tal costs of obtain­ing a con­tract — over­whelm­ing­ly, that means sales com­mis­sions.

The plain-Eng­lish ver­sion: when you pay a sales rep a com­mis­sion to close a deal, ASC 340–40 says you gen­er­al­ly can­not expense that whole com­mis­sion in the month you pay it. Because that com­mis­sion “bought” you a cus­tomer who will gen­er­ate rev­enue for years, the cost has to be cap­i­tal­ized (record­ed as an asset) and amor­tized (expensed grad­u­al­ly) over the peri­od you ben­e­fit from that cus­tomer — which is the expect­ed cus­tomer life­time, not just the ini­tial con­tract term. The log­ic is match­ing: spread the cost of acquir­ing the cus­tomer over the same peri­od you rec­og­nize the rev­enue they bring.

A con­crete ver­sion: you pay a rep a $24,000 com­mis­sion to land a cus­tomer on a 1‑year con­tract, but your data says that type of cus­tomer stays an aver­age of 4 years. ASC 340–40 gen­er­al­ly makes you cap­i­tal­ize the $24,000 and amor­tize it at $500/month over 48 months — not expense $24,000 in month one. There is a prac­ti­cal short­cut — the prac­ti­cal expe­di­ent — that lets you expense com­mis­sions imme­di­ate­ly if the amor­ti­za­tion peri­od would be one year or less. But here is the catch most founders miss: because SaaS cus­tomers typ­i­cal­ly renew and stay mul­ti­ple years, that expect­ed-life peri­od is usu­al­ly well over a year, so most SaaS com­pa­nies do not qual­i­fy to expense new-cus­tomer com­mis­sions imme­di­ate­ly. Mis­us­ing that short­cut is one of the most com­mon rev­enue-and-cost find­ings audi­tors and buy­ers catch.

Why this mat­ters to you: cap­i­tal­iz­ing com­mis­sions changes the shape of your prof­itabil­i­ty. Expens­ing com­mis­sions upfront makes a high-growth quar­ter look unprof­itable; cap­i­tal­iz­ing them spreads the cost and reveals the real unit eco­nom­ics under­neath. It con­nects direct­ly to your cost of goods sold for SaaS treat­ment and to how a buy­er reads your mar­gins — and it is the kind of thing a thor­ough SaaS finance func­tion has but­toned up long before dili­gence starts.

What Most Founders Get Wrong About ASC 606

The same hand­ful of mis­takes show up again and again, and every one of them is avoid­able.

1. Con­fus­ing cash with rev­enue. The sin­gle most com­mon error: treat­ing mon­ey col­lect­ed as rev­enue earned. A $300,000 annu­al pre­pay­ment is not $300,000 of Q1 rev­enue — it is $25,000/month of rec­og­nized rev­enue and a $275,000 deferred-rev­enue lia­bil­i­ty after month one. Founders who run their men­tal P&L on cash get a nasty sur­prise when their accoun­tant shows them GAAP rev­enue.
2. Rec­og­niz­ing set­up and imple­men­ta­tion fees upfront. As cov­ered above, a non-dis­tinct set­up fee usu­al­ly can­not be tak­en as day-one rev­enue. Book­ing it upfront over­states cur­rent rev­enue and cre­ates a restate­ment risk in dili­gence.
3. Count­ing book­ings (or even billings) as rev­enue in board decks. Report­ing “$2M in rev­enue this quar­ter” when $2M was book­ings and rec­og­nized rev­enue was $600K is not lying — but it con­fus­es your board and trains every­one to watch the wrong num­ber. A buy­er will only cred­it rec­og­nized, recur­ring rev­enue.
4. Call­ing can­cellable or shaky-col­lectibil­i­ty deals “ARR.” If the cus­tomer can leave in 30 days or might not pay, the enforce­able, rec­og­niz­able amount is far less than the order-form num­ber. Inflat­ed ARR is the first thing a buy­er recom­putes — and the gap between your ARR and their recom­put­ed ARR poi­sons trust for the whole deal.
5. Expens­ing all sales com­mis­sions imme­di­ate­ly. Under ASC 340–40 most SaaS com­pa­nies must cap­i­tal­ize and amor­tize new-cus­tomer com­mis­sions over the expect­ed cus­tomer life. Get­ting this wrong dis­torts prof­itabil­i­ty and is a fre­quent audit find­ing.
6. Wait­ing until the deal is live to clean up rev­enue recog­ni­tion. Dis­cov­er­ing dur­ing dili­gence that three years of rev­enue was rec­og­nized incon­sis­tent­ly is a bru­tal, expen­sive time to find out. ASC 606 com­pli­ance is cheap to main­tain as you go and painful to retro­fit under deal pres­sure.

The pat­tern: each mis­take makes your report­ed num­bers diverge from the num­bers a buy­er (or audi­tor) will inde­pen­dent­ly recom­pute. Every point of diver­gence is a point of risk, and risk is what com­press­es your mul­ti­ple. Clean ASC 606 account­ing is not bureau­cra­cy — it is pro­tect­ing the val­ue of the thing you are build­ing toward sell­ing.

How ASC 606 Connects to Your Valuation and Diligence

Tie it all togeth­er with the lens that mat­ters: the sale. When a buy­er eval­u­ates your com­pa­ny, ASC 606 shapes the three things that dri­ve your price.

Rev­enue qual­i­ty and the recur­ring-rev­enue pre­mi­um. Buy­ers pay the rich­est mul­ti­ples for rev­enue that is con­trac­tu­al, recur­ring, and rec­og­nized smooth­ly over time — exact­ly the pro­file ASC 606 pro­duces for a clean sub­scrip­tion busi­ness. The more of your rev­enue that is gen­uine­ly recur­ring and rat­ably rec­og­nized (ver­sus one-time ser­vices, lumpy imple­men­ta­tion rev­enue, or front-loaded fees), the high­er the mul­ti­ple. ASC 606 is the stan­dard that proves the recur­ring nature of your rev­enue to a skep­ti­cal buy­er. If you want the mar­ket con­text for what that pre­mi­um looks like, see how SaaS rev­enue mul­ti­ples move with rev­enue qual­i­ty and growth, and why busi­ness­es with recur­ring rev­enue com­mand a pre­mi­um.

The qual­i­ty-of-earn­ings review. Seri­ous buy­ers com­mis­sion a Qual­i­ty of Earn­ings (QoE) study — an inde­pen­dent deep-dive that recon­structs your real, nor­mal­ized rev­enue and earn­ings. The QoE team lives and breathes ASC 606. They will test your per­for­mance-oblig­a­tion judg­ments, your deferred-rev­enue burn-down, your com­mis­sion cap­i­tal­iza­tion, and your book­ings-to-rev­enue-to-cash bridge. If your account­ing holds up, dili­gence moves fast and your cred­i­bil­i­ty ris­es. If it does not, every prob­lem becomes a price nego­ti­a­tion in the buy­er’s favor.

De-risk­ing the fore­cast. The buy­er is under­writ­ing your future rev­enue, and the cred­i­bil­i­ty of that fore­cast depends on the integri­ty of your his­tor­i­cal rev­enue. Con­sis­tent ASC 606 account­ing means your past is reli­able, which makes your pro­jec­tions believ­able, which pro­tects your mul­ti­ple. This is the prac­ti­cal mech­a­nism behind the idea that risk — the gap between your mod­el and real­i­ty — is a mul­ti­ple killer. When you even­tu­al­ly sell your SaaS com­pa­ny, the clean­li­ness of your rev­enue recog­ni­tion is one of the qui­et dif­fer­ences between a smooth close at a strong mul­ti­ple and a grind­ing nego­ti­a­tion that chips away at your num­ber.

The take­away for a founder at $5M to $15M ARR: you do not need to become a rev­enue-recog­ni­tion expert, but you do need to make sure some­one on your team is, well before you run a process. ASC 606 is not a tax you pay — it is an asset you build. Done rou­tine­ly and cor­rect­ly, it is invis­i­ble. Neglect­ed, it sur­faces at the exact moment you can least afford it.

Frequently Asked Questions

What is ASC 606 in simple terms?

ASC 606 is the U.S. account­ing stan­dard (issued by the FASB) that gov­erns how and when a com­pa­ny records rev­enue from cus­tomer con­tracts. Its core rule is that you rec­og­nize rev­enue as you deliv­er the ser­vice, not when you get paid. For SaaS, that means a $120,000 annu­al pre­pay­ment is not $120,000 of rev­enue today — it is rec­og­nized at rough­ly $10,000 per month over the year as you pro­vide access. The cash you have col­lect­ed but not yet earned sits on your bal­ance sheet as deferred rev­enue. The stan­dard orga­nizes all of this into a five-step mod­el: iden­ti­fy the con­tract, iden­ti­fy the per­for­mance oblig­a­tions, deter­mine the trans­ac­tion price, allo­cate that price, and rec­og­nize rev­enue as oblig­a­tions are sat­is­fied.

What are the five steps of ASC 606?

The ASC 606 five-step mod­el is: (1) Iden­ti­fy the con­tract with the cus­tomer — con­firm it is enforce­able and col­lec­tion is prob­a­ble; (2) Iden­ti­fy the per­for­mance oblig­a­tions — the dis­tinct promis­es you have made, like sub­scrip­tion, imple­men­ta­tion, and sup­port; (3) Deter­mine the trans­ac­tion price — the total you expect to keep, adjust­ed for dis­counts, refunds, and vari­able amounts; (4) Allo­cate the trans­ac­tion price across the oblig­a­tions based on each one’s stand­alone sell­ing price; and (5) Rec­og­nize rev­enue as you sat­is­fy each oblig­a­tion, either over time (typ­i­cal sub­scrip­tions) or at a point in time (one-time deliv­er­ables).

When did ASC 606 take effect for private companies?

Pri­vate com­pa­nies were required to adopt ASC 606 for annu­al report­ing peri­ods begin­ning after Decem­ber 15, 2018 (pub­lic com­pa­nies adopt­ed a year ear­li­er, for peri­ods after Decem­ber 15, 2017). The pri­vate-com­pa­ny dead­line was lat­er deferred by one year — to peri­ods begin­ning after Decem­ber 15, 2019 — for com­pa­nies that had not yet adopt­ed. The prac­ti­cal take­away: if your books are audit­ed or you are head­ing toward a sale today, your finan­cials are expect­ed to already be on ASC 606. The stan­dard was issued by the FASB via ASU 2014-09, and its inter­na­tion­al twin, IFRS 15, shares the same five-step mod­el.

What is the difference between bookings, billings, recognized revenue, and ARR?

They mea­sure four dif­fer­ent things. Book­ings is the total val­ue a cus­tomer com­mits to when they sign — count­ed at sign­ing, not on the finan­cials. Billings is what you have invoiced so far — it dri­ves cash and receiv­ables. Rec­og­nized rev­enue is the por­tion of the ser­vice you have actu­al­ly deliv­ered — this is the only one ASC 606 gov­erns, and it is what hits your income state­ment. ARR is your annu­al­ized recur­ring rev­enue run-rate at a point in time — an oper­at­ing met­ric, not a GAAP fig­ure. On a 2‑year, $120,000 deal billed annu­al­ly, you could simul­ta­ne­ous­ly have $120,000 of book­ings, $60,000 of year-one billings, $5,000 of first-month rec­og­nized rev­enue, and $60,000 of ARR — all cor­rect, all dif­fer­ent.

How does ASC 606 treat SaaS setup and implementation fees?

It depends on whether the set­up work is a dis­tinct per­for­mance oblig­a­tion. If the imple­men­ta­tion has stand­alone val­ue the cus­tomer sep­a­rate­ly ben­e­fits from, it can be rec­og­nized as its own oblig­a­tion, often as it is deliv­ered. But if the set­up is sim­ply the cost of switch­ing the cus­tomer on — not dis­tinct from giv­ing them access to the sub­scrip­tion — ASC 606 gen­er­al­ly requires you to spread that fee over the expect­ed cus­tomer rela­tion­ship, not rec­og­nize it upfront. A $30,000 set­up fee for a cus­tomer you expect to keep three years might be rec­og­nized around $833/month over 36 months rather than as day-one rev­enue. Rec­og­niz­ing non-dis­tinct set­up fees upfront is one of the most com­mon ASC 606 mis­takes.

What is ASC 340–40 and how does it relate to ASC 606?

ASC 340–40 is the com­pan­ion cost-cap­i­tal­iza­tion guid­ance that ships with ASC 606. While ASC 606 gov­erns rev­enue, ASC 340–40 gov­erns the incre­men­tal costs of obtain­ing a con­tract — main­ly sales com­mis­sions. It gen­er­al­ly requires you to cap­i­tal­ize a com­mis­sion (treat it as an asset) and amor­tize it (expense it grad­u­al­ly) over the expect­ed cus­tomer life­time, rather than expens­ing the whole amount when you pay it. A $24,000 com­mis­sion on a cus­tomer expect­ed to stay four years would typ­i­cal­ly be amor­tized at $500/month over 48 months. There is a prac­ti­cal expe­di­ent allow­ing imme­di­ate expens­ing if the peri­od is a year or less, but because SaaS cus­tomers usu­al­ly stay mul­ti­ple years, most SaaS com­pa­nies do not qual­i­fy to use it for new-cus­tomer com­mis­sions.

Why does ASC 606 matter when I sell my company?

Because a buy­er pays a mul­ti­ple of your rec­og­nized, recur­ring rev­enue — and ASC 606 defines what counts. Dur­ing dili­gence, a buy­er (and their Qual­i­ty of Earn­ings team) rec­on­ciles your book­ings to your rec­og­nized rev­enue to your cash, tests your per­for­mance-oblig­a­tion and deferred-rev­enue judg­ments, and checks your com­mis­sion cap­i­tal­iza­tion. Clean ASC 606 account­ing makes your rev­enue look as durable and pre­dictable as it real­ly is, which sup­ports the high­est mul­ti­ples. Slop­py or incon­sis­tent recog­ni­tion turns every dis­crep­an­cy into a price nego­ti­a­tion in the buy­er’s favor. ASC 606 done right is a qui­et form of de-risk­ing the busi­ness you are sell­ing.