What Is a Quality of Earnings Report? A Guide for Finance Teams

A quality of earnings report helps buyers, sellers, lenders, and investors understand whether reported earnings are recurring, supportable, and relevant to a transaction. It examines the records and assumptions behind a company’s earnings, explains proposed adjustments, and gives decision-makers a clearer basis for evaluating financial performance. It does not make the transaction decision, guarantee future results, or replace broader diligence.

Request information

What is a quality of earnings report?

A quality of earnings report, often called a QoE report, is a financial analysis commonly prepared for a business sale, acquisition, investment review, or financing decision. It usually starts with reported earnings, often EBITDA, and examines whether the amounts and trends are supported by records and useful for the transaction question. The report may review revenue, operating expenses, margins, working capital, selected balance-sheet accounts, and proposed adjustments.

The word quality does not mean that earnings are good or bad in a general sense. It refers to how well the earnings figure is supported, classified consistently, and connected to the company’s normal activities. An item described as unusual may have occurred once, but similar costs could recur later under different descriptions. A careful report explains evidence and reasoning rather than presenting one adjusted number without context.

A QoE report is not a universal template. The precise work depends on the business, the records available, the transaction timetable, and the questions users need answered. One engagement may focus on a single operating company and several years of results. Another may need to understand earnings across subsidiaries, acquisitions, or accounting systems that do not use the same account structure. Scope determines what the analysis can reasonably conclude.

Why does the report matter?

A buyer who looks only at net income may miss the operating pattern underneath it. A seller who presents an adjusted earnings figure without traceable support may face more questions or delays. A lender may need to understand which assumptions in a credit case are grounded in historical information. QoE analysis gives these readers a structured way to discuss the earnings base and identify unresolved issues before they affect a decision.

• Buyers: Test whether earnings used in a purchase model are supported and repeatable.
• Sellers: Organize financial evidence and identify documentation gaps before a sale process advances.
• Lenders: Understand the assumptions relevant to repayment capacity.
• Management: Find reporting, classification, or reconciliation issues that need attention.

The report can also improve the quality of the questions that follow. If revenue rose sharply in one quarter, the analysis can help determine whether the change reflects volume, price, timing, a new customer, or a recording issue. If expenses appear lower near period-end, it can prompt a check for late invoices or incomplete accruals. This is useful even when the finding is not a proposed adjustment. Knowing what is uncertain is part of making an informed decision.

Consider two companies that each report the same annual EBITDA. In one, monthly results reconcile to the ledger, revenue is supported by contracts and delivery records, and material adjustments have clear documentation. In the other, management has combined several systems, changed account mappings midyear, and supplied adjustments without invoices or recurrence analysis. The headline figure is identical, but the confidence a reader can place in it is not. The report helps explain that distinction.

What does a quality of earnings report examine?

Scope depends on the business, transaction, records available, and engagement agreement. Revenue analysis may look at period cutoff, credits, refunds, deferred revenue, contracts, or delivery evidence. Expense analysis may consider payroll, contractor costs, insurance, occupancy, and consistency of classifications. A margin change can reflect pricing, mix, input costs, accruals, or a mapping change, so the analyst should investigate material movements rather than assume a cause.

The report may also examine proposed adjustments. For each item, readers should be able to identify the amount, period, ledger account, supporting evidence, rationale, and effect on the earnings calculation. A historical correction, a normalization, a future cost reduction, and a projected synergy are different concepts. A hoped-for future saving is not proof that historical earnings were higher.

Balance-sheet accounts can help explain whether reported results are complete and how business activity converts into cash. Receivables, payables, accruals, inventory, and deferred revenue may matter depending on the company and deal terms. Slower collections or late-recorded invoices require investigation; neither proves a conclusion by itself. A large receivables balance, for example, may reflect ordinary billing terms, a concentration of recent invoices, delayed collection, disputed amounts, or a cutoff issue. The team needs detail and context before drawing a conclusion.

Analysis often includes more than a single annual number. Monthly or quarterly results can reveal seasonality, volatility, unusual closing patterns, and the timing of large customer projects. A trailing-period measure may be useful, but the selected period should be stated and reconciled. Readers should be able to see whether the calculation uses complete months, how the latest period compares with prior periods, and whether any major event makes the periods less comparable.

Revenue quality can involve both accounting support and the underlying business pattern. The analyst may consider customer concentration, contract duration, renewals, cancellations, credit notes, and the timing of service delivery. These facts do not automatically make revenue stronger or weaker. They help readers judge concentration and recurrence. A contract renewal signed after the period, for instance, may be relevant context but should not be silently treated as historical revenue.

Expense analysis calls for similar care. A lower expense line may reflect genuine efficiency, a missed accrual, reclassification, or a temporary deferral. A higher expense may include a nonrecurring matter, but the business might still need replacement services or staff after a transaction. Looking at a label alone is not enough; the reason, timing, evidence, and ongoing operating requirement all matter.

