Quality of Earnings Report vs. Audit: What’s the Difference?

A quality of earnings report vs audit comparison starts with a basic distinction: a quality of earnings (QoE) review evaluates the sustainability and composition of earnings, often in a transaction context, while an audit provides an independent opinion on whether financial statements are presented fairly under an applicable reporting framework. They can examine overlapping records, but they answer different questions and should not be treated as substitutes.

Call (718) 512-9660 to discuss financial reporting

Request information about financial reporting

What is a quality of earnings report meant to answer?

A QoE report is a financial diligence analysis used to understand the earnings that may be relevant to a transaction. A buyer, seller, lender, or investor may want to know whether reported earnings reflect ongoing operations, how working capital behaves, and which items require adjustment or further investigation. The exact scope depends on the engagement and the available records.

“Quality of earnings” does not mean a universal certification that earnings are good or bad. It refers to analysis of how earnings were generated and how useful they may be as a basis for evaluating a business. An analyst may examine revenue, expenses, margins, unusual transactions, accounting policies, and the timing or classification of selected items.

A QoE review often presents adjusted or normalized earnings, commonly including an estimate of adjusted EBITDA where appropriate. Adjustments should be explained and supported, not accepted merely because management labels them one-time. The report may also discuss net working capital, debt-like items, customer or product concentration, and trends that affect interpretation.

What question does an audit answer?

An audit is an independent examination of financial statements under applicable auditing standards. Its purpose is to provide an auditor’s opinion on those statements, considered as a whole, in relation to the stated accounting framework. An audit is not designed primarily to set a transaction valuation or determine the amount of earnings a buyer should use in a deal model.

An audit typically involves risk assessment, procedures to obtain evidence, testing of selected balances and transactions, consideration of accounting estimates and disclosures, and evaluation of the financial statements. The auditor’s opinion is not a guarantee that every error or fraud will be found. Nor does an unmodified opinion mean the company has no business risks or that every reported earnings figure will continue.

Some audits are required by law, regulation, contract, or financing terms; others are commissioned for specific reporting needs. The applicable framework, period, materiality, auditor independence, and engagement scope shape the work. Readers should review the actual auditor’s report rather than infer scope from the word “audited.”

How do a QoE review and an audit differ?

The distinction is about objective, not whether one process is “deeper.” A well-scoped audit may involve substantial testing, while a QoE engagement may investigate a targeted transaction issue in detail. Conversely, a QoE report does not automatically provide the assurance, independence, or formal opinion associated with an audit.

Why might a deal team request both?

Each process addresses a different information need. An audited set of statements can provide a useful historical foundation. A QoE analysis can then recast or explain earnings in ways relevant to the transaction and scrutinize items that may affect purchase price, financing, or forecast assumptions.

For example, an audit may establish that revenue and expenses are presented in accordance with the accounting framework, subject to the auditor’s opinion and scope. A QoE analyst may separately ask whether a revenue spike was tied to a nonrecurring contract, whether a cost will persist after closing, or whether an owner-related expense should be treated differently in a buyer’s model. Those are transaction questions, not necessarily audit adjustments.

Using both does not mean their conclusions will always agree. They may use different definitions, materiality thresholds, periods, samples, and assumptions. A transaction team should trace a difference to its source and establish whether it reflects a genuine error, a different analytical purpose, or a disagreement about treatment.

What does a QoE analysis examine?

The scope varies, but a review commonly works from historical financial statements, general ledger detail, trial balances, tax returns, management schedules, and other source records. The analyst may tie reported totals back to underlying records before interpreting them. The analysis may include:

