Guide

Variance Analysis Commentary: Budget vs Actual

Explaining a variance well is different from stating that one exists. Here's how to write the difference in a way that actually answers the question a reader has.

The question every variance line raises

Whoever reads “Revenue: €412,000 vs Budget €450,000” has one immediate question: why? Variance commentary exists to answer that in a sentence, before the reader has to ask. If it doesn't answer why, it isn't doing its job — however precisely the percentage is calculated.

Structure

  1. State the variance — the number and direction, in one clause.
  2. Give the specific cause — not a category, an actual reason.
  3. Classify it — timing difference, one-off, or a trend that needs attention.
  4. Say what happens next — only if there's an action or it's expected to continue.

Weak vs strong wording

“Revenue was below budget due to challenging market conditions and lower-than-expected customer activity during the period.”
“Revenue was €38,000 below budget, mainly due to a large client delaying a €30,000 order into next month. This is a timing difference, not a loss of business, and is expected to reverse in the following period.”

The second version tells the reader exactly what happened, whether to worry, and what to expect next period. The first tells them nothing they couldn't already guess from the number alone.

Common mistakes

  • Vague causes (“market conditions”, “timing”) with no specifics behind them.
  • Treating every variance as equally important — flag the material ones, note the small ones briefly.
  • Not distinguishing a one-off from a trend, which leaves the reader unsure whether to expect it again.
  • Over-justifying a small, unremarkable variance at the same length as a material one.

Turn your numbers into variance commentary

Add your prior period or budget figures alongside this month's actuals and Finnarrate will draft the variance narrative for you, ready to review.

Generate a commentary — €2.99