Quality of earnings for distributors: why clean order and margin data matters

What does a QoE review test at a distributor?#

A QoE review at a distributor tests whether reported earnings reflect repeatable operations, and it concentrates where distribution margins are made and lost: pricing, product cost, vendor rebates, freight and returns. The reviewer normalizes EBITDA for one-time items and checks whether gross margin trends hold up by customer and product line.

Net working capital gets equal attention. Inventory valuation and reserves, receivables aging and supplier terms all feed the working capital target in the purchase agreement, and each is tested against transaction detail rather than summary reports.

This is general information, not accounting or tax advice. QoE scope varies by provider and transaction, so confirm the request list with your advisors early.

QoE data requests and the ERP reports that answer them#

QoE data requests at a distributor are predictable, and most can be answered from standard ERP reports when the underlying data is clean. Preparing these extracts before a provider is engaged shortens the back-and-forth that slows diligence.

Produce every extract from the same cut of data with a fixed as-of date, and say so in the file name. When monthly sales from one request and margin by SKU from another start from different dates, the reviewer spends time reconciling your files to each other instead of testing the business.

Why SKU margin rarely ties out on the first try#

SKU margin rarely ties out on the first try because distributors record revenue at the invoice line but book many costs and credits elsewhere. The reviewer then sees a gap between margin built from invoice lines and margin in the financial statements, and every unexplained gap invites a question or an adjustment.

None of these causes means the earnings are wrong. They mean the bridge between transaction data and the ledger has not been written down, which is work the company can do before a reviewer asks.

• 1Cost at the time of sale was overwritten by a later standard or average cost.
• 2Vendor rebates were booked as a lump sum to cost of goods sold, not allocated to items or customers.
• 3Inbound freight, outbound freight and fuel surcharges were coded inconsistently across periods.
• 4Credit memos were issued without a link to the original invoice.
• 5Drop-ship and special orders used placeholder item codes.
• 6Year-end inventory adjustments posted to cost with no item detail.

Cleaning order and margin data before diligence#

Cleaning order and margin data before diligence means making each extract reproducible and the bridge between invoice lines and the ledger explicit. The goal is not perfect data; it is data where every difference has a documented reason.

Keep the outputs in a data room folder with a short note per file explaining the source, date range and known limitations. Reviewers tend to trust a clearly labeled limitation more than a number that changes between requests.

• 1Reconcile invoice-line revenue to GL revenue for every month in scope and save the bridge.
• 2Confirm that cost on historical invoice lines reflects cost at the time of sale.
• 3Document the rebate method: which programs, how they are accrued, and how they are allocated to products or customers.
• 4Link credit memos to original invoices where the ERP allows, and code the reason.
• 5Merge or map duplicate customer and item records with a crosswalk.
• 6Record each extract's query or report settings so it can be rerun on request.

Who prepares the data inside the company#

The data work behind a distributor QoE usually falls to the controller, supported by whoever administers the ERP. The controller owns the ledger bridge and the narrative for each adjustment; the ERP administrator writes and documents the extracts so they can be rerun the same way each time.

Two other people matter more than most owners expect. The purchasing manager usually understands the supplier rebate programs better than anyone in finance, and the operations or transportation lead knows how freight is billed, recovered and coded. Involve both early, because rebates and freight are where reviewers ask the most follow-up questions at distributors.

How order data quality shows up in the deal#

Order data quality shows up in the deal through the questions it prevents or creates. Clean, reconciled detail lets the buyer's team test margin and working capital quickly; gaps lead to more requests, conservative assumptions in the buyer's model and, sometimes, adjustments to EBITDA or the working capital target.

It also affects the documents. Representations about financial statements, inventory and customer contracts are easier to give, and to stand behind, when the transaction detail behind them is organized. Ask your advisors how specific findings could affect price or terms in your situation.

Illustrative: a roofing supply wholesaler prepares for a sale#

Illustrative: a fictional roofing and exterior products wholesaler with branches in several metro areas runs an on-premises ERP for orders and invoicing and tracks supplier rebate programs in spreadsheets kept by the purchasing manager. The owners plan a sale, and the CFO commissions a sell-side QoE.

The first margin-by-SKU extract fails to tie to the income statement because rebates sit in one cost account and freight is split across several expense lines. The CFO rebuilds rebate allocations by supplier program and product line, recodes freight going forward and writes a bridge for prior periods.

When the buyer's advisors arrive, the data room holds reconciled invoice-line extracts, the rebate method and the bridge. Their questions shift from whether margin is real to why it differs by branch, which the owners can answer from their own records.

Where clean distribution data goes after the deal#

Clean order and margin data keeps its value after the transaction. The same reconciled history supports pricing work, demand forecasting and AI projects, and it can be relevant to data licensing when orders link to credits, notes and outcomes across a long stretch of history.

SourceX assesses that kind of history with the SourceX Enterprise Data Value Framework, in which data cleanliness, scale, recency and rights raise value, and preparation cost and privacy burden lower net value. A data license would typically come up in diligence, so plan its exclusivity and term with a future sale in mind.