We are preparing for a buy-side Quality of Earnings audit and want to make sure our normalized EBITDA adjustments hold up. How do we document our owner compensation, personal expenses, and one-time software integration costs so the auditor does not slash our valuation?

Question

Tyler Smith · Accepted Answer

Preparing for a buy-side Quality of Earnings (QoE) audit requires meticulous documentation to defend your normalized EBITDA adjustments. Auditors are trained to scrutinize these adjustments, and a well-organized, institutional-grade trail is essential to preserve your enterprise value. Proactive preparation of your data room can significantly streamline the process and prevent subjective reductions.

Documenting Key EBITDA Adjustments

Here's how to effectively document common normalization adjustments:

Owner Compensation

To justify adjustments for owner compensation, the goal is to demonstrate what it would cost to replace your role with a non-owner employee at market rates.

• Third-party compensation study: Obtain an independent study that provides data on salaries for similar roles in your industry and geographic region. This objectively proves the market rate for a replacement.
• Role definition: Clearly define your role's responsibilities and how they align with a specific seat on your [Accountability Chart](/qa/promoting-internal-operations-manager-integrator). For example, if you're paying yourself $300,000 but a market-rate replacement for your defined role costs $150,000, the $150,000 difference is a legitimate add-back to EBITDA.

Personal Expenses

For personal expenses run through the business, maintain rigorous separation and clear documentation.

• Separate records: Keep every receipt, invoice, and ledger entry for non-operating expenses distinct from business-related costs.
• Clear categorization: Document categories of personal expenses that are common add-backs, such as:
• Personal vehicle use.
• Club memberships.
• Salaries or benefits for family members who do not hold a defined, active role on the Accountability Chart.

One-Time Software Integration Costs

One-time software integration costs, like expenses for migrating to new automated workflows, require robust proof of their non-recurring nature. This is similar to how you would defend other [AI investment expenses](/qa/defending-ai-investments-in-qofe-ebitda).

• Invoices from external vendors: Provide detailed invoices from external developers or consulting firms that performed the integration work.
• Project timelines: Present project plans or timelines demonstrating clear start and end dates for the integration. This proves it was a finite project, not an ongoing operational expense.
• Capital investment justification: Clearly articulate that these were capital investments aimed at building a more scalable and efficient platform, rather than recurring operational costs required to maintain day-to-day business. Documenting [operational playbooks](/qa/operational-playbooks-for-strategic-premium-multiples) and processes can help illustrate the long-term benefit and non-recurring nature of these investments.

Ongoing Review and Presentation

Your leadership team should regularly review these adjustments. Many companies integrate this review into their weekly [Level 10 Meeting](/qa/how-to-review-scorecard-under-five-minutes) to ensure your financial scorecard is clean and defensible. When you provide auditors with a meticulously organized ledger, supported by third-party data and clear operational roles, you effectively remove their ability to make subjective "haircuts" to your valuation. This level of preparedness is crucial for a [clean exit](/qa/business-exit-readiness-vs-founder-burnout) and to maximize your business's value.