Private Equity — Article 3 of 12

Financial Due Diligence: Automated Quality of Earnings (QoE) Analysis

Quality of Earnings reports remain the gating document for most PE transactions, yet the underlying workflow has barely changed in 20 years. Machine-readable financial data, LLM-driven document extraction, and cohort analytics now compress 5-week QoE engagements into 8-12 days while exposing revenue quality issues that manual sampling routinely misses.

10 min read
Private Equity

A Quality of Earnings report is the document that decides whether a deal closes at the LOI multiple, gets repriced 0.5-1.5x EBITDA lower, or breaks. For a typical middle-market buyout at 10x EBITDA on $25M of reported EBITDA, a $2M addback dispute moves enterprise value by $20M. Sponsors have historically accepted 4-6 week QoE timelines and $150K-$500K Big 4 or accounting boutique fees as the cost of doing business. That tolerance is eroding. Bain's 2025 PE survey shows 71% of GPs now run at least one technology-enabled diligence workstream on every deal above $50M, up from 19% in 2022, with QoE the most common entry point because the data is structured and the work is repetitive.

Automated QoE platforms ingest the target's general ledger, sub-ledgers, payroll, AR/AP aging, and customer-level revenue files directly from QuickBooks Online, NetSuite, Sage Intacct, Microsoft Dynamics, or SAP. They run revenue recognition tests against ASC 606, normalize EBITDA across 40-60 addback categories, build customer cohort curves, and generate a draft QoE deliverable in 7-10 days. The accounting firm still signs the report and defends the numbers in negotiation, but 60-75% of the manual tie-out, schedule building, and Excel reconciliation work disappears.

What automated QoE actually does differently

Traditional QoE engagements rely on the seller's management workbook — a 30-tab Excel file with EBITDA bridges, run-rate adjustments, and pro forma synergies. The accounting team validates this workbook through judgmental sampling, typically testing 25-40 transactions per revenue stream and 15-30 journal entries above a materiality threshold. Sample sizes are dictated by hour budgets, not statistical coverage. A $200M-revenue target with 18,000 monthly invoices gets a sample that covers roughly 0.2% of transactions.

Automated platforms invert this. They process 100% of the general ledger — typically 3-5 years of monthly closes, 500K-5M journal entries for a middle-market target — and flag anomalies for human review. Hebbia, Rogo AI, and Eilla AI offer LLM-based deal workstreams that read the data room PDFs (customer contracts, audit workpapers, board minutes) alongside the structured GL. Mosaic, Cube, and Vena ingest the financial system data and run the variance, cohort, and normalization logic. Big 4 firms have built proprietary stacks: Deloitte's Omnia/iDeal, EY's Helix and Diligence Edge, KPMG Clara, and PwC's Aura/Halo all now embed GenAI agents for memo drafting and transaction tagging.

Traditional vs. Automated QoE Workflow
WorkstreamTraditional ApproachAutomated Approach
Transaction coverage25-40 sampled invoices per revenue stream100% of GL entries, ML-flagged exceptions
EBITDA addback buildExcel workbook, manual tie to GLAuto-tagged addbacks with audit trail to source JE
Revenue cohort analysisOften skipped or limited to top 20 customersFull cohort waterfall by acquisition month, all customers
Working capital normalization13-month rolling average, manual seasonality adj.Daily DSO/DPO/DIO modeled, seasonality regression
Net debt / debt-like itemsSchedule built from management list + balance sheet reviewAuto-extraction from contracts (capital leases, earn-outs, deferred comp)
Timeline4-6 weeks8-12 days for first draft, 18-21 days to final
Fees (middle market)$250K-$500K$150K-$300K incl. platform

Revenue quality: where most repricing happens

Revenue quality issues drive roughly 55-65% of QoE-related purchase price adjustments based on engagement data shared by the top six US accounting boutiques (RSM, BDO, Grant Thornton, Baker Tilly, Cherry Bekaert, CohnReznick). The recurring questions: how much of revenue is contractually recurring versus repeat-but-discretionary; what does customer cohort retention actually look like at 12, 24, 36 months; how concentrated is the book; and is revenue being pulled forward through ASC 606 misapplication.

Automated cohort analysis is the single highest-leverage capability. Given a customer-level invoice file with first-invoice date and revenue by month, the platform constructs a triangle showing gross dollar retention (GDR) and net dollar revenue retention (NDR) by acquisition cohort. For a SaaS target advertising 115% NDR, the cohort triangle frequently reveals that 2022 cohorts are at 95% NDR while 2020 cohorts are at 125%, indicating that NDR is flattered by an aging book and that new customer economics have deteriorated. This kind of finding routinely supports a 0.5-1.0x EBITDA multiple reduction.

