12. Data, analytics, and reporting due diligence

The model assumed margin expansion would start in month four. Procurement savings, sales productivity, lower churn, faster close. The dashboard in the management presentation supported the story.

Then the diligence team asked for the KPI definitions behind those charts.

Gross margin excluded freight in one business unit and included it in another. Churn was calculated on logos for enterprise customers and on monthly recurring revenue for SMB. The sales pipeline report came from CRM, but bookings came from a spreadsheet maintained by finance. Customer profitability was not tied to the general ledger. Nobody was hiding anything. The business simply had not needed deal-grade reporting before.

That is where data diligence matters. Not because every target needs a modern data platform before close. Because a buyer must know whether the reported facts can carry the plan after close.

The primary decision is this:

Can the target’s data, analytics, and reporting support the investment model, Day-100 steering, and synergy measurement, or do you need remediation, new controls, and a slower value clock?

Why data diligence changes deal economics

Data issues show up as management noise until the first post-close steering meeting. Then they become economics.

• EBITDA timing: savings cannot be managed if baseline cost, supplier spend, customer margin, or headcount data is not trusted.
• Revenue plan risk: cross-sell, pricing, churn reduction, and sales productivity depend on common customer, product, and contract logic.
• Working capital leakage: inventory, receivables, billing disputes, and collections reporting break when definitions differ across ERPs or geographies.
• Day-100 control: leadership loses weeks debating numbers instead of making decisions.
• One-time cash: data cleanup, KPI rebuilds, warehouse remediation, and reporting controls become mandatory work, not optional analytics improvement.

The issue is rarely “bad data” in the abstract. It is whether the buyer can make, measure, and defend the decisions that justified the purchase price.

The common mistake: accepting the dashboard as the truth

Management reports are outputs. They are not evidence.

In diligence, teams often review board packs, KPI dashboards, monthly operating reports, and financial bridges. Those are useful. They are not enough. The real questions sit below the slides:

1. Definition: does the KPI mean the same thing across products, regions, and periods?
2. Lineage: where does the number come from, and how many manual steps change it?
3. Reconciliation: can the metric tie back to GL, CRM, billing, payroll, or inventory systems?
4. Repeatability: can the target produce the same report next month without heroics?
5. Actionability: does the metric point to an owner who can change the result?

If those tests fail, the dashboard may still be directionally useful. But it is not ready to steer the first 100 days.

What goes wrong after close

Three failure patterns are common.

1) The baseline moves after the deal closes

The synergy case starts with a baseline: IT run-rate, procurement spend, customer churn, sales productivity, SKU margin, headcount, cloud cost, working capital.

If that baseline is not locked before close, the first post-close debate becomes “what did we buy?” rather than “what do we change?”

One carve-out buyer expected $14M of procurement savings from vendor consolidation. In month two, the team found that the spend cube included intercompany charges, pass-through customer expenses, and one-time project spend. Addressable spend dropped by roughly one third. The savings target did not disappear, but the plan had to be rebuilt with a lower baseline and a later start.

The mechanism is simple: bad segmentation turns gross opportunity into false opportunity.

2) KPI logic breaks when ownership changes

A target can run on informal reporting when the same finance, sales, and operations leaders have worked together for years. They know the adjustments. They know which spreadsheet is “official.” They know when a product code means one thing in ERP and another in CRM.

After close, that tribal knowledge does not scale. New owners ask for faster cadence, tighter variance explanations, and proof of value capture. The informal layer breaks.

This is especially painful for Day-100 steering. The integration team needs weekly facts. The legacy reporting process was built for monthly narrative.

3) The data platform becomes a dependency nobody planned for

Many deal models assume analytics work can happen in parallel with integration. That is only true if the data foundation is stable enough.

Common blockers:

• CRM account IDs do not match ERP customer masters.
• product hierarchies differ between billing, inventory, and margin reporting.
• data warehouse loads are owned by one analyst and fail silently.
• business logic lives in BI tool calculations rather than governed data models.
• reporting access is tied to the seller’s tenant, shared database, or parent-owned tools.

When these blockers appear after close, the data workstream moves from “reporting improvement” to “control remediation.” That changes cost and timing.

A practical diligence lens: model, manage, measure

The fastest way to assess data and reporting is to tie it to what the buyer needs to do.

1) Model: can the data support underwriting?

Start with the investment model. Pick the 5-7 assumptions that carry the most value or risk.

Examples:

