Quick answer: explain the result, evidence and next decision

Write budget commentary as result → evidenced drivers → remaining uncertainty → business implication → owner and next review. Freeze the budget version, reconcile actuals and confirm the reporting basis first. A ledger label does not prove a cause, an underspend does not prove efficiency, and an approved explanation does not authorize a forecast revision.

Use a short paragraph for the decision-maker and a separate evidence record for the reviewer. Do not hide important offsets or replace missing evidence with a confident story. This is an operational writing guide, not accounting, investment, tax or legal advice. A qualified finance professional must review the method, accounting treatment and intended distribution before operational use.

Set the sign convention and use a reviewable template

In these examples, revenue and expense amounts are both displayed as positive values. Variance = actual − budget. With a positive budget, percentage variance = (actual − budget) ÷ budget × 100. A positive expense variance means expense above budget; a positive revenue variance means revenue above budget. Favorable or unfavorable is an interpretation that must be labeled separately, not guessed from a plus sign.

Finance systems may use other conventions. For example, Oracle's Variance/Var documentation describes account-type-dependent behavior, including a reversal for expense accounts. This article uses the explicit formula above, not an assumption about your application's displayed variance. Verify the calculation before importing it into prose.

When budget is zero, state the amount and that the item was unbudgeted; do not manufacture a percentage. When budget is negative or close to zero, agree an interpretable measure with finance. Show gross movements if a small net difference conceals separate issues. Keep monthly and year-to-date comparisons separate, and distinguish original budget, flexible budget and latest forecast.

Part of the explanation What to record What is insufficient
Result Period, entity, basis, budget, actual, signed variance and denominator “Higher than expected”
Driver Amount, operational record and attribution rule “Due to business needs”
Uncertainty Unexplained amount, disputed evidence or unconfirmed future date A balancing “other” presented as a cause
Implication Timing, recurring assumption, one-off scope or unresolved outlook “Savings” because expense is below budget
Follow-up Responsible owner, task, date and evidence that will close it “Continue to monitor”

Download the editable commentary worksheet. Keep source references restricted when they contain payroll, contracts or customer information. A management paragraph can be concise while its linked working papers remain detailed. Replace every fictional amount and action date before adapting an example; never describe the sample as your organization's performance.

Ten budget vs actual commentary examples

All ten cases use one hypothetical reporting month and USD. The cases are independent, not ten rows of a single company's income statement. Expense cases assume the stated actual expense has been recognized under the entity's approved accounting policy; invoices and cash payments alone do not establish that treatment. The role-based follow-ups are illustrative assignments, not instructions to actual employees.

1. Revenue volume: identify what did not happen

Example commentary: Revenue was 450,000 USD against a 500,000 USD budget, a 50,000 USD shortfall, or 10%. The reconciled revenue schedule contains 900 recognized units at 500 USD each versus 1,000 budgeted units at the same price. The arithmetic is a volume difference; the commercial reason for the missing 100 units remains under review. Revenue Operations will reconcile the delivery and cancellation records by the fifth working day after month-end before FP&A proposes an outlook change.

Reviewer check: Confirm these are comparable recognized units, not bookings on one side and revenue on the other. Delivery, cancellation and revenue-cutoff evidence determine whether any units shifted periods. The calculation supports “fewer units,” not an unsupported statement that sales execution was poor. An order expected next month is not automatically recognized revenue next month.

2. Revenue mix: avoid calling a higher average a price increase

Example commentary: Revenue was 550,000 USD versus a 500,000 USD budget, 50,000 USD or 10% above plan. Total recognized units remained 1,000, and product-level prices were unchanged. The budget contained 800 units of product A at 400 USD and 200 units of product B at 900 USD; actuals contained 700 A and 300 B. The increase reflects a larger share of product B, not a price rise. Commercial Finance will confirm the approved product mapping and margin implications at the next monthly review.

Reviewer check: The average rises from 500 to 550 USD while neither product price changes. Do not label the whole difference “pricing power.” Validate product identifiers, returns, discounts and recognition basis. Higher revenue mix does not establish higher contribution without the relevant cost data. A multi-product bridge needs explicit mix rules, not a single blended price calculation.

3. Payroll: show vacancy savings and their offsets

Example commentary: Payroll expense was 905,000 USD against a 1,000,000 USD budget, 95,000 USD or 9.5% below plan. The approved workforce reconciliation attributes 113,000 USD of lower expense to later starts, partly offset by 18,000 USD of additional overtime and employer charges. This is not a demonstrated productivity improvement. People Finance will reconcile revised start dates with the next forecast by the fifth working day, with the forecast owner approving any change.

Reviewer check: The bridge is -113,000 + 18,000 = -95,000 USD. Use authorized payroll and workforce records, excluding individual pay details from broad circulation. Determine whether vacant roles are still planned, cancelled or replaced by contractors; those imply different future effects. Do not extrapolate a monthly vacancy benefit across the year or infer employee performance from it.

