Cost Codes and Payroll Integration for Construction

Cost codes connect every paid hour and labour on-cost to the job, stage and task that caused it. When payroll and job costing share those codes, builders can see actual labour cost without re-keying timesheets or guessing where wages went.

What is a payroll cost code?

A payroll cost code is a label attached to time or earnings. It tells your systems where the labour cost belongs.

For example, a worker might enter:

• Job: 241, Riverside Apartments
• Phase: 03, Structure
• Activity: 120, Formwork
• Hours: 8 ordinary hours and 2 overtime hours

The job, phase and activity make up the cost code. Payroll still works out the correct pay rate, overtime, allowances, tax and super. The cost code tells the job-costing system where to post the resulting cost.

That distinction matters. The cost code should describe the work. It should not try to replace the employee's award classification, EBA classification, pay rule or tax settings.

You can read more about labour budgets, committed costs and actual costs in the construction job costing hub.

Why payroll integration matters

Without integration, the site team submits hours and payroll pays them. Someone then copies totals into accounting or a spreadsheet. That is where jobs disappear, activity codes get changed and overtime gets posted to a general labour bucket.

The pay can still be correct while the job report is wrong.

A proper connection passes approved time entries into payroll with the relevant job and activity codes. Once payroll is finalised, gross wages and selected on-costs return to job costing.

This gives the project team a clearer view of:

• Actual labour against budget
• Labour cost by task or trade
• Overtime by project
• Allowances linked to particular sites
• Productive and non-productive time
• Labour cost to complete

It also gives payroll one approved set of hours instead of multiple spreadsheets, emails and paper dockets.

What should be sent to job costing?

Not every number on a pay run is a job cost. Some amounts are direct labour costs. Others are employer on-costs, balance sheet amounts or general overheads.

Payroll item	Typical job-costing treatment	Common mistake
Ordinary wages	Post to the selected job and activity	Posting all wages to one labour code
Overtime wages	Post to the job, with overtime visible separately if useful	Sending only ordinary hours to the job
Site allowances	Post to the relevant job when the allowance was caused by that site	Spreading every allowance across all jobs
Superannuation	Add as an employer on-cost using a consistent allocation rule	Treating super as part of gross wages
Annual leave and personal leave	Allocate under a documented policy, often to overhead or a leave code	Coding leave to the worker's last active job without checking
Workers compensation premium	Allocate using an agreed rate or post to overhead	Treating an estimate as the final premium
Payroll tax	Allocate by state and business policy, or hold as overhead	Assuming one national threshold applies
PAYG withholding	Do not treat as an extra employer cost	Adding tax withheld on top of gross wages
Reimbursements	Post to the job only when the expense relates to that job	Treating reimbursements as labour cost

The right treatment depends on how you quote and manage work. If estimates include labour on-costs, actual job reports should use a comparable method. Otherwise the budget and actual columns are talking about different things.

Australian payroll figures that affect the setup

A few national payroll rules help shape the integration:

• The compulsory super guarantee rate is 12%, as at August 2026. Super should be calculated under payroll rules before being allocated to jobs. Not every payment is ordinary time earnings, so do not simply add 12% to every payroll line.
• The Australian resident tax-free threshold is $18,200, as at August 2026. PAYG withholding affects the worker's net pay, but it is not an additional labour cost for the job.
• Fair Work employee records must generally be kept for 7 years, as at August 2026. Keep the original time record, approval history, pay result and cost-code allocation traceable.
• Employers must generally give a pay slip within 1 working day of pay day, as at August 2026. A delay in job-cost posting should not hold up compliant payroll and pay slips.

Award rates, EBA rates, allowances and overtime rules can change. The applicable amount depends on the worker's classification, employment arrangement, work performed and effective date. Let payroll calculate those entitlements. Do not hard-code them into a project activity code.

Payroll tax thresholds and rates also vary by state or territory. Workers compensation arrangements vary too. Your allocation rules need to recognise where the wages are connected and how your business accounts for those costs.

A simple cost-code structure

Mate, this is where it is easy to build a monster. A code does not need to contain every fact about the pay run.

A practical hierarchy might be:

1. Job, such as 241
2. Phase, such as 03 Structure
3. Activity, such as 120 Formwork
4. Optional cost type, such as Labour

Keep payroll categories separate. Ordinary time, overtime, allowances and leave are earnings or work types. Carpenter, labourer and apprentice are classifications. They do not all need to be buried inside the cost code.

Use enough detail to answer real project questions. If nobody manages formwork stripping separately from formwork installation, two codes may create admin without improving decisions.

How the data should move

The cleanest process has five steps:

1. The worker selects a permitted job and activity when entering time.
2. The supervisor checks the hours, break details and code before approval.
3. Approved entries pass to payroll with employee, date, hours, work type and cost code.
4. Payroll applies the relevant rates, overtime, allowances, tax and super.
5. Final payroll costs post back to job costing, with a pay-run reference and audit trail.

This can happen through a direct system connection or a controlled file import. Either method can work. The important bit is that employee IDs, cost codes and earning categories map consistently.

Do not allow free-text job names if a worker can select from an approved list. Free text quickly creates three versions of the same project.

Closed jobs should also be blocked. If late time must be entered, require an authorised person to reopen the code or redirect the cost with a recorded reason.

Controls worth putting in place

Start with a short set of rules:

• Every productive hour needs a valid job and activity.
• Yard, training, leave and administration time use approved indirect codes.
• Supervisors cannot approve their own unauthorised code changes.
• Payroll exceptions are reviewed before the pay run is finalised.
• Changes after approval keep the old value, new value, user and time.
• Job totals reconcile to the payroll general ledger posting.
• Rounding is handled once, under a documented rule.

Run a reconciliation each pay cycle. Gross wages by job, plus wages coded to indirect accounts, should agree with the relevant payroll wage total. Then reconcile super and other on-costs separately.

A small unexplained difference can turn into a large reporting problem across several crews and pay runs.

A worked labour-cost example

Suppose an employee records 8 ordinary hours at an illustrative rate of $40 per hour, plus a $24 allowance connected to the site.

The gross amount is $344. If both payments are ordinary time earnings in this example, super at 12% is $41.28. The direct payroll cost posted to the job is then $385.28 before workers compensation, payroll tax or other allocated on-costs.

The actual classification, rate, allowance treatment and super treatment must come from the applicable payroll rules. The example shows the flow, not a rate to use for an employee.

Setting it up without overcomplicating it

Begin with the cost codes already used in estimating and project reporting. Remove duplicates. Decide which codes workers can select and which are restricted to payroll or finance.

Then test a complete pay cycle with a small crew. Check ordinary hours, overtime, allowances, leave, super, job transfers and a correction after approval. Confirm that project totals agree with payroll and the general ledger.

Finally, decide who owns new codes and who closes finished jobs. One person should not create near-duplicate codes whenever a new timesheet arrives.

When comparing system costs, include time capture, payroll processing, job-cost posting and support for your pay rules. The payroll pricing calculator can help you compare the likely cost against your crew size and payroll needs.