IndustriesPublic Sector
You cannot
spend an
appropriation
twice.
Commercial finance asks what you have spent. Public finance asks what you have committed, because an order placed against an exhausted budget is a governance failure whether or not the invoice has arrived. Most systems record the invoice.
Roads has spent 71% and committed a further 33%. On a spend report it is comfortably inside budget with five months to run. On a commitment basis it is already four points over, and the next requisition should not be approved. IT modernisation shows the opposite shape — barely spent, largely committed — which is a delivery question rather than a financial one.
Casework
Eighty-nine cases are
past the statutory
window.
An average response time is a comfortable number. The distribution is the accountable one, because the obligation is per case and the tail is where the complaints, the appeals and the ombudsman referrals come from.
The mean of 11.4 days is comfortably inside the obligation and describes none of the eighty-nine cases that are not. Work is queued by age against the threshold rather than by arrival order, so the tail is worked first.
Control
Designed to be
audited.
Commitment accounting at the requisition
The budget check happens when someone asks to spend, not when the invoice is entered. An appropriation cannot be exceeded by orders nobody has posted yet.
Procurement thresholds enforced, not advised
Value bands determine the required competition, the approvals and the publication obligations. Crossing a threshold changes the workflow automatically rather than relying on the buyer remembering.
Every decision attributable
Who approved what, on what authority and under which delegation, held in an immutable log. Reconstructing a decision for an auditor or a committee is a query rather than an investigation.
Virement is a controlled event
Moving budget between programmes follows the delegation rules, records the justification and leaves both sides of the transfer visible in the year-end position.
Disclosure without a data project
Spend over the publication threshold, contract registers and payment performance are reports over live records, not an annual extract someone assembles by hand.
Year-end is a boundary, not an event
Accruals, commitments carried forward and the treatment of underspend follow rules configured once. The closing position is visible in month nine, which is when it can still be influenced.
Questions public bodies ask
Can this meet our national accounting framework?
The ledger is multi-book, so a statutory framework and a management view are maintained over the same transactions rather than reconciled afterwards. The specific framework — IPSAS, a national code, or a sector variant — is configuration, and it is one of the first things modelled during deployment.
What about procurement regulations and publication duties?
Thresholds, competition rules and publication obligations are configured per jurisdiction and enforced in the workflow. Where a national tendering portal must be used, it is treated as an integration at the perimeter rather than reimplemented inside the platform.
Where would our data be held?
In the region selected at provisioning, including backups and replicas, and it does not move without an explicit logged migration. Where sovereignty requirements go beyond region selection, that is an enterprise conversation before contract rather than a configuration afterwards.
Our staff have used the same system for fifteen years.
Then the risk is change, not software, and the parallel run exists for exactly that. Both systems process the same period until the closes agree, and the incumbent stays available read-only afterwards. We would rather extend that period than compress it.