4. Contractors: distinguish changed scope from delivery timing

Example commentary: Contractor expense was 672,000 USD versus 600,000 USD budget, 72,000 USD or 12% above plan. An approved remediation extension accounts for 46,000 USD. A further 26,000 USD relates to work planned for the previous month but performed and accepted in the current month under the reviewed service schedule. Procurement will confirm the remaining extension scope before the next commitment; Accounting will retain the service-period support with the reporting pack.

Reviewer check: This timing explanation depends on when the work occurred and the applicable recognition policy, not when an invoice arrived. If the service was actually performed earlier and the ledger needs correction, resolve that as an accounting issue before approving the paragraph. A signed change order supports scope, but does not by itself verify delivered work or expense recognition.

5. Marketing: make the gross offsets add up

Example commentary: Marketing expense was 340,000 USD against a 400,000 USD budget, 60,000 USD or 15% below plan. Campaign services budgeted at 85,000 USD were deferred and had not been delivered in the reporting month; an event cost overrun added 25,000 USD. The net underspend is therefore 60,000 USD, not 110,000 USD. The campaign owner will confirm the revised delivery calendar before the next forecast review; event procurement will explain the overrun separately.

Reviewer check: -85,000 + 25,000 = -60,000 USD. Use the media schedule, service-delivery evidence and event cost records, not just cash payment dates. The postponed work may create future expense. Lower current expense says nothing by itself about campaign effectiveness or return on advertising spend. Keep any marketing-performance assessment separate and supported by its own attribution data.

6. Cloud and software: retain a quantified unknown

Example commentary: Cloud and software expense was 840,000 USD versus 700,000 USD budget, 140,000 USD or 20% above plan. The reviewed usage allocation supports 92,000 USD from additional workload, and an approved software tier adds 31,000 USD. The remaining 17,000 USD is unassigned pending invoice-allocation review. The cloud-cost owner will resolve that allocation by the fifth working day; Engineering will assess the workload driver before proposing optimization.

Reviewer check: Supported drivers total 123,000 USD, not 140,000 USD. Do not rename the 17,000 USD remainder “increased usage” without evidence. Preserve usage units, tagged populations, rate basis and invoice version. Lower next-month spending would not establish improved unit economics if workload also fell. Any promised saving needs its own baseline and measurement plan.

7. Travel and events: separate deferred activity from real fees

Example commentary: Travel expense was 152,000 USD against a 190,000 USD budget, 38,000 USD or 20% below plan. The summit reschedule deferred 46,000 USD of travel services, while 8,000 USD of nonrefundable change fees offset part of that reduction. Finance has confirmed the current-month recognition of the stated fees. The event owner will reconcile revised bookings and remaining commitments before the next monthly forecast review.

Reviewer check: -46,000 + 8,000 = -38,000 USD. A prepaid booking, refundable deposit, issued ticket and consumed travel service are not interchangeable expense evidence. Check the entity's policy and actual service period. The 8,000 USD fee is a cost of the change, while the deferred 46,000 USD may return later; neither should disappear from the explanation.

8. Facilities: distinguish a recurring base from an isolated repair

Example commentary: Facilities expense was 324,000 USD versus 270,000 USD budget, 54,000 USD or 20% above plan. Reviewed contract and expense schedules support 41,000 USD of additional recurring occupancy expense effective this month; emergency repairs account for 13,000 USD. Workplace Operations will confirm remaining repair obligations, and the budget owner will propose the revised recurring assumption for approval at the next forecast review.

Reviewer check: The contract's cash rent and recognized lease-related expense can differ. Use the applicable accounting schedule rather than mechanically treating a cash increase as expense. Confirm that repairs are appropriately classified; this example does not prescribe capitalization. Avoid annualizing the entire 54,000 USD: the recurring component and isolated repair have different forecast implications.

9. Currency translation: show constant-currency and reported effects

Example commentary: Reported operating expense was 1,067,000 USD against a 1,000,000 USD budget, 67,000 USD or 6.7% above plan. Under the approved constant-currency comparison, actual expense is 988,000 USD, 12,000 USD below budget. Translation contributes a separate 79,000 USD increase, producing the net 67,000 USD reported variance. Treasury will confirm the rate source and Finance the calculation method before the reporting pack is released.

Reviewer check: -12,000 + 79,000 = +67,000 USD. This is a hypothetical management comparison, not a prescribed statutory translation method. Retain local-currency amounts, entity scope, rates and conversion sequence. Do not also include the same translation effect in an operating driver. A favorable constant-currency result is not proof of cash savings or a recommendation to hedge.

10. Professional fees: service timing is not payment timing

