Fuel Tax Credits and OBM data from a single OBx device.
OneRoad OBx turns your trucks into ATO Fuel Tax Credit–ready and TCA-aligned OBM data sources – capturing engine, GPS, mass and route information in one platform so you can prove where you drove, how heavy you were and how the vehicle was used.
Transport Certification Australia telematics & OBM framework
ATO Fuel Tax Credit record-keeping requirements
The same record can support FTC calculations, mass management, PBS evidence and Chain of Responsibility investigations.
OBx: engine-grade data for FTC, OBM and NHVAS in one place.
Instead of running separate systems for Fuel Tax Credits, OBM and fatigue, OBx turns each truck into a single, trusted data source. Engine, GPS, mass and driver activity all feed the OneRoad platform – so your FTC claims, OBM records and NHVAS evidence share the same timeline.
- OBx plugs into heavy-vehicle harnesses and continuously logs engine and movement data.
- High-resolution GPS traces show where the vehicle drove, for how long and at what speed.
- Connections to supported OBM / scale systems add axle-group and gross mass readings.
- All data is logged against a unique vehicle ID and configuration in OneRoad.
- FTC data: engine state, GPS and duty cycles designed to meet ATO record-keeping expectations.
- OBM data: mass readings and margins relative to limits for PBS, HML and permit routes.
- NHVAS evidence: trips, mass and driver work/rest aligned to your accreditation modules.
- CoR investigations: “what happened, when and where?” answered from a single source of truth.
OBx is the data engine; OneRoad is the surface your finance, operations and compliance teams work in.
What OBx unlocks for Fuel Tax Credits and OBM.
Capture the information your tax advisor actually needs.
- Engine on/off, moving/idling and auxiliary states.
- GPS traces to distinguish public road vs off-road activity.
- Time-stamped events designed for Class Ruling–style approaches.
- Quarterly exports your accountant can plug into their model.
Know how heavy you are before, during and after loading.
- Live views for loaders and supervisors in the yard.
- Colour-coded margins to group and gross limits.
- Snapshots at “load complete” time for each trip.
- Mass history by vehicle, route, contract and depot.
Prepare now for current and future TCA programs.
- Device IDs and vehicle mapping structured for TCA-style schemas.
- Data models built to support Type 2 OBM pathways.
- JSON / CSV outputs that can plug into TCA ecosystems.
- Reduce future re-work when approvals and schemes evolve.
Bring finance, operations and compliance onto the same page.
- Finance sees FTC reports backed by traceable trip data.
- Compliance sees mass and route data for NHVAS and PBS.
- Operations sees live risk and performance indicators.
- Everyone works from one set of OBx records.
Drivers stay in the OneRoad app they already know.
- Mass summaries and warnings surfaced in the driver view.
- No extra logins, tablets or training modules.
- Drivers can see what finance and compliance will see later.
- Supports coaching around speed, loading and idling behaviour.
Start where the risk and opportunity is highest.
- Roll OBx and OBM out to PBS or high-value combinations first.
- Prove FTC and OBM data flows with your advisors.
- Add more vehicles, depots and routes when you’re ready.
- Same platform – more data, not more systems.
OBx is the bridge between your trucks, scales and data.
OBx is installed once per vehicle and becomes the anchor point for all your compliance data. It’s designed to connect to supported OBM and onboard scale systems while feeding the OneRoad platform with engine and GPS data for FTC.
- Heavy-vehicle harnesses and adapter kits cover major Australian truck types.
- OBx devices are labelled and mapped to registrations and configurations in OneRoad.
- Connections to supported OBM / scale solutions bring axle-group and gross mass into the stream.
- All events are time-stamped and geo-referenced for FTC, OBM and NHVAS use cases.
The exact integration path depends on your current OBM provider, hardware and route approvals – we’ll work through this with you as part of your rollout plan.
- ✔ Target PBS combinations, HML routes and FTC-heavy work first.
- ✔ Validate outputs with your tax advisor and compliance team.
- ✔ Standardise installation and changeover processes in your workshops.
- ✔ Expand to more vehicles and contracts once everyone trusts the data.
From loading a truck to lodging FTC claims.
OBx and OBM are designed around the way fleets actually work – quick load turns, busy depots, and end-of-quarter pressure on finance and compliance teams.
The loader uses a OneRoad view showing axle-groups and gross mass as OBM readings stream in through OBx. When everything is in the green, loading is marked complete and a snapshot is saved for that trip.
Drivers continue using the OneRoad app for EWD and journeys. OBx logs engine state, GPS and mass along the way – separating public road running from off-road and auxiliary activity in the data model.
At quarter-end, finance exports FTC-ready data while compliance exports mass and NHVAS evidence – both drawing from the same OBx records. Advisors can trace every number back to trips, vehicles and dates.
- ✔ Separate public road, off-road and auxiliary usage in your data – not just your spreadsheets.
- ✔ Give your tax advisor structured engine, GPS and usage records rather than raw logs.
- ✔ Reduce the manual work needed to build and defend your FTC methodology.
- ✔ Align your approach with ATO record-keeping expectations and future Class Ruling opportunities.
Final FTC positions remain a tax decision for you and your advisors. OBx focuses on the quality and structure of the underlying data so those decisions are easier to justify.
Manual FTC & weighbridges vs OBx-powered FTC & OBM.
Spreadsheets + weighbridges + paper
- ✔ FTC estimates built from fuel purchases and rough usage assumptions.
- ✔ Mass data scattered across dockets, emails and stand-alone OBM screens.
- ✔ Limited ability to replay what actually happened on a given day or lane.
- ✔ High manual effort at quarter-end and during audits.
- ✔ Hard to scale across multiple depots and contractors.
OBx + OBM integrated with OneRoad
- ✔ Engine, GPS and mass data structured to support FTC and OBM together.
- ✔ FTC, mass and NHVAS evidence all draw from the same OBx records.
- ✔ Replay trips by route, weight, driver and vehicle in seconds.
- ✔ Less time building reports, more time managing risk and performance.
- ✔ Built to align with ATO and TCA frameworks as they evolve.
Common questions about OBx, FTC and OBM.
Do I need OBx hardware to use these FTC and OBM features?
Yes. FTC and OBM features in OneRoad rely on OBx as the trusted data source in each vehicle. OBx provides the time, location and usage context that makes your FTC and OBM records defensible.
Is OBx already TCA Type-approved and covered by an ATO Class Ruling?
OBx and the OneRoad data model are being designed to align with TCA telematics/OBM frameworks and to support future Type-approval and Class Ruling processes. Until formal approvals are granted, you should rely on your existing regulatory arrangements and obtain advice from your tax and compliance advisors.
Can I start with OBx for FTC only and add OBM later?
Yes. Many fleets begin by using OBx for FTC and tracking, then connect supported OBM / scale systems once they’re comfortable with the data and reports. The platform stays the same – you simply turn on additional streams when you’re ready.
Which OBM and onboard scale systems will OBx support?
OneRoad is being built to integrate with selected OBM and scale providers. The exact list depends on your hardware and the TCA / road manager environment. Share your current setup with us and we’ll map out integration options.
How is pricing structured for OBx with FTC and OBM?
Pricing is typically based on an OBx subscription per vehicle, plus any additional OBM integration and support required. We’ll help design a staged rollout and pricing model around your fleet size, FTC opportunity and compliance obligations.