Key takeaways
- ASC 606 governs revenue recognition for private companies. It requires recognizing revenue when performance obligations are satisfied, not when cash is received.
- The most common middle market revenue recognition error is recognizing revenue at cash receipt rather than at delivery or completion of the performance obligation.
- A revenue recognition policy must be written, applied consistently across all periods, and applied consistently across all customers and transaction types.
- Changing the recognition methodology mid-review-period without restating prior periods creates a comparability problem that QoE accountants treat as a red flag.
- Multi-element arrangements, where a contract includes product, installation, and ongoing support, require each element to be identified as a separate performance obligation and recognized separately.
Operating diagnosis
For adjacent context, compare this with Monthly Management Reporting Package: Build It Once, Run It for 24 Months and What a Slow Month-End Close Is Really Telling Buyers About Your Business; the strongest operators connect these topics instead of treating them as separate workstreams.
What this means in practice: the first improvement is usually not a new dashboard; it is a named owner, a fixed metric definition, and a recurring decision cadence that forces action.
Operator Checklist
- Name the metric, process, or decision this issue affects.
- Assign a single owner with authority to change the process.
- Pull the last 12-24 months of data and identify the pattern, not just the latest month.
- Choose one corrective action that can be tested in the next 30 days.
- Review the result in the next management cadence and document the decision.
ASC 606
Current GAAP standard governing revenue recognition for private companies
$300K–$1.2M
Typical revenue adjustment in a middle market QoE due to recognition errors
24 months
Minimum period QoE accountants review for recognition consistency
5 steps
The ASC 606 recognition framework all companies must follow
Revenue is the top line of every financial statement, and it is the first number buyers test for quality. Not the amount of revenue, but the timing and consistency of how it is recognized. A business that recognized $8M of revenue in a year may have done so correctly, or it may have recognized $600K of advance payments from customers who had not yet received their product or service.
In a QoE review, revenue recognition errors create adjustments that flow directly through to EBITDA. If $600K of revenue was recognized early, it is reversed out of the period where it was reported and moved to the correct period. At a 6x multiple, that $600K adjustment is a $3.6M reduction in purchase price.
The ASC 606 five-step framework
Private companies are now subject to ASC 606, which replaced the prior revenue recognition guidance. The standard uses a five-step model that applies to all revenue-generating contracts.
The five ASC 606 steps
Step 1: Identify the contract with a customer
A contract exists when there is an agreement with a customer that creates enforceable rights and obligations. Verbal agreements, informal arrangements, and purchase orders without executed contracts create recognition risk.
Step 2: Identify the performance obligations
Each distinct good or service the company promises to deliver is a separate performance obligation. A contract to sell equipment, install it, and provide one year of support contains three performance obligations.
Step 3: Determine the transaction price
The total consideration the company expects to receive, including variable consideration like volume discounts, rebates, and earn-back provisions. Variable consideration must be estimated and constrained.
Step 4: Allocate the transaction price
The total contract price is allocated to each performance obligation based on the standalone selling price of each. A bundle that costs $100K might allocate $70K to the equipment, $20K to installation, and $10K to support.
Step 5: Recognize revenue when each performance obligation is satisfied
Revenue is recognized when control of the good or service transfers to the customer: either at a point in time (delivery, acceptance) or over time (subscriptions, long-term service contracts).
The most common error is skipping Steps 2 through 4 and treating every contract as a single performance obligation recognized at invoice. This is incorrect for any contract that includes installation, support, training, or services alongside a product.
Common revenue recognition errors in middle market companies
Operating workflow scan
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Writing a revenue recognition policy
A written revenue recognition policy is a document that specifies, for each type of revenue the company generates, how and when that revenue is recognized. It is not a general statement ("we recognize revenue when earned"). It is a specific policy for each revenue stream.
Minimum content for a written revenue recognition policy
Revenue streams covered
List each distinct type of revenue: product sales, installation services, support contracts, professional services, subscriptions, licensing.
Performance obligations per revenue stream
For each type, identify how many performance obligations exist and how they are defined.
Timing of recognition
For each performance obligation, specify whether recognition is at a point in time or over time, and what the trigger is: shipment, customer acceptance, percentage of completion, calendar period.
Allocation methodology
For multi-element arrangements, specify how the transaction price is allocated across performance obligations (standalone selling price method, residual approach, etc.).
Variable consideration
Specify how variable consideration (discounts, rebates, returns) is estimated and when it is recognized.
Policy change procedure
Specify how changes to the recognition policy are approved, documented, and disclosed.
The policy should be reviewed by the controller and approved by the CFO or equivalent. It should be signed and dated. It should not change without a formal amendment process that documents the reason for the change and any restatement of prior periods.
Defending the policy in a QoE review
When a QoE accountant reviews revenue recognition, they are testing three things: whether the policy is consistent with GAAP, whether it has been applied consistently across all periods and all customer transactions, and whether the recognition timing matches the actual delivery of goods or services.
The best defense is documentation: a written policy applied uniformly, a contract-to-revenue reconciliation for the top 20 customers, and a deferred revenue schedule that tracks advance payments and their recognition status.
If the QoE review finds inconsistent application, the accountant will re-recognize revenue uniformly and restate the periods. The restatement adjusts EBITDA in each period, which changes the EBITDA base the buyer is using for their valuation. A $400K downward restatement in the trailing twelve months at a 7x multiple is a $2.8M purchase price impact.
A $12M professional services firm had applied its revenue recognition policy differently for government clients (at billing) than for commercial clients (at project completion).
The QoE accountant identified the inconsistency, applied a consistent methodology, and moved $480K of revenue out of the prior year and into two quarters of the current year. The trailing twelve-month EBITDA decreased by $180K.
At a 6.5x multiple, the purchase price decreased by $1.17M. The inconsistency had existed for four years and had never been audited.
Frequently asked questions
What is the first practical step?
Start by defining the metric or process owner and pulling the last 12-24 months of evidence. Most operating issues look different once the pattern is visible over time instead of judged from the most recent month.
How does this affect valuation or buyer confidence?
Buyers value repeatable management discipline because it reduces post-close uncertainty. A documented process, named owner, and consistent review cadence make the result transferable rather than founder-dependent.
What is the most common mistake?
The common mistake is treating the issue as a one-time cleanup project. The value comes when the fix becomes part of the recurring operating cadence and management reviews it consistently.
Work with Glacier Lake Partners
Fix Revenue Recognition Before a Sale Process
We help middle market companies build the financial reporting quality that survives a QoE review.
Start a Conversation →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
