The award is applied approximately.
Payroll configuration encodes someone's interpretation from years ago. Classifications drift, rates age, edge cases fall through — and the system keeps paying confidently.
Smartta runs shadow wage validation against encoded award rules before payroll export — catching underpayments, misapplied rates, and edge cases while they cost minutes to fix, and recording proof of every check.
122+ Modern Awards encoded · checked every cycle, every worker · evidence behind every check.
Payroll governance view
Policy validation
Replaying the period against encoded award rules
Roster-to-time variance
12 flagged — routed with the fix attached
Unmapped pay input
3 high risk — held before export
Evidence readiness
Rule version, inputs, and result per check
Payroll export
Held until high-risk lines are reviewed and evidenced.
Errors don't announce themselves — they compound. Every cycle multiplies the exposure.
The problem
The pay run executes whatever it's given: the classification set three years ago, the rate table nobody re-checked, the award clause the configuration approximates.
Payroll configuration encodes someone's interpretation from years ago. Classifications drift, rates age, edge cases fall through — and the system keeps paying confidently.
Every cycle multiplies the exposure. With intentional underpayment now a criminal offence, "we didn't know" depends on proving you checked — every worker, every cycle.
A dispute, an audit, or a Fair Work query means rebuilding the calculation by hand — rates, hours, penalties, rules — per employee, per period.
Shadow validation
Before the run, Smartta replays the pay period through its own encoded, expert-validated award rules and compares the result to what payroll is about to pay.
Expected 2.5×, paying 1.0×, $127.50 impact — with the award reference cited.
Clean lines pass silently; discrepancies route for review with the fix; high-risk lines hold.
122+ Modern Awards encoded as executable, versioned rules — span limits, breaks, penalties, overtime thresholds.
Which rule version, which inputs, what result — the "we checked" record a good-faith position depends on.
Most pay lines pass silently. Your team only sees the discrepancies that need them.
The plan
Identify where decisions move between roster, time, HR, payroll, credentialing, and care systems.
Here: where classifications, rates, and rule interpretations drift into the pay run.
Configure checks that pass, flag, or gate high-risk workforce decisions before they move downstream.
Here: every pay line shadow-validated against encoded award rules before export.
Keep decision evidence ready for payroll review, compliance checks, incident response, and operational governance.
Here: rule version, inputs, and result per worker, per period — the good-faith record.
Evidence
A dispute, an audit, or a Fair Work query shouldn't mean rebuilding the calculation by hand — per employee, per period.
Clause-level findings — MA000010 Manufacturing Award
4 issues · 3 clean entriesScanned 6 entries in 221ms · every finding carries its clause citation.
What's at stake
The difference between those two outcomes is whether anything checked the pay line before it was paid — and whether you can prove it.
Discrepancies arrive before export with the clause and the fix attached — not in next month's reconciliation.
A standing answer to "are we paying people correctly?" — checked every cycle, not asserted.
The full check history per worker, per period — the good-faith record, already assembled.
Payroll workflows
A short review of how upstream workforce systems feed your pay run — and where shadow validation would surface pay risk before it reaches export.