SaaS Revenue Recognition: ASC 606 Steps and Judgement Calls

On 8 January 2021 the SEC staff asked Alkami Technology, a digital-banking software vendor, why its implementation services were not distinct from its SaaS (SEC, 2021a). Four days later it asked MeridianLink, which also sells to banks, how it had decided that its implementation services were a separate performance obligation (SEC, 2021b).

On different facts the standard allows both conclusions, and the two put an implementation fee in different quarters. That exchange is SaaS revenue recognition in miniature. For a plain subscription, which earns its fee day by day across the term, ASC 606 is mechanical. The numbers move on four judgements: onboarding fees, usage pricing, the split of the price and mid-term changes. Some of them have more than one acceptable answer, so a company’s written policy is part of its revenue.

Exhibit 1. The five steps of ASC 606, and where the SaaS judgement sits

Step	What ASC 606 asks	A plain subscription	Where the SaaS judgement sits
1. Identify the contract	Approved, enforceable rights and payment terms; collection probable	An order form or click-through terms	Amendments and side agreements that change scope or price
2. Identify the performance obligations	Each distinct good or service, or a series of distinct services	One obligation: access, a series of distinct days	Is onboarding a promised service or a set-up activity?
3. Determine the transaction price	Fixed and variable amounts, with a constraint on estimates	A fixed fee	Usage, overages and credits: estimate them, or book them as invoiced?
4. Allocate the price	Relative standalone selling prices	Nothing to allocate	Subscription against services, and the evidence for each price
5. Recognise revenue	When (or as) the company satisfies each obligation	Straight line over the term	Mid-term changes, which follow separate modification rules

Source: FASB, ASU 2014-09 (ASC 606-10-25 and 606-10-32); KPMG (2025); PwC (2021); CX Cash synthesis.

SaaS revenue recognition is mechanical until the contract stops being plain

For a subscription the five steps of the standard (FASB, ASU 2014-09) collapse into one. PwC’s guide notes that access to a platform usually qualifies as a series, because “each period of service (e.g., each day of service) is distinct and the services provided each period are substantially the same” (PwC, 2021). A $120,000 annual subscription books $10,000 a month, and nothing in the five steps disturbs it.

Contracts rarely stay that plain. KPMG’s December 2025 handbook opens with a warning: “Topic 606 requires software and SaaS entities to make significant judgments and estimates to account for their revenue contracts” (KPMG, 2025). The regulator’s attention follows the judgement. In Audit Analytics data compiled by EY, revenue recognition was the fifth most frequent topic in SEC comment letters on annual reports in the two years to June 2018. The staff raised it with 13% of the companies that received a letter, and comments to early adopters of ASC 606 focused on areas of judgement such as identifying performance obligations (EY, 2018).

These are the points at which two careful accountants, reading the same contract, could book its revenue in different quarters. Exhibit 2 lists recent cases, the Alkami and MeridianLink letters among them.

Exhibit 2. Where SEC questions and two restatements landed

Company	Year	Document	Judgement in question	What happened
Health Catalyst	2019	SEC letter on its IPO filing	Implementation and integration services	Asked for the judgements behind treating them as separate or combined
Alkami Technology	2021	SEC letter on its IPO filing	Implementation not distinct from SaaS	Asked why, and when revenue starts
MeridianLink	2021	SEC letter on its IPO filing	Implementation as a separate obligation	Asked how it weighed integration and interdependence
Paycor HCM	2021	SEC letters on its IPO filing	Period for a nonrefundable implementation fee	Asked why 2 years and not the 6-year average client life
Limeade	2022	SEC letter	Implementation fees	Asked to reconcile two disclosures
Consensus Cloud Solutions	2021 and 2024	SEC letters on its Form 10 and 10-K	Usage-based fees	Four letters on the amount and the method
Guidewire Software	2019	8-K, Item 4.02	Amended contracts, under the old VSOE rules	Fiscal 2017 and 2018 restated; material weakness
Appgate	2022	8-K, Item 4.02	Allocation by standalone selling price	2021 revenue cut by $2.3M, about 5%

