Job Cost Reporting Setup for AU Construction: The Active Project Register

May 27
7 min read

The reporting layer that makes the books defensible

Accurate revenue recognition under AASB 15 depends on accurate job-cost data. If your job-cost system is broken — costs miscoded, allocation rules drifted, project register stale — your revenue numbers are broken too. Period.

This is the layer that separates a construction business with defensible monthly close from one that's flying blind. Founders who know which project is making money. Bookkeepers who know which costs belong where. Project managers who can defend their cost-to-complete estimates to the bank.

This guide walks through how we set up job cost reporting at Financial Controller tier engagements at TechEdge — the project register, the cadence, the reconciliations, and the reporting layer that drops into the monthly management pack.

What the active project register needs to track

Per project, every month:

Project code + plain-English project name
Client name + head contractor (if relevant)
Bid value (original contract value, ex GST)
Approved variations — running total of variations formally approved with priced amounts
Pending variations — running total of variations submitted but not yet approved (separate from approved — subject to AASB 15 constraint test for revenue recognition)
Dayworks accrued — work performed at the head contractor's instruction but not yet invoiced
Cost incurred to date — broken out by category: labour, materials, subcontract, plant, allocated overheads
Cost-to-complete estimate — refreshed monthly by project manager, signed off
Forecast final cost = costs incurred + cost-to-complete
Forecast margin at completion = (bid + approved variations + accrued dayworks) − forecast final cost
Variance from bid margin — track to flag projects sliding away from plan
Practical completion target date
Retention released to date / retention outstanding

This is the one-page-per-project record. Run it in Excel, in Procore, in Buildertrend, in Workbench — whichever ERP you've chosen. The format matters less than the discipline of keeping it current.

The cadence — daily, weekly, monthly, quarterly

Daily — cost capture

Every cost incurred on a project gets captured the day it's incurred (or the day the invoice arrives, whichever is earlier). Labour hours, materials, subcontractor invoices, plant hire, fuel, site overheads.

The discipline: cost capture happens in the day's work, not on Friday afternoon, not at month-end. If your bookkeeper is doing a week's worth of coding in one block on Friday, you're losing accuracy.

Weekly — daywork reconciliation + labour timesheets

Every Monday morning:

Daywork sheets from the prior week reconciled — signed off, coded to the right project, sent to AR for invoicing
Labour timesheets approved and posted to projects
Subcontract invoices received in the past week reconciled to delivered work + coded
Plant hire variances flagged (over/under utilisation)

This weekly cadence catches the issues that would otherwise compound into month-end surprises.

Monthly — the full register update + WIP reconciliation

Last working day of the month, before close:

Project managers refresh cost-to-complete for each active project. Documented in the project file.
Project register updated with all month's costs, variations, dayworks.
Finance reconciles the job-cost system to the GL — total costs by project should tie.
Revenue recognition journals posted per the WIP reconciliation process (covered in Construction WIP Reconciliation).
Retention split applied on each progress claim raised.
Allocated overheads flow from clearing accounts to specific projects per allocation policy.
Sign-off: preparer + reviewer initials on the worksheet.

Quarterly — variance commentary

Every three months, projects with margin variance >2 percentage points from bid get a written commentary in the project file. Why the variance, what was the trigger, what action is being taken.

This is the documentation that survives the year-end audit. Auditors will sample projects with margin shifts — the commentary lives in the file.

Cost categories that need clean separation

The chart of accounts should break costs out by category, per project. At minimum:

Direct labour — site labour, sub-contracted labour, supervision attributable to specific projects
Materials — direct materials charged to project
Subcontract — separate from direct labour because retention and AASB 15 treatment differ (see cornerstone)
Plant / equipment — owned plant depreciation + hired plant + fuel + maintenance
Site overheads — security, temporary services, traffic management, site office
Allocated overheads — share of indirect labour, head office overhead, insurance, allocated by hours / labour cost / square metres per policy

Why this matters: margin analysis at category level reveals where you're winning or losing. If labour cost is 8 percentage points above bid but materials are on plan, the issue is productivity not procurement.

Overhead allocation — the easy way to get this wrong

Overheads (indirect labour, head office, insurance, leasing, depreciation on shared equipment) need to be allocated to specific projects monthly. Otherwise they sit in clearing accounts and project margins look better than they are.

Choose one allocation basis and document it in policy:

