Knowledge · Finance
Job cost reporting,
the reports that run the company.
A residential building business runs on a small set of reports, the job cost summary, the variance report sorted by damage, cost-to-complete movement and the company WIP roll-up. This reference covers who reads each one and how often, why movement matters more than totals, and the habits that keep the job reports and the accounts telling one story.
01 / Overview
What job cost reporting is
Job cost reporting is how the numbers a building business already holds get put in front of the people who can act on them. The underlying data on a residential job is budget, committed cost, actual cost and forecast, held against cost codes; a report is an arranged view of that data, produced as at a known date, for a known reader. The distinction matters because many builders do not have a data problem so much as a reading problem, the numbers exist somewhere, but nobody sees them in a form that prompts a decision.
In practice a residential building company runs on four reports. A job cost summary showing budget, committed, actual and forecast by cost code. A variance report with the same lines sorted by dollar damage. A statement of how the cost to complete moved since the last review, and why. And a company-wide work-in-progress roll-up that puts every live job on one page. Almost every other job report is a re-arrangement of these four.
Why it matters
Reporting is the sensing layer of construction cash flow. The decisions that keep a building business solvent, which claim to bring forward, which package to re-quote, which job is quietly consuming the others' margin, are all made off reports, or made blind. The day-to-day capture that feeds every one of them is covered in the builder cost tracking guide; this page is about what happens after capture, turning recorded numbers into read ones. The test of a report is not its accuracy alone but whether last week's edition changed anything, because a report nobody acts on is decoration.
02 / The lifecycle
Where reporting sits in the cost stack
Reporting sits at the top of the cost stack and creates none of the data underneath it. Cost control is the discipline of holding a job to its budget, cost codes give every number its address, and cost to complete supplies the forward-looking column. A report arranges what those disciplines produce, dates it, and puts it in front of a reader. That is also why report quality cannot be fixed at the report; a summary built on invoices coded three weeks late is late everywhere.
Within the finance cluster, the reports are the working face of financial visibility, the visible output of everything underneath. The revenue side of the WIP roll-up comes from progress claims, so billed can be compared with built, and cash flow forecasting consumes the same numbers with dates attached, remaining costs as payments to go out, remaining claims as cash to come in. A reporting habit that is weak makes all three weak with it.
03 / Process workflow
The reporting rhythm, step by step
Eight steps, seven weekly and one monthly. The weekly ones turn recorded numbers into read ones; the monthly reconciliation keeps the job system and the accounts telling the same story.
- 01
Bring the inputs current
Code the supplier invoices, record every order and subcontract raised since the last review, and update the claims. A report built on stale data reports history with today’s date on it, and the review spends its time arguing about inputs instead of reading the job.
- 02
Run the job cost summary
Budget, committed, actual and forecast side by side for every cost code, with the as-at date printed on the page. The date is not decoration; a number without a date cannot be compared with the number before it, and comparison is the whole point.
- 03
Read the movement first
Compare this summary with the last one and list the lines that moved, by how much and in which direction. On a healthy job most lines do not move; the handful that did are the review. Totals come last, if at all.
- 04
Sort the variance report by damage
Re-order the variance lines by dollar impact, worst first, not by cost code order. A report sorted by code buries a $9,000 problem on page three under forty lines that are fine; a report sorted by damage puts the news on the first page.
- 05
Put the uncoded bucket on top
Show every cost not yet allocated to a code, with its size and its age, at the top of the report rather than in a sundry line at the bottom. Uncoded cost is unread news, and hiding it does not make it smaller.
- 06
Record the explanations
Every material movement gets a stated reason on the record, a rate movement, a variation, a scope gap found, a coding correction. A movement without an explanation this week becomes an argument about memory next month.
- 07
Roll up the company position
Bring every live job onto one page, cost position and billed against built, so over- and under-billed jobs are visible together rather than one at a time. The portfolio view is where a business, rather than a job, gets steered.
- 08
Reconcile to the ledger monthly
Agree total job costs in the job system to the job cost accounts in the general ledger and chase every difference to a named cause. The two systems drift apart quietly; the monthly habit is what keeps one story in front of the bank, the accountant and the owner.
04 / Key mechanics
The four reports, and who reads them
Each report is a different arrangement of the same underlying numbers. The arrangement is the analysis, which is why sorting and dating are not cosmetic.
The job cost summary
Budget, committed, actual and forecast for every cost code on the job, as at a stated date. This is the base document; every other report on this page is a re-arrangement of it. Its quality is set upstream, by how current the invoices, orders and claims behind it are.
The variance report, sorted by damage
The same lines re-ordered by dollar impact, worst first. Sorting is the analysis; the reader’s attention lands on the three lines that matter instead of being spent evenly across fifty that do not. Percentages flatter small lines, so sort by dollars.
Cost-to-complete movement
What the forecast final cost did since the last review, line by line, with a reason against every material change. Movement is the early-warning instrument; a forecast that moved for stated reasons can be trusted, and one that never moves is not being reviewed.
The company WIP roll-up
Every live job on one page, cost position against budget and billed against built. This is the report the accountant, the financier and the warranty insurer will ask about, and the one the owner uses to see the business rather than a job at a time.
One set of numbers, three grains
The owner, the supervisor and the accountant need different views, not different numbers. The owner's view is weekly and shallow but wide, movement by job, variance by damage, the company roll-up, a page or two at most. The supervisor's view is live and deep but narrow, committed against budget for every code on their own job, because they raise the orders that move the lines. The accountant's view is month-end and reconciled, job totals agreed to the ledger, WIP stated formally. Serving all three from one report at one grain serves none of them, and each quietly builds their own version, which is how a business ends up arguing about whose spreadsheet is right.
Reconciling the job reports to the accounts
The job system and the general ledger measure the same money and still drift apart, quietly and mechanically. An invoice entered in one system before the other, a credit note applied once, a cost coded to the wrong job, GST carried in the ledger while job reports are commonly kept GST-exclusive. None of these is an error anyone notices at the time. The working habit is a monthly reconciliation, agree total job costs in the job system to the job cost accounts in the ledger, and chase every difference to a named cause rather than a rounding shrug. Where the ledger is Xero, a Xero integration that posts from the same event that updates the job keeps the two systems fed once instead of keyed twice, which shrinks the reconciliation to the genuine differences.
Report hygiene
Three small habits carry most of a report's trustworthiness. An as-at date on every page, because an undated number cannot be compared and will be quoted as current long after it is not. The uncoded cost bucket shown openly, with its size and age, rather than dissolved into sundry lines. And a written explanation against every material variance, recorded when the cause is still visible. Reports with these three habits survive scrutiny from accountants and financiers; reports without them invite it.
05 / Best practice
How experienced builders read the numbers
The operator's observation is that the most useful question a report can answer is not how much have we spent, it is what changed since last week and why. Totals are large, stable and reassuring, which is precisely why they conceal trouble; a job can hold the same total for months while three codes trade places underneath it. Movement is small, specific and actionable. A builder who reviews movement reads five numbers instead of fifty, and the five are the ones with decisions attached.
The same operators watch the uncoded bucket the way a supervisor watches the sky, because uncoded costs are where bad news hides first. An invoice that is hard to code is often hard to code because nobody wants to own it, a variation that was never raised, a scope gap between packages, a back-charge in dispute. Growth in the uncoded bucket is frequently the first written evidence of a problem the site has known about for a fortnight, which is why experienced builders print it at the top of the report and ask about its age, not just its size.
The third habit is putting the same numbers in front of everyone. When the estimator, the supervisor and the owner each keep their own version, the weekly meeting is spent reconciling spreadsheets instead of making decisions, and every disagreement is about whose figure is right rather than what to do. One shared set of numbers, read at different grain by different people, turns the meeting from reconciliation into decision. Many builders find this change alone shortens the meeting and sharpens it at the same time.
Where software fits the workflow
Traditionally the weekly report is a spreadsheet assembled from the ledger, the order file and memory, an evening's work whose as-at date is stale before it circulates. In VIABUILD, cost tracking holds budget, committed, actual and forecast against every cost code as the job runs, and Oryn™ reads and codes supplier invoices as they arrive, so the report is a view of live data rather than a document rebuilt from it. The estimator, the supervisor and the owner read the same numbers at their own grain, and the movement since last week is a question the system can answer rather than a comparison someone has to build.
06 / Australian considerations
Job reports in the Australian environment
Job cost reporting is an internal discipline, but the reports it produces are the documents outsiders judge the business by. The points below are labelled by evidence class; requirements change and differ by jurisdiction, so confirm the current source before relying on any of them.
- Legislation. Australian tax law requires businesses to keep records that explain their transactions, and the ATO publishes record-keeping guidance for businesses. Well-kept job cost records generally satisfy this as a by-product; confirm the current requirements and retention periods against ATO guidance rather than a web page.
- Common practice. WIP schedules built from job cost reports are what accountants, financiers and home warranty insurance eligibility assessments commonly ask a builder to produce, and the hygiene of the underlying reports (dated, reconciled, explained) decides whether those schedules survive scrutiny.
- Common practice. GST is a standing reconciliation difference. Job cost reports are commonly kept GST-exclusive while the ledger carries GST, so a like-for-like comparison must strip it consistently. This is mechanical, but it is the most frequent reason the two systems appear to disagree when they do not.
- Professional recommendation. Reconcile job system totals to the general ledger monthly, and take the question of how the WIP position translates into recognised revenue to the builder's accountant. That translation is an accounting treatment; the builder's job is keeping the cost inputs honest enough to be worth accounting for.
07 / Common mistakes
Where job reporting actually goes wrong
Each of these is recognisable, mechanical and avoidable. None of them requires bad data; a business can fail at reporting with every number correct.
The report nobody acts on
A report that gets produced, circulated and filed has become decoration. The test is retrospective, did last week’s report change anything, an order re-quoted, a variation priced, a conversation brought forward. If nothing changed for a month, change the report.
Totals instead of movement
Totals are big, stable and reassuring, which is exactly why they hide trouble. A job can look the same at the total line for months while three cost codes quietly trade places underneath. The information is in what changed, not in what is.
The uncoded bucket hidden
Costs that resist coding get parked in sundry or miscellaneous lines where nobody reads them. An invoice is often hard to code because nobody wants to own it, an unraised variation, a scope gap, a back-charge. Bad news enters the job here first.
Job system and ledger drifting apart
An invoice entered in one system and not the other, a credit note applied once, a GST difference, and within a quarter the builder has two versions of the truth. Without a reconciliation habit, nobody notices until the accountant does.
No as-at date on the page
A report without a date cannot be compared with the one before it, and comparison is what reports are for. Undated numbers also get quoted weeks later as if they were current, which is how a stale figure ends up in a bank conversation.
One report for every reader
The owner needs movement across jobs, the supervisor needs live line detail on one job, the accountant needs reconciled totals at month-end. A single report at a single grain serves none of them, so each quietly builds their own, and the versions diverge.
08 / Practical example
A worked weekly review
Illustrative only, not a benchmark. A custom home is contracted at $860,000 against a budgeted cost of $770,000. The fifty-line job cost summary looks fine, every code within a few per cent of budget, total forecast final cost $779,000 against $772,000 last week. Read as totals, the job has drifted $7,000 and nobody knows where or whether it is finished drifting.
Read as movement, the review is five numbers. The cabinetry order landed $4,000 over allowance (a current quote, now committed, finished moving). An unpriced drainage instruction is carried at $3,000 (not finished, needs a variation raised this week). And the uncoded bucket has grown from $3,100 to $9,400, mostly one electrician's invoice referencing works nobody recognises, which turns out on a phone call to be an unraised variation for switchboard changes the client asked for on site. Five numbers, three decisions, twenty minutes. The totals view had the same facts and produced none of them.
09 / FAQ
Common questions.
Four cover almost everything. A job cost summary showing budget, committed, actual and forecast by cost code, a variance report sorted by dollar damage, a statement of cost-to-complete movement since the last review, and a company-wide WIP roll-up. Most other job reports are re-arrangements of these, and adding more reports rarely adds more decisions. The discipline is less about which reports exist and more about whether each one has a named reader and a known cadence.
It depends on the reader. Supervisors need committed against budget on their own job continuously, because they are the ones raising the orders that move it. Owners commonly work to a weekly rhythm, reading movement and the company roll-up. Accountants work month-end, on totals reconciled to the ledger. In practice the weekly owner review is the load-bearing one; a month between reviews is long enough for a small drift to become a settled fact.
Job cost reporting is the wider discipline, all the arranged views of a job’s cost position. WIP reporting is one specific view, comparing the value of work done against what has been billed across unfinished jobs, which is how over- and under-billing become visible. The WIP roll-up depends on the same inputs as every other job report, so a builder with stale cost data has a stale WIP position too, however tidy the schedule looks.
Usually through quiet mechanical drift rather than error in either system. Invoices entered in one system before the other, credit notes applied once, costs coded to different jobs, GST carried in the ledger but excluded from job reports, and timing differences around month-end. Each difference is small and explainable; unreconciled, they accumulate into two versions of the truth. A monthly reconciliation that chases every difference to a named cause keeps the drift near zero.
Uncoded costs are amounts recorded against a job but not yet allocated to a cost code, invoices waiting for someone to decide where they belong. They matter because they are invisible to every report built on cost codes; a variance report cannot show damage that has not been coded yet. They also skew toward bad news, because an invoice that is hard to code is often one nobody wants to own. Report the bucket’s size and age openly, and treat growth in it as a signal.
The cause, the dollar effect, whether it is finished moving, and what was decided. A rate movement on a supply line, a variation priced or still pending, a scope gap found at ordering, a coding correction. The explanation is written for the reader three months from now, who needs to know whether this line’s history is noise or a trend. Builders who keep this record find close-out reviews take an afternoon instead of an argument.
10 / Terms
Glossary for this topic
Job cost summary (budget, committed, actual and forecast by cost code as at a date), variance (the difference between a line and its budget), movement (the change in a number between reviews), as-at date (the date a report's numbers were true), uncoded costs (amounts recorded against a job but not yet allocated to a code), WIP roll-up (every live job's cost and billing position on one page), reconciliation (agreeing the job system to the general ledger). Definitions for the wider vocabulary live in the construction glossary.
Every number in these reports ultimately follows the build itself, and the timeline the build follows is the subject of residential construction scheduling.
11 / Keep reading
Related knowledge, guides and features
12 / Further reading
Primary sources
- Australian Taxation Office , publisher of the record-keeping requirements for businesses, the reference for what must be kept and for how long.
- Australian Accounting Standards Board , publisher of the accounting standards governing how construction revenue is recognised, the reference to take to the builder's accountant.
- Your state or territory's building regulator and fair trading body, for any financial reporting and home warranty insurance eligibility requirements that apply to licensed builders in your jurisdiction.
Read five numbers, not fifty.
VIABUILD holds budget, committed, actual and forecast against every cost code as the job runs, so the weekly report is a live view of what moved and why, not a spreadsheet rebuilt from the ledger every Thursday night.