HR & Payroll
Payslip Allowance Anomalies
Out-of-band allowances and unbacked earnings codes are a common route for payroll leakage and policy non-compliance.
Why unbacked allowances erode payroll integrity
Allowances, manual adjustments and recurring earnings codes are where payroll fraud and policy drift most often hide, because they sit outside the standard salary scale and are easy to add without scrutiny. Every earnings code paid to an employee should trace to an approved policy, a council or board resolution or a signed instruction; where it cannot, the expenditure is exposed to an irregular-expenditure finding under the MFMA or PFMA. AuditPro Core profiles allowances against policy bands and flags codes that recur without authority, giving HR and internal audit a clear list of items to substantiate.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Out-of-band claims
126
▲ 18
Manual adjustments
R 3.4 m
Codes without policy
9
Recoverable
R 1.1 m
Anomalous earnings by code
Top unsupported allowance claims
| Entity | Earnings code | Amount | Policy backing |
|---|---|---|---|
| KZN Education | Standby | R 412 000 | None |
| Sedibeng DM | Acting allow. | R 287 000 | Expired |
| Transnet | Danger pay | R 198 000 | None |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Policy-backed versus discretionary pay
Each allowance should map to an approved rate and eligibility rule. Discretionary or manually keyed amounts that exceed the policy band are the first candidates for review.
Recurring manual adjustments
A manual adjustment is meant to be a one-off correction. When the same manual code recurs month after month it has effectively become a permanent benefit without ever being approved as one.
Earnings-code proliferation
Uncontrolled creation of earnings codes makes payroll opaque and lets unauthorised payments masquerade as routine. A lean, governed code set is itself a control.
Tax and benefit consequences
Allowances often carry PAYE and fringe-benefit implications. An allowance paid outside policy is frequently also mistreated for tax, compounding a control weakness into a statutory exposure.
How AuditPro Core Bridges the Gap
- Policy-band testing: each allowance is measured against its approved rate and eligibility rule, with out-of-band amounts raised for review.
- Recurrence detection: manual adjustments that repeat across cycles are flagged as de facto permanent benefits lacking formal approval.
- Authority traceability: every flagged code links to the resolution, policy or instruction that should authorise it — or shows the gap where none exists.
- Audit-ready export: the anomaly register exports with policy references attached for the working-paper file.
Key Takeaways
- Every earnings code paid should trace to an approved policy or instruction.
- Recurring manual adjustments are permanent benefits that never went through approval — treat them as such.
- Controlling the earnings-code catalogue is a preventive control, not housekeeping.
- Unbacked allowances usually carry a parallel PAYE or fringe-benefit exposure.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.