Budget vs Actual for Startups: From Variance to Decision

Budget vs Actual compares what you planned for a period with what was actually recorded or realized. The useful part is not the variance alone, but understanding why it happened and whether it changes the operating plan.

What Budget vs Actual measures

A budget records assumptions about a future period. Actual records what happened in that period using the selected financial basis. Comparing the two reveals where an assumption, timing expectation, or operating choice differed from the plan.

The comparison does not prove that the budget was wrong or the outcome was good or bad. It identifies a difference that needs context.

What belongs in a startup budget

Use categories that match how the business makes decisions. Payroll, tools, contractors, facilities, inventory, marketing, taxes, and other commitments may matter, but no fixed category count or percentage fits every company.

Separate recurring commitments from one-time items where the distinction helps explain future cash pressure. Keep category definitions stable enough that the next comparison uses the same meaning.

Set assumptions without false precision

Start with available recorded history, known commitments, and explicit planned changes. Record the timing and reasoning behind material assumptions. If a value is uncertain, use a range or scenario rather than disguising an estimate as a precise outcome.

A buffer, budget horizon, or review threshold should reflect the business's volatility and decision needs. There is no responsible universal percentage, three-month rule, or fixed variance threshold.

What counts as Actual

Actual means recorded or realized financial values for the period. Expected revenue is not Actual. An expected customer receipt remains a planning input until the cash lands and is recorded as received.

Use consistent periods and category definitions. If the budget is cash-based, compare it with realized cash values. If another accounting basis is used, label it clearly and avoid mixing it with cash without reconciliation.

Calculate dollar and percentage variance

A common convention is:

Dollar variance = Actual - Budget

Percentage variance = (Actual - Budget) / Budget x 100

State the sign convention because positive has different meaning for an expense and a receipt. If the budget is zero, percentage variance is undefined or not meaningful. Use the dollar difference and an explanation instead of dividing by zero.

Interpret revenue and expense variance in context

An expense above budget may reflect unplanned cost, deliberate acceleration, or a payment that arrived earlier than modeled. An expense below budget may be a saving, a delayed hire, or an invoice that has not been paid yet.

Cash received below budget may reflect collection timing rather than lost revenue. Cash received above budget may be a durable improvement or a one-time prepayment. The explanation determines whether the plan should change.

A worked monthly example

This example uses Actual minus Budget. Contractor spend was $7,000 above plan, but the next step is to ask why. The work may have accelerated, expanded, or shifted from another period. Cash received was $12,000 below plan; that may reflect slower collections, a changed deal, or an assumption that did not occur.

What to do with a variance

1. Verify the value. Confirm the period, category, and recorded amount.
2. Explain the movement. Identify timing, volume, price, scope, or another operating cause.
3. Classify the effect. Decide whether it is one-time, recurring, delayed, or likely to reverse.
4. Review the plan. Change an assumption only when the new evidence supports it.
5. Carry the context forward. Preserve the explanation for the next review.

Overspend is not automatically bad, and underspend is not automatically good. The test is whether the variance supports the operating objective and whether its future effect is visible.

How RunwayCal relates to the workflow

Planner provides product context for planning and variance review. The Budget Variance Analysis documentation explains the current workflow. Use reviewed and recorded financial context conservatively; do not assume every external transaction or category is mapped automatically.