What commitment accounting
changes about budgeting

A budget report built on invoiced spend is accurate and out of date at the same time, which is a difficult combination to argue with.

Every figure in it is correct. It simply describes a position that existed several weeks ago, before the orders currently sitting with suppliers were approved.

The gap nobody sees

Consider a budget where a meaningful amount has been invoiced and a further amount sits on approved orders that have not been billed yet.

The report shows the first number. The second is invisible, and it is money the organisation has already committed to spending. Anybody making decisions against that budget in the meantime is working from a figure that is wrong in a predictable direction.

Nobody decides to overspend a budget. They approve reasonable things against a number that was already out of date.

Three states rather than two

Commitment accounting introduces a third state between nothing and spent.

Most reporting shows only the first. The second is where the surprises live, and the third answers the question people actually have.

What actually changes

Approvers see the real position. The person signing off sees what is genuinely left rather than a figure that ignores three open orders. Approving over budget becomes deliberate rather than accidental.

Alerts arrive while they are useful. A warning at a threshold you choose, naming the open requests creating the pressure, gives somebody a decision to make. The same warning at month end gives them an explanation to write.

Forecasting improves without better modelling. Committed spend is a fact rather than an estimate. Including it converts part of the forecast from projection to arithmetic.

What it asks of you

Being honest about the cost of this, because it is not free.

It requires purchases to be approved in a system that knows about budgets, which means the approval cannot happen in email. That is the real change, and it is the reason commitment accounting usually arrives alongside procurement software rather than on its own.

It also requires charge codes that mean something. If purchases are coded loosely or corrected later, the committed figure is committed against the wrong thing and the benefit disappears.

Effect on month end

This is where finance teams notice it most, and it is often unexpected.

Accruals for goods received but not invoiced normally require somebody to work out what arrived and was not billed. When both the order and the goods receipt already exist as records, that calculation runs rather than being assembled.

Teams that adopt this typically report the close becoming more predictable rather than dramatically shorter, which is arguably more valuable.

Where to start

Two things, in order.

First, make sure approvals happen somewhere that knows about budgets. Until that is true, nothing else works, because there is no moment at which the commitment can be recorded.

Second, get the charge code structure right before worrying about thresholds and alerts. A commitment recorded against a vague code is not much better than no commitment at all.