Skip to main content

Plant hire chargeout and job costing

Charge the project for the plant it used, and know what each machine costs to own. Both need the same thing underneath: costs, hours and location captured against the machine at the time, not reconstructed at month end.

Lachlan McRitchie

Lachlan McRitchie

GM of Operations

Published 3 September 2026

Trusted by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuilt
Rated 4.9 out of 5 on G2Rated 5.0 out of 5 on Capterra15 reviews on G2 · 17 reviews on CapterraCapterra Best Value 2026 badgeCapterra Best Ease of Use 2026 badge

What is plant chargeout?

Plant chargeout is charging a project for the machine it used, at a rate, as if the yard hired it to the job. The machine stays owned by the business, but the project carries the cost of the time it held it. Doing that fairly needs three facts recorded against the machine as they happen: what it cost, how many hours or days it ran, and which job it was on. MapTrack holds those facts on the asset record. The rate itself and the invoicing stay in your finance system.

  • Costs: Maintenance, parts, fuel and labour recorded by category against the asset.
  • Hours: Meter and run-hour readings, plus assignment history for where it was allocated.
  • The rate: Set and applied in your finance system. MapTrack supplies the underlying data.

Why does the yard end up absorbing everything?

Because the costs are visible and the usage is not. A machine breaks, the repair invoice arrives, and it goes against plant overhead because that is the only code anyone is sure of. Meanwhile the project that ran it into the ground has already closed out looking profitable. Over a year that pattern makes the yard look expensive and every project look better than it was, and no amount of month-end reconciliation fixes a cost that was never coded to a machine in the first place.

The problem

Plant is usually the second largest cost in a civil or construction business and the least well attributed. Repairs get coded to overhead because that is easier than working out which job caused them. Hours come off a pre-start sheet if they come at all. Nobody can say what a specific machine cost to run last year, or whether the project that had it for three months paid its way. The result is project margins that are quietly wrong in both directions.

How MapTrack addresses it

Record the costs against the machine as they happen. Maintenance, parts, fuel and labour go on the asset by category and can be linked to jobs or projects where you use those. Meter and run-hour readings give you the usage side, either recorded by the crew or fed from a configured telematics integration. Assignment history shows where the machine has been and who held it. That gives finance the three inputs a chargeout calculation needs, captured at the time rather than rebuilt from memory at month end.

How it works

  • 1

    Decide what you are trying to answer first

    Charging a project, or knowing what a machine costs to own. They share data but they are different reports, and building for both at once is how these projects stall.

  • 2

    Code costs to the machine, not to plant overhead

    Maintenance, parts, fuel and labour recorded by category against the asset. This is the step that determines whether any later number means anything.

  • 3

    Capture hours from a source you trust

    Meter readings from the crew or from a configured telematics integration. Be clear whether a figure is measured hours or allocated time.

  • 4

    Keep the assignment history

    Where the machine was and who held it, so a cost can be traced back to the period and the job that produced it.

  • 5

    Apply the rate in the finance system

    MapTrack supplies costs, hours and location. The rate card and the invoicing belong where your accounting already lives, connected by integration or the public API.

Where this usually falls over

Chargeout projects fail on data capture rather than on the calculation. The arithmetic was never the hard part.

Costs coded at the time, on the asset

A repair invoice coded to plant overhead is unrecoverable later. Coded to the machine, it feeds both the project view and the ownership view.

Hours with a known source

Meter readings measure use. Assignment history measures allocation. Saying which one a number came from is the difference between a report and an argument.

Machine costed and job costed together

Damage follows the job, wear follows the machine. Keeping both views is what makes the yard defensible at review time.

The rate stays in finance

We do not try to own your rate card or your invoicing. The gap worth closing is the data underneath it, which is the part that is currently missing.

Code the cost to the machine

Capture costs, hours and location against the asset as they happen, and let finance apply the rate.

  • No credit card required
  • 30 days free trial
  • Cancel anytime

Frequently asked questions

It is the practice of charging a project for the plant it uses, at a rate, as though the yard were hiring the machine to the job. The machine is still owned by the business. The point is that the project carries the cost of the time it held the machine, so project margins are honest and the yard is not quietly absorbing the cost of idle gear.

A repair that is job costed lands on the project that caused it. The same repair machine costed lands on the machine, and rolls up into what that machine costs to own. Both views are legitimate and teams need both: damage caused on a job should follow the job, and fair wear and tear should follow the machine. The mistake is having only one of them.

Costs recorded by category against an asset, and linked to jobs or projects where you use those. Meter and run-hour readings. Assignment history showing where a machine has been and who held it. Maintenance and parts costs on the asset record. That is the data a chargeout calculation needs. The calculation itself, and the invoicing, sit in your finance system.

You can build toward one. Maintenance, parts, fuel and labour costs recorded against the asset give you the running side, and our total cost of ownership calculator covers the method for combining that with purchase, finance and depreciation. Whether the number is any good depends entirely on whether the costs were captured against the machine at the time.

That depends on where they come from. Meter readings recorded by the crew, or fed from a configured telematics integration, are the reliable source. Utilisation derived from assignment history tells you how long a machine was allocated somewhere, which is a proxy for use rather than a measure of it. Idle time is the gap between the two, and it is usually larger than people expect.

Because the cost, the hours and the location of a machine are recorded by three different people in three different places, and only combined at month end. By then nobody can say whether the hydraulic repair belonged to the job that damaged it. Recording the cost against the asset at the time it happens is the only version that survives.

Give finance data it can charge from

Join construction, mining and field service teams across Australia.

G2 4.9 out of 5 stars4.9 on G2 · 5.0 on CapterraCapterra 5.0 out of 5 stars
  • No credit card required
  • 30 days free trial
  • Cancel anytime