10 Revenue Recognition Mistakes SaaS Companies Make Before Their First Audit

Your first real audit is when revenue recognition mistakes stop being theoretical and start being expensive. Restatements. Delayed closes. Investor questions you can't answer. Audit fees that balloon because your auditor is untangling what should have been straightforward.

We reviewed the most common issues from KPMG's Revenue for Software and SaaS handbook — 770 pages of interpretive guidance on ASC 606 — and identified the ten mistakes that hit SaaS companies hardest. Every one of them is avoidable.

Mistake 1: Treating SaaS as a License (or Vice Versa)

The SaaS-vs-license classification determines whether revenue is recognized over time or at a point in time. Get it wrong and revenue lands in the wrong periods — potentially for every deal in your portfolio.

The test: can the customer take possession of the software and run it independently? If no, it's SaaS. If yes, it's a license. Calling it a "subscription" doesn't make it SaaS if the customer downloads and installs it.

Fix: evaluate each arrangement based on the rights granted, not the label. Document the classification and the reasoning.

Mistake 2: Assuming Every Bundled Deal Is One Performance Obligation

SaaS + implementation + training + support isn't automatically one obligation. Each promise needs the two-part distinct test. Light onboarding is usually separate. Significant customization is usually combined. Assuming everything is one bucket means you're either recognizing too fast or too slow.

Fix: test each promise against both prongs of the distinct test. Document the conclusion for each component.

Mistake 3: Using List Price as Stand-Alone Selling Price

Your list price and your SSP might be the same — but under 606, a list price is not presumed to be the SSP. If you routinely discount off list (and most SaaS companies do), the SSP is the price customers actually pay, not the price on your website.

Fix: analyze your actual selling prices across transactions. Establish SSP ranges based on observable data. Document the methodology and update it periodically.

Mistake 4: Ignoring the Constraint on Variable Consideration

Usage overages, performance bonuses, volume discounts — when you estimate these, you can only include amounts where a significant revenue reversal is unlikely. Some companies include best-case estimates. Then actuals come in lower. Revenue gets reversed. Auditor raises an eyebrow.

Fix: apply the constraint conservatively. If you're not confident, constrain down. Adjust upward in later periods as uncertainty resolves. Document your estimation methodology and the factors you considered.

Mistake 5: Recognizing Usage-Based Royalties Before Usage Occurs

When usage fees are tied to a license of intellectual property, the royalty exception requires you to recognize revenue only as usage occurs. Not estimated. Not at contract inception. Only as usage happens.

Some companies estimate these upfront like other variable consideration. That's wrong — the royalty exception overrides the general variable consideration rules when it applies.

Fix: determine whether the royalty exception applies (usage fee + license of IP + license is predominant). If yes, recognize only as usage occurs. No estimation, no constraint analysis.

Mistake 6: Failing to Capitalize Sales Commissions

ASC 340-40 requires capitalizing incremental costs to obtain a contract — primarily sales commissions — if the amortization period exceeds one year. The one-year practical expedient only applies if the expected benefit period (including anticipated renewals with non-commensurate commissions) is twelve months or less.

Many companies expense all commissions immediately, assuming they qualify for the practical expedient. Often they don't — because anticipated renewals extend the benefit period beyond one year.

Fix: evaluate the amortization period for each commission structure, including anticipated renewals. Apply the practical expedient only when the math actually supports it.

Mistake 7: Treating All Contract Modifications the Same Way

Upgrades, downgrades, price changes, and early terminations each have different accounting treatments depending on whether the modification adds distinct services at SSP, whether remaining services are distinct from past services, and the scope of the change.

Applying the same treatment to all modifications — say, always treating them prospectively — will be wrong in cases where a separate contract treatment or cumulative catch-up is required.

Fix: evaluate each modification against the 606 framework. Distinct additions at SSP = separate contract. Distinct remaining services = prospective. Non-distinct remaining services = cumulative catch-up.

Mistake 8: Missing Material Rights in Renewal Discounts

If your contract gives the customer a renewal option at a price that's significantly below what a new customer would pay, that discount is a material right — a separate performance obligation. Revenue must be allocated to it and deferred.

Many companies treat renewal discounts as simple pricing decisions with no current-period accounting impact. Under 606, if the discount is incremental to what similar customers receive, it affects the original deal's revenue allocation.