How should teams organize source information?

Good analysis starts with a clear record trail. Before preparing schedules, define the legal entities and reporting periods under review. Identify the authoritative source for each balance and report. If management reporting differs from the general ledger, preserve both versions and explain the bridge rather than overwriting one with the other. Record the extraction date, report parameters, currency, and any manual edits so another reviewer can reproduce the schedule.

1. Set a period and entity map. List each included company, its fiscal calendar, accounting system, and the periods provided. Note acquisitions, disposals, entity changes, or changes in year-end.
2. Collect the base records. Gather trial balances, general ledger detail, financial statements, account mappings, reconciliations, and supporting schedules for the same periods.
3. Tie totals before interpreting them. Reconcile the management reporting package to the relevant ledger and identify missing accounts, period differences, and manual journal entries.
4. Preserve detail and provenance. Keep source files intact, name versions consistently, and record report settings, filters, owners, and changes to working schedules.
5. Build explanations alongside the numbers. For major movements, identify the driver, evidence, preparer, and open question rather than waiting until the end to reconstruct the story.
6. Track open items. Assign each request to an owner, note the period and account affected, and record whether the response resolved the question or needs follow-up.

This preparation is about making records complete, traceable, and explainable, not making the numbers look better. A controlled reporting process can help a finance team create consistent schedules across entities and source systems. For example, consolidated financial reporting across systems can give a team a repeatable base for assembling entity results; transaction-specific QoE procedures still need to be scoped and performed for the deal.

Where several systems or entities are involved, keep a mapping table that shows source account, reporting account, entity, and effective date. A mapping change may alter presentation even when underlying activity did not change. Preserve old mappings and document why a new rule was made, who reviewed it, and which periods were affected. This makes it easier to distinguish an operational change from a presentation change.

How does QoE analysis differ from an audit?

An audit is designed to express an opinion on financial statements under an applicable framework and professional standards. A QoE analysis is commonly transaction-focused and concentrates on earnings and financial trends relevant to the agreed diligence question. Scope, procedures, intended users, and conclusions depend on the engagement. Do not assume that a QoE report provides the same assurance as audited statements. Audited statements can be useful inputs, but they may not answer every transaction-specific question.

The work products may use overlapping financial data, but their questions differ. An audit reader asks whether the financial statements are presented fairly in the context of the applicable framework and audit scope. A transaction reader may ask whether a particular earnings measure is supported, what adjustments should be considered, and whether period trends are consistent. A valuation reader asks how a set of assumptions and methods lead to an estimate. None of those questions can be answered simply by substituting one document for another.

When a company has audited statements, the QoE team can use them as a starting point and then investigate areas relevant to the transaction. When statements are unaudited, readers should understand what records and procedures support the analysis and what limitations follow. The point is not to rank one engagement as universally better. It is to understand the purpose and boundaries of each piece of work.

How does the process work?

1. Define scope. Identify the entities, periods, earnings measure, intended readers, and decision to be supported. Clarify whether the work includes selected balance-sheet or working-capital procedures.
2. Collect source records. Gather financial statements, trial balances, general ledger detail, reconciliations, mappings, and relevant supporting schedules.
3. Reconcile totals. Tie management reports to the ledger and investigate differences in period, entity, or classification.
4. Analyze trends. Review revenue, margins, expenses, and relevant balance-sheet accounts across periods.
5. Evaluate adjustments. Inspect evidence, consider recurrence, and separate historical amounts from forecasts and synergies.
6. Discuss findings. Ask management or relevant record owners to explain material movements and provide missing support. Keep the question and response documented.
7. Document conclusions. Explain assumptions, limitations, unresolved questions, and the basis for each material finding.
8. Connect findings to decisions. Determine which issues affect the transaction model, require additional diligence, or are simply useful context.

The sequence is iterative. A trend review can reveal a gap in source records; a ledger tie-out can change the period used for a proposed adjustment; a management explanation can lead to a request for a contract or invoice. Maintain a question log rather than treating the process as a one-time data upload. For each request, state what is needed, why it matters, the owner, and the date received. A response that does not answer the question should remain open.

At the outset, agree on communication and review practices. Decide who can provide source records, who approves management schedules, and who can explain accounting choices. Establish a secure way to exchange files and keep a record of updates. If multiple teams work on the analysis, clarify which schedule is the current version and how changes are communicated. These basic controls reduce confusion, especially when the timetable is compressed.

How should readers assess proposed adjustments?

A label such as one-time expense or owner cost does not make an item nonrecurring. Trace it to the ledger, confirm the period and entity, understand its business purpose, check whether similar costs occur in other periods, and consider what resources a buyer would need after closing. Keep forecast savings separate from historical earnings. Avoid double-counting an item that was already excluded or offset elsewhere.