• net revenue retention, churn, and expansion by segment
• gross margin by product, customer, channel, or geography
• addressable supplier spend
• headcount and contractor cost by function
• customer acquisition cost and sales productivity
• inventory turns, receivables aging, and billing leakage

For each assumption, ask: what source data proves this, who owns it, and can it be reconciled?

If the answer is “finance adjusts it offline,” that may be acceptable. But it must be priced as a control and repeatability issue.

2) Manage: can leadership steer the first 100 days?

Day-100 reporting is different from diligence reporting. It needs cadence, ownership, and variance logic.

Test whether management can produce:

• a weekly revenue and bookings view with clear source systems
• a cost baseline by owner and controllable category
• a synergy tracker that separates gross savings, offsets, one-time cost, and run-rate impact
• a close pack that reconciles operational KPIs to finance
• a customer and product view that supports pricing, retention, and cross-sell decisions

The question is not whether the target has all of this today. Many do not. The question is whether the gap is a two-week control fix, a 90-day rebuild, or a full data platform dependency.

3) Measure: can value capture be proven?

Value capture fails when the team cannot separate real improvement from mix, timing, accounting changes, and baseline drift.

A good synergy tracker is not just a list of initiatives. It ties each initiative to:

• the pre-close baseline
• the data source and calculation owner
• the action owner
• the expected P&L, cash, or working-capital impact
• the timing of when the benefit appears in management reporting and in financial statements

If the target cannot support that linkage, do not put early value capture on autopilot. Fund the reporting spine first.

Evidence asks that produce signal quickly

Do not start with a broad “data maturity” questionnaire. Pull artifacts that show whether the reporting engine works.

1) KPI dictionary for the top investment metrics

Ask for definitions, formulas, inclusions, exclusions, source systems, and owners for the metrics used in the management deck and investment model.

Why it matters:

If the target cannot define the metrics it uses to sell the business, the buyer should not assume those metrics can steer the business after close.

2) Source-to-report lineage for five critical reports

Pick five reports that matter to the deal: revenue, margin, churn or retention, sales pipeline, and cost or working capital. Ask for the path from source system to final report, including manual steps.

Why it matters:

Manual work is not automatically bad. Undocumented manual work with no controls is the problem.

3) Reconciliation evidence

Ask where operational metrics tie to audited or management financials:

• bookings to revenue recognition
• customer count to billing
• product margin to GL
• headcount to payroll and HRIS
• supplier spend to AP and procurement systems

Why it matters:

Reconciliation separates useful management views from numbers that cannot survive a steering committee debate.

4) Data quality exceptions and issue logs

Ask for open data quality issues, recurring report adjustments, failed data loads, duplicate master records, and known BI defects.

Why it matters:

Teams that track data issues usually know where the risk is. Teams that do not track them often depend on informal fixes.

5) Reporting operating model

Ask who owns the data warehouse, BI models, KPI definitions, access, and report publication. Include finance, RevOps, sales operations, IT, and business analysts.

Why it matters:

Reporting often fails because ownership is split: IT owns the pipes, finance owns the numbers, and commercial teams own the definitions. Without decision rights, fixes stall.

Decision triggers that should change the deal plan

The point of data diligence is not to produce a long defect list. It is to decide what must change before the model can be trusted.

Trigger 1: Top value assumptions cannot be reconciled to source systems

If two or more of the top five model drivers rely on offline adjustments that cannot be traced to GL, CRM, billing, payroll, or inventory systems, treat the related value lever as unproven.

What it changes:

• delay the benefit in the model
• require a pre-close baseline lock
• fund KPI and reconciliation remediation in the first 30-60 days

Trigger 2: Core KPI definitions differ across business units

If churn, gross margin, active customer, ARR, utilization, or supplier spend is calculated differently across material segments, do not combine them into one steering metric without normalization.

What it changes:

• separate reporting by segment until definitions are aligned
• slow cross-sell, pricing, or margin actions that depend on common customer and product logic
• make KPI harmonization a Day-100 workstream with a named finance owner

Trigger 3: Manual reporting controls are weak for finance-adjacent metrics

If revenue, margin, working capital, or synergy reports depend on spreadsheets with no version control, review logs, or clear owner, the first reporting cycles post-close will consume leadership time.

What it changes:

• add control remediation to Day-1 or Day-30 scope
• avoid committing to weekly executive reporting until the process is stable
• keep finance and data capacity free for reporting stabilization, not just integration projects

Trigger 4: Master data does not support the value plan

