The underpayment you built into your payroll on day one
Somebody configured the payroll system when the business was smaller, mapped the pay items as best they understood them, and the system has been applying that configuration faithfully ever since. It does not make errors. It repeats the one it was given, every cycle, for every employee it applies to.
That is what makes payroll configuration errors expensive. A manual mistake affects one pay. A configuration error affects every pay until somebody finds it, and it is rarely the business that finds it.
Why the system will not tell you
Payroll software is built to process, not to interpret. It will calculate overtime exactly as the rule was written, including when the rule was written wrong. It will accrue leave on the basis it was set, including when that basis does not match the award.
The compliance judgement sits outside the software. Where a business configures payroll by working out what looks reasonable, rather than by reading the award, the system becomes an efficient way to apply a misreading at scale.
The configuration errors that cause the most damage
Error | How it is configured | What it produces |
Overtime thresholds set to a flat weekly figure | Overtime triggers only after a weekly total of hours | Misses daily overtime, shift-based thresholds and overtime on days outside the ordinary pattern |
Penalty rates mapped to the wrong time bands | Weekend, evening and public holiday windows approximated rather than taken from the award | Underpayment or overpayment on every shift that touches a boundary |
Allowances omitted at setup | Allowances not in the initial build are never added | Industry, tool, travel, meal and laundry allowances simply never paid |
Leave accruing on the wrong basis | Accrual set on a fixed amount per period rather than on ordinary hours worked | Compounding error for part-time and variable-hours employees, surfacing at termination |
Casual loading absorbed into the base rate | One combined rate entered as the base | Loading not visible in records, and overtime and penalties calculated on an incorrect base |
Superannuation calculated on the wrong earnings base | Super applied to a subset of payments | Shortfalls across every affected cycle |
Public holiday rules not configured by state | One national calendar applied | Incorrect payment for employees in states with different gazetted days |
Annualised salary arrangements with no reconciliation | Salary entered, award comparison done once at setup | No mechanism to detect when actual hours have outgrown the salary |
Termination payments calculated by the system without review | Final pay run automatically | Leave loading, notice and redundancy components misapplied at the point of highest scrutiny |
Where the exposure compounds
Two features of payroll make configuration errors worse than they first appear.
The first is dependency. Base rate feeds overtime, penalties, leave loading, superannuation and termination payments. An error in the base does not stay in the base. One wrong setting produces errors in six places.
The second is time. Nobody audits a payroll that is running. There are no complaints, the pay runs process, and the configuration is treated as settled because it has been in place for years. Length of service in a payroll system is routinely mistaken for evidence that it is correct. It usually just means the error is older.
Record-keeping obligations sit alongside this. An employer who cannot produce records showing how hours were classified and paid is in a weaker position than one who can, independent of whether the underlying payment was right.
How to audit your own configuration
You do not need a project to find out whether you have a problem. You need a sample.
Identify the awards that apply to your workforce. If this is uncertain, resolve it before touching the payroll, because every setting downstream depends on it.
Take one employee from each distinct employment type: full-time, part-time, casual, shift worker, salaried.
For each one, take a single completed pay period and calculate the pay by hand from the award, working from their actual hours.
Compare your calculation to what the system produced, line by line rather than on the total. Totals can match while the components are wrong.
Where the figures differ, identify the setting that caused it rather than correcting the individual pay. The pay is the symptom.
Check the same setting's effect across everyone it applies to, which tells you the scale.
Get advice before remediating. How a remediation is calculated, documented and communicated affects both the liability and how employees receive it.
Five employees and one pay period each is a morning's work. It is the cheapest diagnostic available in this area.
Frequently asked questions
Does using reputable payroll software mean we are compliant?
No. The software applies the configuration it is given. Award interpretation is the employer's responsibility, and most products are explicit about that in their own terms.
Our bookkeeper handles payroll. Is that covered?
Processing and award interpretation are different skills. A bookkeeper may process payroll accurately against settings that were never checked against the award.
We pay above award rates. Does configuration still matter?
Yes. A higher base does not automatically cover every entitlement, and allowances, loadings, overtime and penalty components are assessed on their own terms. Paying more than the minimum is not the same as paying correctly.
Find it before it finds you
Payroll configuration errors are inexpensive to fix and expensive to discover late. IndustrialHR Payroll handles payroll processing, system configuration, compliance review and leave management, and IndustrialHR runs the remediation projects where an error has been running for some time.
IndustrialHR Alliance members can get written award and payroll guidance before a setting is changed rather than after.
To discuss a payroll review, contact Rhiannon on 0481 100 416, email [email protected] or schedule a consultation.
Employers dealing with this now can book a free 30 minute discovery call or a 60 minute case review with Rhiannon. Book a consultation. IndustrialHR does not provide legal advice.
