Employment Hero Payroll Implementation: The Ideal Process

All blogs & guides

Checked against Employment Hero’s Help Centre and current Australian guidance on 13/08/2026.

The short version

1. Award interpretation, pay-category mapping and opening balances must be resolved before the first parallel run.
2. A mid-year migration can require year-to-date data and STP finalisation across two payroll systems.
3. One or two reconciled parallel runs are the last safe place to find configuration errors before employees are paid.

Full detail below.

Three controls deserve particular attention in an Employment Hero payroll implementation for Australian SMEs: award interpretation, qualifying-earnings mapping under Payday Super and reconciled opening balances.

Some errors appear only when a particular employee, shift or payment type reaches a live pay run. The six-stage process below is the control Payd Co, an Australian Employment Hero Certified Partner based in Perth, uses for businesses running modern awards.

Employment Hero Payroll Implementation in Six Stages

Each stage depends on the one before it. Skip ahead and the gap shows up later as underpayments, super errors or a rejected STP lodgement.

Stage	What Happens	Where It Commonly Breaks
1. Discovery	Confirm awards, classifications, pay cycle and allowances	Award interpretation treated as a dropdown choice
2. Configuration	Build pay categories, award rule sets, leave and super	Qualifying earnings mapped incorrectly on a pay category
3. Data migration	Bring employee records and opening balances across	Opening leave balances carried over unchecked
4. Parallel pay runs	Run old and new systems side by side, reconcile to the cent	Skipped to save a fortnight, costs far more later
5. Training and go-live	Hand the system to admins, managers and staff	Configured correctly but never adopted
6. Post-go-live review	Confirm STP, super and adoption are holding	Manual workarounds creeping back in after week one

Stage 1: Discovery, Before You Touch the System

Discovery is the most skipped stage, and the one that causes the most damage when rushed. Good discovery confirms which Modern Award or awards apply, to whom, and maps every employee classification to actual duties, not job titles. It documents the pay cycle, every allowance, loading and penalty, and the integrations the build needs, such as Xero, MYOB or a rostering tool.

If you cannot write the requirement down, you are not ready to configure it. Award interpretation is rarely as simple as picking an award from a dropdown, and getting it wrong here is the root cause of most penalty rate errors we see later.

Stage 2: Configuration, Building the Payroll Engine

Configuration turns the discovery document into a working system, in order: business settings and STP first, then pay categories, then the award rule sets that convert hours worked into correct pay, then leave, then super. The pay-category step is where the qualifying-earnings trap sits.

For wages paid from 1 July 2026, Payday Super uses qualifying earnings. That base includes OTE plus some payments that need separate attention, including all commissions and eligible contractor payments. Pay-category mapping therefore has to be tested against QE, not copied from a pre-July OTE checklist. If your super amount looks wrong, start with that mapping and the employee’s overrides.

Stage 3: Data Migration, Bringing People and Balances Across

Migration covers employee records, balances and STP identity. Names, tax file numbers, bank details and super fund details all need validation, while opening balances require a separate reconciliation against the former system.

Employment Hero documents four mid-year STP transition options. They cover importing YTD data where STP was not previously reported; importing YTD data while retaining the former BMS and payroll IDs; importing YTD data under a new BMS after clearing the old record; and starting under a new BMS without importing prior YTD earnings. A financial-year-boundary move has a separate, simpler path. The right option depends on timing, prior reporting, whether YTD earnings will migrate and whether the former BMS and employee payroll IDs will be retained.

The BMS ID is not an admin detail. Employment Hero warns that an incorrect BMS ID or STP Payroll ID during a mid-year transfer can create duplicate records or overstated earnings in an employee’s ATO income statement. We document the chosen transition option and reconcile the imported payroll IDs and YTD data against the former system. Where the original payroll ID is unavailable, the employee can retrieve it from their own myGov income statement. We then lodge the update, finalisation or first pay event required by the selected option.