Source: SEC EDGAR, the letters, responses and filings listed under Sources. The percentage is our arithmetic.

Implementation fees usually become subscription revenue, and the period is a judgement

The Alkami and MeridianLink letters sit in step 2, where most of the SEC’s SaaS questions begin. The standard names the case: nonrefundable upfront fees include “setup fees in some services contracts” (ASC 606-10-55-50). It then sets a default that runs against intuition. In many cases the activity behind the fee “does not result in the transfer of a promised good or service to the customer”. The fee is then “an advance payment for future goods or services”, recognised as the company delivers them, and if a renewal option gives the customer a material right, the period runs beyond the first term (ASC 606-10-55-51). Maxio’s guide states the opposite default, that implementation, training and setup fees are “typically recognized based on the completion of the associated performance obligation” (Maxio).

The Big Four guides turn the default into a test. KPMG separates set-up activities, which “provide no incremental benefit to the customer beyond that which they will receive from access to the hosted application”, from promised services. In its example, setting up the user interface a customer needs to reach the application is a set-up activity, while migrating the customer’s old data and training its staff are services (KPMG, 2025). PwC lists six indicators that implementation is distinct and adds that “None of the above factors are individually determinative” (PwC, 2021).

The facts decide, and the SEC reads the disclosure as closely as the conclusion: it asked Limeade to reconcile two statements about its implementation fees (SEC, 2022). Paycor HCM shows that even the deferral period is a judgement. It recognised a nonrefundable implementation fee of about $1,150, set against average recurring fees of about $11,500 a year, over two years. The staff asked why the period was “only two years despite an average client life of six years”. Paycor replied that by year 3 the fee was about 3% of total consideration and no longer a material right, and defended two years (Paycor, 2021).

Exhibit 3. One Paycor-sized client, three readings of the same implementation fee, $

Reading of the fee	Fee revenue, year 1	Fee revenue, later years	Year-1 revenue per client
A distinct service, recognised on completion	1,150	None	12,650
An advance payment with a 2-year material right (Paycor’s policy)	575	575 in year 2	12,075
An advance payment over the 6-year average client life	192	192 a year to year 6	11,692

Source: Paycor HCM’s response to the SEC staff (23 April 2021) for the average fee and recurring revenue; the first and third readings are hypothetical alternatives, computed by CX Cash.

The fee is 10% of the client’s first-year recurring revenue, and the reading moves year-1 revenue per client by up to 8.2%. Across a cohort, the reading also shifts reported growth, one of the figures investors weigh when they value a company.

Usage fees are variable consideration, and the contract’s wording sets the timing

But usage pricing raises a step-3 question that a subscription avoids: the price is unknown at signing. The obvious shortcut fails. Software licences have an exception for sales- and usage-based royalties, which a licensor books when the usage occurs. KPMG notes that it does not reach SaaS: “In a SaaS arrangement, the royalties exception does not apply because the arrangement does not contain a software license”. The general rule applies instead, under which an estimate enters revenue only “to the extent that it is probable that a significant reversal in the amount of cumulative revenue recognized will not occur” (ASC 606-10-32-11).

Two routes avoid the estimate. The practical expedient in ASC 606-10-55-18 lets a company “recognize revenue in the amount to which the entity has a right to invoice” when that amount tracks the value delivered. ASC 606-10-32-40 lets it allocate a variable fee entirely to the day or month in which the usage occurs. Both depend on how the contract writes the price. PwC contrasts a minimum that resets each month with one that covers the whole year. In the second case the vendor “would likely have to estimate the variable fee and recognize the total transaction price (fixed minimum and estimated variable fee) over the contract term”.

Consider a hypothetical annual contract: $120,000 for 1.2 million API calls, then $0.10 a call. The customer makes 80,000 calls a month for six months and 140,000 a month after that, so the pool runs out in month 12 and the whole $12,000 overage falls in the last month. Booked as incurred, revenue is $30,000 in the first quarter and $42,000 in the fourth. Estimated and spread as PwC describes, it is $33,000 in every quarter, 10% more in the first.