If customer, product, supplier, or employee masters are duplicated or inconsistent across ERP, CRM, HRIS, procurement, and billing systems, the value plan may be directionally right but operationally slow.

What it changes:

• move master data cleanup ahead of pricing, procurement, cross-sell, or workforce actions
• fund deduplication, ownership, and governance
• reset the Day-100 sequence around what data can actually support

Trigger 5: Reporting sits inside seller-owned or parent-owned tooling

If a carve-out depends on the seller’s data warehouse, BI tenant, shared ERP reporting layer, or parent finance team to produce management reports, the TSA is now a reporting dependency.

What it changes:

• add reporting access, data extracts, and historical data rights to TSA terms
• create a standalone reporting minimum viable product before TSA exit
• price the risk of delayed separation or duplicated reporting run-rate

What best teams do before signing

Strong deal teams do not try to fix the data estate in diligence. They make the gap decision explicit.

1) Lock the baseline before close

Pick the metrics that will decide whether the plan is working. For each, freeze:

• definition
• time period
• source system
• exclusions and adjustments
• owner
• reconciliation point

This becomes the starting line for synergy measurement and Day-100 steering. Without it, every benefit discussion becomes negotiable.

2) Build a data confidence score for the value plan

Score each major model driver on three tests:

• Traceable: can the number be followed back to source systems?
• Consistent: does the definition hold across segments and time periods?
• Actionable: does an owner control the drivers behind the metric?

Low confidence does not always mean the deal is unattractive. It means the buyer should change timing, price remediation, or avoid putting too much value in the first 100 days.

3) Create a Day-100 reporting spine

The reporting spine should be deliberately narrow. Do not rebuild enterprise analytics in the first quarter.

Include:

• weekly revenue, bookings, margin, and cash indicators
• cost and synergy baseline by owner
• customer and product cuts tied to the thesis
• data quality exceptions that block decisions
• one version of each KPI, published on a fixed cadence

The goal is not perfect analytics. The goal is a controlled set of facts that leadership can use to act.

4) Separate analytics ambition from control remediation

Targets often have a long analytics wish list: new warehouse, new BI tool, AI forecasting, customer 360, self-service dashboards.

Some of that may be valuable. Most of it should not compete with the first 100 days.

Best teams split the backlog into two buckets:

• Control work: baseline, definitions, reconciliations, access, data quality, repeatable reporting
• Value acceleration: pricing analytics, churn models, procurement analytics, sales productivity views

Control work comes first when the numbers are not trusted. Value acceleration comes first only where the underlying data is already fit for purpose.

A simple decision tree for the deal team

Use this posture before signing:

If the top model drivers are traceable, definitions are stable, and the reporting process is repeatable:
Use the current reporting stack for Day-100 steering. Add light controls and make finance the KPI owner.

If the model drivers are directionally sound but require manual reconciliation:
Keep the value case, but delay benefit timing until the baseline is locked. Fund a 30-60 day reporting control sprint.

If customer, product, supplier, or cost data is fragmented across multiple ERPs or operational systems:
Do not assume fast pricing, procurement, or cross-sell actions. Put master data cleanup and KPI harmonization before scaled value capture.

If reporting depends on seller-owned systems or parent analysts:
Treat reporting as a TSA workstream. Secure data rights, extracts, historical access, and a standalone minimum reporting stack before exit.

If management cannot reproduce the key diligence reports on demand:
Do not underwrite early Day-100 value with confidence. Rebuild the baseline, price remediation, and force an explicit investment committee call on timing.

What to do Monday morning

In the next 10 business days, force data diligence into the deal decision rather than leaving it as a post-close cleanup item.

1. Name the top 5-7 value metrics (deal lead + finance). Tie them directly to the model and the first two steering meetings after close.
2. Pull the KPI dictionary and lineage for those metrics (tech DD lead + target data owner). Include source systems, formulas, manual steps, and owners.
3. Reconcile the numbers that matter (finance + RevOps + IT/data lead). Test revenue, margin, churn or retention, supplier spend, headcount, and working capital where relevant.
4. Create a Day-100 reporting spine (integration lead + CFO sponsor). Decide which metrics will be published weekly, who owns each one, and what data quality exceptions must be visible.
5. Make one timing call before signing (deal lead + IC sponsor). Decide whether the reporting stack can carry the model as written, or whether value capture moves right and remediation becomes mandatory cash.

Data diligence is not a tour of dashboards. It is a test of whether the buyer can trust the facts that will steer the first 100 days and prove the thesis. If the facts are not ready, fix the clock before the clock fixes the deal.