Forecast vs Projection Under SAE 3400: How CAs Examine Prospective Financial Information

Budgets, forecasts and financial projections are often grouped together in business discussions, but SAE 3400 draws an important line between a forecast and a projection. That distinction affects the assumptions management may use, the purpose for which the information is suitable, the evidence a chartered accountant examines and the wording of the final assurance report.

ICAI lists SAE 3400, The Examination of Prospective Financial Information, in its current Engagement and Quality Control Standards repository. The detailed requirements are in the official SAE 3400 text.

What is prospective financial information?

Prospective financial information is financial information based on assumptions about events that may occur in the future and possible actions by an entity. It may comprise complete financial statements or only selected elements, such as a cash-flow statement prepared for a lender. SAE 3400 says it can take the form of a forecast, a projection, or a combination of both.

Management remains responsible for preparing and presenting the prospective financial information, identifying its sources, setting out the basis of the forecast or projection and identifying and disclosing the underlying assumptions. The accountant's examination is designed to enhance credibility; it does not transfer responsibility for the future information to the accountant.

Forecast vs projection: the core difference

Forecast

A forecast is based on best-estimate assumptions: assumptions about future events that management expects to occur and actions management expects to take as of the date the information is prepared. A normal operating forecast may therefore use expected sales volumes, contracted prices, approved hiring plans, current borrowing terms and management's expected collection pattern.

Projection

A projection uses hypothetical assumptions, or a mixture of best-estimate and hypothetical assumptions. The hypothetical events or management actions are not necessarily expected to occur. A projection is therefore a what-if analysis showing the possible financial consequences if the stated scenario occurs.

For example, a company may currently operate one plant but prepare a five-year projection assuming that a second plant is commissioned next year and sales capacity rises materially. If the expansion is not yet an event management actually expects to occur, the model is a projection rather than a forecast.

Why the distinction matters in practice

• Nature of assumptions: a forecast is anchored in management's current best estimates; a projection can deliberately model hypothetical conditions.
• User interpretation: a projection must be read as a scenario, not as management's prediction of what will happen.
• Examination approach: the accountant evaluates whether best-estimate assumptions are not unreasonable and whether hypothetical assumptions are consistent with the stated purpose and are not clearly unrealistic.
• Reporting: the report must contain appropriate caveats about achievability, and a projection should make its intended purpose and hypothetical nature clear so users do not apply it to an unsuitable purpose.

What assurance does SAE 3400 provide?

Future events have not occurred and may never occur, so evidence about them is inherently different from evidence about historical transactions. SAE 3400 therefore states that the accountant is not in a position to express an opinion that the forecast or projection results will actually be achieved.

When reporting on the reasonableness of management's assumptions, the standard provides for a moderate level of assurance expressed in negative-assurance form. Separately, the report includes an opinion on whether the prospective financial information is properly prepared on the basis of the assumptions and presented in accordance with the relevant financial reporting framework. The report also warns that actual results are likely to differ, potentially materially, from the prospective information.

A practical examination workflow

1. Clarify purpose and users. Before accepting the engagement, understand whether the information is for internal use, a lender, investors or another defined audience; whether distribution is general or restricted; the period covered; and whether the model is a forecast, projection or combination.
2. Reject an unsuitable premise. SAE 3400 says the engagement should not be accepted, or should be withdrawn from, when assumptions are clearly unrealistic or the prospective information is inappropriate for its intended use.
3. Understand the business and forecasting process. Evaluate how the entity develops assumptions, the people involved, internal controls over the model, supporting documentation and the accuracy of prior prospective information where available.
4. Test the assumption base. For best-estimate assumptions, assess the source and reliability of supporting evidence using relevant internal and external information. For hypothetical assumptions, check that significant consequences of the scenario have been incorporated and that the assumptions fit the intended purpose.
5. Check model mechanics and consistency. Recompute important schedules and test whether linked assumptions are internally consistent. If sales growth requires capacity beyond the existing plant, the model should also reflect the investment or alternative costs needed to deliver that volume.
6. Focus on sensitive variables. Identify assumptions where a reasonable change could materially alter the result, such as selling price, volume, interest rate, foreign-exchange rate, collection period or project completion date, and assess whether the related uncertainty and sensitivity are adequately disclosed.
7. Obtain written representations. Management representations should cover the intended use, completeness of significant assumptions and management's responsibility for the prospective financial information.
8. Review presentation and disclosures. Confirm that assumptions, accounting policies, preparation date, uncertainty and any range used are presented clearly and not misleadingly.

Worked example: lender forecast vs expansion projection

Assume a manufacturer seeks a working-capital facility. Management prepares a 12-month cash-flow model using signed customer orders, current production capacity, approved salary budgets and expected collection periods. If those assumptions represent management's actual expectations, the information is a forecast.

Management also asks what cash generation could look like if a proposed new plant becomes operational after six months, even though final approval has not yet been obtained. That second model is a projection because it includes a hypothetical expansion assumption. The projection should reflect the consequences of that assumption, such as plant investment, additional staffing, ramp-up time and financing costs, rather than increasing revenue alone.

The accountant examines the evidence supporting the assumptions and the model's preparation, but does not certify that either set of future numbers will occur.

Common mistakes to avoid

• Calling every future model a forecast even when it contains material hypothetical assumptions.
• Presenting a projection without clearly stating its intended use and what-if assumptions.
• Testing spreadsheet arithmetic but not challenging the assumptions that drive the numbers.
• Using aggressive sales growth without reflecting the capacity, working-capital or financing consequences.
• Extending the forecast period beyond the horizon for which management has a reasonable basis for its assumptions.
• Giving users the impression that the accountant guarantees the achievement of future results.
• Failing to disclose sensitivity where material assumptions are subject to a high degree of uncertainty.

File checklist for a CA firm

• Engagement purpose, intended users and distribution restrictions.
• Clear classification of the information as forecast, projection or a combination.
• Assumption register identifying best-estimate and hypothetical assumptions.
• Support for key assumptions from historical data, contracts, budgets, external data and board-approved plans where relevant.
• Back-testing of prior forecasts where useful and explanations for significant past variances.
• Model checks, sensitivity analysis and evidence that important interdependencies have been considered.
• Management representations and approval of the prospective financial information.
• Final report containing the required assurance wording, opinion, intended-use references where applicable and achievability caveats.

Practical takeaway

The simplest way to distinguish the two is to ask what the assumptions mean. If they reflect what management currently expects to happen, the model is a forecast. If they deliberately ask what would happen under events or actions that are not necessarily expected, the model is a projection. Under SAE 3400, a strong examination goes beyond checking formulas: it tests the credibility or purpose-consistency of assumptions, their consequences, the model's preparation, disclosures and the boundaries of the assurance being given.