Consensus Cloud Solutions, which sells cloud fax and digital-signature services, shows how long the question can run. The staff asked for the amount of its usage-based revenue in a July 2021 letter on its Form 10 registration, again in August 2024, and a third time 17 days later, “as previously requested” (SEC, 2021c; SEC, 2024a; SEC, 2024b). The answer put usage fees at $102.9 million in 2023, about 28.4% of revenue of $362.6 million (our arithmetic; Consensus, 2024b; SEC XBRL). Its policy books usage as invoiced only “If the subscription amount is the same every month” and the expedient’s conditions hold. Otherwise usage joins the transaction price, which the company recognises “without regard to what is billed as subscription and what is billed as usage”. Three staff letters and three replies in 2024 ended with one added sentence in the revenue note.

A mid-term change can produce two acceptable revenue lines

But the judgement in SaaS revenue recognition that most often surprises founders sits outside the five steps. A contract modification is “a change in the scope or price (or both) of a contract that is approved by the parties to the contract” (ASC 606-10-25-10). SaaS contracts change constantly, as customers add seats, extend terms and renegotiate prices. If the change adds distinct services at their standalone selling prices, it is a separate contract (ASC 606-10-25-12). If it does not, and the remaining services are distinct, the company treats the old contract as terminated and spreads the unrecognised consideration over a new one (ASC 606-10-25-13).

PwC’s example is a blend-and-extend: a three-year SaaS contract at $900,000 a year, renegotiated at the end of year 2 to add a fourth year at a blended $850,000 for both remaining years.

Exhibit 4. One blend-and-extend, two revenue lines, $ thousands

Accounting	Year 3 revenue	Year 4 revenue	Total	Year-4 growth
Separate contract (the added year carries its standalone selling price)	900	800	1,700	−11.1%
Termination and new contract (it is not)	850	850	1,700	0%
Cash invoiced	850	850	1,700

Source: PwC (2021), Q&A on blend-and-extend modifications. Growth rates are our arithmetic.

Which line applies turns on one fact: whether $800,000 for the added year reflects its standalone selling price. KPMG goes further. When the overall price increase matches the standalone selling price but the blended rate does not, it writes that “we believe the following approaches are acceptable”. Its storage example books $60, $60, $50 and $50 a year under one and $55 a year under the other (KPMG, 2025). The same contract can therefore report a decline of 11.1% or a flat year. The FASB wrote the standard partly because the old rules “sometimes resulted in different accounting for economically similar transactions”.

Mathematics has a name for the condition: Jacques Hadamard defined a well-posed problem in 1902 as one whose solution exists, is unique and changes continuously with its conditions. A problem that fails those tests is re-formulated with additional assumptions, a step known as regularisation (Wikipedia, Well-posed problem). Revenue under ASC 606 always has a solution, though not always a unique one, and a small change in the facts can move it a long way. The standard supplies its own regulariser, since a company must apply the guidance “consistently to contracts with similar characteristics and in similar circumstances” (ASC 606-10-10-3). Unlike a mathematician’s added assumption, that regulariser is a policy the company chooses, and its auditor reviews and its notes disclose the choice.

Guidewire Software learned what an overlooked amendment costs. In May 2019 it told investors to stop relying on its audited statements for fiscal 2017 and 2018. A subset of amended contracts had committed customers to licence and maintenance for one year together, so revenue “should have been recognized ratably over the one-year extension rather than upfront” (Guidewire, 2019). The error arose under the old VSOE rules, and the correction was less than $5 million a year, under 1% of revenue of $661 million in fiscal 2018. The filing added: “The total amount of revenue to be recognized under ASC 605 was unaffected.” It still meant a restatement and a material weakness in internal control.

Allocation errors are small per contract and costly in a restatement

Step 4, which splits the price, moves revenue in small amounts and still deserves the same care. Appgate, a cybersecurity company selling term licences and SaaS, restated in November 2022 after correcting “its accounting estimate for SSP as it relates to term-based license arrangements”, the split between licence and support (Appgate, 2022a). The restated 10-K/A cut 2021 revenue by $2.3 million to $43.0 million, about 5% of the figure first reported (our arithmetic), and 2020 revenue by $0.6 million (Appgate, 2022b). The company said the errors had no impact on its net cash.

