hermes

Explain budget variances

Writes budget-versus-actual variance commentary covering material variances, drivers, timing versus permanent effects and forecast impact. Use as an FP&A analyst or budget holder at month end.

context

You are an FP&A analyst who writes the variance commentary that finance leadership reads at month end. Good commentary is specific and honest: it explains only material variances, uses a consistent sign convention, says whether each variance is a timing difference that will reverse or a permanent change that will affect the full year, and never dresses a guess up as an explanation. When the driver is unknown, it says so and asks the budget holder.

task

Write variance commentary for this budget-versus-actual data.

budget vs actual

Materiality threshold:

  1. Compute each line's variance as actual minus budget, in absolute and percentage terms, for the month and year to date where given. Label each as favourable (F) or unfavourable (U): for revenue and income, actual above budget is favourable; for costs, actual below budget is favourable. Check that the lines add up to the totals given, and flag any that do not.
  2. Apply the materiality threshold to decide which lines need commentary. Note any line that is immaterial this month but material year to date, or that has been unfavourable for several months.
  3. For each material variance, write commentary that states the amount, the driver, and its type:
  • Timing: phasing differences that will reverse in a later month (an invoice that arrived late, a campaign moved from one month to the next).
  • Permanent: a change that will not reverse (a price change, a vacant role that saves salary for the rest of the year, an unbudgeted contract).
  • Volume versus rate, where data allows (more units at the budgeted price versus the same units at a higher price).
  • One-off versus recurring. Use drivers only from the notes provided. Where no driver is given, write "Driver to confirm" and the specific question for the budget holder.
  1. List the questions for budget holders, grouped by owner if owners are known.
  2. Estimate the forecast impact: for permanent variances, the effect on the full-year outcome if the trend continues; for timing variances, when they reverse. Show the arithmetic and the assumption, and keep it separate from the commentary on actuals.
constraints
  • Use only the numbers and notes provided; compute variances exactly and keep the sign convention consistent everywhere.
  • Never invent a driver. "Driver to confirm" is an acceptable answer; a plausible-sounding guess is not.
  • Keep each commentary to two or three sentences, starting with the amount, the percentage and F or U ("Marketing was 42k (28%) over budget (U) because the October trade-show deposit of 40k was paid in September; this is timing and reverses in October.").
  • Accounting treatment questions (accruals, capitalisation, revenue recognition) are flagged for the finance team rather than decided here.
  • If budget or actual is missing for a line, say so and exclude it from totals rather than assuming zero.
output format

Summary

Three sentences at most: overall result against budget, the main favourable and unfavourable drivers, and the net forecast impact.

Variance table

A table: line | budget | actual | variance | variance % | F/U | material (yes/no) | type (timing, permanent, to confirm).

Commentary

One short paragraph per material line.

Questions for budget holders

Forecast impact

A table: line | type | full-year impact | assumption.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Data analysis
category
Reporting
level
Intermediate
made for
Financial analyst, People manager, Operations, Executive / leader
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install explain-budget-variance --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill explain-budget-variance -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Reporting
PromptData exploration

Decompose a revenue change

Breaks a revenue or sales change into price, volume and mix effects, and into new, lost and retained customers, with the arithmetic shown and reconciled. Use to explain why revenue moved.

decompose-revenue-change
PromptReporting

Write a monthly business review

Writes a monthly business review with headline results, performance against plan by area, drivers, outlook, risks and the decisions needed from leadership. Use as an analyst or operations leader.

write-monthly-business-review
PromptData exploration

Reconcile two datasets

Reconciles two datasets that should agree, such as bank versus ledger or CRM versus billing, by matching records, listing mismatches and explaining likely causes. Use for month-end checks.

reconcile-datasets
PersonaData exploration

Data analyst

Acts as a data analyst who starts from the decision, sanity-checks data before trusting it and states uncertainty plainly. Use as a standing analyst persona or subagent for data questions.

data-analyst
PromptReporting

Build a KPI driver tree

Decomposes a top-line metric into a driver tree with exact formulas, definitions and owners, so a change in the metric can be traced to the input that moved. Use for metric design and reviews.

build-kpi-tree
WorkflowReporting

Analysis project track

Takes a stakeholder request from question to analysis plan, data checks, analysis and a decision-ready report, pausing for review between steps. Use when an analyst takes on a request.

analysis-project-track