• Revenue quality: trends by customer, product, service, or location; cutoff; credits; returns; and unusual concentration.
• Expense patterns: recurring operating costs, changes in classification, unusual charges, and expense completeness.
• Earnings adjustments: proposed additions or removals, with evidence, rationale, and clear treatment of items that recur.
• Working capital: seasonality, receivables, payables, inventory where relevant, and the level needed to operate.
• Cash and debt-like items: potential obligations or balances that may affect transaction economics, as defined in the engagement.
• Accounting practices: consistency of policies, estimates, cutoffs, and reconciliations across periods or entities.
• Data limitations: missing records, inconsistent classifications, weak reconciliations, or assumptions that reduce confidence.

These are common analytical areas, not a promise that every QoE report covers all of them. The engagement letter and report should specify what was reviewed, the period covered, limitations, and any procedures not performed.

How should you evaluate proposed earnings adjustments?

Do not treat an adjustment as valid just because it is described as nonrecurring, exceptional, or owner-related. Ask what happened, when it happened, where it appears in the ledger, whether cash was paid, and whether a comparable cost is likely to continue. Then record the evidence and the conclusion separately.

1. Identify the recorded item. Capture the account, period, transaction description, amount, and source document.
2. Understand the business event. Ask what drove the expense or revenue and whether it relates to normal operations.
3. Test recurrence and replacement cost. A cost may be unusual in form but still have a recurring equivalent. A role or service may continue after closing.
4. Check classification and timing. Confirm whether the item belongs in the period and account where it was recorded.
5. State the treatment. Document whether it is accepted, rejected, modified, or unresolved, with a concise reason.

Consider a one-time consulting fee. The label alone is not enough. The team should check the engagement, invoice, work performed, and whether similar advisory work is expected again. A seller may propose an add-back; a buyer may accept only part of it or conclude that ongoing replacement services make a full add-back inappropriate.

Likewise, an unusually high repair cost may be a genuine event rather than a recurring operating cost. But if equipment needs ongoing maintenance, removing all repair expense could overstate sustainable earnings. The report should distinguish evidence from judgment.

What should companies prepare before either process?

Preparation begins with consistent, traceable records. Build a schedule that ties each reported figure to the source system, account, reporting period, and supporting documentation. If several entities or accounting platforms are involved, define the reporting basis and mapping rules before combining totals.

• Reconcile bank, debt, intercompany, and major balance sheet accounts for the periods under review.
• Keep trial balances and general ledger exports for each entity and period, with clear version control.
• Document accounting policies, estimates, cutoff practices, and changes in classification.
• Prepare revenue and expense schedules that tie to the ledger; label manual adjustments and preserve their support.
• Explain unusual items with dates, amounts, counterparties, business purpose, and relevant agreements or invoices.
• Maintain a list of open items, late entries, unresolved differences, and data limitations.
• Assign an owner to each request and track what has been provided, reviewed, and revised.

For multi-entity organizations, common account names do not always mean common accounting treatment. One business may classify a cost differently or use a different period cutoff. Standardize the mapping only after confirming what the source accounts represent. Keep the original ledger detail available so an analyst can trace consolidated figures back to source records.

A reporting layer can help teams organize repeatable consolidated views while preserving the source systems and mapping rules. Helix Reports is web-based, read-only financial reporting software designed to consolidate data across entities and platforms such as QuickBooks, AppFolio, Sage, MRI, and Rent Manager. It is a reporting layer, not an audit provider or a substitute for transaction diligence. Learn more about how the reporting process works and the reports and capabilities available.

How should readers use the two reports together?

Start by establishing the purpose of each document. Identify the reporting entity, periods, accounting framework, scope, preparer, and intended users. For an audit, read the auditor’s report and accompanying notes. For a QoE report, read the scope and limitations, definitions, adjustment schedule, and data sources before relying on headline earnings.

Then reconcile important differences. A practical bridge can show:

• Audited or management-reported starting earnings by period.
• Corrections or reclassifications identified in diligence, with their evidence.
• Each proposed adjustment and the buyer’s or lender’s treatment.
• Working-capital or debt-like observations that affect deal analysis but do not change earnings.
• Items that remain uncertain, the person responsible, and the next evidence needed.

