Most spend surprises are not overspending. They are late information. When commitment is recorded at approval rather than at invoice, the number in front of you is one you can still act on.
Written for the person signing off. Not for the person configuring the system.
Finance viewWhat you see today
COMMITTED SPEND/BUDGET CONTROL/SEPARATION OF DUTIES/AUDIT EVIDENCE/ACCRUALS/SPEND ANALYSIS/APPROVAL THRESHOLDS/MONTH END/COMMITTED SPEND/BUDGET CONTROL/SEPARATION OF DUTIES/AUDIT EVIDENCE/ACCRUALS/SPEND ANALYSIS/APPROVAL THRESHOLDS/MONTH END/
The situation
The number arrives after the decision has been made
Finance leaders rarely complain that they cannot see spend. They complain that they see it too late to do anything about it.
A budget report showing invoiced spend is describing decisions made weeks earlier. The orders are out, the goods may already have arrived, and the conversation about whether it was affordable is happening after the money was committed.
The gap is not small. A charge code showing one hundred and seventeen thousand spent against two hundred and twenty can have another fifty eight thousand sitting on approved orders that have not been invoiced. On paper there is a hundred thousand left. In reality there is under five.
Recording commitment closes the gap
When an order is approved, its value counts against the budget immediately. Budget owners see what is genuinely left, and so does the next approver before they decide. The month end surprise stops happening because the information arrived while it was still useful.
The controls come with it
Separation of duties enforced by the system rather than by policy. Every override logged with a reason. Evidence produced by a filter rather than a fortnight of asking people for emails. These are the things that make an audit routine rather than an event.
The timing problem
Five stages, and only one of them is visible today
Stage 1
Somebody decides they need something
No financial impact yet, and correctly invisible to finance.
VisibleNot yet
1
Stage 2
It is approved
This is the moment the company commits. In most systems nothing happens to the budget here, which is the entire problem.
Should be visibleYes
2
Stage 3
The order goes to the supplier
The commitment is now external and difficult to unwind. Still invisible in invoiced reporting.
UnwindingNow expensive
3
Stage 4
Goods arrive
The obligation is real. Finance still has not seen it in the budget position.
ObligationNow certain
4
Stage 5
The invoice posts
Finally visible, weeks after the decision. This is where most reporting starts and it is far too late.
VisibleAt last
5
What changes for finance
Three practical differences in the first quarter
The budget position is current
Not a report you request. A number that includes what has been promised, available to whoever needs it, whenever they look.
Commitment recorded at approval
Owners see their own position without asking
Approvers see impact before deciding
No consolidation exercise to produce it
Charge code 4403Live
Allocation$180,000
Spent$117,000
Committed$58,300
Available$4,700
CurrentNot as at last month end
Month end stops being a rebuild
Accruals come from open commitments and from goods received but not yet invoiced, both of which the system already knows. Nobody assembles them by hand.
Accruals calculated from records that already exist
Goods received not invoiced included automatically
Ageing live rather than assembled
Close timeline becomes predictable
Month endLive
AccrualsAutomatic
Received not invoicedIncluded
Manual rebuildNone
TimelinePredictable
Built as you goNot assembled at the end
Evidence is a filter, not a fortnight
When somebody asks for a sample of approvals with supporting documents, that is a search and an export rather than a week of asking people to forward emails.
Every approval carries who, when and why
Overrides exported as their own report
Documents attached to the transaction
Sampling done by filter
Evidence requestLive
PopulationFilterable
SampleExportable
DocumentsAttached
Time to produceMinutes
A searchNot an investigation
Controls that hold
Five things enforced by the system, not the policy
The distinction matters. A control that depends on somebody remembering is not a control.
Control
How it is enforced
What it prevents
Separation of duties
The same person cannot request, approve and release payment, including through delegation
The most common internal fraud pattern
Approval thresholds
Rules match on department and amount before anybody is notified
Purchases quietly approved below the right level
Budget checks
Charge code balance checked at submission, warn or hard stop per code
Commitments made against money that is not there
Three way matching
Order, receipt and invoice compared before payment is released
Paying for goods that never arrived
Override logging
Every exception carries an approver, a reason and a timestamp
Exceptions becoming invisible over time
None of these require anybody to consult a policy document, which is why they still work in the fourth quarter when everyone is busy.
Questions you get asked
Six things a CFO is asked to answer
Committed
What have we actually committed?
Open orders by charge code, current to the minute, including what has not been invoiced yet.
AnswerOn screen
Overspend
Why did that budget go over?
Drill from the variance to the transactions behind it, with the approver and reason on each.
AnswerTraceable
Audit
Show me a sample with support
Filter the population, export the sample, documents attached.
AnswerMinutes
Savings
What did procurement actually save?
Sourcing baseline against award, plus findings from spend analysis with the transactions attached.
AnswerWith evidence
Suppliers
How exposed are we to one supplier?
Spend by supplier and concentration, visible without building a report.
AnswerStandard view
Timing
Why is the close slipping?
Usually accruals. Building them from open commitments removes the step entirely.
AnswerAutomatic accruals
Who does what
The short version of your involvement
The aim is that finance spends its time deciding rather than assembling the information needed to decide.
What you do
Set the thresholds, look at the position, and decide on the genuine exceptions.
The human partLive
Set thresholdsOnce, with procurement
Review the positionWhenever you want
Decide exceptionsThe ones that reach you
Answer the boardFrom current numbers
DecisionsNot assembly
What eProcureAI does
Keeps the numbers current and the controls running without your attention.
The automatic partLive
Record commitmentAt approval
Enforce separation of dutiesStructurally
Check budgetsBefore approval
Build accrualsFrom open commitments
Log every overrideWith a reason
Runs unattendedIncluding in a busy quarter
0commitment recorded, not at invoice
0separation of duties enforced, including via delegation
0accruals built from open commitments
0to produce an evidence sample with documents
FAQ
Questions people actually ask
What is the single biggest change for finance?
Commitment being recorded at approval rather than at invoice. It moves a large part of your spend picture from history to something you can still act on.
Does this replace our accounting system?
No. Your accounting system keeps the financial record. This runs the buying process and keeps the commitment position current, which is something invoiced reporting cannot do by definition.
How does it help at month end?
Accruals build from open commitments and from goods received but not yet invoiced, both already recorded. That removes the manual reconstruction most teams do every month.
Can a budget stop a purchase outright?
Per charge code, yes. Most teams warn on operating budgets and hard stop on capital and project codes, because the consequence of getting those wrong is different.
How is separation of duties enforced?
Structurally. The same person cannot request, approve and release payment, and that holds through delegation chains, which is the loophole most implementations forget.
What does an auditor actually get?
A filterable population, an exportable sample, and the documents attached to each transaction along with who approved it and why. It takes minutes rather than a fortnight.
How long before we see the benefit?
Cycle time and visibility improve immediately. Spend analysis needs a quarter or two of clean data behind it before the findings are substantial enough to act on.
What if we already have strong controls?
Then this is about timing and effort rather than control. The same controls run without anybody having to remember them, and the information arrives while it is still useful.
Bring a budget you cannot currently see clearly
We will show the committed position against it and where the gap sits. Thirty minutes, no slides.