eProcureAI / Solutions / See committed spend
Use caseInvoiced reporting is history. Counting commitment at approval moves a large part of your spend picture from something you report on to something you can still change.
One change in timing. Everything else about how you report stays as it is.
A budget report showing invoiced spend is describing decisions taken weeks earlier. The orders are out, the goods may already be on site, and the question of whether it was affordable is being asked after the money was committed.
The gap is larger than most people assume. A charge code showing one hundred and seventeen thousand spent against an allocation of two hundred and twenty looks comfortable. If fifty eight thousand is sitting on approved orders that have not been invoiced, the real position is under five thousand.
Everyone making decisions against that budget in the meantime is working from a number that is wrong by an order of magnitude, and nothing in the report tells them so.
Nothing here requires new data. The moment an order is approved, the company knows what it has committed. That fact simply is not carried into the budget position until an invoice arrives to force it.
Recording commitment at approval closes the gap without changing a single control or asking anybody to do extra work.
No commitment yet, and correctly invisible in the budget.
The company has now committed. In most systems the budget does not move, which is where the gap opens.
The commitment is external and awkward to unwind. Still invisible in invoiced reporting.
The obligation is certain. Finance still has not seen it in the position.
Visible at last, weeks after the decision. This is where most reporting begins.
Their position includes what has been promised, so the figure on screen is one they can plan against rather than one describing the past.
The person signing off sees what is genuinely left before they click, so approving over budget becomes a deliberate act rather than an accident.
Accruals come from open commitments and goods received but not invoiced. Both are already recorded, so the reconstruction step disappears.
Once this is true, most budget questions answer themselves.
| State | What it means | When it updates | Who cares most |
|---|---|---|---|
| Spent | Invoiced, matched and posted | When the invoice clears | Accounting |
| Committed | On an approved order, not yet invoiced | At approval | Budget owners and approvers |
| Available | Allocation less spent less committed | Continuously | Anybody about to request something |
Most reporting shows only the first. The second is where the surprises live, and the third is the only one that answers a requester's actual question.
The owner hears while there is still time, and the alert names the open requests creating the pressure.
Committed spend is known months before it invoices, which moves a chunk of the forecast from estimate to fact.
Drill from a variance to the transactions behind it, each with an approver and a reason.
Comparing available across codes shows where the pressure actually is rather than where it was last quarter.
When a code is short, moving budget is a recorded action with an approver rather than a quiet edit.
The two inputs are already recorded, so the calculation runs rather than being assembled.
The information already existed. All that changes is when it reaches the person who needs it.
Look at a number they can trust, and decide.
Moves the number at the right moment, then keeps it current.
We will show the committed position against it and where the gap sits.
Book your free demoRelated: All solutions and Budgets and Charge Codes