Is the problem job carrying costs that belong somewhere else?

A red number deserves a closer look

One project's report looks disastrous while another appears unusually profitable. That may reflect the work, but it can also reflect where invoices and labour were coded. Before deciding which project is draining the business, check the information behind the report. Correct classification will not remove a genuine loss, but it can stop the wrong project being blamed.

Start with the largest unexpected entries

Select significant charges and compare them with the purchase order, delivery address and actual work performed. Ask the person who approved the purchase to explain the allocation. Avoid moving costs simply because another project has more margin available. The aim is to reflect what happened, with an evidence trail for any correction made.

Keep the supporting records connected

Business.gov.au identifies expense and bank records among business records to retain. Link the relevant invoices and supporting information to the project entries. For shared items, ask the accountant or bookkeeper to establish a consistent allocation basis. A spreadsheet adjustment without an explanation may solve this month's appearance while making next month's comparison harder to trust.

Source: business.gov.au: Record keeping

A shared hire can distort two jobs

Imagine a hypothetical equipment invoice covering three weeks on one site and one week on another. The full invoice was coded to the first job because its supervisor ordered the hire. That job's report may overstate its share of the cost. Checking the hire history helps establish a more accurate allocation without pretending the business incurred less total expense.

Keep cash and profitability separate

Reallocating an expense between projects does not put money back in the bank or reduce the supplier's invoice. Show the corrected job result alongside the actual payment obligation. If the business still has a shortage, continue addressing it. Better reports support the decision; they do not fund the next wage run or authorise postponing a bill.

Fix the point where the error starts

After correcting supported errors, agree who supplies job references and who checks shared items before posting. Review the troubled project's remaining costs using the corrected information. If it still shows a loss, make that visible rather than continuing to search for a coding explanation. The useful outcome is a reliable diagnosis and a practical change to prevent repeated misclassification.