Example commentary: Professional-fee expense was 375,000 USD versus a 250,000 USD budget, 125,000 USD or 50% above plan. Finance reviewed 90,000 USD of additional review scope and 35,000 USD of work performed this month rather than in the later month assumed by the budget. The engagement owner will confirm remaining work and whether the additional scope recurs before the next forecast approval. These amounts remain in actual expense; calling them unplanned does not remove them.

Reviewer check: 90,000 + 35,000 = 125,000 USD. An invoice received early or a payment made early would not, on its own, explain an expense variance. Inspect service dates, deliverables and accounting treatment. “One-time” must be supported by the engagement scope, not used to imply that similar costs cannot recur. Keep any adjusted management metric separately defined and approved.

Produce the commentary in six controlled handoffs

  1. Lock the inputs before drafting. Record budget and actual versions, entity, period, recognition basis, account mapping and currencies. If actuals are provisional, label them and define what could change.
  2. Select items using approved criteria. Combine amount, percentage and decision risk as appropriate. There is no universal threshold; an unbudgeted sensitive item can require explanation despite a small value.
  3. Build a signed driver bridge. Recompute totals, retain significant offsets and calculate the unexplained remainder. Keep alternative causal labels non-additive unless the allocation method explicitly supports them.
  4. Ask owners a narrow question. Provide the record and the exact gap: “Which delivery evidence supports this 35,000 USD shift?” is more useful than “Why are fees high?” Record disagreements rather than deleting them.
  5. Review words against the evidence. Check every “because,” “saving,” “temporary” and “will.” The finance reviewer approves the explanation; separate owners approve forecast, staffing, purchasing or treasury actions.
  6. Release a dated version and follow up. Retain the approval, recipient scope and prior version. At the next review, revisit unresolved drivers and predicted timing rather than copying last month's paragraph forward.

An illustrative cadence places input locking after the approved close extraction, owner questions before the reporting deadline, and unresolved-item review at the next agreed check. The fifth-working-day dates in the examples are teaching assumptions, not a standard or a promised completion time. The actual calendar must fit your close and management meetings.

Recompute the examples before polishing the narrative

Check the ten independent headlines

The following table is the arithmetic summary of the ten cases above. A minus sign means actual is below budget under this article's convention; it is not an automatic favorable-performance label. Do not sum the cases: they are independent scenarios, and the two revenue examples in particular are not additive.

Example Budget, USD Actual, USD Actual − budget, USD Variance / budget
1 Revenue volume 500,000 450,000 -50,000 -10%
2 Revenue mix 500,000 550,000 +50,000 +10%
3 Payroll 1,000,000 905,000 -95,000 -9.5%
4 Contractors 600,000 672,000 +72,000 +12%
5 Marketing 400,000 340,000 -60,000 -15%
6 Cloud/software 700,000 840,000 +140,000 +20%
7 Travel 190,000 152,000 -38,000 -20%
8 Facilities 270,000 324,000 +54,000 +20%
9 Currency 1,000,000 1,067,000 +67,000 +6.7%
10 Professional fees 250,000 375,000 +125,000 +50%

Download the ten-scenario CSV with signed drivers and residuals. It contains synthetic numbers for independent recalculation, not operational proof. The cloud row includes a 17,000 USD unexplained remainder deliberately: the table can reconcile without the cause being known. Use the companion worksheet to record the evidence that would be needed in a real report.

When volume and price both change, declare the allocation order

Consider a separate single-product illustration: budget 1,000 units at 500 USD gives 500,000 USD; actual 950 units at 480 USD gives 456,000 USD. The total revenue variance is -44,000 USD, or -8.8%. Using budget price for volume gives (950 − 1,000) × 500 = -25,000 USD. Using actual volume for price gives 950 × (480 − 500) = -19,000 USD. Together they explain -44,000 USD.

If both effects were calculated only on budget quantities or prices, the components would be -25,000 and -20,000 USD, requiring a separate +1,000 USD interaction term. Omitting that term would produce a wrong -45,000 USD explanation. State the method, and do not mix decompositions within one report. This is revenue analysis, not a contribution-margin calculation.

The Association of Chartered Certified Accountants explains the relationship between quantity, selling price and revenue, alongside model assumptions, in its cost-volume-profit analysis material. Our figures and decomposition are original teaching examples, not figures attributed to that source. Product mix and recognition issues require their own additional analysis.

Choose the simplest process that preserves evidence

A spreadsheet and manual review work well for a small reporting pack. Lock formulas, preserve versions and use the same evidence fields for favorable and unfavorable differences. The method becomes difficult when source files, reviewers and late changes multiply. Longer prose does not resolve that version problem.

Native planning reports can keep the calculation close to the governed data. Inspect the actual account mappings, signs and permissions, including the Oracle account-type variance behavior if relevant to your environment. A correct native variance still does not establish the commercial reason for it; owners must provide evidence.

