Award Rate Checker | Real Minds AI
HR & Payroll /Decisioning live field guide · 9 min

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.

theater/demos/hr-payroll_award-rate-checker.html · sandbox · read-only
Open
FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads each payslip line, compares the paid rate to the modern-award minimum for that classification and shift, and surfaces every shortfall with its clause cited for a payroll officer to approve before any back-pay is posted.

Input 01
The pay run + the award

The period's pay records — clean STP earnings feeds and/or scanned payslip PDFs — plus each employee's award classification and the applicable modern award or enterprise agreement.

Agent 02
Matches, prices, flags

Extracts each earnings line, matches it to the right penalty, loading or allowance, looks up the award minimum versioned to the pay period, and computes the per-line shortfall.

Output 03
A reconciliation, with its working shown

A per-employee reconciliation showing paid rate beside award minimum, the dollar shortfall, and the clause behind each flag — for a payroll officer to review, edit or reject before any back-pay is queued. Nothing posts on the tool's say-so.

Where it works well

It does the line-by-line award cross-check every run, in full, and shows its working.

  • Done by hand it is the first thing skipped under deadline; one missed weekend penalty across a fortnightly run of casuals compounds silently until an audit finds it years later.
  • Best for a 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.
  • As the last gate before the run leaves, the recaptured hours go back into the cases that need judgement, not into re-checking every line.

The slow, invisible problem is the penalty that quietly never gets applied — a casual rostered across a Saturday, a Sunday and a public holiday should draw three different multipliers, and the failure mode is mundane: the shift gets paid at the ordinary rate because nobody re-checked.

Where it works badly

It is confidently wrong when the classification is wrong or the rules are stale — and a clean "compliant" hides it.

  • Weak where the payslip doesn't say enough — a line labelled "weekend hours" with no Saturday/Sunday split, or a casual rate with the loading folded in and no breakdown. It should flag for a person, not guess.
  • An annualised salary meant to absorb penalties under a set-off clause is an interpretation call, not arithmetic — it flags, it doesn't rule.
  • If most of your pay is salaried with no penalty exposure, the tool has little to find and isn't worth the build.
The honest test

If your own payroll officer couldn't tell from the payslip alone whether a Sunday penalty was actually paid, neither can this — and a wrong classification just makes the wrong answer faster, not safer.

Code an employee to the wrong award level and the tool faithfully checks against the wrong minimum, clearing a payslip that is actually underpaid. Encode last July's rates and it flags correct pay as short. The arithmetic is reliable; the inputs are where it fails.

What it doesn't do — and shouldn't

It drafts the correction. A payroll officer approves. That boundary is deliberate.

WHAT IT DOES
Surfaces the paid rate beside the award minimum it checked against
Cites the award and clause behind each flagged shortfall
Drafts a plain-language correction memo with the recommended back-pay
WHAT IT WON’T
Post anything to payroll or queue a back-payment
Decide a contested classification or interpret an enterprise agreement
Certify the pay run as award-compliant

Intentional underpayment is now a criminal offence under the Fair Work Act, enforced by the Fair Work Ombudsman, and the law turns on intent and good faith, not honest mistakes. A tool that decided and acted on its own would undermine exactly the human judgement that makes a compliance effort genuine. The accountable person stays on the decision because the consequence lands on them — not the tool.

What your data has to look like

Correct classifications tied to the right instrument, and earnings lines detailed enough to reconcile.

44%
Typical readiness
across orgs we see, before the first job
Correct award classification per employee
Needs shaping
Award rules versioned to the pay period
Usual weak point
Earnings lines that distinguish the shift
Usual weak point
Non-hours allowances as their own line
Needs shaping
The super contribution rate per employee
Usually ready
The real first job

Most organisations have only some of this in good shape — classifications drift, shift labels are inconsistent between rosters and payslips, and 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 about how the information is captured at the roster and payslip level, not about buying a new tool. That capture work is usually bigger and more valuable than the checking layer on top of it.

Right fit if…
You run award-covered, penalty-heavy rosters — retail, hospitality, aged care
The same casuals cross several penalty bands in one pay period
Volume is too high to hand-check every earnings line every run
Your classifications and shift labels are accurate, or you're ready to fix them
Walk away if…
Most of your pay is salaried with no penalty exposure
Employee classifications are out of date and nobody owns re-coding them
Payslips roll shift types into a single figure with no breakdown
You need a tool that certifies the run compliant for you
Open questions

The worried-buyer questions, answered straight

It never posts anything itself. It flags a suspected shortfall, shows the paid rate beside the award minimum it checked against, and cites the clause behind the flag — then a payroll officer approves, edits or rejects. A “compliant” result only 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.
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 casual loading is folded into one figure with no breakdown, it flags 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.
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, enterprise-agreement interpretation and the decision to back-pay all stay with the human. The capacity it recaptures is redirected to those harder calls, not removed.
Current enough that the encoded rules match the period being paid. Minimum rates change from 1 July each year, the Super Guarantee reached 12% of ordinary time earnings 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.
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. Payroll and super data carries obligations under the Privacy Act, so 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. The demo here runs entirely on fabricated data; Tahlia Nguyen is not a real employee.
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.
What it takes to build
3–4 weeks · 4 phases
Reused from template~65%
Bespoke to this skin~35%
stack · Claude · structured award rules · review UI
What it would cost

Fixed scope, fixed price, fixed dates.

01
Bite-sized first piece
One contained change, low risk
02
Pilot build
Most builds land here
03
Embedded support
Scale on proof

Considering this for your payroll?

The honest place to start is a bite-sized first piece — one award, one pay run, low risk. Tell us where it hurts; we'll play it back, scope it, and show you what's possible.

More in HR & Payroll
PALM Piece-Rate Validator
View →
STP Phase 2 Category Auditor
View →
Tier-1 HR Query Assistant
View →
Timesheet-to-Payroll Reconciler
View →
How We Work Proof Talk to us
How We Work Proof Talk to us
Ask us anything