Budget monitoring
Compare actual spend to the approved plan each period and surface the overrun while there is still budget left to move.
Tools
Pigment, NetSuite, Metabase, Validis, SAP S/4HANA
Outcomes
Variance pack issued within two days of close • Overruns flagged before the spend happens • Every variance carries a named owner • Plan changes recorded with an approver
Documentation
Instruction-ready detail below
A department head usually learns they are forty percent over plan three weeks before the budget meeting, because the last comparison of actual to budget was run in December. The monthly variance pack is kept by one person in a spreadsheet, and that person is on leave more often than not. This workflow rebuilds the comparison on a fixed schedule, taking actuals from the ledger and the plan from the approved budget, grouped by department, by cost center, and by the person who can act on it. Lines that cross a set threshold are pulled out with the size of the gap attached, and each is marked as a one-off or as a run rate that will repeat. Anything posted to the wrong cost center is separated out first, because a coding error and a genuine overrun need different conversations. The pack reaches each owner before anyone else sees it, so the fix starts with the person who can make it. A person still decides which variances are acceptable and who absorbs them.