Variance report: What it is and how to build one

A variance report compares your budgeted or forecasted figures against actual results for a period and explains the gap between them. But budgets don’t portray the actual results—think of them as an educated guess.

The final amounts of income and expenses at the end of the period will differ from what's projected in the budget. That difference is called a variance, and it’s important for getting a fuller picture of the financial well-being of a company.

What is a variance report?

A variance report compares budgeted or forecasted figures against actual results for a period and explains the gap. Variances in accounting are those gaps, the difference between the number you planned for and the number you booked.

Your finance team owns the report. Depending on the size of the company, that's an accountant, an analyst, or a controller, and they typically run it every month, sometimes quarterly. Variance reporting exists to catch overruns and forecast misses early, while you can still cut a line, renegotiate a contract, or reset an assumption.

The practice isn't unique to corporate finance. Property managers run the same report against a property budget, and payroll teams run a payroll variance report on labor cost lines.

Every variance report is built from the same core columns:

• Budgeted amount: What you planned to spend or earn on the line
• Actual amount: What the accounting system recorded for the period
• Variance in dollars: Actual minus budget, showing the size of the gap
• Variance as a percentage: The same gap relative to budget, for comparison across lines
• Notes or explanation: A short written reason for any gap worth flagging

Get these five columns right and the rest of the report is arithmetic and interpretation.

Budget variance report vs. forecast variance report

A budget variance report compares actuals to the plan you set at the start of the year, while a forecast variance report compares actuals to your most recent projection. The first is an expense-control lens. The second tests whether your latest assumptions are holding up.

Both reports can turn up favorable or unfavorable variances, and each one is either controllable or outside your team's hands. Sorting variances by cause and by direction is done by performing a variance analysis, a step beyond the report itself.

Choose the comparison that matches the decision in front of you: the budget when you're defending a plan, the forecast when you're testing whether it still holds.

Variance report formulas

Two formulas produce every number in the report. The dollar variance sizes the gap, and the percentage variance makes gaps comparable across lines of very different sizes.

Dollar variance = Actual – Budget (or Forecast)

Percentage variance = (Actual – Budget) / Budget

Use dollars to size the impact of a single line, and use percentages to compare a small line against a large one or to track the same line over several months. A $5,000 miss means something different on a $10,000 line than on a $500,000 one, and the percentage is what tells you which miss is more serious.

Say you budgeted $20,000 for software and spent $23,000. The dollar variance is $23,000 – $20,000 = $3,000. The percentage variance is $3,000 / $20,000 = 15%. Software came in 15%, or $3,000, over plan for the period.

Run every line through both, and you'll know how big each gap is and how much it matters.

How to build a variance report (with example)

Building a variance report is a five-step sequence you can run in any spreadsheet. Work through it once with a real month of numbers, and you'll have a template you can reuse every period.

1. Organize your data into revenue and expense lines

Pull your actuals for the period straight from your accounting system or financial statements, then list revenue lines and expense lines separately. Keep the standard lines in the order a profit and loss (P&L) statement uses them:

1. Revenue
2. Cost of goods sold (COGS)
3. Gross profit
4. Operating expenses
5. Earnings before interest, taxes, depreciation, and amortization (EBITDA)
6. Net income

Separating the two sides keeps a revenue miss from hiding inside an expense line when you scan the report later.

2. Set up your columns

Give the report one column for each piece of the comparison: line item, budget or forecast, actual, dollar variance, percentage variance, and notes. This is the reusable skeleton of the report. Once it's laid out, every future month is a matter of dropping in new actuals and letting the variance columns recalculate.

3. Calculate the dollar and percentage variance

Run both formulas down every line. For the software line, an actual of $23,000 against a $20,000 budget gives a $3,000 dollar variance and a 15% percentage variance. Fill the same two columns for every revenue and expense line so the whole P&L is measured on one basis.

4. Flag what's significant