A mid-financial-year move can also leave STP finalisation responsibilities across two systems. Moving at the financial-year boundary is cleaner because prior earnings can remain finalised in the old system while Employment Hero begins the new year with leave balances and a new BMS ID.

Stage 4: Parallel Pay Runs, Proving It Before You Trust It

Run the same pay period through both old and new systems for at least one full cycle, ideally two. Compare gross pay, tax, super, allowances and net pay employee by employee. Investigate every variance and sign off only when each difference has an explanation and resolution.

A parallel run is the cheapest insurance in the process. A discrepancy found here is a configuration note. The same discrepancy found after go-live is an underpayment, a correction pay run and an uncomfortable conversation with a staff member.

Stage 5: Training and Go-Live

A correctly configured system that nobody uses properly still fails, so go-live is as much about people as it is about payroll. Training covers three groups:

• Payroll administrators: processing a pay run, handling adjustments, reading reports and lodging STP.
• Managers: approving timesheets and leave, and why doing it on time matters to the pay run.
• Employees: the self-service app for payslips, leave requests and updating their own details, usually the single biggest driver of adoption.

Before the first live pay run, confirm the parallel runs are signed off, the ATO connection and any standing authority are configured, the accounting integration is mapped correctly, and support is on standby. Lodge the update or pay event required by the chosen transition path; do not rely on an undocumented employer test-lodgement step.

Stage 6: Post-Go-Live Review

Implementation is not finished at the first successful pay run. Build in a checkpoint two or three cycles later: are pay runs processing without manual workarounds creeping back in, are STP lodgements going through clean every time, are leave balances accruing as expected, and is adoption sticking or have people gone back to email and spreadsheets. It is also worth checking whether you are using what you are paying for: some features get switched on at setup and never touched again.

Employment Hero’s implementation options and where each fits

Employment Hero offers a self-serve route, Guided Payroll Implementation and Managed Payroll Implementation. Guided is positioned for organisations under 100 employees with a supported pre-built award and enough internal capacity to complete the project. Managed is positioned for larger or more complex organisations, including custom rulesets and businesses without experienced payroll capacity. Employment Hero’s current implementation page lists Managed Payroll from $100 per employee and custom build work at $250 per hour excluding GST, with additional complexity costs possible. Those are vendor-published figures checked on 12 August 2026 and should be rechecked before publication.

EH’s own managed option can be the right fit where the organisation wants the vendor to own the base platform build. A Certified Partner is more useful where award interpretation, migration decisions, business-specific rule design and ongoing support need to sit with one operator. We scope both routes before recommending one.

Where payroll exposure remains

Discovery and configuration decide the quality of an Employment Hero payroll implementation because every later stage inherits those decisions. Award rule-set building, qualifying-earnings mapping and opening-balance reconciliation carry Fair Work and ATO exposure if they go wrong. They also take award and payroll knowledge to get right the first time.

That is the work our implementation and award setup service covers for Australian SMEs, particularly in award-heavy industries like hospitality, social and community services, construction and manufacturing. The Employment Hero platform covers far more than payroll too, from onboarding to compliance reporting, and sits alongside the same implementation.

What Are the Six Stages of an Employment Hero Payroll Implementation?

An Employment Hero payroll implementation runs through discovery, configuration, data migration, parallel pay runs, training and go-live, then a post-go-live review. Each stage depends on the one before it: discovery sets the requirements, configuration builds the engine, migration brings people and balances across, and parallel runs prove it all matches before anyone relies on it.

Why Does Qualifying Earnings Affect My Employment Hero Super Setup?

For wages paid from 1 July 2026, Superannuation Guarantee is calculated on qualifying earnings. QE includes OTE plus specified payments such as all commissions and eligible contractor payments, so each pay category and employee override needs checking against the current ATO definition.

Do I Need a Parallel Pay Run Before Going Live on Employment Hero?

Yes. Running at least one full pay cycle through both your old system and Employment Hero side by side, then reconciling gross pay, tax, super and net pay line by line, is how configuration errors are found before they become live underpayments. The run should include representative awards, employment types, allowances and boundary cases.