Multi-state Australian payroll
A national employer paying people in several Australian jurisdictions — where the hard part is not the pay run, it is that payroll tax, long service leave and workers compensation multiply at every border.
A composite worked example, not a client. It is assembled from patterns that recur in national Australian employers with sites in more than one state or territory, and from this library's model. No organisation is described, and every derived section is computed from the same model the rest of the site runs on. No rates, thresholds or scheme premiums are stated — those change, and the programme has to name the current source rather than freeze a figure.
Where it stands
People are employed in more than one state, paid from one payroll system, and reported as if the obligation were national. The pay run works; the lodgements around it are assembled afterwards.
Payroll tax is treated as a single national calculation and then split. Grouping, taxable wage definitions and lodgement calendars differ by jurisdiction, and the spreadsheet that bridges them is held by one person.
Long service leave accrues under the rule of the state where each employee works, but balances were migrated as numbers rather than as service. Nobody can reconstruct a contested payout from the record alone.
Workers compensation is declared annually against an industry classification set at registration and rarely revisited. The wage base used for the declaration matches neither payroll tax nor superannuation.
Single Touch Payroll and superannuation submit on time. They are the national obligations that work, which is why the state obligations are the ones that get deferred.
Why now
- —Growth into additional states has turned one payroll tax and one long service scheme into several, without the design catching up.
- —A grouping or nexus question from a revenue office would today be answered from a spreadsheet, not from the system.
- —Long service leave liability is an estimate that cannot be recalculated from service history, and the first contested payout will expose that.
- —Award and enterprise agreement interpretation differs by site and by instrument, and the gaps are discovered in the pay run rather than in design.
- —None of those is an end-of-support clock on its own. Together they are the reason a replacement or re-platform has to treat jurisdictions as first-class design, not as reporting afterthoughts.
What that scope actually implies
9 areas picked, 19 topics in scope across 5 modules
The streams these picks sit on cross into Financial Accounting, Integration, PMO & Programme Governance. Nobody picked those, and the work still happens there.
The end-to-end it sits on
Time-to-Pay
Human Capital Management → Financial Accounting
Benefits & Compliance
Human Capital Management
Migrate-to-Steady-State
Data & Analytics → Integration
Plan-to-Cutover (Go-Live)
PMO & Programme Governance → Data & Analytics → Integration
Deliberately out of scope
Exclusions cause scope fights when they are assumed rather than written. Each one here has the reason attached.
Core HR and the establishment
Out of scope for this release, in scope as a master. Payroll still needs a reliable employee, assignment and location record; if HR is not changing, the interface and the ownership of work-state are named rather than assumed.
Recruitment, learning and performance
Deliberately later. They do not change the jurisdictional obligations this programme exists to get right, and adding them now doubles the change load on the same payroll team.
Finance beyond the payroll journal
Out of scope, in scope as an interface. The period journal, the net pay file and the superannuation payment all land in finance, so not changing the ledger still means testing the postings — especially costed by state and site.
Roster optimisation and workforce planning
Stay with operations. This programme needs approved time and interpreted allowances out of those tools, not to replace how sites are staffed.
The boundary
Every system the finance core exchanges data with, and what happens to that interface. An interface with no disposition is an interface somebody will discover during testing.
Employee master and work location
Rebuild
Starters, movers, leavers, employing entity and primary work state←HR / employee master
Without a trusted work-state on the assignment, every jurisdictional calculation is a guess. Mover is the case that usually breaks it — people change site without the payroll attribute following.
Approved time and allowances
Rebuild
Approved hours, penalties earned, site allowances, public-holiday flags←Time, rostering or works systems
Public holidays and site allowances differ by state. If time arrives without jurisdiction context, interpretation re-creates it by hand.
Payroll journal
Rebuild
Period journal costed to cost centre, site, project and jurisdiction where needed→Finance / general ledger
Finance will ask for labour cost by state the first time a payroll-tax or workers-compensation reconciliation fails. Design the grain now rather than add it after go-live.
Net pay and deductions
Rebuild
ABA direct entry file→Banking platform
The bank's testing window sits on the critical path and is outside the programme's control. Book it before the plan is baselined.
Superannuation contributions
Rebuild
Contribution data and payments→SuperStream gateway and funds
National obligation, but still on the critical path. Late or failed contributions attract the superannuation guarantee charge, which is not tax deductible.
Single Touch Payroll
Rebuild
Pay event, on or before each pay day→ATO
Phase 2 disaggregates gross into components, so wage-type design and reporting design are the same decision — and that decision has to survive multi-state allowance structures.
Payroll tax lodgement
Rebuild
Taxable wages, deductions and grouping position per jurisdiction→State and territory revenue offices
Today assembled in a spreadsheet. The replacement either produces each jurisdiction's return from the wage-type mapping or inherits the spreadsheet deliberately.
Workers compensation declarations
Rebuild
Declarable wages by jurisdiction and classification→Scheme insurer in each jurisdiction
Own wage definition, per state. Classification drift since registration is a common silent error — review it as part of design, not as part of the annual return.
Portable long service scheme returns
Not decided
Service returns and levies→State portable schemes, where industry coverage applies
Whether any site or occupation is covered has to be closed before entitlement rules are configured. The obligation can exist whether or not leave has been claimed.
Flows the model says straddle this boundary
Derived from the scope, not written here: hand-offs where one side is being changed and the other is not. Compare them against the boundary list above — anything present here and missing there is a gap.
Payroll journal←Payroll
General Ledger · per pay run · without it: Labour cost is missing from the period and the month cannot close.
Employee and position master←Core HR
Payroll · continuous · without it: Starters are unpaid and leavers keep being paid.
Payroll journal→General Ledger
Payroll · per pay run · without it: Labour cost is missing from the period.
Net pay file→ABA
Payroll · per pay run · without it: Staff are not paid.
Opening balances and master data→General Ledger
Data Migration · at cutover · without it: The new ledger opens on numbers nobody can reconcile to the old one.
What this context does to a generic finance build
Jurisdiction is an attribute on the person, not a report filter
Payroll tax, long service leave and workers compensation are assessed where the employee works (and sometimes where the employer is grouped). Work location, employing entity and cost centre are different facts. If the system only knows cost centre, every state obligation is reconstructed outside it.
Payroll tax is one obligation per jurisdiction
Thresholds, rates, grouping rules and lodgement calendars are set by each state and territory. The taxable wage base rarely matches gross pay. Mapping reportable classifications onto the wage type — and deciding the grouping position in writing — belongs in design, not in the lodgement spreadsheet.
Long service leave follows the workplace, and sometimes the worker
Accrual, qualifying periods and pro-rata rules differ by jurisdiction. In some industries a portable scheme means the entitlement follows the worker rather than the employer. Migrating balances without service history makes every one of those rules unenforceable.
Workers compensation has its own wage definition
Each scheme declares on a wage base that matches neither payroll tax nor the superannuation guarantee, rated on an industry classification that is usually set once and never revisited. Build the mapping on the wage type; do not reconstruct it annually.
Federal obligations do not vary at the border
Single Touch Payroll, the superannuation guarantee and the Fair Work modern award system are national. They are not the part that changes when a site opens in another state — which is exactly why the state obligations above are the ones a national payroll design has to make explicit.
Awards and agreements are site-local even when the employer is national
A multi-site employer often carries more than one modern award and more than one enterprise agreement. Penalty, allowance and overtime interactions have to be interpreted per instrument and per roster pattern, including public holidays that fall on different dates in different states.
Do not freeze rates in the design
Thresholds, rates, portable-scheme levies and premium bases move. The design names the current published source and the owner who updates the figure; it does not treat a number copied into a workbook as the specification.
The order to do it in
The grouping is computed from the model's dependency edges. The goal and the exit condition for each release are a delivery judgement.
Jurisdiction foundation
Data Migration · Benefits · Time & Attendance
Work location and employing entity trusted on every assignment, wage types mapped to payroll tax, workers compensation and STP components, and the grouping position written down.
Done when A payroll-tax extract per jurisdiction produced from the system that reconciles to the current lodgement method, with differences explained rather than forced.
Time, awards and entitlements
Payroll
Time and award interpretation live across sites, including state public holidays and site allowances, and long service leave accruing under the rule for where each employee works — recalculated from service history, not carried as a balance.
Done when A full cycle of multi-state time flowing without re-keying of jurisdiction, and long service leave verifiable for the longest-serving cohort in each state employed.
Pay and statutory lodging
Cutover & Go-Live
Payroll live with STP, superannuation, payroll tax and workers compensation produced from the run, after parallel runs that agree across jurisdictions.
Done when Consecutive parallel runs agreeing on gross, net, tax, super and allowances, and each jurisdictional return reconciling without a side spreadsheet as the system of record.
The model also flags Programme Governance, Core HR as depended on but not included. Fine if they are staying as they are — a gap otherwise.
Decisions to settle
In which jurisdictions do we employ, and under which employing entities?
It sets how many payroll-tax, long-service and workers-compensation regimes apply, and whether grouping is available or already locked in by structure.
By: Before wage-type and entitlement design starts. · Payroll Tax
What is the grouping position for payroll tax?
Related entities, thresholds and who lodges where. Left informal, it is rediscovered under enquiry; written early, it constrains entity and costing design usefully.
By: With scope, with tax advice named as an input rather than assumed. · Payroll Tax
Is work state mastered in HR or derived in payroll?
Every jurisdictional calculation hangs off it. Dual maintenance diverges within a quarter; a single owner with a tested mover process does not.
By: Before the HR interface is specified. · Payroll
Which awards and agreements apply at which sites?
Interpretation effort scales with instruments, not with headcount. Discovering a second agreement during parallel running extends the tail by months.
By: Before award configuration, with industrial relations in the room. · Award Interpretation
Are any occupations covered by a portable long service scheme?
Portable schemes add levies and service reporting whether or not leave is taken. Deciding after go-live means catching up underpaid levies and rebuilding history.
By: Before leave rules are configured. · Long Service Leave
How many parallel runs, and what makes one pass across states?
A run that agrees nationally but fails a state allowance or public-holiday case is not a pass. Criteria have to include jurisdictional samples, not only company totals.
By: At mobilisation, because it sets the length of the plan's tail. · Payroll
Who runs the pays — and the lodgements — while the programme is running?
The people who know the state returns are the people who lodge them. Without funded backfill, both the programme and the lodgement calendar degrade together.
By: Before mobilisation, with the budget. · Digital Transformation Readiness Checklist
Risks worth writing down
Jurisdiction is treated as a reporting dimension added at the end.
So: Wage types, time interfaces and the employee master ship without work-state integrity, and every state return stays a spreadsheet.
Instead: Make work location and wage-type jurisdictional mapping a foundation-release gate, proven against a current lodgement before entitlements are configured.
Service history is migrated as long service balances.
So: Entitlements cannot be recalculated under the correct state rule, and the first contested payout cannot be defended from the system.
Instead: Migrate continuous service, verify the longest-serving cohort per jurisdiction before trial load, and reconcile recalculated entitlement to the ledger provision.
Public holidays and site allowances are modelled from one state's calendar.
So: The first conflicting holiday or remote-site allowance produces mass corrections in a live pay run.
Instead: Build interpretation tests from real multi-state rosters, including overlapping holiday periods, before signing off the rule set.
Workers compensation classifications are copied forward unexamined.
So: Premium and declaration error accumulates quietly until a scheme audit, then becomes a prior-period correction across every state employed.
Instead: Review classification per jurisdiction as a design input, and map declarable wages on the wage type rather than in the annual return.
Parallel running passes on national totals only.
So: Go-live with unexplained state-level variances that become live defects affecting real people at real sites.
Instead: Set pass criteria that include jurisdictional samples and allowance cohorts, require consecutive passes, and keep no-go as a genuine gate option.
Rates and thresholds are pasted into design documents.
So: The specification is stale before configuration finishes, and somebody treats the outdated figure as authoritative.
Instead: Reference the published source and name the owner who updates it; configuration holds the figure, documents hold the pointer.
Readiness
Employment footprint by jurisdiction confirmed
gap
Headcount and employing entity per state and territory, agreed by HR and payroll rather than inferred from cost centres.
Payroll tax grouping advice current
unknown
Written position on grouping, nexus and who lodges where — or an explicit decision to obtain it before design.
Industrial instruments collected per site
gap
Awards, enterprise agreements and side letters that actually apply, not the ones people remember applying.
Service history verifiable per jurisdiction
gap
Continuous service dates for the longest-serving employees in each state employed, evidenced rather than carried forward.
Workers compensation classifications reviewed
gap
Current scheme, classification and wage definition in each jurisdiction, checked rather than assumed from registration.
Portable scheme coverage decided
unknown
Which occupations or sites fall under a portable long service scheme, closed before leave configuration.
Payroll capacity released and backfilled
gap
Named people for the pay run and for each jurisdictional lodgement, with funded backfill — or the programme is resourced on goodwill.
The artefacts this programme has to produce
Each one has a guide behind it. The library is the general case; this list is the order it is needed in.
Jurisdiction and employing-entity matrix, with work-state ownershipPayroll and HR
Wage-type catalogue mapped to STP, payroll tax and workers compensationPayroll
Payroll tax grouping position and lodgement design per jurisdictionPayroll and finance
Award and agreement interpretation rule set per instrument and sitePayroll and HR
Multi-state time and public-holiday interface specificationPayroll and operations
Long service leave rules per jurisdiction, including portable schemesPayroll
Workers compensation declaration basis and classification reviewPayroll and risk
Superannuation and Single Touch Payroll reporting setupPayroll
Service history migration and reconciliation planPayroll and data
ABA payment file specification and bank testing planPayroll and treasury
Parallel run plan with jurisdictional pass criteriaPayroll
Payroll journal grain design, including state and site where requiredPayroll and finance
Change impact assessment by site and by roleChange
Argue with it
The scope, the phase order and the straddling interfaces are all computed from the model. If a phase looks wrong, the dependency edge behind it is the thing to change — say so here.