Native sync
Employment Hero HR + construction payroll.
Employment Hero HR can stay as your employee system of record while Project Payroll runs construction payroll. Employee records, onboarding and leave balances sync natively, and award or EBA interpretation happens in our engine with our team maintaining it.
Data flows
What data moves, and which way?
- Employee recordsEmployment Hero → Project PayrollOnboarding, details, terminations
- LeaveEmployment Hero ↔ Project PayrollRequests in, balances back
- Pay detailsProject Payroll → Employment HeroPayslip availability
- ClassificationsEmployment Hero → Project PayrollMapped to award or EBA levels
In context
Where does Employment Hero HR sit in the pay run?
Flow · from Employment Hero HR, no CSV
Step 1
Timesheets
Approved on site
Step 2
Award & EBA
Interpreting award…
Step 3
Payroll
Paid, STP2 filed
Step 4
Super
Every pay run
Step 5
Job costs
Live to cost codes
Employment Hero HR questions
Do we have to leave Employment Hero HR?
No. Many clients keep HR there and run payroll with us.
Who maintains EBA configuration?
We do, included in your price — no paid configuration projects and no waiting weeks for a change.
What about support hours?
Ours are 24/7 and free, which matters when a pay run breaks at 9pm on a Thursday.
Is leave calculated twice?
No. One system of record per object, agreed at setup.
Reviewed August 2026. Connection scope confirmed during setup before you rely on it.