Keep a distinction between financial statement corrections and transaction adjustments. If a material error is found, discuss the accounting and reporting implications with the company’s accounting team and auditor as appropriate. A QoE adjustment schedule should not quietly become a replacement set of financial statements.

Use the audit to understand the financial statements and the auditor’s stated conclusion. Use the QoE analysis to evaluate earnings composition and transaction-specific assumptions. Neither should be read without context, and neither removes the need for professional judgment by the people making the investment or lending decision.

What questions should you ask before commissioning a QoE?

Before engaging a provider, clarify the decision the analysis must support. The answers help define a useful scope rather than a generic checklist.

• Which entities, periods, and accounting systems are in scope?
• Will the work focus on historical earnings, a particular acquisition, working capital, or specific concerns?
• How will adjusted earnings be defined, and who will review proposed adjustments?
• What source records and management representations will be used?
• How will missing information, sampling, and limitations be disclosed?
• Will the analysis include cash, debt-like items, or working-capital observations?
• How will findings be communicated, and who can rely on the report?

For an audit, questions are different: confirm the framework, period, required deliverables, auditor independence, timing, and responsibilities. If transaction diligence is also needed, define the QoE work separately so no one assumes that an audit covers it.

Call (718) 512-9660 to request information

Request information about Helix Reports

How does the difference appear in a worked example?

Imagine a multi-entity company preparing to sell one operating division. Its monthly close package shows three years of revenue, operating expenses, and earnings. The latest year includes a large customer implementation, a legal settlement, and a late invoice from a supplier. The company also operates through several entities that use different accounting systems. The audit and the QoE review may both draw on the same trial balances and invoices, but their questions diverge.

The audit work considers the financial statements as a whole under the applicable framework. It may test revenue recognition and cutoff, examine evidence for the settlement accrual, assess presentation, and evaluate whether material balances and disclosures are fairly stated. The auditor’s opinion speaks to those statements and the defined audit scope. It does not, by itself, determine whether the implementation revenue will recur or what earnings a buyer should underwrite.

The QoE analyst follows the commercial story behind the numbers. Was the customer implementation a one-time project or the start of a repeatable service line? Was the revenue recorded in the right period? What direct costs accompanied it? Is the customer still buying? The analyst may present a trend with and without the project, but must explain the basis and avoid treating a correct accounting entry as automatically recurring earnings.

The legal settlement raises a different issue. The audit may evaluate whether the liability and expense were recognized appropriately and adequately disclosed. The diligence team may ask whether the underlying dispute is resolved, whether similar claims remain, and whether insurance proceeds are collectible. A seller might propose adding back the expense as unusual. A buyer should seek the settlement agreement, counsel correspondence where available, payment evidence, and information about comparable claims before accepting that treatment.

The late supplier invoice can affect both analyses. If services were received before year-end, the relevant question may include whether the expense belongs in that period. An audit may consider the accounting treatment and its effect on the statements. A QoE review may quantify any proposed correction, recalculate earnings by period, and examine whether the same late-accrual pattern exists elsewhere. One finding can therefore have a financial reporting consequence and a separate transaction-analysis consequence.

Finally, suppose the divisions’ account mappings differ. One entity records freight in cost of sales; another includes it in operating expenses. Consolidating them without understanding the source accounts can distort gross margin comparisons even if the total expense is unchanged. A reliable analysis documents the mapping, preserves source detail, and makes the treatment consistent for comparison. The auditor and QoE team may each need to understand the mapping, but the reason for reviewing it and the form of their conclusions remain different.

What does “scope” mean in each engagement?

Scope is the boundary around what the professional is asked to do. It identifies the entities, reporting periods, records, procedures, deliverables, and users involved. Two reports with similar titles can differ substantially if one covers a single legal entity and another covers a group, or if one includes detailed working-capital analysis and another does not.

