If your company is heading toward a sale, revenue recognition is the first number a buyer’s quality-of-earnings team tests — and the fastest way to lose leverage at the deal table. ASC 606 governs when revenue becomes real, and getting it wrong can strip millions off a valuation or stall a close while diligence reopens the books. The standard has been in effect since 2018, yet many companies still carry revenue recognition errors that stay invisible until a transaction drags them into the light.
ASC 606 — the converged U.S. GAAP revenue recognition standard, formally ASU 2014-09 — replaced a patchwork of industry-specific rules with a single five-step model for recognizing revenue from customer contracts. The mechanics are well documented, but the mistakes are where deals get repriced.
For CFOs, controllers, and finance leaders at companies preparing for a sale, an acquisition, or an exit, these are the ASC 606 revenue recognition mistakes that most often surface in diligence, what each one costs, and what clean revenue recognition looks like before you ever open a data room.
Why Revenue Recognition Lands First on the Diligence List
Most companies are operating with a transaction on the horizon — 99% of investor-backed finance leaders expect at least one material transaction in the next 12 months, whether an equity raise, an acquisition, or a sale. In a quality-of-earnings (QoE) review, revenue is the headline: a buyer wants to confirm that reported revenue is durable, correctly timed, and defensible under ASC 606 before agreeing to a multiple.
It’s one of the first things a buyer evaluates. When revenue recognition is sloppy, the buyer discounts the price.
- Revenue that should have been deferred gets pushed into future periods, trailing-twelve-month figures shrink, and the purchase price moves with them.
- Restating revenue mid-process also signals weak financial controls, which invites deeper scrutiny across every other line.
A revenue recognition problem reprices the entire deal, well beyond the revenue line. The companies that protect their valuation treat exit readiness as a standing discipline, so the numbers hold up the day a buyer asks.
Every Revenue Error Traces Back To These 5 Steps
Every ASC 606 mistake maps to one of the five steps in the model. Knowing which step broke is how a controller or a diligence analyst finds the error fast.
| Step | What It Requires | Where Companies Slip |
|---|---|---|
| 1. Identify the contract | A valid, approved agreement with enforceable rights and payment terms | Side letters, verbal change orders, and unsigned renewals never make it into the system |
| 2. Identify performance obligations | Break the contract into distinct promised goods or services | Bundled software, implementation, and support get treated as one undifferentiated line |
| 3. Determine the transaction price | Include variable consideration, discounts, and financing components | Usage credits, rebates, and service-level penalties are ignored or estimated loosely |
| 4. Allocate the transaction price | Spread the price across obligations by standalone selling price | Revenue is loaded onto whatever’s delivered first to pull it forward |
| 5. Recognize revenue | Record revenue as each obligation is satisfied | The full contract is booked up front at signing |
4 ASC 606 Mistakes That Surface in Diligence
These errors rarely look urgent on a quiet quarter, so they sit until a transaction forces a closer look. They’re common enough that revenue recognition and required restatements rank among the functions finance leaders most often hand to a partner — 42% of finance leaders outsource revenue recognition and restatement work. Here are the four that cost the most when a buyer finds them.
1. Recognizing Revenue Too Early
The most expensive mistake is also the most common: booking revenue before the performance obligation is satisfied. A one-year support contract recognized in full at signing inflates the current period and starves the next three quarters.
In a QoE review, that revenue gets re-spread across the contract term, and your trailing-twelve-month total (the basis for the multiple) drops. Pulling revenue forward borrows growth from your own future, and a buyer’s analyst will hand the bill back to you at the worst time.
2. Getting SaaS and Hybrid Contracts Wrong
Software and subscription models are where ASC 606 gets genuinely hard. Pure cloud-subscription revenue usually recognizes ratably over the term, but term licenses, perpetual licenses, and hybrid deals each follow different timing — and hybrid contracts that bundle a term license with ongoing support are the easiest to misstate.
Getting the split wrong distorts monthly recurring revenue, the metric buyers lean on hardest to value a software business. For SaaS businesses, a clean recurring-revenue figure is only as trustworthy as the ASC 606 logic underneath it.
3. Thin or Missing Disclosures
ASC 606 expanded what companies have to disclose about the nature, amount, timing, and uncertainty of revenue. Private companies often treat disclosures as a public-company concern and skip them until an audit or an IPO process demands them and there’s no historical data to reconstruct. Weak disclosures make every other number look less reliable and slow the entire diligence timeline.
4. Treating IFRS 15 as Someone Else’s Problem
For companies with cross-border or international entities, IFRS 15 is the international twin of ASC 606 — same five-step model, with narrow differences in areas like licensing and disclosure. A company consolidating a foreign subsidiary can’t apply one standard at home and ignore the other abroad.
Inconsistent revenue recognition across entities is a red flag a sophisticated buyer spots immediately, and reconciling it under deal pressure is far more expensive than handling it as routine policy.
Adjusted EBITDA and Non-GAAP Measures: Where the Story Gets Flagged
ASC 606 sets when revenue is real. Non-GAAP measures — adjusted EBITDA, adjusted earnings, and the add-backs that accompany them — shape how that performance is presented to investors. Both get tested at exit, because EBITDA and margin expansion sit near the top of what investors reward.
The two have to tell a consistent story; a buyer’s QoE team reads them side by side.
Aggressive or inconsistent adjustment is the mistake. Add-backs that strip out recurring costs as if they were one-time, EBITDA bridges that change methodology between periods, or non-GAAP figures presented without the GAAP reconciliation regulators expect all get stripped back out in diligence. The result is a lower “real” earnings number than the one you brought to market.
Used with discipline, non-GAAP measures give investors a clearer read on the business and the metrics investors weigh most. The guardrails are simple to name and easy to neglect:
- Quality: every adjustment rests on reliable inputs and a documented rationale.
- Accuracy: non-GAAP figures reconcile cleanly to the GAAP statements and to prior reporting.
- Consistency: the same definitions and add-back logic apply period over period, with the reconciliation shown every time.
An adjusted EBITDA number a buyer can’t reconcile is worth less than a smaller number they can trust.
What Clean ASC 606 Revenue Recognition Looks Like Before a Deal
Diligence-ready revenue recognition starts with capturing every contract — including amendments, renewals, and variable terms — in a system that ties revenue to satisfied obligations. From there it depends on internal controls that catch exceptions before they compound and on financial reporting that an auditor can follow without a guided tour.
Audit- and diligence-ready financials keep your numbers defensible on any timeline, so a buyer’s review confirms the story your statements already tell.
The mechanics scale with contract volume, and the right level of automation depends on how complex your revenue is:
| Contract Profile | Recognition Approach | What It Automates |
|---|---|---|
| Low contract volume | Order-entry model | Amortizes revenue over the contract life and separates invoicing from recognition |
| Higher volume, multi-product | Deferred-revenue model | Automates allocation and reallocation across products and discounts, with a full audit trail |
| High volume, complex | Contracts module | Automates deferral, recognition, and billing schedules from contractual rules end to end |
Companies that run revenue recognition this way close faster and walk into diligence without a backlog of cleanup. It’s the same discipline that underpins a tight month-end close and the audit readiness a buyer expects before they’ll commit to a price.
Clean revenue recognition is leverage. When your ASC 606 numbers hold up under a buyer’s scrutiny, you keep control of the timeline, the multiple, and the narrative. That kind of readiness is hard to build in-house on a deal calendar, which is why 87% of investor-backed finance leaders now work with a third-party finance and accounting partner.
A partner like Consero pairs a curated, automated finance stack with an expert team that keeps revenue recognition diligence-ready year-round — so the data room is ready before you need it.
Schedule a consultation to see where your revenue recognition stands before diligence does it for you.
Frequently Asked Questions
How long before a sale should we clean up revenue recognition?
Plan for at least four to six quarters. A quality-of-earnings review looks at trailing-twelve-month revenue, so any restatement needs clean periods behind it to be credible. Fixing recognition the quarter before a process starts means a buyer sees the change — and the restated history — at the worst possible time.
Will a buyer hold a private company to the same ASC 606 standard as a public one?
In diligence, yes. Private companies got an extra year to adopt and carry lighter disclosure requirements, but a sophisticated buyer — and any auditor in an exit or IPO process — expects revenue recognized correctly under the full five-step model. That relief applies to disclosures; the timing rules still apply in full.
Can a quality-of-earnings review reverse revenue we’ve already recognized?
It effectively does. A QoE team re-spreads revenue to match when obligations were satisfied, which can move recognized revenue out of the periods that set your valuation. The reported number stays on your books, but the number the deal is priced on is the one the buyer’s analysis produces.
