Integrations
Construction payroll integrations.
Directory
Which platforms connect to construction payroll?
Procore
Native sync
Xero
Native sync
QuickBooks Online
Native sync
Employment Hero HR
Native sync
MYOB
Supported
Deputy
Supported
Tanda
Supported
NetSuite
Supported
Zoho Books
Supported
FreshBooks
Supported
Saasu
Supported
Roubler
Supported
Deep dives
What does native sync mean?
Live API both ways. No CSV anywhere in the flow.
Native sync
BuildPass
BuildPass captures and approves site time; Project Payroll pays it. Approved timesheets sync with job and cost code attached, get interpreted against your award or EBA, then flow to wages, super, STP2 and job costing without a CSV or a re-key.
Read the flow →Native sync
Procore
Project Payroll syncs Procore projects, cost codes and timecards natively. Approved site hours arrive with their cost code, get interpreted against the award or EBA, and post back as costed labour so your Procore budget reflects what payroll actually paid.
Read the flow →Native sync
Xero
Project Payroll posts a GL journal to Xero after every pay run, mapped to your chart of accounts and tracking categories. Payroll compliance — STP2, PAYG, super and payment files — is handled natively by us, so nothing lands back in your bookkeeper's lap.
Read the flow →Native sync
QuickBooks Online
Project Payroll posts payroll journals to QuickBooks Online after each pay run, mapped to your accounts and classes. We keep STP2, PAYG and super in our engine; QuickBooks receives the accounting entries only, so your reconciliation is a read, not a rebuild.
Read the flow →Native sync
Employment Hero HR
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.
Read the flow →
What does supported mean?
It works, and the page states the exact shape of the connection.
Supported
MYOB
MYOB is supported, and we are honest about the shape: depending on your MYOB product, payroll journals post via API or as a structured journal export. Payroll itself — interpretation, super, STP2, payment files — runs natively in Project Payroll either way.
Read the flow →Supported
Deputy
Deputy and similar rostering and time-and-attendance tools feed approved hours into Project Payroll. We interpret those hours against your award or EBA, pay them, remit super the same day and cost the labour to your job codes.
Read the flow →
Integration questions
What's the difference between native sync and supported?
Native sync is a live API connection both ways, with no file in the middle. Supported means the connection works but the shape is narrower — sometimes one-way, sometimes scheduled — and each page says exactly which.
Do you replace our site software?
No. Capture and approval stay where your foremen already work. We own everything after approval: interpretation, wages, super, STP2 and job costing.
What if our system isn't listed?
Tell us. We build connections where there's a real API, and we'll say plainly when a system only supports a scheduled file rather than pretending otherwise.
Does the ledger keep its own payroll?
No. We take payroll off the accounting platform and post a GL journal each run, so the ledger stays accurate without doing interpretation it can't do.
Reviewed August 2026.