For an audit, confirm which financial statements are covered, the period-end dates, the accounting framework, and whether the report is for a consolidated group or individual entities. Read any qualifications or other explanatory language in the auditor’s report. Look at the notes and accounting policies as well as the opinion. A report that covers one entity or one period does not automatically address every affiliate, later event, management forecast, or transaction question.

For a QoE engagement, define the deal question first. A buyer assessing a business may need a view of earnings by month, customer, or product. A seller preparing for a process may want to identify documentation gaps and explain unusual items. A lender may focus on cash generation and the reliability of the earnings base relevant to repayment. These possible objectives should be stated rather than assumed.

Scope documents should also explain the period and data included. Is the analysis based on the last three fiscal years, trailing twelve months, monthly management accounts, or a selected period? Are acquisitions or discontinued operations included? Are forecasts being tested, or only historical results? Is the analyst reviewing all transactions, selected samples, or schedules supplied by management? The answer affects what the reader can reasonably infer.

Ask how limitations will be reported. Missing source data, incomplete reconciliations, inconsistent chart-of-account mappings, limited access to personnel, or compressed timing may constrain the work. A useful report names meaningful limitations instead of letting a polished summary imply broader coverage than was performed.

How do assurance and diligence conclusions differ?

An audit report expresses an opinion in a defined reporting context. That opinion is not a statement that the company is healthy, that every transaction was examined, or that future results will match historical results. It also does not decide whether the business is worth a proposed price. Readers should interpret the opinion together with the statements, notes, framework, and scope.

A QoE report generally communicates findings and analysis rather than a standardized audit opinion. It may provide a range of adjustments, identify unresolved questions, and explain how the analyst interpreted records. The exact language depends on the engagement. Do not assume that every QoE report offers the same level of assurance, uses the same definition of earnings, or is available for reliance by every party.

This difference matters when a transaction participant summarizes a report. “The company was audited” is not the same as “a buyer has tested the earnings base for this transaction.” Likewise, “the QoE found adjusted earnings of a certain amount” is not the same as an auditor’s opinion on a set of financial statements. Keep descriptions precise, and refer to the actual documents when making a decision.

It is also possible for a QoE report to identify a proposed accounting correction. The finding does not turn the QoE into an audit. The company’s accounting personnel should consider whether the underlying records or financial statements need correction and whether the auditor should be consulted. Separately, the transaction team may decide how the item affects its deal model. Those are related but distinct decisions.

How should you build a reliable earnings bridge?

An earnings bridge makes the path from reported results to a transaction-useful measure visible. It reduces the risk that people debate a headline number without understanding which entries and assumptions created it. Build it by period, use consistent definitions, and keep a source reference for every adjustment.

1. Choose the starting measure. State whether the bridge begins with net income, operating income, EBITDA, or another defined figure. Name the source statement and period.
2. Tie the starting amount. Reconcile it to the trial balance or financial statements. If the source is management reporting, say so and document any difference from audited statements.
3. List each proposed adjustment separately. Avoid combining unrelated items into a single “other” amount. Show account, date range, description, and proposed treatment.
4. Attach support. Link to invoices, contracts, payroll records, settlement documents, or other evidence, while respecting access controls and confidentiality.
5. Assess recurrence and replacement. Explain whether the item is expected to continue, recur in another form, or require replacement spending.
6. Show alternate positions. Where buyer and seller views differ, present the seller proposal, buyer response, and unresolved amount without hiding the dispute in a net figure.
7. Review consistency across periods. Apply the same logic to similar transactions in each year, or explain why a different treatment is justified.
8. Document approval and version. Identify who prepared, reviewed, and updated the bridge so later drafts do not silently change the calculation.

A simple illustrative bridge might start with reported operating earnings of 1,000 units. Management proposes adding back 40 units for a transaction fee, 25 for a one-off legal matter, and 15 for an owner expense. The analyst should not simply report 1,080. The fee may be supported by an invoice and a completed transaction, but similar advisory costs may arise in future deals. The legal matter may be resolved, yet ongoing legal costs remain part of ordinary operations. The owner expense may include personal items, but a replacement executive’s compensation could exceed the amount removed.

