Browse documentation

Planning

Review Budget vs Actual

Compare what the business planned with what was actually recorded, then decide whether the plan or operating response needs attention.

In this guide

  1. Prerequisites
  2. Define the comparison
  3. Run a planning comparison
  4. Worked example
  5. Understand what can count as actual
  6. Handle edge cases deliberately
  7. Carry the variance into the next decision
  8. Troubleshooting and common questions

Prerequisites

  • A budget for the period and category being reviewed.
  • Recorded or realized values for the same period and financial domain.
  • A shared sign convention and period boundary for interpreting the comparison.

Define the comparison

Budget vs Actual reference
ItemWhat it meansWhy it matters
BudgetThe planning target or context for the selected period and category.Provides the reference point for comparison.
ActualThe recorded or realized value from the relevant financial domain.Shows what happened, not what was expected or modeled.
Variance $Actual minus Budget using the displayed sign convention.Shows the absolute difference between result and plan.
Variance %The variance relative to the budget when a valid non-zero budget exists.Provides scale, but needs careful handling when the budget is zero or signs differ.

Run a planning comparison

  1. Choose the period

    Use the same period boundary for the budget and the recorded result.

  2. Choose the category

    Compare like with like. Do not compare a total budget with a partial actual or mix unrelated domains.

  3. Confirm the actual source

    Verify that the actual is recorded or realized. Expected receipts and hypothetical values do not qualify.

  4. Read both variance measures

    Use the absolute difference and, where valid, the percentage to understand amount and scale.

  5. Interpret the cause

    Ask whether the difference comes from timing, a changed fact, a missing record, or an assumption that needs review.

  6. Choose the response

    Decide whether to correct data, update a future plan, or keep the plan and monitor the difference.

Worked example

Example

Tools budget compared with recorded cost

The actual tools cost is $1,500 above the $12,000 budget. The percentage is 12.5%. This describes the difference; it does not decide whether the result is acceptable.

Tools budget
$12,000
Actual tools cost
$13,500
Variance
+$1,500
Variance %
+12.5%
Conceptual example. Use reviewed workspace values for an actual decision.

For an expense category, a positive Actual minus Budget variance can mean spending exceeded the target. For revenue, the same sign can describe a different result.

Do not apply one favorable or unfavorable label across every category without considering what the values represent.

Understand what can count as actual

  • Payroll actuals should come from recorded active payroll, effective overrides, and separate one-time payroll for the period.
  • Tools actuals should come from recorded tool costs and effective period values.
  • Commitment actuals should reflect the relevant recorded event without assuming every obligation has already been paid.
  • Revenue actuals should use realized receipts where the comparison is about cash. Expected revenue must remain expected.

Handle edge cases deliberately

Variance edge cases
ItemWhat it meansWhy it matters
Zero budgetA percentage variance cannot use zero as a meaningful denominator.Use the absolute variance and treat percentage as unavailable or separately defined by the interface.
Missing actualThe record may be absent or the period may not be complete.Do not automatically interpret missing as zero without checking the source.
Negative valueRefunds, reversals, or sign conventions can change interpretation.Verify the domain and sign before assigning meaning.
Late-recorded actualA value entered later may change a previously reviewed period.Revisit the comparison and retain the reason in the review process.
Changed budgetEditing the target changes the reference point.Distinguish a deliberate replan from erasing learning from the original variance.
Period mismatchBudget and actual may cover different dates.Align the period before interpreting the difference.

Carry the variance into the next decision

Planning review loop

  1. Budget
  2. Recorded actual
  3. Variance
  4. Interpretation
  5. Next action
Variance is evidence for a human review. It is not an automatic recommendation.
  • Correct a missing or misclassified record before changing the plan.
  • Update future assumptions when operating reality has genuinely changed.
  • Keep a timing difference visible when the cost or receipt only moved between periods.
  • Use a separate scenario when the response is still hypothetical.

Troubleshooting and common questions

Budget review questions
ItemWhat it meansWhy it matters
Actual looks inflatedExpected or duplicate values may have entered the comparison.Verify the source and remove hypothetical or merely expected values from actual.
Variance sign feels backwardsExpense and revenue categories can carry different business meaning.Read labels and formula before applying an interpretation.
Percentage is missingThe budget may be zero or invalid as a denominator.Use the absolute difference and document the edge case.
A past period changedA late record or mapping correction may have altered the actual.Re-run the review with the corrected source context.