Live Construction Cost Reporting: Why Your Month-End Cost Report Is Already Out of Date

Here's how cost reporting works on a lot of Australian jobs.

Month-end comes. Accounts close off the period in the ERP or Xero. The QS pulls the commitments out of a spreadsheet, because the subcontracts and POs live somewhere else. The claims were assessed in another system, so someone exports those. The variations are in a register, so someone types those in. The PM updates their cost-to-complete in a separate tab. Then it all gets stitched together, checked, argued about and issued.

By the time the cost report lands, it's describing a job that existed four to six weeks ago. Every decision made off it is made on old numbers. And the problem it should have caught, the trade that's blowing out or the variation nobody's secured, has had another month to grow.

That's a historical cost report. It's not a bad report. It's just a photo of the past, taken slowly.

What we mean by live

ClaimStack's Financial Hub doesn't build the cost report from imports. It calculates it from the commercial record itself: the contracts you've let, the POs you've raised, the claims you've assessed, the invoices you've approved, the timesheets you've signed off, and the variations on all of them.

So when a subbie's claim is certified, a supplier invoice is approved or a variation is assessed, the cost picture follows. There's no month-end import, no batch job and no one re-keying numbers into a spreadsheet.

Change a number in the Financial Hub and the budget recalculates there and then. Every PDF report is generated fresh from the record when you run it.

Plan: the Financial Hub, cost reports, cashflow forecasting and company financials are on Commercial OS, at $140 per seat per month.

Where every number comes from

The reason it can be live is that ClaimStack already holds the transactions. It isn't a reporting tool bolted onto your accounts. It's where the commercial work is done.

Here's what counts as cost, and when:

Commitments come from the subcontracts and POs themselves, and they can be split across budget lines by percentage.

Supplier invoices come in through the AI invoice inbox: email them in, they're read and matched to the PO, and once approved they hit the budget line the PO sits against.

Every source has one definition of actual cost. The budget table, the summary cards and the PDF reports all use the same rule, so they can't disagree with each other.

What each budget line shows

For every line in your budget, by cost code, trade or package:

• Original and current budget
• Committed, split into subcontracts, POs, staff and direct costs
• Actual cost to date
• Cost to complete, either entered by the PM or calculated as budget less committed
• Risk allowance and released savings
• Forecast final cost: committed, plus cost to complete, plus risk
• Forecast variance and the uncommitted balance
• What procurement expects the package to come in at

At project level you get the contract sum, budget movement, forecast final cost, gross margin, the committed breakdown and pending variations.

Variations in the forecast

Variations are usually where the forecast is most wrong, because the register and the cost report are in different places.

Here they're in the same place:

• Approved variations move the contract sum and the budget.
• Pending variations are shown against each contract, so you can see what's still unsecured.
• Each variation can be forecast at its submitted amount, its assessed amount or your own figure. A PM who expects a $40,000 claim to land at $25,000 can forecast it that way without waiting for the assessment.
• Head contract variations can carry cost-to-complete, risk and opportunity lines, and they can be linked to the subcontract variations and POs underneath. You see what you got approved upstream against what it costs you downstream.

There's more on this in how ClaimStack manages variations.

Setting up the budget

You don't start from a blank screen:

• Import from Excel or CSV, or have AI extract the budget from a PDF or a photo
• Import a Procore budget CSV
• Build it from the contract breakdown
• Use your company cost-code library, which maps to your Xero items

Procurement feeds it too. As packages are tendered, each budget line shows what procurement expects that package to cost: the awarded price, the lowest bid, the average of the three lowest, or your own figure. Savings against the estimate show up before the contract is even signed.

Budgets can be locked, and every transfer and reallocation is recorded in a change register.

The month-end report still exists

Live doesn't mean you lose your reporting period. It means the period report is a photo of the live picture, not the only picture you've got.

Snapshots of the budget are taken automatically on the cycle you set, weekly, fortnightly or monthly. A snapshot keeps the full position, reopens read-only and can be compared with today. The cost report can show movement columns against a snapshot, so "what's changed since last month's report" is built in, not a second spreadsheet.

