A QoE validates the numbers. The IRA validates whether the business will survive having its numbers validated.

What a QoE does well

A Quality of Earnings report from a credible provider — CFGI, Riveron, CrossCountry, the Big 4 transaction services teams, or a respected boutique — is the gold standard for one specific question: do the financial statements in front of the deal team reflect the actual earning power of the business? That is non-trivial work and the IRA does not try to replace it. A good QoE:

• Reconstructs adjusted EBITDA. Normalizes for one-time items, owner perks, accounting policy choices, and run-rate adjustments. This is the line buyers actually pay against.
• Tests the working capital cycle. Validates the AR / AP / inventory shape against the financial statements and identifies the working capital peg.
• Surfaces accounting policy risks. Revenue recognition timing, expense capitalization, deferred items, contingent liabilities — the things that can change the deal price when found late.
• Carries institutional credibility. A Big 4 or top-tier QoE name on the cover materially shifts how the buyer’s IC reads the financials. The IRA does not try to recreate that credibility — it sits underneath it.

What a QoE doesn’t do

The QoE answers one question well. The IRA answers a different, broader question that is upstream of QoE and adjacent to it:

• It runs late. A QoE is commissioned inside a transaction window — usually after a term sheet or LOI. The conflicts and blockers it surfaces are surfaced under deal pressure, with a clock running, and often kill or re-price the deal. The IRA runs months or years earlier, with the same evidence discipline, so the same conflicts are surfaced before they are expensive.
• It scopes only to financial consistency. The IRA grades ten axes: data integrity, financial consistency (where the QoE overlaps), KPI completeness, reporting maturity, operational risk, governance, customer concentration, management responsiveness, key-person dependency, and stress tolerance. The QoE looks at one of those.
• It does not produce a verifiable artifact. A QoE report is a bound document. There is no public verification URL, no deterministic fingerprint, no way for a downstream lender or board to confirm independently that the report wasn’t edited. The IRA artifact carries a tamper-evident verification path on every export.
• It is not reproducible by third parties. Re-running a QoE means hiring another firm to write another QoE. Re-running the IRA means re-running compose_ira() on the new evidence and watching the named blockers disappear (or not) deterministically.
• It does not surface what is blocking institutional readiness more broadly. Customer concentration, governance gaps, key-person dependency, KPI completeness, reporting cadence — none of this is the QoE’s job. All of it is a deal killer if surfaced at the wrong moment.

What the two look like side by side

The healthiest sequence

Run the IRA Gap Review now, when the deal is months away. Surface the institutional-readiness blockers the QoE won’t see and the QoE provider isn’t scoped to fix. Remediate. Re-run the IRA closer to the transaction window so the Lift Ledger documents what changed. Then commission the QoE on a business whose evidence trail is clean enough that the QoE provider isn’t the one discovering the conflicts under deal pressure. See it on a real Cedarbrook proof case.

That sequence costs less, surfaces fewer surprises late, and produces a more credible artifact stack for the buyer. The QoE remains the gold standard for what it does. The IRA is the layer that makes the QoE’s job easier and the deal’s outcome more predictable.