Project
Payroll

Native sync

BuildPass + construction payroll.

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.
See pricingAll integrations

Data flows

What data moves, and which way?

  • Approved timesheetsBuildPass → Project PayrollHours, job, cost code, allowances flags
  • Jobs & cost codesBuildPass → Project PayrollStructure mirrored, external IDs retained
  • WorkersBuildPass ↔ Project PayrollSingle system of record per field
  • Costed labourProject Payroll → BuildPassTrue actuals after the pay run

In context

Where does BuildPass sit in the pay run?

Flow · from BuildPass, no CSV

  1. Step 1

    Timesheets

    Approved on site

  2. Step 2

    Award & EBA

    Interpreting award…

  3. Step 3

    Payroll

    Paid, STP2 filed

  4. Step 4

    Super

    Every pay run

  5. Step 5

    Job costs

    Live to cost codes

BuildPass questions

Do timesheets still need approving in payroll?

No. Approval happens on site in BuildPass. Timesheets cross the boundary already approved, which is why there is no second approval queue in payroll.

Is estimated cost the same as actual cost?

No, and we keep them separate. Nightly estimated cost uses each worker's rate; true actuals are written back after the pay run is finalised.

What happens if a timesheet changes after payroll runs?

The change comes through as an adjustment and is paid in the next run with an audit trail against the original line.

How long does connecting take?

It is switched on during setup, inside the standard four-week go-live, and tested in a parallel pay run before you rely on it.

Reviewed August 2026. Connection scope confirmed during setup before you rely on it.