The buy-side Quality of Earnings firm is challenging our historical revenue recognition for our long-term customer projects, claiming we are front-loading earnings. How do we defend our revenue recognition policies to protect our trailing twelve-month EBITDA?
When a buy-side Quality of Earnings (QoE) firm scrutinizes your revenue recognition, their goal is often to adjust your EBITDA downward, which can lead to a lower purchase price for your business. To effectively defend your trailing twelve-month EBITDA figures, shift the focus from abstract accounting theory to concrete operational realities.
Operational Evidence for Revenue Recognition
You must provide clear and compelling documentation that demonstrates how your revenue recognition policies accurately align with your actual project delivery milestones.
• Link Revenue to Deliverables: Provide the buyer with historical data that directly links every dollar of recognized revenue to specific, completed deliverables. This moves beyond mere accounting entries to show the tangible progress underpinning your financial statements.
• Proof of Completion: Present a historical log of signed customer acceptance forms and other evidence of project completion. This concrete documentation validates the fulfillment of contractual obligations.
• Operational Discipline: If your business uses the Entrepreneurial Operating System (EOS), leverage your internal data. Pull historical Level 10 Meeting data and past quarterly Rocks to illustrate how project timelines were consistently met and managed. This demonstrates that your revenue recognition reflects disciplined operational execution, not just an accounting method. For more on EOS metrics, you might find [How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics) or [How do we trim the Scorecard down to the numbers that actually matter?](/qa/trimming-your-eos-weekly-scorecard) helpful.
Financial Reality and Collectibility
Beyond project completion, you also need to prove the economic reality and collectibility of your recognized revenue.
• IVS 105 Income Approach: Under the IVS 105 Income Approach framework, your cash flows must reflect economic reality. This means showing that recognized revenue translates into actual, collectible funds.
• Accounts Receivable Analysis: Present a detailed historical analysis of your accounts receivable and collection cycles.
• Payment History: Demonstrate that customers consistently paid their invoices within a reasonable timeframe (e.g., thirty days) of billing. This proves that the recognized revenue represents real, collectible cash, minimizing concerns about potential bad debt or extended payment terms impacting future cash flow. Understanding how buyers evaluate these aspects can be further explored in [What are the hidden risks in my business operations that will cause a buyer to walk away or renegotiate the price during due diligence?](/qa/identifying-operational-risks-before-buyer-due-diligence).
By combining robust accounting records with incontrovertible operational performance data and evidence of collectibility, you can effectively counteract any attempts by the Quality of Earnings firm to arbitrarily reduce your EBITDA and, consequently, your valuation. This proactive approach will help ensure your company's value is accurately represented, a crucial step when considering [cleaning financials for business sale valuation](/qa/cleaning-financials-for-business-sale-valuation).
Related questions
• [What moves business valuation multiples?](/qa/what-moves-business-valuation-multiples)
• [How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics)
• [What are the hidden risks in my business operations that will cause a buyer to walk away or renegotiate the price during due diligence?](/qa/identifying-operational-risks-before-buyer-due-diligence)
• [Cleaning financials for business sale valuation](/qa/cleaning-financials-for-business-sale-valuation)
Category: Valuation & Deal Structure