Plant fuel usage

Plant and vehicle fuel usage per project, for fuel tax credit claims.

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

v1Current version.

Download JSON SchemaSee an example record

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

18 fields: 7 required, 11 optional.

Required

Every record carries these fields.

external_idText

Deterministic per-row identity the producer builds from project + item + key + period.

Example: fuel-2026-3287

source_systemText

Which system emitted the fact (today always DEMITON)

Example: NAVMAN

projectText

The project the fuel was consumed on.

Example: BWG-2025-002

occurred_atDateYYYY-MM-DD

The usage date (month start for plant, transaction date for LV/HV)

Example: 2026-07-15

itemTextUnit: light_vehicle \

heavy_vehicle)

Example: diesel

litresDecimal numberUnit: litres

Fuel volume consumed/purchased.

Example: 185.4

claim_amount_audDecimal numberUnit: AUD

The final computed claim figure = litres × the claim month's price variance, never re-derived downstream.

Example: 342.1

Optional

Present when the source system records them.

financial_periodText

The claim month (YYYY-MM) the usage is attributed to.

assetText

The plant/vehicle the fuel belongs to.

Example: 9302

hoursDecimal numberUnit: hours

Machine hours the fuel is attributed to.

Example: 9.5

burn_rate_lphDecimal numberUnit: L/h

Derived litres per machine hour.

hours_sourceTextUnit: inferred \

Empty)

attribution_methodTextUnit: allocation_name \

navman_gps)

asset_labelText

The Assignar display label for a plant asset (or its split sub-label)

Example: Excavator 320 #2

regoText

Vehicle registration for LV/HV rows.

driver_nameText

The person who purchased the fuel on an LV/HV row.

alloc_daysNumberUnit: days

Allocation days attributed to a light-vehicle row.

km_from_projectNumberUnit: km

Distance from the project for a heavy-vehicle transaction, from 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.

plant_fuel_usage.example.json

{
  "asset": "9302",
  "asset_label": "Excavator 320 #2",
  "claim_amount_aud": 342.1,
  "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"
}

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.

Schema URL

https://docs.demiton.io/registers/plant_fuel_usage/v1.json

Show the full JSON Schema

Loading the schema…