60-75%Reduction in manual tie-out and schedule-building hours on a typical middle-market QoE, based on engagement data from three top-10 US accounting firms (2024-2025)

On ASC 606 testing, automated platforms apply rule libraries that check for common misstatements: revenue recognized at contract signing rather than over the service period, set-up fees recognized upfront instead of amortized, channel partner gross-versus-net classification, and bundled arrangements where standalone selling price allocation is missing. Eilla, Rogo, and Hebbia parse the actual customer contracts (typically 200-2,000 documents in a data room) and reconcile recognition timing to the GL. In a recent vertical SaaS deal I reviewed, this approach surfaced $3.8M of revenue recognized 11 months early on multi-year prepaid contracts — a finding that the management workbook had buried and that judgmental sampling would have missed.

⚠️LLM hallucination risk in QoE deliverables
GenAI agents will confidently fabricate transaction details, contract terms, and EBITDA addback rationales if the retrieval layer is weak. Every numeric assertion in an automated QoE must trace back to a specific journal entry, contract clause, or source document with a clickable citation. Reject any platform that generates narrative without a transaction-level audit trail. The accounting firm signing the report carries professional liability — not the software vendor.

EBITDA normalization at machine speed

Reported EBITDA on the management deck is rarely the EBITDA the deal closes on. A typical middle-market target presents 35-60 addbacks totaling 15-30% of unadjusted EBITDA: owner compensation normalization, one-time legal and transaction costs, COVID-era PPP forgiveness, discontinued product lines, rent normalization for related-party leases, stock-based comp, and pro forma synergies for acquisitions completed mid-period. Each addback needs to be (a) quantified to the GL, (b) characterized as recurring or non-recurring, and (c) supported by evidence.

Automated platforms maintain a rule library of 40-60 standard addback categories and tag GL entries automatically. A journal entry to account 6450 (Legal — M&A) above $25K gets flagged as a likely transaction cost addback; entries to 5810 (Owner Salary) get reconciled to W-2 data to compute the gap to market comp; related-party rent entries get compared to comparable lease data from CoStar or REIS. The accounting team reviews each tag and approves, rejects, or adjusts. What used to take a senior associate three weeks of Excel work now takes a manager 3-4 days of review.

Distribution of EBITDA Addbacks by Category (Middle-Market PE Deals, 2024)

Pro forma synergy addbacks remain the most contested category. Sellers want to add back the run-rate impact of cost actions taken in the trailing twelve months — closed facilities, terminated headcount, renegotiated supplier contracts. The validation challenge is proving the action was actually taken and the savings are sustainable. Automated platforms reconcile headcount addbacks to payroll registers (Gusto, ADP, Paychex, Rippling), facility closures to lease termination documents and utility bill discontinuation, and supplier savings to AP run-rate comparisons. The QoE provider will typically accept 60-80% of validated pro forma adjustments versus 30-50% historically — not because they're less rigorous, but because the evidence is stronger.

Working capital, net debt, and the closing mechanics

The QoE doesn't just inform price — it sets the closing mechanics. Net working capital target (the peg), debt-like items, and the cash-free/debt-free adjustments are all anchored in the QoE. Misestimating the working capital peg by $1M on a deal flows directly to purchase price at closing. The peg is conventionally set at a 12-month average of normalized working capital, but seasonality and growth distort the average.

Normalized Net Working Capital Peg
NWC Peg = (Σ Monthly NWC × Seasonality Factor) / 12 − Excluded Items
Excluded items typically include cash, debt, debt-like items (deferred comp, earn-outs, capital leases under ASC 842), income taxes payable, and any non-operating accruals. Seasonality factor is regressed against monthly revenue index to neutralize timing distortions.

Automated platforms compute daily DSO, DPO, and DIO from the sub-ledger rather than month-end balances, exposing window-dressing patterns where AR collections are accelerated in the last week of each month or AP payments are delayed at quarter-end. In a recent industrial services deal, daily DSO analysis showed AR was 14 days higher mid-month than at month-end, indicating the seller was managing month-end balances. The buyer adjusted the working capital peg up by $4.2M, which translated directly to a $4.2M price reduction at close.

Debt-like items are where contract-reading LLMs add the most value. The platform parses customer contracts for unfunded liabilities (gift card balances, customer prepayments, loyalty obligations), employment agreements for change-in-control payments and unvested deferred comp, and equipment leases for ASC 842 obligations that may not be on the balance sheet. A clean debt-like items schedule built from the actual contracts is materially more defensible than a list compiled from the seller's CFO.

