Budget variance

How to investigate municipal budget variances

A practical approach to moving from variance signal to financial explanation.

7 min read
Planned audience: Municipal finance teams
Status: Published guide

A budget variance is a signal. It tells finance teams that actual activity differs from the expected amount.

The next step is investigation.

A good investigation does not assume that every variance is a problem. It asks what caused the movement, whether it matters, whether it was expected, and what should happen next.

Start with the variance signal

The first step is to identify the variance clearly.

Finance teams should know:

  • Which fund, department, or category is affected
  • Whether the variance is monthly or year-to-date
  • Whether it is favorable or unfavorable
  • The dollar amount
  • The percentage amount
  • Whether the variance exceeds a materiality threshold

Check whether timing explains it

Many municipal variances are caused by timing.

Before treating a variance as a problem, ask whether the actual activity is following a known seasonal, billing, reimbursement, payroll, or project pattern.

Examples:

  • Property tax collections arrive later in the cycle
  • Grant reimbursement has not been received yet
  • Insurance was paid earlier in the year
  • Public works spending increased during a seasonal period
  • A project invoice arrived in one month instead of another

Compare against historical actuals

Historical actuals help determine whether a variance is unusual.

A category may appear off track compared with the budget but normal compared with prior years. Or it may appear normal in one month but unusual compared with the same month historically.

Useful comparisons include:

  • Same month last year
  • Year-to-date compared with prior years
  • Multi-year average
  • Highest and lowest recent years
  • Historical monthly pattern
  • Budget versus actual history

Drill into the ledger drivers

Once a material variance is identified, finance teams should look at the categories or transactions driving the movement.

The goal is not to inspect every transaction. The goal is to identify the main driver.

For example:

  • A public works variance may be driven by fuel, materials, or contracted services
  • A revenue variance may be driven by lower permit activity
  • A payroll variance may be driven by overtime or vacancies
  • A grant variance may be driven by reimbursement timing
  • A capital variance may be driven by invoice timing

Determine whether it affects the forecast

Not every variance changes the forecast.

A timing variance may resolve later in the year. A one-time variance may not affect recurring revenue or expenditures. A recurring variance may require a forecast update.

Ask:

  • Is this timing-related or structural?
  • Is it one-time or recurring?
  • Does it affect year-end expectations?
  • Does it affect reserves?
  • Does it require a budget adjustment?
  • Should future assumptions change?

Write a clear explanation

A variance explanation should be specific, brief, and useful.

A weak explanation says:

“Expenses are over budget.”

A better explanation says:

“Public works expenditures are above the seasonal target due to earlier-than-planned road maintenance materials. The variance is expected to normalize over the next two months.”

Good explanations include:

  • What changed
  • Why it changed
  • Whether it was expected
  • Whether it affects the forecast
  • What happens next

Decide the next action

The investigation should lead to a practical next step.

Possible next actions include:

  • No action needed
  • Monitor next month
  • Department follow-up
  • Update forecast
  • Review reserve impact
  • Prepare council explanation
  • Consider budget amendment
  • Review policy threshold

How Aurelius Civic supports variance investigation

Aurelius Civic helps municipal finance teams move from variance signal to explanation.

The variance module is designed to support monthly heatmaps, seasonalized targets, investigation drilldowns, historical comparisons, and narrative summaries. This helps users identify material movement, understand the drivers, and explain what changed.

The platform does not replace finance judgment. It supports a clearer investigation workflow.

Review variance with clearer context.

Aurelius Civic helps municipal finance teams connect monthly variance, seasonal targets, drilldowns, and financial explanation.

Explore varianceStart free

Common questions

Does every variance need investigation?

No. Variances should be prioritized based on materiality, timing, recurrence, and financial impact.

What is the first step in investigating a variance?

Start by identifying the fund, department, category, period, amount, percentage, and whether the variance is favorable or unfavorable.

How do historical actuals help?

Historical actuals show whether the current variance is unusual compared with prior years or normal seasonal behavior.

What should a variance explanation include?

It should explain what changed, why it changed, whether it was expected, whether it affects the forecast, and what happens next.

Related resources

Ready to explore Aurelius Civic?

Start free to explore our financial planning views or request a walkthrough to discuss your municipality’s needs.