Fuel transaction
Individual fuel purchases and fills from fleet systems.
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.- Each record is
- An eventSomething that happened at a point in time.
- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1Current version.
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.
- source_systemText
Which bound system emitted the row.
- assetText
The vehicle or plant the fuel was bought for.
- transacted_atDate and time
When the purchase happened.
- quantityDecimal number
The amount of product bought.
Optional
Present when the source system records them.
- quantity_unitText
The unit of the quantity, e.g. litre or kilogram.
- external_idText
The source system's own transaction id.
- transaction_typeText
A purchase, or a void that reverses one.
- productText
The product bought, e.g. diesel.
- costMoney amount
What the purchase cost.
- currencyText
The currency of the cost.
- tax_paidTrue or false
Whether fuel tax was paid on the purchase.
- consumerText
What consumed the fuel: the vehicle itself or ancillary equipment.
- purchase_sourceText
Whether the fuel came from a retail site or bulk storage.
- driverText
The driver on the transaction.
- supplierText
The fuel supplier or card provider.
- site_nameText
Where the fuel was bought.
- odometerDecimal number
The odometer reading at purchase.
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 keep current from them, on your data, in a 30-minute call.