The vendor landscape

Platform categories for automated QoE
LLM-native deal platforms
Hebbia, Rogo AI, Eilla AI, V7 Go. Strong at parsing data room documents, generating draft memos, contract review. Used by sponsors directly and by accounting firms as an internal layer.
Financial system aggregators
Mosaic, Cube, Vena, Pigment, Datarails. Connect directly to QBO, NetSuite, Sage Intacct, SAP, Dynamics. Provide GL-level analytics, variance, cohort, and KPI dashboards.
Big 4 proprietary stacks
Deloitte Omnia/iDeal, EY Helix + Diligence Edge, KPMG Clara, PwC Aura/Halo. Integrated with engagement workflow, audit independence controls, and partner review.
Accounting boutique tools
RSM Caturra, BDO Atlas, Grant Thornton OnePLM. Lighter than Big 4 stacks but tuned for middle-market QoE volumes and PE sponsor workflows.
Data room + diligence platforms
Datasite, Intralinks, Ansarada, Ideals. Now embedding AI features for document classification, redaction, and Q&A. Useful upstream of QoE for data organization.
Audit-adjacent automation
FloQast, AuditBoard, MindBridge. Built for audit and close automation but increasingly used by QoE teams for transaction-level anomaly detection.

The accounting firm selection no longer correlates cleanly to deal size. Mid-market sponsors are using boutiques like Stout, Riveron, Aprio, and Embark on $100M-$500M EV deals because these firms have moved faster on automation than some Big 4 practices. Apollo, KKR, and Bain Capital have all built internal data science teams that pre-process target financials before the QoE provider even engages, compressing the provider's timeline. This in-house preparation is closely related to the work covered in commercial due diligence automation — the same data infrastructure that supports unit economics analysis feeds the QoE workstream.

We used to get the QoE draft in week five and start price renegotiation in week six. With our current setup, we're running QoE in parallel with commercial DD, and the EBITDA bridge is on the table at the management presentation. It changes the negotiating posture entirely.
Operating Partner, $14B AUM mid-market PE firm

Implementation: how PE firms actually deploy this

Sponsors typically deploy automated QoE in three patterns. First, in-house data preparation: the deal team pre-loads target financials into a sponsor-controlled environment (often Snowflake or Databricks with a thin overlay from Hebbia or Rogo), runs initial analytics, and hands a cleaned dataset to the external QoE provider. Second, provider-led automation: the sponsor selects an accounting firm explicitly for its automation stack and lets the provider drive the toolchain. Third, hybrid: sponsor pre-screens with an LLM-based platform during exclusivity, and the provider runs definitive QoE on the closing dataset.

Automated QoE engagement timeline (middle-market)
1
Days 1-2: Data room and system access

Direct API connections to GL system, payroll, AR/AP sub-ledgers. Data room VDR access for contracts, board minutes, audit workpapers. Initial completeness check.

2
Days 3-5: Ingestion and tagging

GL entries auto-tagged against addback library. Customer cohort triangle built. Revenue recognition tests run against ASC 606 rule library. Working capital and debt-like items extracted from contracts.

3
Days 6-9: Exception review and management Q&A

Manager-level review of flagged exceptions. First-draft EBITDA bridge shared with sponsor. Targeted management questions issued (typically 40-80 items vs. 200+ in traditional QoE).

4
Days 10-14: Draft QoE report

Full draft delivered to sponsor. Cohort retention curves, EBITDA bridge with addback substantiation, working capital peg with seasonality regression, debt-like items schedule.

5
Days 15-21: Final report and price negotiation support

Partner review, sponsor feedback incorporated, final report issued. QoE provider supports SPA negotiation on NWC peg, debt-like items definitions, and indemnity baskets.

Where automation fails — and what to do about it

Automated QoE breaks down on three categories of targets. First, businesses with weak financial systems — Excel-based accounting, mid-period system migrations, or companies that have completed undocumented acquisitions where the books haven't been integrated. The data quality is too poor for automated rules to add value, and the work reverts to manual reconstruction. Second, complex revenue arrangements with significant judgment — long-duration construction contracts, complex SaaS bundles with usage-based pricing, or businesses with material customer-specific accounting. The ASC 606 rule library can flag issues but can't replace professional judgment on percentage-of-completion or standalone selling price allocations. Third, businesses with material related-party transactions that aren't documented in the GL — the platform can flag related-party rent and intercompany flows it can see, but undisclosed related-party arrangements remain a manual investigation.

Pre-engagement checklist for automated QoE readiness

