Same job same pay compliance means that, under a regulated labour hire arrangement order, a labour hire provider must pay placed workers at least the host's protected rate of pay: the full rate the host's own employees receive for the same work. Getting it right is a calculation built on two organisations' data, which disciplined automation can make accurate, current and provable.
Key takeaways
- Regulated labour hire arrangement (RLHA) orders come from the Fair Work Legislation Amendment (Closing Loopholes) Act 2023 and could commence operation from 1 November 2024.
- The protected rate of pay is the full rate under the host's instrument, including bonuses, loadings, allowances, overtime and penalty rates.
- Classification errors are the largest source of mistakes and flow into every downstream calculation.
- Being able to show how each protected rate was derived matters as much as the number, because liability can extend to hosts.
- Model the host agreements and classifications first, then build the calculation and evidence trail on top.
How does same job same pay change labour hire pricing?
For a labour hire provider, pricing a placement used to be self-contained. You knew your cost to employ a worker, added a margin, and quoted the host. The rate lived inside your own systems and agreements.
Under an RLHA order, the rate you must pay a placed worker comes from the host employer's workplace instrument, and you have to match it. A provider can no longer answer "what do we pay this worker?" from its own records. It has to know what the host's directly employed staff earn for the same work, reconstruct that full rate with all its components, and apply it.
Get the reconstruction wrong and the exposure is real: underpayment claims, back pay, and liability that can reach both provider and host.
This guide is for payroll managers, compliance leads and operations directors at labour hire and staffing providers, and for workforce and HR leads at host employers with significant labour hire use.
What does a regulated labour hire arrangement order require?
The RLHA provisions were introduced by the Fair Work Legislation Amendment (Closing Loopholes) Act 2023, which amended the Fair Work Act 2009. Employees, their unions or a host employer can apply to the Fair Work Commission for an order. Where an order is made, labour hire workers supplied to that host must be paid no less than the protected rate of pay: the full rate the host's own employees would receive for the same work under the applicable instrument. Orders could commence operation from 1 November 2024.
"Full rate of pay" is where the difficulty lives. It covers bonuses, loadings, allowances, overtime and penalty rates as they apply under the host's instrument. Reconstructing it means understanding the host's enterprise agreement well enough to apply the right components to the right hours, and keeping that current as the agreement changes.
The Commission does not make orders automatically. It considers whether an order is fair and reasonable, including the pay arrangements of the host's employees and the industrial history of both host and provider. The legislation also contains exceptions, such as for host employers with fewer than 15 employees and for short placements (three months by default, which the Commission can vary). Once an order applies, the obligation is concrete.
| Standard Arrangement | Under an RLHA Order | Impact | |
|---|---|---|---|
| Source of the pay rate | Provider's own agreement | Host's workplace instrument | External |
| What is included | Agreed base rate plus loadings | Full rate: base, bonuses, allowances, overtime, penalties | Reconstructed |
| Who can be liable | Provider | Provider and, in some cases, the host | Shared |
| Data required | Internal payroll | Host agreement plus placement detail | Two organisations |
Why is the protected rate of pay a data problem?
Once an order is in place, the legal question is settled: the worker must receive the protected rate. What remains is operational, and hard, because the calculation draws on data from two organisations that were never designed to line up.
On the host side, the enterprise agreement defines base rates, classifications, and the allowances, loadings and penalties attached to particular hours and conditions. On the provider side sit the placements: who is working, in what classification, on which shifts, with what overtime and penalty exposure. Paying correctly means mapping every placement onto the host's agreement structure and applying the right components to the right hours, for every affected worker, every pay cycle. Done by hand against a dense agreement, errors are close to inevitable.
- InterpretExtract rate components from the host agreement
- MapMatch each placement to the right classification
- CalculateApply base, allowances, penalties to actual hours
- EvidenceRecord how each protected rate was derived
The last step deserves emphasis. A protected rate you cannot reproduce or explain is a weak position even when it is correct. The compliance value lies in paying the right amount and showing, worker by worker and pay run by pay run, how you got there.
The same discipline applies across Australian payroll compliance, including wage compliance now that underpayment can be a criminal offence and the wider shift to automating Fair Work compliance. The organisations that cope are the ones whose pay calculations are systematic, current and evidenced.
Where does AI help with same job same pay compliance?
The value sits in structured work: interpreting a dense agreement, mapping placements, calculating the full rate and keeping an audit trail. For example, picture a provider with workers placed across several hosts, one of which is now covered by an order.
Extracting rate components from the host agreement. Classifications, base rates, allowances, loadings and penalty conditions are scattered through long agreements. Document interpretation can pull that structure into a usable rate model, and a payroll specialist reviews and confirms it before it is used, instead of rereading the whole instrument every time it changes.
Mapping placements to classifications. A worker in the wrong classification is the single largest source of error. Automation can propose a classification for each placement based on the work performed and flag anything it cannot map confidently for a person to decide, so guesses never reach the pay run.
Calculating the full rate against actual hours. With the host's rate model and actual hours, including overtime and penalty conditions, a calculation engine applies the correct components and produces the protected rate for each worker each cycle. Accurate hours are the foundation, which is why this links closely to automating timesheets and time tracking.
Maintaining the evidence. Every protected rate should carry its derivation: agreement version, classification, and which components applied to which hours. That record turns a claim of compliance into something you can show.
A payroll officer approves each pay run before it is processed. The automation does the first pass and highlights exceptions; it does not pay anyone on its own.
What is hardest to get right today?
- Interpreting the host's enterprise agreementAgreement extraction and rate modelling
- Placing workers in the correct classificationClassification mapping with exception flags
- Applying penalties and allowances to hoursFull-rate calculation engine
- Proving how a rate was calculatedDerivation and audit trail
What does getting the protected rate wrong cost?
Underpayment against a protected rate can create back-pay obligations across every affected worker and pay cycle, and hosts with significant labour hire use can carry exposure too. A systematic calculation and evidence capability delivers value every pay cycle, unlike a one-off remediation.
- Classification errors caught before they reach payrollFewer claims
- Full rate computed rather than estimated by handAccuracy
- Every protected rate carries its derivationDefensible
- Host agreement changes flow through automaticallyAlways current
These items are qualitative on purpose. Dollar exposure depends on workforce size, hosts and agreements, and inventing a figure would be dishonest. The logic holds regardless: avoid calculation errors becoming claims, and be able to prove compliance.
There is a commercial benefit too. Hosts share the liability and increasingly want assurance that their labour hire providers have protected rates under control. A provider that can demonstrate an evidenced approach is in a stronger position to win and keep that work.
How do you implement a protected rate capability?
You do not need to replace your payroll system. Get the source data trustworthy first, then add calculation and evidence on top.
- Weeks 1-2Model the agreementsExtract rate components from each covered host's instrument
- Weeks 3-5Map placementsMatch workers to classifications with exceptions flagged
- Weeks 6-8Calculation engineCompute the full rate against actual hours per cycle
- Weeks 9-12Evidence and monitoringDerivation trail and change monitoring on agreements
The order matters. A calculation engine built on a shaky agreement interpretation or misclassified placements produces confident, wrong rates, which is worse than an honest manual estimate because it looks authoritative. The new engine should run alongside your existing payroll process until its results match, before anyone relies on it.
Our team has built this kind of logic before: a workforce management app used by a company of 1,500+ staff, taken from MVP to live use and still running, covered in our workforce app case study. Rostering, hours and pay calculation are the same foundations a protected rate capability depends on.
This obligation does not sit alone. From 1 July 2026, superannuation must be paid with each pay cycle under the payday super changes, leaving less room to correct errors later. Look at a protected rate project alongside payroll automation for payday super, because both pull on the same systems. Payroll connections like these are core process automation and system integration work.
What mistakes undermine same job same pay projects?
- Treating agreement interpretation as a one-off. Enterprise agreements change. A rate model built once and never updated drifts out of compliance, so it has to be maintained and monitored.
- Rushing classification. A wrong classification poisons everything downstream. The mapping deserves care and proper exception handling.
- Neglecting the evidence trail. A correct rate you cannot explain is weak when a claim arrives or a host asks for assurance. Build the derivation record in from day one.
- Buying a generic payroll add-on first. The hard part is interpretation and mapping specific to your hosts. A tool that assumes clean, standard inputs rarely survives a real enterprise agreement.
How Solve8 can help
Our consultants and engineers model host agreements, map placements and build protected rate calculations with a full derivation trail, connected to the payroll and rostering systems you already run. The work runs on your infrastructure in Australia and alongside your team until it proves accurate. See our process automation services or talk to us.
