Budget Lifecycle: Draft, Approve, Lock, Track

A budget spreadsheet has one state: whatever it currently says. Nobody can tell you, six months later, whether a number was the original plan, a revision after pushback from the CFO, or a resubmission after finance rejected the first draft. Rexfin treats a budget as something with a lifecycle, not a file: draft, submitted, approved or rejected, and locked, with every transition kept on the record.

What the lifecycle actually looks like

A budget version starts as a draft. Someone submits it for review. From there it goes one of two ways: approved, which moves it toward being locked as the plan of record, or rejected, which sends it back with a reason attached. Rejection is not a dead end: a rejected version is resubmittable, and once it’s resubmitted the rejection markers clear so the version’s status never contradicts its own history. What it isn’t is silent: rejecting a budget requires a note, so “no” always comes with “because.”

Locking is the meaningful boundary. An approved-and-locked version becomes the baseline everything else measures against: the number in budget-vs-actual variance reports, the anchor a rolling forecast carries forward from. A rejected version never gets locked, precisely because it was never approved.

Every transition is logged, not overwritten

Behind the visible status, Rexfin keeps an append-only event log: who submitted, who approved or rejected, what the status was before and after, the note attached, and when it happened. Nothing gets updated in place. If a budget was rejected twice before it was approved, that history stays intact rather than being quietly replaced by the final “approved” flag. That log is what makes the audit trail real instead of decorative: you can reconstruct exactly how a number came to be the plan, not just what the plan currently says.

Currency mismatches are flagged, never guessed

A budget is built in whatever currency someone typed it in. If that doesn’t match the entity’s reporting currency, Rexfin doesn’t quietly convert it and hope the rate was close enough: it shows an explicit note wherever the plan appears, on the variance view, the plan page, and any comparison that does arithmetic across the two currency, saying plainly that no FX translation has been applied. A budget-vs-actual bridge that silently mixes AED and USD is worse than one that admits it can’t reconcile them yet.

Mid-year rebudgets don’t fake a full year

Plenty of budgets aren’t built on January 1st. A version created in June only covers the months it was actually meant to cover, and Rexfin derives that coverage from the plan itself rather than assuming a clean twelve months. Ask for a variance on a month the budget never covered and you get a blank, not a zero, because a missing budget number and a budget of zero mean completely different things, and collapsing them into the same cell would make an unbudgeted month look like a blown target.

Timezone-correct month boundaries

One detail that sounds trivial and isn’t: what counts as “this month” for a partial-period actual. Rexfin computes that boundary in the entity’s own business timezone, not the server’s UTC clock, so a transaction near midnight doesn’t get filed into the wrong month just because of where the calculation happened to run. Partial months are marked as month-to-date and excluded from the favorable/unfavorable read that applies to closed periods, a half-finished month isn’t a miss yet.

Who this is for

Finance teams running a real approval chain: someone drafts, someone else signs off, and a rejected draft needs to come back with a fix, not disappear into a new spreadsheet with no record of what changed. It’s also for teams operating across currencies or with non-calendar planning cycles, where the honest answer to “does this tie out” is sometimes “not yet, and here’s why,” rather than a number that only looks reconciled.

If your current budget process is a shared file with tracked changes turned off, book a demo and we’ll show you what a lifecycle with a memory looks like. For the full set of planning and reporting tools this connects to, see the Rexfin product tour.