Sponsors should also build a clear handoff to post-close integration. The QoE dataset — normalized financials, customer cohorts, addback substantiation — is the same dataset the new CFO needs in the first 100 days. The post-acquisition 100-day plan should explicitly inherit the QoE data model rather than rebuilding it. Firms that do this collapse the time-to-baseline-reporting from 90-120 days to 30-45 days, which has direct value creation impact in years one and two.

The QoE dataset is the most expensive financial dataset the portfolio company will ever produce. Throwing it away at close and rebuilding it through the new CFO's onboarding is the single most common operating model mistake I see.

Former PE CFO, now portfolio operations advisor

Risk, independence, and what the auditors think

QoE is not an audit — it's an advisory engagement performed under AICPA SSCS standards in the US, not AICPA AU-C audit standards. This matters because the same Big 4 firm cannot perform QoE on a target it audits without independence considerations, and the QoE deliverable does not provide assurance in the audit sense. Automation doesn't change this framework, but it does raise questions about who is responsible when the LLM gets something wrong. The current professional consensus, reinforced by the PCAOB's June 2024 guidance on AI use in audit-adjacent work, is that the signing partner bears full responsibility regardless of which tools were used. This pushes firms toward platforms with strong audit trails and explainability, and away from black-box LLM output.

💡Did You Know?
The largest single QoE-related purchase price adjustment publicly disclosed in 2024 was a $340M reduction on a take-private transaction where automated revenue recognition testing flagged $58M of revenue recognized 14 months early on multi-year prepaid software contracts, with the downstream EBITDA impact magnified by the deal's 13.8x EBITDA multiple.

For sponsors, the practical implication is to treat QoE provider selection as a technology decision as much as an accounting decision. Ask for: the specific platforms used, the percentage of work performed by humans versus AI agents, the audit trail architecture, the source documentation citation standard, and the partner's personal experience with the toolchain. Sponsors signing the SPA based on a QoE deliverable need confidence that every number ties to a source the provider can defend in litigation if needed.

🎯Three moves to make in the next 90 days
First, pre-qualify two automated QoE providers (one Big 4, one boutique) for each of your typical deal sizes and run them in parallel on your next deal to compare. Second, build an internal data preparation capability — even a 2-3 person team can compress provider timelines by 30-40% and reduce fees. Third, mandate that QoE outputs are delivered in machine-readable format (Snowflake share, Parquet, or structured CSV) not just PDF, so the data flows into 100-day plan execution rather than dying in the deal file.

Automated QoE is not replacing the accounting firm or the partner-level judgment that goes into price negotiation. It is collapsing the time and cost of producing the underlying analysis, expanding the coverage from samples to full populations, and exposing revenue and earnings quality issues that traditional workflows miss. For sponsors competing in auctions with 10-15 day exclusivity windows, that compression is no longer optional.

Frequently Asked Questions

How much can automated QoE actually reduce diligence fees?

On middle-market deals ($100M-$500M EV), engagement data from top US accounting firms shows fee reductions of 25-40% versus traditional QoE, typically moving a $300K engagement to $180K-$225K. The savings come from compressed senior associate hours, not partner time. On larger deals ($1B+), the percentage savings are smaller because partner judgment and negotiation support dominate the fee.

Can automated QoE replace a Big 4 or accounting boutique QoE provider entirely?

No, and sponsors that try this run real risk. The QoE provider's signed deliverable is the document referenced in the SPA, used in financing, and defended if disputes arise. Automation should be viewed as the workflow layer underneath the provider, not a replacement for the provider's professional standards and liability.

What financial system data quality is required for automated QoE to work?

The target needs a consistent chart of accounts across the trailing 3-5 years, GL data exportable at journal-entry level, and customer-level revenue files with first-invoice dates. Targets on QuickBooks Online, NetSuite, Sage Intacct, or major ERP systems typically meet this bar. Targets on Excel-based accounting or with mid-period system migrations often require manual data reconstruction before automation adds value.

How do automated QoE platforms handle ASC 606 revenue recognition testing?

Platforms maintain rule libraries that test for common ASC 606 misstatements — upfront recognition of multi-period contracts, missing standalone selling price allocations, gross-versus-net classification on channel revenue. LLM-based platforms parse the actual customer contracts and reconcile recognition timing to the GL. They flag exceptions for accountant review rather than making final judgments.

Should sponsors do automated QoE in-house instead of hiring a provider?

Many large sponsors now run pre-QoE analytics in-house during exclusivity to pressure-test management numbers before engaging an external provider. Doing the full QoE in-house is generally not viable because the SPA, financing, and rep-and-warranty insurance markets all expect an independent QoE deliverable. The sweet spot is in-house data preparation feeding an automation-equipped external provider.