Cashflow

The cashflow forecast runs monthly against each contract's breakdown:

• Enter it, import it from CSV or Excel, or build it from your programme. AI matches the programme activities to the breakdown and spreads them on an S-curve or evenly.
• Certified months replace the forecast and lock, and you get suggestions for redistributing what's left.
• Inflow, outflow and net position on certified, applied and forecast bases, with a cumulative curve and your worst cash position flagged.

Reports

Ten formatted PDF reports, generated from the record when you run them:

• Cost report
• Executive summary
• Detailed budget
• Variation register
• Variation forecast position
• Risk and opportunity register
• PO vs invoiced
• Invoice burn rate
• Labour tracker
• Staff timeline

Cashflow and invoices export to Excel.

Across the business, Company Financials brings revenue, direct costs, overheads, cash flow and labour together across all your projects, with P&L and cash position reports.

Every side of the contract sees the right numbers

ClaimStack works for whichever side of the contract you're on, and the Financial Hub follows that:

• Head contractors get the full picture: revenue, cost, margin and forecast.
• Clients and developers paying on a head contract get a budget view and a change register, without the builder's margin.
• Subcontractors see their own contract.

Each party sees only the contracts they're party to.

Your accounts stay your accounts

ClaimStack pushes approved bills, sales invoices and credit notes to Xero, and payment status comes back. Approve a supplier invoice in ClaimStack and the bill goes to Xero without anyone retyping it.

The cost report doesn't wait on the ledger, though. It's calculated from the commercial record, which is the point: it knows what you've committed, certified and approved before accounts has posted anything.

What it doesn't do (yet)

We'd rather you hear it from us:

• Actual cost isn't "paid to date". It's what's been certified or approved. Paid figures are tracked per contract, not per budget line.
• The cost report is PDF only. Cashflow and invoices export to Excel; the cost report itself doesn't yet.
• No cross-project forecast roll-up. Company Financials rolls up P&L and cash across projects, but not forecast final cost.
• No ERP connector. We integrate with Xero, and import budgets from Procore. Commitments aren't pushed to your accounting system.

The short version

• Cost is calculated from the commercial record, not imported at month-end
• Updates as claims, invoices, timesheets and variations are approved
• One definition of actual cost across every view and report
• Committed, actual, cost to complete, risk and forecast final cost on every line
• Variations forecast individually, and linked upstream to downstream
• Snapshots and movement columns for your reporting period
• Cashflow built from your programme, with certified months locked
• Every side of the contract sees the numbers it should
• On Commercial OS, $140 per seat per month

A cost report you have to build is history. One that builds itself while the job runs is control.

See cost reporting on ClaimStack →

Frequently asked questions

Is ClaimStack's cost reporting real time?

ClaimStack calculates cost, commitments and forecast final cost from the commercial record itself: assessed claims, approved invoices, receipts, approved timesheets, POs, contracts and variations. There's no month-end import or batch job. Changes in the Financial Hub recalculate straight away, and PDF reports are generated from the record when you run them.

What counts as actual cost in ClaimStack?

Certified subcontract and consultant claims, approved or paid supplier invoices and receipts (ex GST), approved timesheet labour at the rate locked in on approval, and cost-plus direct and staff costs. A subcontractor's tax invoice that settles a claim isn't counted twice.

How is forecast final cost calculated?

Forecast final cost is committed cost, plus cost to complete, plus risk allowance. Cost to complete can be entered by the project manager or calculated as budget less committed.

Does ClaimStack replace Xero?

No. ClaimStack pushes approved bills, sales invoices and credit notes to Xero, and payment status comes back. The cost report is calculated from the commercial record in ClaimStack rather than from the ledger.

Can I still report monthly?

Yes. Budget snapshots are taken automatically weekly, fortnightly or monthly. You can compare them with the current position, and show movement against a snapshot on the cost report.

Which plan includes the Financial Hub?

The Financial Hub, cost reports, cashflow forecasting and company financials are on Commercial OS, at $140 per seat per month (AUD, ex GST).