Blog · How-to guides · Finance and FP&A teams
Choose forecasting tools around the decision, the files you have and the evidence needed to trust a forecast. Compare approaches, work a sales-and-cash evaluation, and check whether saved versions can be reconciled to actual results.
Forecasting tools for business should be chosen by the decision they support, the files they can use and the checks they let a reviewer repeat. A useful evaluation compares saved forecasts with actual sales and cash results at the same horizon. A polished output matters only after its figures reconcile.
Write the question as a decision: whether to change a purchasing commitment, adjust a revenue outlook or arrange funding before a payment date. Then name the forecast owner, the target period and the date the decision must be made. Those choices determine the required level of detail.
Do not group every forward-looking task together. Preparing an estimate, collecting departmental submissions, displaying an approved outlook and explaining a miss are separate jobs. A company may need more than one approach because the people and evidence differ.
Inspect the history before selecting a method. NIST's introduction to time series analysis identifies trend, seasonality and dependence over time as structures to consider. A purchase decision driven by seasonal units needs a different evaluation from a payment schedule driven by known due dates.
The table describes selection criteria, not claims that every product in a category has the same features. Ask each provider to demonstrate the required work on your files.
| Approach | Choose it when the main job is | Files to bring | Evidence to request |
|---|---|---|---|
| Spreadsheet | Inspect a manageable set of drivers and formulas | Sales history, assumptions and period calendar | Visible formulas, saved inputs and reconciled totals |
| Planning workflow | Coordinate contributions and approvals | Cost-center or business-unit submissions | Version identity, contributor responsibility and approval evidence |
| Reporting tool | Distribute repeatable views of approved numbers | Approved forecasts and matching actuals | Correct filters, stable definitions and totals tied to exports |
| File analysis | Compare exported versions and explain computed differences | Forecast snapshots, ledger exports and cash schedules | Row-level support for changes, errors and reconciliation exceptions |
Microsoft documents Excel forecasting functions for estimating future values from historical data, including exponential smoothing. That is a concrete calculation option. It does not settle whether the business also needs coordinated submissions or an explanation of movements between approved versions. Covirage is not affiliated with Microsoft.
For specialized requirements, use the separate guides to demand forecasting software, sales forecasting software and inventory forecasting software. Their operational questions belong in those evaluations rather than in a general finance checklist.
Ask finance for approved forecast snapshots, closed actual sales and actual cash receipts. Each forecast needs an issue date and target period. Keep the forecast amount separate from any later adjustment, and distinguish invoiced or recognized sales from receipts.
Use the same business units and periods for every candidate. A method that omits a difficult segment cannot fairly be compared with one that covers the entire company. Record missing rows and unmatched identifiers before calculating any accuracy measure.
Reserve outcomes that were unknown when the forecasts were produced. The authors of Forecasting: Principles and Practice describe evaluation on new observations and rolling forecast origins. Use that principle in a business evaluation: no candidate should receive information that would have arrived after the decision date.
An illustrative US industrial supplier compares a baseline and a challenger for monthly sales. Each forecast was saved at the same lead time, before that month's actual was known. The amounts below are illustrative submitted outputs; the test measures their errors rather than deriving the forecasting methods themselves.
| Target month | Baseline sales forecast (USD) | Challenger sales forecast (USD) | Actual sales (USD) | Baseline absolute error (USD) | Challenger absolute error (USD) |
|---|---|---|---|---|---|
| July 2026 | 100,000 | 90,000 | 95,000 | 5,000 | 5,000 |
| August 2026 | 200,000 | 230,000 | 220,000 | 20,000 | 10,000 |
| September 2026 | 150,000 | 130,000 | 140,000 | 10,000 | 10,000 |
| Total | 450,000 | 450,000 | 455,000 | 35,000 | 25,000 |
Absolute error = Absolute value of Forecast − Actual.
Weighted absolute percentage error = Sum of absolute errors / Sum of actuals.
The baseline's error ratio is 35,000 / 455,000 = 7.7%. The challenger's is 25,000 / 455,000 = 5.5%. The reduction in absolute error is (35,000 − 25,000) / 35,000 = 28.6%. All percentages are rounded to one decimal place.
Both forecasts total $450,000, so both have a signed total error of 450,000 − 455,000 = −$5,000. Looking only at the quarter total would miss the difference in monthly performance. The challenger improves August in this example; it does not improve every month.
This is a useful acceptance exercise, not enough evidence for a universal winner. Repeat it over additional saved origins and the lead times that matter to the company. Inspect the expensive misses as well as the average result.
The same supplier also evaluates its existing cash-receipts forecast. These amounts represent customer payments received, not sales recorded in the income statement.
| Target month | Forecast receipts (USD) | Actual receipts (USD) | Signed error (USD) | Absolute error (USD) |
|---|---|---|---|---|
| July 2026 | 80,000 | 85,000 | -5,000 | 5,000 |
| August 2026 | 180,000 | 160,000 | 20,000 | 20,000 |
| September 2026 | 120,000 | 130,000 | -10,000 | 10,000 |
| Total | 380,000 | 375,000 | 5,000 | 35,000 |
Receipts have a 35,000 / 375,000 = 9.3% absolute error ratio, rounded. The total signed error is only $5,000, but the August overestimate is $20,000. Treasury should inspect that month's collection assumptions before deciding how much funding is available. Do not add sales and receipt errors together: they measure different events.
Use mandatory conditions before scoring preferences. Require a recoverable forecast version, an agreed actuals definition, visible missing inputs and a total that reconciles. If the trial cannot meet a condition, request the missing evidence before drawing a conclusion.
Then assess the daily work. Can a cost-center owner explain an assumption? Can finance reproduce the approved outlook? Can treasury distinguish a receipt delay from a revenue change? Record the time needed to answer those questions during the evaluation instead of accepting a generic productivity claim.
Keep the budget as its own baseline. The budget versus forecast comparison explains why an approved target and an updated expectation should remain identifiable. A tool evaluation should preserve both even when the display combines them.
Upload saved forecast versions and matching sales or cash-result files; Covirage maps the columns, and its tools compute and check the comparisons. The external AI model explains the results with every figure traced to its rows, giving your team evidence to review alongside its forecasting process. Create a free Covirage account and bring a sample of your own data.
See Covirage forecast analysis for the supporting use case.
Start with reproducibility: can the team recover the inputs, issue date, assumptions and result for a past forecast? The next requirements depend on the job. Coordinating submissions, calculating a baseline and explaining a revenue miss need different capabilities, even if all are called forecasting.
Yes. A spreadsheet can hold assumptions, formulas and comparisons for a defined business question. Agree on ownership, protect approved snapshots and test totals against source files. Whether it is sufficient depends on the number of contributors, review needs and complexity of the decisions.
Use the company's own historical files and forecasts issued before the actual results were known. Require matching scope, periods, horizons and currencies. Compare errors with a simple baseline, inspect exceptions, and have the responsible business users explain how they would act on the output.