Financial model review
IFERROR in financial models: what to check
See how IFERROR can hide missing costs, undefined margins and broken references in Excel financial models, with worked examples and safe review steps.

IFERROR can make a financial report easier to read. It can also turn an unexplained calculation failure into a convincing zero. Before accepting a clean-looking dashboard, inspect what the formula substitutes and whether that substitute means the same thing as the missing result.
The important question is not whether error handling exists. It is whether the model makes unavailable information distinguishable from a genuine zero. The invented examples below illustrate that review; they are not instructions to remove all error handling.
Understand what the replacement means
In Excel, IFERROR(value, value_if_error) returns its second argument when the first evaluates to one of the supported error types. These include division, reference and lookup errors. Otherwise, it returns the original result. See Microsoft's IFERROR documentation.
For a reviewer, =IFERROR(B8/B5,0) deserves two separate questions: why might the division fail, and why would zero be the appropriate response? The function does not answer either business question. A missing input, a deleted reference and a deliberately unavailable metric may need different handling even if they reach the same replacement value.
Example: zero revenue is not a zero margin
Suppose B5 contains revenue and B8 contains gross profit. In one month, revenue is EUR 10,000 and gross profit is EUR 3,000. The formula =B8/B5 returns a gross margin of 30%.
In a pre-launch month, revenue is zero and gross profit is zero. The ratio is undefined because its denominator is zero. Wrapping the calculation as follows displays 0%:
=IFERROR(B8/B5,0)
That display can suggest a meaningful measured margin, although there were no sales from which to calculate one. A separate status such as No revenue this period may communicate the situation more accurately.
If the intended presentation rule is specifically to explain zero revenue, one possible formula is:
=IF(B5=0,"No revenue",B8/B5)
This is a presentation choice, not a universal repair. Text in a metric cell can affect charts and downstream calculations. Consider keeping a numeric calculation and a separate status cell when another formula needs the result. Agree how unavailable periods should appear before changing an entire report.
Example: a missing cost becomes extra profit
Imagine a product forecast with 100 units sold at EUR 60 each. A lookup should supply a unit cost of EUR 40. Revenue is EUR 6,000, cost is EUR 4,000 and the simplified gross profit is EUR 2,000.
Now suppose the lookup cannot find the product identifier. If error handling substitutes zero for the missing unit cost, the forecast can show EUR 6,000 gross profit. It has overstated the intended result by EUR 4,000 while displaying ordinary numbers.
Do not conclude that the product has no cost. Inspect the identifier, the approved source table and the expected lookup match. The replacement might be appropriate for a genuinely free item, but that requires evidence beyond the absence of a match.
Use the financial model lookup review to count missing and duplicate keys, inspect exact-match settings and reconcile one product's cost independently before choosing an error-handling fallback.
For an expected missing-match case, IFNA is narrower than IFERROR: it substitutes for #N/A, rather than also hiding the other listed errors. Microsoft documents the distinction in its IFNA guide. A more selective function still needs an appropriate replacement; IFNA(...,0) can conceal the same missing-cost problem.
Review a formula before rewriting it
In a separate working copy, select a reported or suspicious cell and read its formula bar. Identify the calculation inside the wrapper and its fallback. Follow the main inputs before deciding whether a failure is expected.
For a simple scalar formula, temporarily test its inner expression in a spare cell in the same worksheet. This can reveal the underlying error without overwriting the original formula. Be careful with relative references and array formulas: a copied expression may behave differently in a different location. Remove the test afterward, or keep a clearly labelled review note outside the delivered model.
Check the result when inputs are valid, missing and genuinely zero. Record what each case should mean. Do not fill missing costs, exchange rates or quantities with invented values merely to make the calculation finish.
A short error-handling checklist
- Identify what business quantity the formula calculates.
- Separate expected unavailable cases from unexpected failures.
- Inspect whether the fallback is a number, text or an empty string.
- Check which totals, charts and decisions consume that fallback.
- Test a valid input, a zero input and a missing input in a copy.
- Keep a visible explanation for results that cannot be calculated.
A deliberate wrapper can be useful in a user-facing report. For example, a dashboard might show a readable message while a nearby control counts unresolved inputs. The key is to retain a route from the presentation back to the cause.
What the checker can and cannot tell you
FinModelCheck inspects supported saved Excel errors, broken references, external workbook links and embedded numeric coefficients. It does not recalculate Excel, decide whether a fallback is financially appropriate, or audit every error-handling formula. A saved numeric zero does not reveal that an inner expression failed. A broken-reference token inside a guarded formula can still be reported without claiming that the branch was evaluated.
Use the checker for its supported checks and download the free complete PDF in the current valid owning browser session, without registration. The example report shows the layout. For related investigations, read the saved Excel errors guide and forecast formula review.


