Module 04

Suggestions arrive somewhere. Someone decides.

The engine never applies its own reallocation. That design choice only works if getting a decision made is frictionless, so routing is built around a single question: who owns this budget line, and what is the amount they can approve without a second pair of eyes.

Routes onOwner, amount, department
StepsOne to three
HistoryEvery decision retained
Two things get approved here

Spend before it happens. Reallocation after a flag.

Request type one

Spend approval

Someone needs to commit money against a category. The request carries the amount, the category, the reason and, critically, what the category reads right now and what it would read if approved. An approver should never have to open a second screen to know whether a request breaks a budget.

Request42,000 to Marketing
Category reads now78% of limit
Reads if approved113% of limit

A request that would breach the limit is marked as such before anyone clicks approve, and can be configured to require the reallocation to be approved alongside it.

Request type two

Reallocation approval

A category has been flagged and the engine has named a source. The request states the source, the destination, the amount, and what both categories read after the move. Approving it changes budget limits. It does not move a single rupee of actual money.

FromSupplies, 61% used
ToTravel, 112% used
Amount18,000
Reads afterTravel 100%, Supplies 91%

Where source and destination have different owners, both are asked. One cannot quietly take room from the other.

Routing configuration

Configured once, in the language of your org chart.

Routing is a set of rules, not a workflow builder you need training for. Most businesses need two rules. Larger ones rarely need more than five.

How finance teams configure this at scale
  • 01

    By category owner

    Every category names an owner. Anything touching that category goes to them first. For an owner-led business this single rule is the whole configuration.

  • 02

    By amount threshold

    Below a figure you set, the owner decides alone. Above it, a second approver is added. Thresholds are per category, because the amount that is routine for payroll is not routine for supplies.

  • 03

    By department boundary

    A reallocation that stays inside a department can be settled by the department head. One that crosses between departments escalates to finance, because it changes two budgets that answer to different people.

  • 04

    By delegation and absence

    Approvers can delegate for a date range. Requests do not sit in an empty queue while someone is away, and the delegation is recorded on the decision rather than hidden behind it.

Pending does not mean forgotten

Open requests carry the age of the request and the day of the cycle. A reallocation that sits unanswered for four days loses most of its value, so the queue makes that visible rather than quietly ageing.

Declines are as informative as approvals

A declined reallocation keeps the flag standing and records why. Three declines against the same category across three cycles is a budget that was set wrong, and the reporting will say so.

No silent approvals

There is no auto-approve, no timeout that assumes consent and no engine authority to proceed without an answer. An unanswered request stays unanswered, visibly.

Worth restating

Approving a reallocation changes a budget limit. It never moves money.

BudgetGaga holds no payment credentials and has no write access to any connected account. When you approve a reallocation, two budget figures change inside BudgetGaga. Whatever happens in your bank is still done by you, through your bank.

Pick your month end

There are only two ways to find out you went over budget.

One of them still lets you do something about it.

The statement routeDay 31

You read the number after it is spent

The category closed at 112 percent. The money left the account three weeks ago. The only decision available now is which line to explain it against.

  • Overage discovered at close
  • Reallocation window already gone
  • Next cycle starts on the same blind footing
The BudgetGaga routeDay 11

You read the pace while it still bends

At 74 percent on day 11 the category is flagged as trending over, with an under-spent line named as the source. You approve the shift, or you tighten the spend. Either way you chose.

  • Flagged the moment the pace breaks
  • Reallocation source named, not hunted for
  • Every move still waits on your approval