Direct labour hours — most common. Each project gets a share of overheads in proportion to its direct labour hours that month.
Direct labour cost — similar but weighted by hourly rate (captures skill mix).
Total direct cost — share of overheads in proportion to total direct cost charged to project.
Revenue-based — share of overheads in proportion to revenue recognised. Less common but defensible for stable margin operations.

Whichever basis you pick, apply it consistently. Re-allocating with a different method at year-end for "cleaner numbers" is exactly what triggers auditor concern.

The reporting layer — what feeds the management pack

Out of the project register, four reports flow into the monthly management pack:

1. Project register snapshot

One-pager per active project (the table from the start of this guide). Bid → variations → forecast → margin. This is the document the founder reads in 60 seconds before the weekly leadership meeting.

2. Margin distribution chart

Bar chart showing projects on the X-axis, forecast margin % on the Y-axis. Quick visual on which projects are pulling vs dragging. Colour-code: green for projects on plan, amber for >2pp variance, red for >5pp variance.

3. Variation register

Living spreadsheet tracking every variation by VOC number, date raised, value, approval status (approved / pending / disputed), date approved, date invoiced, date paid. Reconciled monthly; any "approved" line aged >30 days without invoice escalates to finance.

4. Single-contract concentration

Pie chart of revenue or backlog by head contractor. If one head contractor is >40% of revenue, that's a single-customer concentration risk the bank will flag in covenant reviews.

Tools — what works in AU construction

Stack choices we see working at $5M-$50M operators:

Xero + Xero Projects — works for sub-$10M operators with simple project structures. Limited cost-to-complete features; manual reconciliation needed.
Procore — international standard for mid-to-large operators. Cost-to-complete, variation register, daywork tracking native. Integrates with Xero / NetSuite / Sage for GL.
Buildertrend — popular with residential and small commercial builders. Job costing + scheduling + change orders native.
Workbench — AU-built option, particularly strong for civil contractors.
NetSuite + project module — enterprise-class, multi-entity operators, $25M+ scale. Heavy lift to implement but most complete.

Tool choice should follow the cost-to-complete and variation register requirements. A bookkeeper running Xero alone without a project layer can deliver clean monthly close but won't pass an AASB 15 audit on cost-to-complete documentation.

Common job cost mistakes

Mistake 1 — Project codes without sub-account discipline

Single project code in GL but costs aren't sub-accounted by category. Margin analysis at category level becomes impossible.Fix: chart of accounts with cost categories (labour / materials / sub / plant / overheads) sub-accounted under each project.

Mistake 2 — Allocated overheads sitting in clearing accounts

Overheads accumulated monthly but never flow to specific projects = inflated project margins.Fix: monthly allocation journal based on documented policy.

Mistake 3 — Stale cost-to-complete estimates

PM hasn't refreshed in 3 months. Revenue recognition drifts.Fix: monthly PM sign-off as part of close timetable.

Mistake 4 — No variation register

Variations get lost between operations and finance. Unbilled revenue accumulates.Fix: living register with monthly reconciliation. See the cornerstone piece for the structure.

Mistake 5 — Weekly daywork capture skipped

Daywork sheets pile up from multiple weeks; some get lost; some get coded to wrong projects.Fix: Monday-morning daywork reconciliation as a fixed weekly cadence.

When this is a specialist conversation

A competent bookkeeper can run the daily and weekly cadence if they're given a clean chart of accounts and the project register template. The CPA-led work is:

Setting up the chart of accounts with project sub-accounting
Writing the cost allocation policy (which method, why, how applied)
Monthly review of cost-to-complete estimates — defensibility check
Quarterly variance commentary review
Annual policy refresh as project mix changes

At TechEdge, this is part of every Financial Controller tier engagement (from $4,950/month). Construction operators typically engage at this tier once they're running three or more concurrent projects without a clean job-cost system in place.

TL;DR for the busy founder

Active project register, one row per project, updated monthly.
Cost categories separated: labour / materials / subcontract / plant / overheads.
Daily cost capture; weekly daywork; monthly register update; quarterly variance commentary.
Cost-to-complete refreshed monthly by the project manager — they're the source of truth.
Overheads allocated to projects monthly per documented policy.
Variation register kept current — unbilled variations are the largest hidden revenue leakage in AU construction.
Project register feeds the monthly management pack and the AASB 15 revenue recognition.