For each proposed adjustment, a reader can use a consistent test:

1. What is the exact amount? Identify the account, period, entity, and calculation. Confirm whether the figure is gross or net of related credits.
2. What evidence supports it? Look for invoices, payroll detail, contracts, bank records, board materials, or a reconciliation that fits the item.
3. Why is it unusual? Explain what happened and why it is not part of the expected cost of operating the business.
4. Could the cost recur? Search other periods and ask whether the underlying activity or need continues under another name.
5. What replaces it? Consider whether the buyer or ongoing company must incur another cost to perform the same function.
6. Has it already been reflected? Check whether it was booked outside the selected earnings period, excluded elsewhere, or offset by an associated benefit.

For example, a professional fee described as a one-time project cost should be supported by invoices and a description of the completed work. If similar services will continue after closing, removing the full expense may not describe the ongoing business. If the invoice covers several periods, the analyst should also consider the correct period allocation. The conclusion depends on evidence and context, not the label in a schedule.

Owner-related expenses need the same disciplined treatment. A payment to an owner may be personal, business-related, or a mixture. The record should establish what was purchased and whether the business needs that service after the transaction. If the owner performed a role that must be filled, the replacement cost is relevant to the ongoing earnings discussion. Simply deleting the expense without considering the work performed can overstate normalized earnings.

One-time revenue deserves scrutiny too. A single large project may be valid historical revenue but may not recur at the same level. Conversely, a customer may have a recurring relationship even when invoices vary by project. Readers should distinguish whether the question concerns accounting recognition, customer continuity, or forecast expectations. Those are related but not interchangeable judgments.

Suppose a company claims a $40,000 adjustment for a legal matter. A useful review would ask which invoices make up the amount, whether the expense appears in the ledger, what matter it relates to, whether the matter is resolved, and whether similar legal costs occur in other periods. It would then consider whether ordinary legal support remains necessary in the ongoing business. The arithmetic may be straightforward; the reasoning behind treating the expense as exceptional is the substantive issue.

What do earnings trends reveal?

Trend analysis gives a reader context that a single adjusted total cannot provide. Compare monthly or quarterly revenue, gross margin, operating expenses, and earnings across periods. Use consistent definitions where possible and identify differences that cannot be normalized. If the business has a seasonal cycle, compare like periods rather than assuming each month should look alike. Record whether a period contains an acquisition, disposal, new product, or material customer change.

Ask what drove each meaningful movement. Revenue growth might reflect higher volume, pricing, a change in product or customer mix, or a transaction that shifted the entity perimeter. A margin decline might follow higher input costs, discounts, delivery costs, or an accounting reclassification. The report should not present a causal explanation as fact unless supporting records and discussions support it. Where evidence is incomplete, label the explanation as an open question.

Monthly patterns can also expose cutoff and accrual questions. If revenue consistently spikes in the final days of a period, check the underlying delivery or service evidence and the applicable recognition policy. If expenses are unusually low at quarter-end, review invoice timing and accrual practices. A pattern is a signal to investigate, not a conclusion that something was recorded incorrectly.

Readers should compare performance measures with cash conversion where that is relevant to the transaction. Earnings and cash movement differ for many reasons, including receivables, payables, inventory, capital spending, taxes, and financing. A profitable period can coincide with slower collections or large working-capital needs. This does not mean the earnings figure is wrong, but it may affect the capital required to operate the business and the questions that belong in diligence.

How do multiple entities affect the analysis?

A group may use different accounting systems, account names, fiscal calendars, and reporting conventions. The team should establish which records belong to each legal entity, document mappings, and preserve the source detail behind consolidated totals. Intercompany balances need review for reciprocal amounts, timing differences, and elimination treatment. A difference should be investigated, not erased merely to make totals tie.

Imagine a parent company and two operating subsidiaries that record shared payroll and management costs differently. Before analyzing group earnings, the team needs to understand which entity incurred each cost, whether allocations are consistent, and whether intercompany charges eliminate in consolidation. If one entity reports a charge but the other has not recorded the corresponding amount, the mismatch may reflect timing, an incomplete entry, or a classification issue. A clean consolidated total can conceal the question unless the supporting detail is retained.

Acquisitions and disposals create another comparability challenge. Determine when the acquired business entered the reporting perimeter and whether historical periods include comparable operations. A simple year-over-year comparison can mislead if one period includes a full year of an acquired entity and the other includes only part of a year. Any pro forma view should be identified as such and its assumptions kept separate from historical reported results.

Teams can use a structured intercompany reconciliation workflow to make reciprocal balances and elimination differences easier to inspect. A repeatable reporting workflow can also help connect, standardize, reconcile, and present information from different systems. Those reporting capabilities support data organization; they do not replace transaction-specific analysis or determine whether a proposed adjustment is appropriate.

