Plant fuel usage (v1)
Plant fuel usage is one of Demiton's published registers for Australian civil construction. Plant and vehicle fuel usage per project, for fuel tax credit claims. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Assets in the register catalog.
- Register ID
plant_fuel_usageUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- An eventSomething that happened at a point in time.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.2)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- ATO business record-keeping rulesATO record-keeping for business (general 5-year retention; longer for depreciating assets)
- Corporations Act 2001 (Cth) s 286Corporations Act 2001 - obligation to keep financial records (7 years)
- ISO 55001Asset management - Asset management system - Requirements
- ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)
Connectors
Connected today
Demiton keeps this register current from these systems now.
No system fills this register yet.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- EROADPartial
- Geotab
Fields
17 fields: 6 required, 11 optional.
Required
Every record carries these fields.
- itemText
heavy_vehicle)Example:
diesel- litresDecimal number
Fuel volume consumed/purchased.
Example:
185.4- projectText
The project the fuel was consumed on.
Example:
BWG-2025-002- external_idText
Deterministic per-row identity the producer builds from project + item + key + period.
Example:
fuel-2026-3287- occurred_atDate
The usage date (month start for plant, transaction date for LV/HV)
Example:
2026-07-15- claim_amount_audDecimal number
The final computed claim figure = litres × the claim month's price variance, never re-derived downstream.
Optional
Present when the source system records them.
- regoText
Vehicle registration for LV/HV rows.
- assetText
The plant/vehicle the fuel belongs to.
Example:
9302- hoursDecimal number
Machine hours the fuel is attributed to.
Example:
9.5- alloc_daysNumber
Allocation days attributed to a light-vehicle row.
- asset_labelText
The Assignar display label for a plant asset (or its split sub-label)
Example:
Excavator 320 #2- driver_nameText
The person who purchased the fuel on an LV/HV row.
- hours_sourceText
Empty)
- burn_rate_lphDecimal number
Derived litres per machine hour.
- km_from_projectNumber
Distance from the project for a heavy-vehicle transaction, from Navman GPS.
- financial_periodText
The claim month (
YYYY-MM) the usage is attributed to.- attribution_methodText
navman_gps)
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asset": "9302", "asset_label": "Excavator 320 #2", "claim_amount": 342.1, "currency": "AUD", "external_id": "fuel-2026-3287", "hours": 9.5, "item": "diesel", "litres": 185.4, "occurred_at": "2026-07-15", "project": "BWG-2025-002", "source_system": "NAVMAN"}Version history
- v2 (current)
- v1
Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/plant_fuel_usage/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.