How to Write Budget vs. Actual Variance Commentary (With Examples)

The numbers in a budget-vs-actual report don't explain themselves. A line that says revenue came in $240K under plan tells the board that something happened. It doesn't tell them what, why, or whether to worry. That's the job of the commentary, and most of the commentary finance teams write is close to worthless.

Here's a sign of how much this matters. When Gartner asked 100 finance leaders which use of generative AI would hit their function fastest, the top answer wasn't forecasting or a faster close. It was explaining budget and forecast variances. Sixty-six percent put it first, ahead of everything else (Gartner, June 2024).

Read that again. The single thing finance leaders most want a machine to take off their plate is writing the "why" behind the numbers. That tells you two things. Explaining variances is the highest-value output of the whole reporting cycle. And almost everyone finds it a slog.

So most people skip the hard part. They restate the number in a sentence and call it commentary. That's the version nobody reads.

What good commentary actually answers

Useful variance commentary answers four questions, in this order: What moved? Why? Is it a one-time thing or a trend? What are we doing about it?

Miss any one of those and the reader has to come find you. Most commentary stops at the first question. "Marketing was over budget by $85K." Okay. And? A board member reads that and still has every question they started with, plus a new one about why you bothered typing it.

Here's the difference on the page.

Weak: "Opex was over budget for the quarter."

Better: "Opex ran $85K (7%) over plan. About $60K of that is timing. We prepaid the annual software renewal in Q2 instead of Q3. The other $25K is two contractors we brought on to cover the analyst seat we're still recruiting for. That gap closes when the full-time hire starts in September."

The second one takes fifteen seconds to read and answers every question the first one raises. Nobody has to email you. Notice it also leads with the driver, not a wall of setup. Say what moved and why in the first clause, then add the detail. Your reader is busy and skims.

Don't explain everything

You can't write a paragraph about every line, and you shouldn't. Commentary on a $900 variance buries the $90K one that actually matters.

Set a materiality threshold before you start, and let it do the filtering. A common rule: flag anything off by more than 5% and more than a dollar floor, say $25K, so a rounding difference on a big account doesn't trip the wire. Anything above the line gets a sentence. Everything below it stays quiet. This isn't laziness. It's respect for the reader's attention, and it keeps the focus on the two or three things worth a decision.

The timing trap

The most common mistake in variance work is treating a timing shift like a real overspend. A vendor invoice you expected in March lands in April. March looks favorable, April looks over. Neither number means anything about how the business is running.

Call timing out by name and move on: "May was $40K under plan on rent, which is a timing item. The Q2 lease payment posts in June." If you fold a timing shift in with a genuine miss and let the board react to the total, you've taught them to distrust the whole page. And once they don't trust the page, they stop reading the commentary and start scheduling calls.

Favorable variances need a note too

A number coming in better than plan is not automatically good news, and skipping it because it looks fine is a mistake.

Revenue $300K over plan because a large deal closed a quarter early isn't outperformance. It's a pull-forward that leaves a hole in Q4. Costs way under budget might mean the team is efficient, or it might mean a hire you needed didn't happen and a project is quietly slipping. Explaining the good surprises does two things. It stops the board from banking a win that isn't there, and it tells you whether your budget was just wrong to begin with, which matters for every forecast after this one.

What is variance commentary, in one line? It's the short written explanation that sits next to each meaningful gap between budget and actual. Not a restatement of the number. The reason behind it, and what it means going forward.

The payoff isn't the board deck

There's a benefit here that has nothing to do with reporting. Writing honest commentary forces you to understand your own business, line by line. A variance you can't explain is a variance you didn't forecast, and left alone, it'll show up again next month wearing a different hat.

The teams with the sharpest forecasts tend to be the ones who write the most disciplined variance notes, because the discipline is the same skill pointed in two directions. The problem is time. FP&A Trends' 2025 survey found finance teams still spend close to half their working hours just collecting and validating data, 24% on collection and 21% on checking it (FP&A Trends, 2025). The more the numbers eat, the less is left for the part a machine still can't do for you.

Because that's the catch with the Gartner stat. AI can draft a first pass at "spend was up because volume was up." It can't tell you whether that volume is a durable trend or a one-time spike, whether your board is already nervous about that line, or which of three plausible drivers is the real one. That's judgment. It comes from knowing the business, and it's the whole reason the commentary is worth reading.

Good variance commentary is mostly that judgment, and only a little bit writing. You're deciding what deserves the reader's attention and what the number actually means for the next quarter. Get that right and a board meeting turns into a conversation about decisions instead of an interrogation about spreadsheets.

That judgment is a big part of what an outsourced FP&A team brings. At Plametrix we run the monthly close and the budget-vs-actual, and we write the commentary that goes with it, so the story is already on the page before anyone has to ask for it.