Fuel transaction (v1)
Fuel transaction is one of Demiton's published registers for Australian civil construction. Individual fuel purchases and fills from fleet systems. 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
fuel_transactionUse this name to ask for the register. The API calls it a shelf ID.- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.1)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- 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.
None planned yet.
Fields
17 fields: 4 required, 13 optional.
Required
Every record carries these fields.
- assetText
The vehicle or plant the fuel was bought for.
- quantityDecimal number
The amount of product bought.
- source_systemText
Which bound system emitted the row.
- transacted_atDate and time
When the purchase happened.
Optional
Present when the source system records them.
- costMoney amount
What the purchase cost.
- driverText
The driver on the transaction.
- productText
The product bought, e.g. diesel.
- consumerText
What consumed the fuel: the vehicle itself or ancillary equipment.
- currencyText
The currency of the cost.
- odometerDecimal number
The odometer reading at purchase.
- supplierText
The fuel supplier or card provider.
- tax_paidTrue or false
Whether fuel tax was paid on the purchase.
- site_nameText
Where the fuel was bought.
- external_idText
The source system's own transaction id.
- quantity_unitText
The unit of the quantity, e.g. litre or kilogram.
- purchase_sourceText
Whether the fuel came from a retail site or bulk storage.
- transaction_typeText
A purchase, or a void that reverses one.
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/fuel_transaction/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.