From telematics
A completed trip becomes a journey with start and end times, odometer readings, distance and the route. The driver is notified and classifies it with a swipe in the app.
Deriving logbook data from bookings does not survive an audit. Bookings record intent, journeys record what happened. Vectis keeps purpose-built journey records built around IRD and ATO logbook rules, then assesses each vehicle under every method available to you and recommends the cheaper one.
418 telematics · 194 manual
Weighted by distance
km in period
Clears at 0 unclassified
Telematics journeys arrive with distance, route and times already filled in. The driver supplies the classification and, for business trips, the purpose.
Whichever path a journey takes, it lands in the same record with the same audit fields: who recorded it, when, and from what source.
A completed trip becomes a journey with start and end times, odometer readings, distance and the route. The driver is notified and classifies it with a swipe in the app.
For vehicles without a device, the driver starts and stops the journey on their phone, with GPS tracking in the background and breaks recorded along the way.
Retrospective entry with odometer continuity checks, and bulk classification for catch-up periods.
Manual (all entries by hand), confirm only (telematics creates the journey, the driver classifies it) or fully automatic (geofence zones classify it, drivers confirm the uncertain ones).
Business zones such as depots, offices and client sites classify as business; a driver's home zone classifies as home-to-work. A journey matching only one zone is queued for the driver, and one matching none stays unclassified until a person decides.
Vectis runs each applicable method for every vehicle in the FBT year and recommends the one with the lowest taxable value. You keep the choice, and the record of why it was made.
No logbook required. Simple to administer and defend. Usually best when private use is above 50%.
Requires a validated logbook period. Costs include fuel, repairs, maintenance, registration, insurance, tolls, plus deemed depreciation and imputed interest on owned vehicles, or lease payments. Can save materially above 70% business use.
Requires proven business kilometres for the period. Available to New Zealand organisations.
The same boundary in New Zealand and Australia. Periods, assessments and reports roll on it.
The period must be representative. Vectis warns when business use moves more than 10% from the previous period, which is when a new logbook is needed.
Recorded per vehicle per year and deducted inside each method, so the comparison stays honest rather than being adjusted afterwards in a spreadsheet.
The reason logbooks fail is that they ask drivers to do bookkeeping. Vectis asks the driver a single question at the end of a trip and does the rest behind them.
Classify journeys, add a purpose for business trips, review their own history.
Create periods, review entries, validate the period, run assessments.
View assessments, run reports, record employee contributions and select the method.
See logbook entries and compliance status for their own pools.
Set the FBT jurisdiction, automation mode and permissions.
Business use 81.4% from a validated 90-day period. The statutory method would give $7,120 on a $35,600 cost base.
Summary, by vehicle, by driver and by booking: method, cost base, days available, business use, contributions and the resulting value.
Which vehicles hold a valid period, which are short, which have unclassified journeys, and how long remains to fix them.
The journey-level export an auditor asks for: date, times, odometer, distance, classification, purpose, driver and source.
Bring one vehicle's costs and three months of trips. We will show you each method, side by side.