BAMML Executive Insights
Irregular Expenditure Is a Process Failure Before It Is a Governance Failure
Few phrases in South African public finance carry as much weight, or as much misunderstanding, as irregular expenditure.
It is read publicly as a synonym for money lost. Inside entities it is frequently something narrower: expenditure where the entity received what it paid for, at a defensible price, through a process that did not comply with a prescript.
That distinction is not a defence. Non-compliance is non-compliance. But it does determine where the problem actually is — and therefore what would fix it.
What is actually happening
Irregular expenditure is a compliance classification. It describes how the expenditure was incurred, not whether value was received.
Which means it usually traces back to a specific step in a process. A threshold that determined which procurement route applied, and the wrong route was taken. A required quotation that was not obtained, or was obtained after the fact. An approval given by someone without the delegated authority to give it. A deviation used where the circumstances did not justify one. A contract extended beyond its term without the right authorisation.
Each of those is a step. A step has an owner, a moment, and usually a reason — often an operational one. The deviation was used because the service was needed urgently. The approval was given by the available official because the delegated one was away. The contract was extended because re-tendering would have interrupted delivery.
None of that makes it compliant. But it tells you that the problem lives in the process, not primarily in anyone's intent.
Why it matters
The standard institutional response to irregular expenditure is investigation, followed by a determination, followed by condonation or recovery or write-off. All necessary. None of it preventive.
That response deals with expenditure already incurred. It does not touch the step that produced it. So the same step produces the same finding the following year, and the register grows, and the effort required to manage the register grows with it — until managing the accumulated balance consumes more capacity than fixing the process would have.
There is also a distortion effect. When everything from a minor procedural lapse to a serious failure carries the same label, the label stops discriminating. Officials become defensive about small things. Serious matters get less attention than they deserve, because they arrive in the same queue as everything else.
Entities that reduce irregular expenditure meaningfully tend to do so by treating it as a process-control problem with a compliance consequence — rather than as a compliance problem with an investigative response.
The Integrated View
| Discipline | The question it asks | What it produces |
|---|---|---|
| Risk & Compliance | Which prescript was not complied with? | The classification |
| Operational Performance | At which step did the process break, and why? | The cause |
| Financial Governance | Was value received, and at what price? | The financial reality behind the classification |
| Workforce Governance | Did the official know the rule, have the authority, and have a workable alternative? | Whether this is capability, authority or conduct |
| Executive Decision Intelligence | Which steps produce the most findings, repeatedly? | The short list worth fixing |
The bottom row is where the leverage sits. Most entities can produce a register of irregular expenditure. Very few can produce an analysis of which process steps generate it most often — which is the single most useful report in this whole area.
What good looks like
Three things separate entities that make progress from those that manage a growing register.
They analyse by cause, not only by amount. The register is sorted by the step that failed, so the pattern becomes visible. Usually a handful of steps generate most of the findings.
They ask whether the process is workable. If officials routinely deviate, the deviation is information. Sometimes the rule is being ignored. Sometimes the process cannot deliver at the speed the service requires, and the deviation is the only way anything gets done. Those two situations look identical in a register and require opposite responses.
And they fix the step. Clarify the delegation. Simplify the route below a threshold. Build the approval into the system so the transaction cannot proceed without it. Prevention at the step is cheaper than determination after the fact, by a wide margin.
What to do on Monday
- Sort the current register by the process step that failed, not by value. If that analysis does not exist, that is the first finding.
- Identify the top three steps. In most entities, a small number of steps produce the majority of findings.
- For each, ask whether the failure was capability, authority or workability. The corrective action differs completely depending on the answer.
- Check whether deviations cluster around particular services or periods. Clustering usually points at a process that cannot meet an operational deadline.
- Build one control into the system — a step that cannot be skipped — rather than issuing another circular reminding officials of the rule.
If the register is growing while the compliance training calendar is full, the problem is unlikely to be that people do not know the rules.
