How are budget vs. actual variances explained in month-end reporting?

Short answer

Each material variance gets a short note on its cause, whether it's timing or permanent, and what it means for the forecast, tied to the numbers.

A variance report shows where results landed against plan. The explanation is what makes it useful to leadership and budget owners: it says why the gap exists and whether it will persist.

What a variance explanation includes

The cause: Specific enough to act on. "Two engineering hires started in March, ahead of the June plan" rather than "headcount timing."
Timing or permanent: Whether the gap reverses later in the year or holds. This decides whether the forecast changes.
Favorable or unfavorable: Labeled the same way every month. A favorable expense variance can still be a problem, such as a delayed hire.
Forecast impact: What the variance means for the quarter or full-year number.
Owner: Who confirmed the explanation, usually the budget owner for that line.

Keeping explanations consistent

Write explanations from closed numbers, at the level the report is read (department or line item), and apply the same materiality threshold each month. Where the same account also has a flux explanation, the two notes describe the same driver the same way.

Writing budget variance notes with Ramp Stack

Put the reporting rules in the skill: Stack's variance analysis skill covers budget-versus-actual changes. Under Stack > Knowledge > Skills, the team adds its materiality threshold, the level the report is read at (department or line item), how favorable and unfavorable are labeled, and the fields every note carries.
Start from closed actuals: After close, the agent pulls actuals from QuickBooks Online, NetSuite, or Sage Intacct and measures each line against the plan.
Break each material variance into drivers: For lines over the threshold, it builds a waterfall from plan to actual and traces each driver to the transactions behind it.
Draft the note: Each note states the cause, whether it's timing or permanent, and the forecast impact, in a formula-backed workbook.
Route it to the owner: The task goes to an approver on the Close Checklist. The controller or budget owner edits the note, adds what the ledger can't show (a hire moved up, a deal that slipped), or rejects it.
Trace it later: The Session Audit Log keeps the sources and actions behind each note, so a question from leadership traces back to the entries.