Fix: compare renewal pricing to what new customers pay. If the discount is incremental, account for it as a material right. Allocate a portion of the original transaction price and defer recognition.

Mistake 9: Not Adjusting for Significant Financing Components

If a customer pays significantly before or after delivery — and the period exceeds one year — there may be a significant financing component. Large upfront annual payments for multi-year SaaS deals can trigger this.

The practical expedient (period between payment and delivery is one year or less) covers most SaaS billing. But multi-year prepayments or extended payment terms that stretch well beyond the service period may require an adjustment to the transaction price for the time value of money.

Fix: evaluate whether the payment-to-delivery gap exceeds one year for any contracts. If it does, assess whether a financing component adjustment is needed. If within one year, document your use of the practical expedient.

Mistake 10: Ignoring Implied Rights from Modification Patterns

A history of allowing license-to-SaaS conversions, granting mid-contract price reductions, or permitting plan changes without penalty can create implied rights. Under 606, implied rights from customary business practices are treated the same as explicit contractual rights.

If your company routinely grants concessions that aren't in the contract, those concessions may need to be factored into how you account for new contracts — as variable consideration or material rights from inception.

Fix: document your modification and concession history. Evaluate whether patterns have emerged that create implied rights. If they have, adjust how you account for new contracts accordingly.

The Common Thread: Documentation

Every one of these mistakes shares the same root cause: insufficient documentation of judgment. ASC 606 is a principles-based standard that requires companies to make judgment calls and defend them. The standard is fine with judgment. It's not fine with undocumented judgment.

Before your first audit, the single most valuable thing you can do — beyond getting the accounting right — is document why you made the calls you made. SSP methodology. Distinct test conclusions. Modification classifications. Variable consideration estimates. Practical expedient elections.

Your auditor isn't looking for perfection. They're looking for evidence that you applied the standard thoughtfully and consistently.

How JustPaid Helps You Avoid All 10

JustPaid automates the judgment-intensive parts of ASC 606. AI Contract Extraction identifies performance obligations and classifies arrangements. SSPs are estimated from historical data. Contract modifications are detected, classified, and applied automatically. Commission capitalization tracks alongside revenue. And every decision is documented for audit — without your team building a single spreadsheet.

The companies that get through their first audit cleanly aren't the ones with the biggest finance teams. They're the ones with the right systems.

Key Takeaways

• Classification (SaaS vs. license), obligation identification, and SSP estimation are the three areas where mistakes are most common and most consequential.
• The one-year practical expedient for commission capitalization is narrower than most companies think — anticipated renewals extend the benefit period.
• Material rights, implied rights, and financing components are the three "hidden" areas that companies miss until audit.
• Documentation of judgment is as important as the judgment itself. Auditors want evidence of thoughtful, consistent application.
• Automation doesn't just save time — it ensures consistency, which is what 606 fundamentally requires.

Frequently Asked Questions

What are the most common ASC 606 mistakes for SaaS companies?

The most common mistakes include: misclassifying SaaS as a license (or vice versa), treating all bundled services as one obligation, using list price as stand-alone selling price, failing to constrain variable consideration, expensing commissions that should be capitalized, and missing material rights in renewal discounts. Each of these affects when and how much revenue is recognized.

How should SaaS companies prepare for their first ASC 606 audit?

The most important preparation is documentation: SSP estimation methodology, performance obligation analysis for each deal type, modification classification rationale, practical expedient elections, and variable consideration estimates with constraint analysis. Auditors are looking for evidence that the standard was applied thoughtfully and consistently — not perfection, but documented judgment.

What triggers a revenue restatement for SaaS companies?

Common triggers include: incorrect SaaS-vs-license classification (wrong timing), missing performance obligations in bundled deals (wrong allocation), unsupported SSP estimates, improper variable consideration treatment, and failure to identify material rights. Restatements require retrospective correction across all affected periods, which can be expensive and damaging to investor confidence.

Does ASC 606 require documenting revenue recognition judgments?

Yes. ASC 606 is a principles-based standard that relies on management judgment in multiple areas — SSP estimation, distinct test evaluation, variable consideration constraint, and modification classification. While the standard doesn't prescribe specific documentation formats, sufficient documentation is necessary to support audit procedures and demonstrate consistent application.

Preparing for your first audit? Schedule a demo to see how JustPaid automates ASC 606 compliance and audit documentation.