Rules and scheduled queries suit stable comparisons. They can flag exceptions and build tables before a person writes the paragraph. Add failure handling for missing periods, changed mappings and partially refreshed actuals. Do not let a failed import silently publish yesterday's narrative next to today's numbers.

An agent-assisted workflow is worth evaluating when evidence collection is the bottleneck. It may help organize permitted records and questions, but introduces access, retention and verification requirements. Compare all approaches on reproducibility, explanation quality, permissions, version control and reviewer effort. If the existing native report and a short owner meeting already solve the task, an agent may not improve it.

Evaluate OpenMax as a commentary coordinator, not a finance approver

The OpenMax website describes human–agent collaboration, agent integration, role-based access and audit capabilities. These are vendor descriptions, not proof that your budget system, payroll register or planning model is already connected. No OpenMax-specific budget-commentary deployment or time-saving result is claimed here.

The proposed role to evaluate is coordination around approved finance inputs: organize source references, surface unanswered driver questions and prepare a review-ready draft. Ask for a demonstration of the actual connectors, entity and field restrictions, calculation handoff, source-version preservation, retention settings and approval gates. Do not rely on a prompt alone to prevent write access or confidential data sharing.

Prepare a sanitized month with a frozen budget, reconciled actuals and a finance-reviewed answer key. Include the marketing offset, the cloud residual, a zero budget, a changed forecast version and an early-payment/unchanged-expense case. A successful bounded test must reject unsupported explanations and preserve uncertainty, not merely produce ten polished paragraphs.

Require independent recalculation, working restricted evidence links, no unsupported causal assertions, no disclosure of individual payroll details and no unauthorized forecast or distribution action. Measure reviewer corrections and actual review time if you want evidence of usefulness; this guide supplies no performance benchmark. Discuss a bounded commentary workflow with OpenMax using the worksheet, not production credentials.

Reporting boundaries, risk and the next useful step

Internal budget notes are not automatically suitable for an annual report or investor communication. In June 2025, the International Accounting Standards Board revised its investor-focused Management Commentary Practice Statement; the International Financial Reporting Standards Foundation's supporting material explains that context. This guide is a narrower internal workflow and does not establish compliance with that statement or local disclosure obligations.

Do not infer employee performance, marketing effectiveness or permanent savings from spending alone. Do not remove expenses from actuals because they are unbudgeted, nor make accounting entries simply to match budget. Qualified finance owners decide recognition, correction, materiality and approved metrics; communications owners determine external distribution.

If actuals are still changing, use the month-end close checklist first. If the question is about settlement rather than expense, use cash-flow variance analysis. For assembling the wider pack, see financial reporting automation. These are related OpenMax resources, not independent capability verification.

Return to the opening marketing question: the useful answer is not only “15% below budget.” It is which work moved, which cost offset it, what remains to confirm and who will do that next. Start by opening one source-backed driver and checking its sign; only then polish the sentence.

Frequently asked questions

How long should budget commentary be?

Use the shortest explanation that includes the material result, supported driver, uncertainty and owned next step. One paragraph can be enough when detailed evidence is linked separately. Complex offsets may require a table; length is not a quality target.

Do favorable variances need the same review?

Yes. Lower expense can reflect postponed activity, incomplete accruals or a missing input. Higher revenue can reflect mix or timing rather than repeatable growth. Apply the same evidence and completeness checks to both directions.

Can I report only percentage variance?

No. Include the absolute amount, budget base and comparison scope. With a zero budget there is no defined percentage under the formula used here. A small or negative base requires a finance-approved presentation that avoids misleading interpretation.

Can AI provide the final causal explanation?

It can draft from permitted records, but a responsible business owner and finance reviewer must confirm material causes and implications. Model confidence, a ledger description or a plausible pattern is not evidence that an event caused the variance.

Are these examples actual OpenMax financial results?

No. They are independent fictional teaching scenarios with explicit assumptions and reproducible arithmetic. Replace the numbers, sources, dates and responsibilities with reviewed information before adapting their structure.

Sources, editorial method and correction history

This is an OpenMax-owned commercial resource by the OpenMax content team. The team created the examples, checked their arithmetic and used primary references for specific definitions and product descriptions. It did not conduct a customer finance deployment or verify a model's financial performance. No named qualified finance reviewer has been supplied; obtain professional review before operational use.

Sources checked September 4, 2026:

Correction, September 4, 2026: the earlier marketing example incorrectly combined an 85,000 USD reduction and a 25,000 USD increase as a 110,000 USD reduction. The corrected net reduction is 60,000 USD. The professional-fees explanation has also been rewritten to distinguish service-period expense from invoice or payment timing. All ten examples now expose budget bases, signed differences and review conditions. To request a correction, identify the section and supporting evidence through the site contact channel without sending confidential finance records.