Sort or highlight by the size of the gap, not by percentage alone. A 40% overrun on a $600 subscription line is $240 and rarely worth a meeting, while a 4% overrun on a $500,000 payroll line is $20,000 and clearly is. Rank your variances by dollar impact first, then let percentage break ties between lines of similar size.

5. Write the explanation for each material variance

For every line you flagged, write one or two plain sentences covering what happened, why, and the likely effect. For example, "Software ran $3,000 over because we added 12 seats during the sales onboarding push, and the higher run-rate carries into next quarter."

Keep it factual and unemotional, because this becomes the raw material for the narrative review later.

Once the table is filled and the material lines carry explanations, you have a variance report you can act on.

How to run a monthly variance review

A one-off spreadsheet becomes a monthly variance report when you tie it to month-end close and give it an owner. As a finance team grows, an analyst usually builds the report each month, and a controller or finance lead reviews it with the people who own each line.

Set a threshold so the review focuses on variances that matter. A threshold is the cutoff that decides which lines get a written explanation, for example, any line off by more than $5,000 or more than 10%, whichever you hit first. Set it too tight and you'll write narratives for rounding noise. Set it too loose and a real problem slips through unexplained.

The variance narrative is the short written explanation that turns a number into a decision. State the variance, name the driver, and recommend an action: "Marketing was $12,000 over on a paid-media test that returned no pipeline, so we're pausing the channel next month."

Run the review on the same loop every month:

1. Close the books for the period.
2. Pull actuals into the report template.
3. Calculate the dollar and percentage variance on every line.
4. Apply your threshold to flag the lines that need explaining.
5. Write a narrative for each flagged line.
6. Review the report with the owners of those lines.

Do this every month and budget owners come to expect the conversation, which is when a variance report starts changing behavior instead of just recording it.

When spreadsheets stop working

Spreadsheets are the right place to start, and plenty of teams run variance reporting in them for years. They start to strain when spend scatters, when actuals live across corporate cards, reimbursements, bills, and purchase orders, and pulling them into one plan-vs-actuals view becomes a manual reconciliation job every month. By the time the numbers line up, the overrun you're reading about already happened.

The friction shows up in a few specific places:

• Manual reconciliation lag: Someone exports and matches actuals from several systems by hand before the report is even accurate.
• No live view before close: You can't see where a line stands until the books close, which is days after the money moved.
• No line-owner visibility: Department heads can't check their own budgets without asking finance, so overruns surface late.

One boundary is worth setting before you change tools. Live spend data covers the expense side of the report: your corporate card, reimbursement, bill, and PO actuals can update on their own.

Revenue, COGS, gross profit, EBITDA, and net income still come from your accounting system or FP&A tool. A tool that tracks spend closes the expense gap, and that's usually where the manual pain is worst.

Track budgets vs. actuals in real time with Ramp

By the time a spreadsheet variance report flags an overrun, the spend is already booked and the month is closed. That lag between money moving and the number showing up is exactly where budgets quietly blow past plan.

Ramp Budgets gives you a live view of budget vs. actuals across every spend type flowing through Ramp. Upload a budget once, and every dollar maps to the right line automatically, so there's no manual reconciliation and no waiting for close. That closes the expense-side lag that keeps spreadsheet variance reporting one step behind.

Ramp Budgets turns variance tracking into something continuous:

• Maps every dollar to a line automatically: Corporate cards, reimbursements, Bill Pay, and committed POs post to the right budget lines as they happen, so your actuals are never stale.
• Gives line owners their own view: Role-scoped dashboards let each budget owner track their own lines without waiting on finance for a status update.
• Shows approvers remaining budget at decision time: Every approver sees the live budget impact before a spend is approved.
• Alerts finance before a line goes over: Proactive alerts fire before a line trips into overrun, instead of after the money is gone.

Try an interactive demo to see how Budgets keeps your variance report current, and why companies that use Ramp save an average of 7.5% a year across all spending.