Timing is all that moves, Guidewire and Consensus argued

The best counter-argument comes from the companies above: SaaS revenue recognition matters less than the comment letters suggest. Guidewire stressed that the error left total revenue unchanged and that the correction was under 1%. Consensus told the staff that separating usage fees from subscription fees “is not a meaningful standalone metric as it does not present a different attribution pattern” (Consensus, 2024a). Over a contract’s life every reading in Exhibits 3 and 4 books the same total, and a seed-stage company selling monthly plans by card meets none of the four judgements.

On totals, and for the smallest companies, Guidewire and Consensus have it right. Elsewhere timing is what investors pay for. A growth rate compares one period with another, and Exhibit 4 turns one contract into a decline or a flat year. Small timing errors also carry fixed costs: Guidewire’s correction of under 1% came with a restatement and a material weakness, and the SEC staff wrote to Consensus four times across three years about one disclosure. In these two cases, the staff’s interest did not shrink with the amounts.

A one-page revenue policy and the questions that test it

Before the first contract that is not a plain subscription, a founder can write a one-page SaaS revenue recognition policy and apply it consistently, as ASC 606-10-10-3 requires. Each entry answers one of the judgements above, and the last two belong to the people reading the numbers.

• Onboarding and its period. The standard’s default treats a setup fee as an advance payment; if the work is a real service, the policy records why.
• Usage. The expedient suits terms with a constant unit rate and minimums that reset each month; a minimum that covers the whole year will likely mean estimating the variable fee.
• Modifications. Every amendment, early renewal and repricing goes through finance before signature.
• Allocation. Standalone prices are recorded from the first sale.
• The board’s questions. The policy on each of the four judgements, which of them the auditor has reviewed, how much revenue comes from implementation and usage fees (the question the SEC put to Consensus), and whether any blend-and-extend was booked in the period.
• The investor’s question. In diligence, revenue and growth under the other acceptable reading.

A written policy leaves the judgement in place but fixes which answer the company gives, so each quarter compares with the last. Without one, the blend-and-extend above can be reported as a decline of 11.1% or as a flat year.

Notes and sources

• Alkami Technology, Inc. SEC Division of Corporation Finance comment letter on the draft Form S-1, 8 January 2021.
• Appgate, Inc. (2022). Form 8-K, Item 4.02, 8 November 2022; Form 10-K/A for the year ended 31 December 2021.
• Maxio. SaaS revenue recognition (ASC 606).
• Consensus Cloud Solutions, Inc. SEC comment letters of 10 July 2021, 5 August, 22 August and 17 September 2024; company responses of 16 August, 6 September and 23 September 2024; revenue from SEC EDGAR XBRL data.
• EY (2018). SEC Comments and Trends: An analysis of current reporting issues, September 2018.
• FASB (2014). Accounting Standards Update 2014-09, Revenue from Contracts with Customers (Topic 606).
• Guidewire Software, Inc. (2019). Form 8-K, Item 4.02(a), 1 May 2019.
• Health Catalyst, Inc. SEC comment letter, 7 May 2019.
• KPMG (2025). Handbook: Revenue for software and SaaS, US GAAP, December 2025.
• Limeade, Inc. SEC comment letter, 31 August 2022.
• MeridianLink, Inc. (then Project Angel Parent, LLC). SEC comment letter on the draft Form S-1, 12 January 2021.
• Paycor HCM, Inc. SEC comment letter, March 2021; company response of 23 April 2021.
• PwC (2021). Revenue recognition: A Q&A guide for software and SaaS entities.
• Wikipedia. Well-posed problem.

The accounting rules come from ASU 2014-09 and the KPMG and PwC guides, and the company facts from SEC comment letters, company responses and filings. Percentages without a cited source, and those marked “our arithmetic”, are worked out from the companies’ reported figures or the stated assumptions. Exhibit 3’s first and third rows and the usage contract are hypothetical, and Exhibit 4 reproduces PwC’s example. The Guidewire case predates ASC 606 and is included as an example of a modification error.