Budget variance

Budget-to-Actual Report: A Practical Guide for Local Government

Learn what a municipal budget-to-actual report includes, how to interpret variances, and how local governments can improve monthly budget monitoring.

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

A budget-to-actual report compares what a municipality planned to collect and spend with what has occurred so far. At its best, the report does more than show whether a line item is over or under budget. It helps finance leaders understand what changed, whether the difference matters, and what action—if any—should follow.

That context is especially important in municipal finance. Revenues arrive on different schedules. Expenditures may be affected by encumbrances, contracts, emergencies, grants, capital projects, and the timing of service delivery. A simple percentage-of-year calculation rarely tells the whole story.

This guide explains what a municipal budget-to-actual report should include, how to read budget variances, and how to make the monthly review process more useful for staff, administrators, and elected officials.

What is a budget-to-actual report?

A budget-to-actual report—also called a budget vs. actual report or budget variance report—compares an approved financial plan with recorded financial activity for a defined period.

The comparison usually includes:

  • The original adopted budget
  • The current or amended budget
  • Actual revenue and expenditures for the reporting period
  • Year-to-date actual results
  • The dollar and percentage variance between plan and actual results
  • Remaining budget or available appropriation

For a municipality, the report should preserve the structure of the adopted budget. Depending on the organization, that may mean reporting by fund, department, function, program, project, grant, or account. The most useful level of detail is the one that supports accountability without burying the reader in immaterial line items.

A budget-to-actual report is a starting point for budget monitoring, not the end of the analysis. The Government Finance Officers Association recommends a formal process for comparing budget with actual results and advises governments to consider revenues, expenditures, operations, capital activity, economic trends, and performance measures when evaluating financial performance.

What should a municipal budget-to-actual report include?

A practical report should give readers enough information to recognize a meaningful variance and understand its context. Include the following fields when they are relevant to the municipality's accounting and budgeting practices.

Reporting context

Include municipality and reporting entity, fiscal year, reporting period and 'as of' date, fund, department, program, or other reporting level, budgetary basis used for the comparison, and date the financial data was last updated.

Budget information

Include original adopted budget, approved amendments or transfers, current or final amended budget, and year-to-date budget or expected amount when available. Showing both original and current budget helps readers separate operational changes from plan changes.

Actual and committed activity

Include current-period actual amount, year-to-date actual amount, encumbrances, purchase orders, or commitments, and projected year-end result if maintained. Actual expenditures alone may understate expected obligations.

Variance and explanation

Include dollar variance, percentage variance, favorable/unfavorable designation, materiality threshold, plain-language explanation for significant variances, and responsible owner with follow-up action. A plain-language explanation is often the most valuable part of the report.

How is a budget-to-actual variance calculated?

At its simplest, a variance is the difference between a budgeted amount and an actual amount:

Variance = Actual amount − Budgeted amount

However, municipalities do not all use the same sign convention. Some systems calculate budget minus actual, particularly for expenditures or remaining appropriation. Others calculate actual minus budget for every line.

The important rule is consistency. The report should clearly label the formula and should not rely on a positive or negative sign alone to communicate whether a result is favorable.

For revenues, actual collections above the expected amount are generally favorable, while collections below expectations are generally unfavorable. For expenditures, spending below the expected amount is generally favorable, while spending above expectations is generally unfavorable. Even these labels require context: delayed spending may represent timing rather than savings, and revenue above budget may be restricted or nonrecurring.

Variance percentage is commonly calculated as:

Variance percentage = Variance ÷ Budgeted amount × 100

When the budget is zero or very small, a percentage can be misleading or undefined. In those cases, use the dollar variance and an explanation instead.

See how Aurelius Civic brings clarity to municipal financial reporting.

Variance Watch highlights material changes using consistent thresholds, while investigation views preserve scenario, period, and driver context.

Request a walkthroughLearn about the platform

How to read a budget-to-actual report

Following a structured process turns variance review from a search for unusual numbers into a repeatable investigation process:

  1. Confirm the scope and data date: Start with the fiscal year, reporting period, funds included, and last update. Determine whether the report uses the original budget, amended budget, or both. Confirm that actual results use the same budgetary basis and reporting structure as the plan.
  2. Compare activity with the expected pattern—not just the calendar: If six months of the fiscal year have passed, it does not follow that every revenue or expenditure should be at 50% of budget. Property taxes, permits, grants, seasonal programs, and annual contracts follow different schedules.
  3. Focus on material variances: Reviewing every difference with equal attention creates noise. Establish thresholds reflecting both dollars and percentages, combining minimum dollar thresholds, minimum percentage thresholds, high-risk accounts, and overrides for items affecting appropriations or essential services.
  4. Identify the cause of each significant variance: Classify the reason before deciding what it means (Timing, Seasonality, Volume or demand, Price or rate, Vacancy or staffing, One-time event, Recurring trend, Classification/data issue, or Budget change).
  5. Assess the effect on the full financial picture: Ask what the variance changes beyond its individual line item—does it affect the year-end forecast, cash timing, fund balance, appropriations, or service delivery?
  6. Decide whether action is needed: Possible responses include continued monitoring, transaction reclassification, forecast updates, department context requests, operating adjustments, budget amendments, or council communication.

