Financial model review
Revenue forecast checks for financial models
Check revenue forecasts in Excel with worked examples for volume, price, discounts, seasonality and collection timing, plus a practical review checklist.

To check a revenue forecast, rebuild one period from its business drivers, trace deductions and confirm that the timing matches what is being sold. Then change one input and predict the result before opening Excel. A smooth growth chart cannot tell you whether sales were counted twice or whether customers can actually receive the forecast volume.
Work in a separate review copy. The examples below are invented planning exercises with explicit assumptions, not recommended growth rates or a revenue-recognition policy.
Define what the revenue row represents
Write a plain-English definition beside each revenue stream. For example: units delivered during the month, multiplied by price per unit, less the specified discounts and expected returns. State currency, units, tax treatment and period. A row labelled Sales might otherwise mix orders, deliveries, invoices and payments.
The IFRS Foundation's IFRS 15 overview connects revenue recognition to satisfying promises to customers. A forecast therefore needs an explanation of when goods or services are transferred; a signed order or cash receipt alone does not establish revenue for every arrangement. Complex contracts need their own accounting assessment.
Separate recurring subscriptions, one-off projects and product sales when they use different drivers. Multiplying the same customer count by three prices may accidentally count three purchases where the business expects only one.
Rebuild gross-to-net revenue for one month
Assume a simple product model has these monthly inputs:
- Units delivered: 1,200.
- List price: EUR 50 per unit, excluding sales tax.
- Discount: 5% of gross sales.
- Returns allowance: 2% of the amount remaining after discounts.
- No other deductions, revenue streams or recognition adjustments.
The independently expected result is:
Gross sales = 1,200 × 50 = EUR 60,000
Discounts = 60,000 × 5% = EUR 3,000
Sales after discounts = EUR 57,000
Returns allowance = 57,000 × 2% = EUR 1,140
Net revenue = 57,000 - 1,140 = EUR 55,860
Follow the model's formulas through each line. If returns are calculated on gross sales instead, the result becomes EUR 55,800. That EUR 60 difference is not automatically a spreadsheet defect: first confirm the intended contractual and modeling basis. The important check is that the definition, assumption labels and formula agree.
Also inspect whether the input price is already discounted. Applying a second discount to a net price understates revenue. Conversely, adding a gross-sales subtotal and its component products together overstates it.
Check growth at the driver level
Volume growth and price growth interact. In a separate example with no deductions, revenue of EUR 50,000, volume growth of 10% and price growth of 5% produce:
Next-period revenue = 50,000 × 1.10 × 1.05
= EUR 57,750
Combined growth = 15.5%
Adding the two percentages gives 15%, which misses their interaction. Applying another 10% revenue uplift after the volume increase gives EUR 63,525 and counts that volume growth twice, if no separate driver justifies it.
Trace each growth assumption to the formula where it belongs. A top-level override may be intentional, but its relationship to the underlying drivers should be documented. See the embedded-assumptions guide for reviewing numbers hidden inside formulas.
Check the period of the percentage too. An annual growth assumption should not be applied in full to every monthly column. Decide whether the forecast uses compound growth, annual step changes or a different documented approach, then verify that the formulas implement it.
Reconcile seasonality and operational limits
If an annual forecast is allocated using monthly weights, their sum should be 100%. With annual sales of EUR 600,000 and a January weight of 8%, January receives EUR 48,000. Weights totaling 110% allocate EUR 660,000 before any other adjustments.
Check whether seasonality redistributes an annual total or changes the underlying monthly demand. Applying both a weighted allocation and a second seasonal multiplier can repeat the same effect. Compare the twelve-month sum with the controlling annual figure.
Now connect demand to capacity. If the model forecasts 1,200 deliveries but the documented production limit is 1,000, identify overtime, inventory drawdown, outsourcing or expansion that explains the difference. A volume formula can be arithmetically sound while its assumptions are unsupported. Capacity should reflect the actual business, not a universal benchmark.
Keep sales and customer receipts separate
Use the working-capital checklist to trace receivables and collection assumptions. Suppose a business begins with EUR 20,000 in receivables, records EUR 55,860 of credit revenue and collects EUR 45,000. With no other movements, closing receivables are EUR 30,860.
If the cash forecast also uses EUR 55,860 as receipts, compare that formula with the separate EUR 45,000 collection schedule. Review whether the workbook assumes immediate payment or has simply linked cash to the wrong row. Advance payments, sales tax, credit notes and write-offs would need additional explicit treatment.
The cash-flow review shows how these collections feed closing cash. For the wider connection to assets and equity, use the balance-sheet checks.
Run a controlled input test
In the first example, increase volume by 100 units while leaving everything else fixed. Expected additional net revenue is 100 × 50 × 95% × 98%, or EUR 4,655. The revised total should be EUR 60,515.
Check every dependent revenue total and the relevant receivables and cash timing. A fixed-capacity constraint or discount tier may legitimately change the response; identify that logic before judging the result. Restore the original inputs and retain a short record of the test. The scenario-testing guide explains how to test linked assumptions without confusing scenarios.
Use saved-file checks alongside the financial review
FinModelCheck does not validate sales assumptions, determine revenue recognition, reconcile this forecast or recalculate Excel. It inspects supported saved-file evidence, including saved Excel errors, broken references and external workbook dependencies. Its provisional score does not certify a revenue forecast.
Open the checker or inspect the example report. Online results show the score and counts by Finding type without cell-level details. The complete PDF is free without registration in the current valid owning browser session. Treat those Findings as a supplement to the business and financial checks above.
Frequently asked questions
Can revenue grow faster than units sold?
Yes. Higher prices, a different product mix or fewer deductions can explain the difference. Rebuild those drivers rather than assuming the extra growth is an error.
Should monthly seasonality weights always total 100%?
Yes when they allocate a single annual amount. Other seasonal factors may use a different scale; label their purpose and test the resulting annual total.
Does a clean Excel formula prove the forecast is realistic?
No. A formula can work exactly as written while demand, delivery capacity or collection assumptions are unsupported. Saved-file checks and financial review answer different questions.