What common preparation problems slow the work?

One common problem is supplying a polished summary without the underlying ledger detail. A summary may be useful for orientation, but reviewers need to trace material amounts to records and understand how the schedule was constructed. Provide the source and the calculation, not just the result.

A second problem is inconsistent periods. Management may provide a calendar-year income statement, a fiscal-year trial balance, and a monthly schedule with a different cutoff. Label the period on every file and reconcile the differences. Do not combine the schedules until the dates and entity coverage are clear.

A third problem is unexplained mapping changes. If expense categories have been recoded, preserve the old and new mappings and document the effective date. Otherwise, a reported trend may reflect the chart of accounts rather than a real change in spending. Similarly, if a new accounting system was introduced, note conversion balances, opening adjustments, and any reports that do not cover the same basis.

Late or incomplete accruals can also distort comparisons. If invoices arrive after close, document the accrual process and whether subsequent information changed prior-period results. A material late adjustment should be shown with its period and reason. The goal is not to assume that every late entry is a problem, but to make the process visible to the reader.

Finally, avoid treating a request list as a substitute for an organized response. Use consistent filenames and include entity, period, and schedule type. Mark whether a file is a source extract, management-prepared schedule, or supporting document. Keep a change log when replacing a file, and state what changed. This reduces the risk that the analysis relies on a stale version or an unexplained manual edit.

How can repeatable reporting help before diligence?

Ongoing financial reporting and QoE work have different purposes, but a repeatable reporting process can make the source information easier to prepare and review. When entity results use consistent mappings, reconciliations, and period definitions, a finance team can spend less time reconstructing the same schedules and more time explaining material changes. That preparation does not create assurance or guarantee that transaction questions will not arise.

Helix Reports is positioned as a read-only financial reporting layer that works with existing source systems; it is not an audit or QoE engagement. Teams that need recurring multi-entity reporting can review the reports and capabilities included with Helix Reports and determine whether those reporting needs match their workflow. The relevant distinction is between organizing repeatable financial information and independently assessing transaction-specific earnings evidence.

A useful readiness exercise is to select one prior reporting period and test whether another finance professional can reproduce its totals. Can that person identify the source files, mappings, eliminations, adjustments, and reviewer sign-offs? Can they explain a large variance without relying on undocumented knowledge held by one employee? Gaps uncovered in this exercise do not necessarily mean reported earnings are wrong. They show where documentation or process consistency may need work before a high-pressure diligence request.

What questions should readers ask?

• Which entities and periods are included?
• What earnings measure is used, and how does it tie to the underlying records?
• What procedures were performed, and what are the stated limitations?
• Which adjustments were accepted, rejected, or left unresolved?
• Are periods comparable after acquisitions, seasonality, or account mapping changes?
• How are revenue cutoff, credits, and material customer changes addressed?
• What assumptions affect the treatment of owner costs or expenses described as unusual?
• How do working-capital movements relate to the earnings trend?
• What additional information would resolve the remaining questions?
• How will the findings affect the transaction model or the next diligence request?

Read the qualifications and scope, not only the executive summary. If a material assumption is unclear, ask the preparer to explain it before using the number in a decision model. Separate what the report demonstrates from what management expects to happen. QoE analysis is one input among many; it does not replace legal, tax, operational, market, or commercial diligence.

It can also help to keep a decision log. For each material issue, record the finding, evidence, management response, remaining uncertainty, and the person responsible for deciding what to do next. A decision log does not eliminate judgment. It keeps the judgment visible and makes it less likely that a contested assumption disappears from discussion as the transaction moves forward.

Frequently asked questions

Is a quality of earnings report the same as adjusted EBITDA?

No. Adjusted EBITDA may be a measure in the report, while the report is the broader analysis of earnings, adjustments, trends, evidence, and limitations.

Can a quality of earnings report guarantee future earnings?

No. It analyzes historical information and assumptions within a defined scope. It cannot ensure future performance or market conditions.

Does every proposed adjustment belong in adjusted earnings?

No. Each item needs support and a reasoned assessment of recurrence, business purpose, and ongoing replacement costs. Labels alone are not enough to establish that an amount should be excluded.

Can ongoing financial reporting replace QoE work?

Not necessarily. Recurring reporting can make data more consistent and traceable, but transaction diligence has its own purpose, scope, and procedures.

What should a finance team prepare first?

Start by confirming the entities, periods, and authoritative records in scope. Then assemble reconciled trial balances, ledger detail, mappings, financial statements, and support for material movements and proposed adjustments.

Request Helix Reports information

A quality of earnings report is most useful when its conclusions can be traced to consistent records, clearly explained adjustments, and a scope that matches the decision at hand.