Award Rate Checker
Reconciles every payslip line against the modern award before the pay run leaves, so an underpaid weekend penalty or missed allowance gets caught — and corrected — before it becomes a wage-theft exposure.
It reads each payslip line, compares the paid rate to the award minimum for that classification and shift, and flags the gap with the clause cited — a payroll officer approves before any back-pay is posted.
Where this works well
The slow, invisible problem this surfaces is the penalty that quietly never gets applied. A casual rostered across a Saturday, a Sunday and a public holiday should be paid three different multipliers — 150%, 175% and 250% under the General Retail Industry Award 2020 [MA000004] — and the failure mode is mundane: the shift gets paid at the ordinary casual rate because nobody re-checked. Multiply one missed weekend penalty across a fortnightly run of casuals and the shortfall compounds silently until a back-pay audit finds it years later.
This pattern earns its keep for the payroll officer or bookkeeper running award-covered, penalty-heavy rosters — retail, hospitality, aged care — where the same employee crosses several penalty bands in one period and the volume is too high to hand-check every line. It is most valuable as the last gate before a pay run leaves: it reads each earnings line, compares the paid rate to the award minimum for that classification and shift, and puts the gap in front of a human with the clause attached, so the catch happens before the money moves rather than at audit.
Where it works badly
It is only as right as the rules and classifications loaded into it. If an employee is coded to the wrong award level, the tool will faithfully check against the wrong minimum and clear a payslip that is actually underpaid — a confident, wrong "compliant". The same applies to an out-of-date rule set: encode last July's rates and it will flag correct pay as short, or miss a shortfall, against superseded numbers. The arithmetic is reliable; the inputs are where it fails.
It also struggles where the payslip doesn't say enough to reconcile. A line labelled "weekend hours" with no Saturday/Sunday split, a casual rate with the 25% loading folded in and no breakdown, or an annualised salary that's meant to absorb penalties under a set-off clause — these are interpretation calls, not arithmetic, and it should flag them for a person rather than guess. The honest test: if your own payroll officer couldn't tell from the payslip alone whether a Sunday penalty was paid, neither can this. If most of your pay is salaried with no penalty exposure, the tool has little to find and isn't worth the build.
What it doesn't do — and shouldn't
It does not post anything to payroll, queue a back-payment, or clear a run. It surfaces a suspected shortfall, shows the paid rate beside the award minimum and the clause behind the flag, drafts a correction memo, and stops. A payroll officer approves, edits or rejects — and that boundary is deliberate. Whether to back-pay, how to handle a contested classification, whether an annualised arrangement validly absorbs a penalty, and how to interpret an EBA against the award floor are all human decisions with legal weight.
That line matters more here than in most verticals. Intentional underpayment is now a criminal offence under the Fair Work Act, and the difference between a defensible position and a prosecutable one turns on intent and good faith. A tool that decided and acted on its own would undermine exactly the human judgement that makes a compliance effort genuine. It accelerates the checking; the person stays on the decision.
What your data has to look like for this to work
Concretely: each employee needs a correct award classification (the level and employment type — e.g. Retail Employee Level 2, casual) tied to the right instrument, the modern award or EBA, encoded as versioned rules for the pay period being checked. Each earnings line needs to carry enough to reconcile — the shift type or date so a Saturday can be told from a Sunday, the hours, and the paid rate — rather than a single rolled-up figure. Allowances that aren't hours-based, like a per-shift clothing allowance, need to be visible as their own line, not buried in gross.
Most organisations have only some of this in good shape. Classifications drift as people change roles and never get re-coded; shift labels are inconsistent between rosters and payslips; the casual loading is baked into a rate with no breakdown. Getting that data into a state where every line can be matched to a rule is usually the real first job — and it's typically about how the information is captured at the roster and payslip level, not about buying a new tool. That capture work is what RMAI helps with, and it is usually bigger and more valuable than the checking layer on top of it.
Could this tell me to underpay someone, or wave through a payslip that's actually wrong?
It never posts anything itself. It flags a suspected shortfall, shows the paid rate beside the award minimum it's checking against, and cites the clause behind the flag — then a payroll officer approves, edits or rejects. A "compliant" result means every line it checked met or exceeded the minimum it had encoded; it is only as right as the award rules and classifications loaded into it, which is exactly why a person signs off rather than the tool clearing the run.
Our payslips are a mess — scanned PDFs, inconsistent shift labels, casuals with loading baked into the rate. Will it cope?
It reads scanned payslips as well as clean STP feeds, but messy input is where it earns its review step rather than its automation. If a shift is labelled "weekend" without saying Saturday or Sunday, or the 25% casual loading is folded into one figure with no breakdown, it will flag the line for a human to interpret instead of guessing. The honest test – if your own payroll officer couldn't tell from the payslip whether a Sunday penalty was paid, neither can this.
Does this replace our payroll officer or our compliance advice?
No. It does the line-by-line arithmetic a payroll officer would do by hand if they had time to check every run — surfacing the shortfall and the clause — so their judgement goes to the cases that actually need it. It is not legal advice; classification disputes, EBA interpretation and the decision to back-pay all stay with the human. The capacity it recaptures is redirected to those harder calls, not removed.
How current does the award data have to be? Rates change every July.
Current enough that the encoded rules match the period being paid. Minimum rates change from 1 July each year, the super guarantee reached 12% on 1 July 2025, and penalty structures change by determination — so the award rule set has to be versioned to the pay period or it will confidently check against last year's numbers. Keeping that rule set current is part of what the build maintains; it is not a set-and-forget tool.
Where does our payroll data go? This is sensitive employee information.
The reconciliation runs against your payroll data within the controls you set; nothing is posted to payroll, sent to anyone, or actioned without an approver. We scope data handling, retention and access with you up front, and the human-approval step means no employee's pay changes without a named person signing off. Payroll and super data carries privacy obligations, so where it sits and who can see it is part of the engagement, not an afterthought.
We're worried about the new wage-theft laws. Does this make us compliant?
It doesn't make you compliant — it gives you a defensible trail. Intentional underpayment became a criminal offence under the Fair Work Act from 1 January 2025, and the law turns on intent, not honest mistakes. Catching and correcting shortfalls before the run leaves, with the clause cited and a human sign-off recorded, is evidence of a genuine compliance effort rather than wilful blindness — but it supports your obligations, it doesn't discharge them.
Estimated build: 3–4 weeks. Most of it is template work we've already done.
Fixed scope, fixed price, fixed dates.
The cost band reflects the engagement shape, not a per-feature line item. We work on fixed scope, fixed price, fixed dates — see the services catalogue for what falls inside each band.
Considering this for your org?
The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where it hurts; we’ll play it back, scope it, and show you what’s possible.