The Budget-vs-Actuals Review, Without the Argument About Whose Numbers Are Right

Every finance team runs some version of the same monthly ritual: pull the actuals, pull the budget, line them up, and explain the gap. The ritual is not hard conceptually. It becomes hard when the budget file is a spreadsheet someone rebuilt in March, the actuals are still being finalized, and half the meeting is spent agreeing on what the numbers even are before anyone discusses why they moved. Rexfin’s budget-vs-actuals view is built to remove that first half of the meeting, not to replace the judgment in the second half.

What the grid actually shows

The BvA table puts four things side by side for each line: the actual figure, the budget for that fiscal year, the variance between them, and next year’s forecast. The budget and forecast columns carry a visible unaudited tag: they are plan data, not filed results, and the interface never lets you forget that. The variance column gets a directional arrow and a color, and the color logic knows the difference between a revenue line and an expense line: spending more than budgeted is unfavorable, but recognizing more revenue than budgeted is favorable, even though both are the same arithmetic sign. Get that backwards once in a live meeting and you lose the room.

The variance column only appears when the actual period you’re looking at is genuinely the same year the budget was built for. If those two don’t match, Rexfin doesn’t render a variance at all rather than compare figures that were never meant to be compared. And if a month hasn’t been budgeted yet, the cell shows as blank, not zero: a blank means “no budget submitted,” a zero would wrongly read as “spent exactly nothing,” and those are very different things to walk into a variance review meeting believing.

Actuals you can click into, plan numbers you can’t

Every actual in the grid traces back to the page it came from: click it and you land on the source document. Budget and forecast cells don’t get that same drill-through, and that’s deliberate rather than an oversight: they were never verified against a filed source in the first place, so giving them a citation affordance would imply a level of assurance they don’t have. The honesty is the feature. You get to see plan and actual next to each other without the tool pretending the plan side has been audited.

When the budget itself changes mid-year

Budgets get revised. Someone submits a version, a reviewer sends it back with a note, it gets reworked and resubmitted, and eventually a version gets approved. Rexfin keeps every submit, approval, and rejection as a permanent, ordered record, so if a version bounced twice before landing, that history is still there to check rather than reconstructed from memory during a board reporting cycle. When a rebudget happens partway through the year, the tool also notes which months the new version actually covers, so the review doesn’t compare this month’s actual against a budget baseline that was drafted for a different stretch of the year.

The currency question nobody likes answering live

If a budget was built in a currency that doesn’t match your reporting currency, Rexfin does not quietly convert it for you. There’s no FX translation layer on plan values yet, so rather than fabricate a converted figure, it puts an explicit note on the BvA, the plan page, and the comparison view saying the numbers aren’t on the same currency basis. That’s a deliberately unglamorous answer, but it’s the honest one: a silently-wrong conversion is worse than a visible gap during budgeting season.

Seeing more than one year at once

Because actuals accumulate across every filing you load, the trend view can pivot a line item across several fiscal years at once, and if a later filing restates a prior year’s number, the restated figure is what shows, not the stale original. Year-over-year and multi-year growth are only calculated where the comparison is real: consecutive years for YoY, and only where the math actually holds for a growth rate. Fiscal years that don’t run calendar-year also aren’t silently forced onto a January boundary; the comparison respects whatever year-end your entity actually uses.

None of this replaces the conversation about why a line missed. It just means the meeting starts from numbers everyone in the room already agrees on, which is most of the argument you were having anyway. For the fuller picture of how this fits the rest of the close, see the monthly close walkthrough or browse the rest of the finance team use cases pillar.