Evaluation method
Budget vs Actual Variance Analysis with Source Checks
A variance report should show what changed and what evidence explains it. Start with matching source periods and categories, then calculate the difference. A fluent explanation cannot repair mismatched data.
Match scope before subtracting
Freeze the approved budget version and actual extract. Match period, entity, currency, net/gross basis and category mappings. A mid-month actual extract compared with a full-month budget can be useful only if the partial-period boundary is explicit.
Do not silently translate an unmapped source category into the nearest familiar budget line. Ask the owner to approve the mapping. Preserve excluded rows and their reasons so the final comparison can be reproduced.
Declare the calculation and sign convention
Use actual minus budget for the amount variance. For percentage variance, divide by the declared budget basis and explicitly handle zero or negative budgets. A zero denominator is not a zero-percent variance.
Interpret the amount by line type. Higher revenue and higher expense can both create a positive variance, but they have different implications. Keep the raw calculation separate from a favourable/unfavourable label.
| Illustrative line, PLN | Budget | Actual | Actual - budget | Interpretation |
|---|---|---|---|---|
| Revenue | 100000 | 90000 | -10000 | Below the revenue plan |
| Operating cost | 40000 | 45000 | 5000 | Above the cost plan |
| New unbudgeted line | 0 | 2000 | 2000 | Percentage unavailable; review the new item |
Tie the comparison to source controls
Compare selected budget and actual totals to independent source controls before commenting on differences. A balanced-looking table can still omit a category. Retain source cell addresses and the exact file version.
The illustrative amounts above explain the method only; they are not a measured Braio customer outcome. The synthetic source pack provides a separate reproducible format and identifies its deterministic generation boundary.
Explain drivers without inventing causes
Separate a mathematical contributor from its business cause. A larger expense line explains part of the total variance; it does not establish whether prices rose, volume changed or an item was miscoded. Request invoices, headcount or another appropriate source before naming the cause.
Mark an explanation as confirmed, hypothesised or unresolved. Assign a person and next check to a material unresolved item. Do not remove it because it weakens the narrative.
Deliver a reviewable package
Provide a summary, line-level variance table, source references, controls and open questions. Preserve the original and deliver a new revision when inputs change. Verify that the exported workbook and management document agree with the canonical calculation.
Reviewers decide the action to take; the report does not book corrections or approve spending. Start with one closed period and a small comparable set of categories before expanding the process.
Sources
Continue with your workflow
- How to Verify Numbers in an AI Financial Report
- Month-End Management Reporting Checklist
- From Excel Actuals to a Reviewable Management Report
- 13-Week Cash Flow Template and Verifiable Example | Braio
- Braio help - first workflow, QA and SEO/GEO reports
- AI agent security - access, approvals and costs | Braio