The bridge could therefore show each proposal and a separate conclusion: accept, reject, partially accept, or pending support. If the fee is accepted only in part, state the amount and rationale. If no reliable evidence is available for the owner expense, show the issue as unresolved rather than implying that it is verified. The number becomes more useful when readers can see uncertainty as well as arithmetic.

Keep working-capital analysis in its own schedule unless the engagement explicitly defines otherwise. A seasonal increase in receivables may affect cash needs and the working-capital peg without changing earnings. A debt-like obligation can affect transaction proceeds without changing EBITDA. Mixing these items into an earnings bridge obscures the question each one answers.

How should you analyze revenue and customer patterns?

Revenue totals can hide important differences in timing, mix, and concentration. A QoE review may examine monthly revenue, customer activity, credits and returns, contract terms, and the relationship between recorded revenue and cash collection. The purpose is not simply to reward growth or penalize volatility. It is to understand what the reported pattern represents and what evidence supports it.

Start by reconciling the revenue schedule to the ledger and financial statements. Then select useful dimensions based on the business: customer, product, service, geography, location, or contract type. Confirm that the dimensions are consistently coded. If customer names changed after a merger or system migration, build a documented crosswalk rather than treating each spelling as a new customer.

For a large late-year sale, inspect the contract, delivery or service evidence, acceptance terms where relevant, invoice, credit notes, and subsequent collection. Consider whether the activity belongs in the period under the accounting policy and whether it reflects ordinary demand. A sale can be properly recorded and still be unusual for forecasting. Conversely, a single customer may represent a recurring relationship supported by a long-term agreement. The conclusion needs evidence, not a rule based on size alone.

Compare gross revenue with credits, refunds, discounts, and returns. A rising top line paired with growing credits may tell a different story from revenue alone. Check whether manual journal entries or end-of-period adjustments are concentrated in particular months. Ask whether new billing systems, acquisitions, or changes in service mix explain apparent breaks in the trend.

Concentration analysis should be interpreted carefully. A high share from one customer is a risk to investigate, not automatic proof that earnings are unsustainable. Review renewal history, contract duration, customer activity, pipeline information supplied by management, and any known transition issues. A QoE report can describe the concentration and evidence, but it cannot guarantee what a customer will do after closing.

How do working capital and debt-like items fit?

Working capital and debt-like items are often central to transaction economics, but they answer questions different from the core audit-versus-QoE distinction. A company can report a given level of earnings while its receivables, payables, inventory, or other operating balances create a separate cash requirement. The transaction agreement may define these terms in a particular way, so the engagement’s definitions matter.

To understand working capital, first identify the relevant accounts and reconcile them to the general ledger. Review monthly balances rather than relying on a single period-end snapshot. Consider seasonality, billing cycles, collection timing, payment practices, and changes in business volume. A year-end balance may be unusually high or low and may not represent what operations typically require.

Then investigate aging and movements. For receivables, compare invoice dates, due dates, subsequent receipts, credits, and disputes. For payables, look at invoice timing, subsequent payments, and whether expenses were recorded in the correct period. If inventory is relevant, examine the basis for valuation, slow-moving items, and how the balance relates to sales. These analyses do not automatically establish a final working-capital target; they supply evidence for transaction discussion.

Debt-like items require a similarly explicit definition. Possible items can include obligations that parties agree should be treated like debt in the transaction, but classification depends on facts and negotiated terms. Do not label an item debt-like solely because it is unusual or due soon. Document the contractual obligation, accounting treatment, expected settlement, and relevant deal definition.

Keep the schedules separate and make their connection to the deal model clear. A working-capital shortfall may affect the closing adjustment. A debt-like item may affect proceeds. Neither should be counted again as an earnings adjustment without a clear rationale. A reconciliation across schedules helps prevent double counting.

