Stopping the spend at the point of commitment, not discovering it at month end.
Budgetary control checks spending against available budget before it is committed, reserving funds when a requisition or purchase order is raised rather than when the invoice arrives. Available budget is the budget less actuals less outstanding commitments.
Reporting actual against budget tells you what has already happened. By the time an invoice posts, the order was placed weeks earlier and the money is contractually owed. Control means the check happens at requisition or order, when declining it is still possible.
Set at the level control is wanted — cost centre, project, account group. Too granular and everything blocks; too coarse and nothing does.
A purchase order reserves funds. Available budget falls at that moment, not at invoice.
At requisition or order, against available budget. The response is pass, warn or block, configured per budget.
When the invoice posts, the commitment is released and the actual replaces it. Both must move, or the budget double-counts.
What happens at year end to open commitments — a policy decision that has to be made deliberately.
A department has a 20 lakh budget. Actual spend is 12 lakh, so the system shows 8 lakh available and approves a 6 lakh purchase order without comment.
What the check missed is 7 lakh of orders already raised and not yet invoiced. Genuine available budget was 1 lakh, not 8. The new order takes the department 5 lakh over, and nobody will know until those invoices post over the following weeks — by which point the goods have been received and the commitment is irreversible.
The fix is configuration rather than discipline: check the budget at the point of commitment, when the order is raised, rather than at the point of invoice. Most ERP systems support this and many are left on the invoice-level default, which makes the control a reporting mechanism rather than a preventative one. A budget check that triggers after the money is committed is telling you about history.
| Term | What it means |
|---|---|
| Budget holder | The person accountable for a budget line and its consumption. |
| Commitment | Money committed by an order but not yet spent, which must count against budget. |
| Available budget | Budget less actuals less commitments. The only figure worth checking against. |
| Budget check | The control preventing or warning on transactions exceeding available budget. |
| Virement | Transferring budget between lines, which should be controlled rather than informal. |
The commitment already exists. The check needs to be earlier to be a control at all.
Budget appears consumed twice and legitimate spend gets blocked.
Operations halt for trivial variances and people route around the system. Use warn where the risk is low.
Control at an excessively detailed level generates constant exceptions and the process is abandoned.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Available budget including commitments | The only meaningful measure of what is left. | |
| Budget overruns by department | Where control is failing, and whether it is systematic or occasional. | |
| Budget checks triggered and overridden | How often the control fires and how often it is bypassed. | |
| Virements processed | Transfers between lines. High volumes suggest the original budget was not realistic. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.