A simple budget-to-actual example

The following hypothetical example uses a year-to-date budget so the comparison reflects the expected timing of activity.

Hypothetical municipal budget-to-actual variance comparison with year-to-date targets and interpretations
General Fund itemYTD budgetYTD actualVariance to planInterpretation
Permit revenue$200,000$185,000$15,000 unfavorableCollections are below the expected pace; review permit volume and the year-end forecast.
Public safety overtime$300,000$345,000$45,000 unfavorableStorm response increased overtime; determine whether the effect is one-time or likely to continue.
Fleet fuel$400,000$360,000$40,000 favorablePrices and usage are below plan, but open purchase orders and the remaining seasonal pattern should be reviewed.

The interpretation column matters because the same numerical variance can imply different actions. The permit variance may change recurring revenue expectations. The overtime variance may require a forecast update or budget amendment. The fuel variance may be temporary and may not represent year-end savings.

How often should local governments review budget-to-actual results?

The right cadence depends on the size of the municipality, volatility of the item, reporting requirements, and the time needed to take corrective action. Monthly review is a practical standard for core operating funds and is specifically recommended for governing bodies by the Tennessee Comptroller's local-government guidance. Large, volatile, legally sensitive, or cash-critical items may need more frequent monitoring.

A consistent monthly process might include:

  1. Close or validate the reporting period.
  2. Refresh budget, actual, commitment, and forecast data.
  3. Apply materiality thresholds.
  4. Assign significant variances for investigation.
  5. Document cause, expected duration, and financial impact.
  6. Update forecasts and identify required actions.
  7. Prepare an audience-appropriate summary for administrators or elected officials.
  8. Track unresolved items into the next review cycle.

Frequency matters, but timeliness and clarity matter just as much. A detailed report that arrives too late to support a budget amendment or operational adjustment has limited value.

Common budget-to-actual reporting mistakes

Municipal finance teams can avoid common pitfalls by watching for these six issues:

  • Treating every month as an equal share of the year: Straight-line comparisons create false alarms when revenue or spending is seasonal.
  • Showing only the current budget: If the original budget disappears after an amendment, readers cannot see how the plan changed.
  • Ignoring encumbrances and commitments: Actual spending may not reflect purchase orders, contracts, or other obligations already in motion.
  • Using color without explanation: Red and green indicators do not explain materiality, cause, or impact and can create accessibility issues.
  • Reporting variance without root cause: 'Over budget' is an observation, not an explanation. State what changed, why, and what happens next.
  • Mixing budgetary and accounting bases: Internal budget monitoring and annual external financial reporting serve different purposes. GASB Statement No. 103 addresses annual budgetary comparison information, which should not be confused with monthly internal monitoring.

Turning a report into a decision process

The recurring challenge is not producing another table. It is preserving the path from a reported variance to the evidence, context, and decision that follow.

A stronger process connects:

  • The adopted and amended budget
  • Current actual results
  • Materiality thresholds
  • Prior periods and forecasts
  • The reason for a variance
  • The underlying transactions or drivers
  • The person responsible for follow-up
  • The effect on cash, fund balance, services, and future periods

When those elements remain connected, finance leaders can answer the questions that matter: What changed? Why did it change? Does it matter? What should we monitor or do next?

How Aurelius Civic supports variance review

Aurelius Civic is built to help municipal finance leaders move from a reported difference to an explainable decision. Variance Watch highlights material changes using consistent thresholds, while investigation views preserve the relevant scenario, period, and driver context. Executive Cash Outlook helps place budget performance alongside the municipality's broader cash position.

The goal is not to prescribe a decision or replace the municipality's accounting system. It is to make changes easier to investigate, explain, and stand behind—without relying on disconnected spreadsheets and manual reconciliation.

Sources

Common questions

What is the difference between a budget-to-actual report and a budget variance report?

In most contexts, the terms describe the same basic comparison. A budget-to-actual report emphasizes the planned and recorded amounts, while a budget variance report may place greater emphasis on the dollar or percentage difference and its explanation.

What is the difference between budget to actual and budget vs. actual?

There is no meaningful difference in most usage. 'Budget to actual,' 'budget vs. actual,' and 'budget versus actual' generally refer to comparing a budgeted amount with actual financial activity.

Should a report use the original budget or the amended budget?

Ideally, it should show both. The original budget preserves the plan adopted at the beginning of the fiscal year. The current or final amended budget reflects authorized changes. Showing both helps readers understand whether a variance came from financial activity or a revision to the plan.

What is a favorable budget variance?

A favorable variance generally means revenue is above the expected amount or expenditures are below the expected amount. Context still matters. Revenue may be restricted or nonrecurring, and delayed spending may not result in year-end savings.

When should a municipality investigate a variance?

Investigate when a variance exceeds established materiality thresholds or may affect appropriations, cash, fund balance, grants, debt, legal compliance, service delivery, or future-year plans. Some high-risk items warrant review even when the percentage difference is small.

How often should a budget-to-actual report be prepared?

Monthly reporting is a practical standard for core municipal operations, but the appropriate cadence depends on volatility, risk, reporting requirements, and the time needed to act. Some revenues, expenditures, projects, and cash positions may require more frequent monitoring.

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.