How do multi-entity records affect the review?

In a group with several entities, the same word on account labels can conceal different meanings. “Repairs,” “management fees,” or “rent” may be used differently across systems. Entities may have different fiscal calendars, cutoffs, currencies, approval practices, or chart-of-account structures. Before comparing earnings, understand the source data and document how it is combined.

Create an entity inventory with the legal entity name, ownership relationship, accounting platform, reporting period, currency, and responsible finance contact. Map each source account to a common reporting category only after confirming the underlying activity. Retain the original account and entity identifiers in the working files so an analyst can trace consolidated figures back to their origin.

Reconcile intercompany balances and transactions. A management fee recorded as revenue in one entity should be understood alongside the corresponding expense in another. Differences in timing, amount, or account mapping can leave unmatched balances. Reconcile the pair, document legitimate timing differences, and identify any entries needed to present the group consistently. Do not assume that an elimination entry resolves the underlying cause.

For acquisitions or disposals during the reviewed period, state which entities and months are included. A group’s reported trend can change because its perimeter changed, not because the underlying operations improved or weakened. Show the effect of acquired operations separately when records permit, and avoid presenting a pro forma view as historical fact.

Where reporting is assembled from several platforms, repeatability matters. A stable mapping and documented close procedure make it easier to compare periods and answer diligence requests. A read-only reporting layer can organize data from existing systems without replacing those ledgers. Helix Reports provides web-based financial reporting across multiple entities and platforms; it is not an audit provider, and its reporting outputs do not replace source accounting records or transaction diligence. See how consolidated financial statements across systems are organized and why a reporting layer may fit multi-entity teams.

What common mistakes should teams avoid?

• Using the words interchangeably. An audit opinion and a QoE finding are different outputs. State which document supports each conclusion.
• Assuming audit coverage answers deal questions. Historical statement work does not automatically analyze recurrence, customer concentration, or a transaction-specific working-capital target.
• Accepting labels instead of evidence. “One-time” and “owner-related” describe proposed explanations, not proof. Trace the item to records and consider replacement costs.
• Confusing a reclassification with an earnings improvement. Moving an expense between categories may change a margin presentation but not total earnings.
• Combining unrelated adjustments. A net add-back can conceal different evidence levels, recurrence patterns, and counterarguments.
• Ignoring period consistency. Apply the same test to comparable items across years, and document exceptions.
• Overlooking source-system limitations. A consolidated report can look tidy while unresolved mappings or unreconciled balances remain beneath it.
• Double counting transaction effects. Check whether an item appears in earnings, working capital, net debt, and the purchase-price model before including it more than once.
• Reading a summary without its scope. Review definitions, source data, limitations, and intended users before relying on any headline amount.

A practical review meeting can prevent these errors. Put the audit opinion, QoE scope, earnings bridge, open diligence list, and supporting schedules side by side. For every contested item, ask: What is the recorded fact? What is the proposed interpretation? What evidence would change the conclusion? Who owns the next step? That discipline keeps discussion focused and makes uncertainty visible.

How can finance teams organize document requests?

A well-run request process saves time and preserves context. Create a secure folder structure by entity, period, and topic. Use consistent file names that identify the date range and version. Keep a request log with the request, owner, due date, status, source location, reviewer, and follow-up. Avoid sending multiple files with the same name and no indication of which is final.

When preparing exports, record the source system, report name, filters, date range, and extraction date. Preserve the unmodified export, then make analysis copies. If a schedule is revised, note what changed and why. A reviewer should be able to distinguish original source information from management adjustments and analyst calculations.

For every adjustment, make a compact support packet: a short description, ledger reference, calculation, relevant documents, business explanation, and proposed treatment. If the item has an ongoing operational substitute, include the basis for estimating that cost. If support is incomplete, mark the gap plainly and state what would resolve it.

Set a regular cadence for questions and updates. A daily stream of disconnected questions can burden a small finance team and produce inconsistent answers. Group related requests, appoint a knowledgeable owner, and log answers so that all participants use the same explanation. Escalate potential financial statement errors promptly to the appropriate accounting professionals rather than burying them in a transaction tracker.

Confidentiality is part of the process. Limit access to people who need it, follow the transaction’s handling rules, and avoid placing sensitive employee or customer information in broadly accessible folders. A clear document index can point reviewers to controlled files without duplicating confidential material unnecessarily.

Which process should you choose first?

The order depends on the decision and the current state of the records. If a company needs financial statements audited for a legal, contractual, regulatory, or financing reason, a QoE review does not remove that requirement. Engage the appropriate independent auditor and confirm the reporting framework and period.

If the immediate need is to understand earnings for a proposed acquisition or sale, define the transaction diligence question and scope a QoE review accordingly. If audited statements already exist, provide them as a starting point but do not assume they answer every deal question. If no audit exists, determine what historical financial information is available and how its limitations should be described.

Some teams benefit from parallel work when timing is tight, but coordination is essential. Agree on definitions, periods, access to records, and communication protocols. Make sure the audit and diligence teams understand which questions belong to each engagement. A shared document repository can reduce duplicate requests, while separate work programs preserve each professional’s responsibilities.

Before starting either engagement, make a one-page decision brief: the decision to be made, entities and periods involved, intended report users, critical questions, records available, deadlines, and known limitations. This brief helps prevent scope drift and gives providers a concrete basis for explaining what is and is not included.

How can a repeatable reporting process support diligence?

Transaction analysis often exposes routine reporting weaknesses: inconsistent entity mappings, late reconciliations, manually assembled schedules, and unclear adjustment histories. The goal is not to make a reporting platform stand in for professional assurance. It is to make underlying information easier to organize, compare, trace, and reproduce.

Start with a controlled source-to-report path. Define source systems and owners; establish mapping rules; document intercompany treatment; set review checks; and preserve the detail behind totals. Reuse stable configuration where appropriate, but review exceptions each period. A rule that worked last month should not silently override a new account, entity, or transaction type.

Useful checks include comparing imported totals with source trial balances, flagging unmapped accounts, identifying unexpected period-over-period changes, and reconciling intercompany activity. Assign someone to investigate each exception and record the resolution. These checks improve the reliability of the reporting process, but they do not create an audit opinion or certify the earnings assumptions used in a deal.

For teams consolidating across several companies and systems, Helix Reports is a web-based, read-only reporting layer designed to standardize and present financial data while leaving existing accounting platforms in place. It can support repeatable financial reporting; a buyer or lender still needs to define transaction diligence independently. To discuss fit, contact Helix Reports.

What questions should you ask before commissioning a QoE?

Does a quality of earnings report certify that earnings are correct?

No. It reports findings within the scope and procedures agreed for the engagement. Review the report’s definitions, evidence, assumptions, and limitations; it is not automatically an audit opinion or a guarantee.

Can an audited company still need a QoE review?

Yes. An audit and a QoE analysis serve different purposes. A transaction may call for analysis of earnings sustainability, adjustments, working capital, or other deal-specific questions beyond the objective of a financial statement audit.

Does a QoE report replace audited financial statements?

No. A QoE report is not a substitute for audited statements when an audit is required or otherwise needed. It is a separate diligence analysis, with its own scope and limitations.

Will a QoE report always calculate adjusted EBITDA?

Not necessarily. Scope and terminology vary. Confirm whether the engagement includes an adjusted EBITDA analysis, how the metric is defined, and what evidence supports each proposed adjustment.

Choose the report based on the question

An audit addresses whether financial statements are fairly presented under an applicable framework and provides an auditor’s opinion within a defined scope. A quality of earnings report examines earnings composition and transaction-specific considerations. When both questions matter, use the reports together, trace findings to supporting records, and keep accounting conclusions distinct from deal judgments.