Choose your 12-week FBT period

The logbook method rests on one decision: which continuous twelve weeks your business-use percentage is based on. Get it right and the number stands up. Get it wrong — a flattering fortnight of site runs, a stretch where tracking dropped out — and it's the figure your accountant or the ATO queries first.

Axlerun turns that into a choice with evidence behind it. You don't set a period up front; you pick a window, check its numbers, and the period record is created when you actually export a document from it.

The flow, end to end

Open Settings → Reports → FBT Logbook.

1. Pick the vehicle and FBT year. You can go back five years, because that's how long one logbook stays valid.

2. Choose a window. Axlerun scans the year and ranks the twelve-week candidates. Each row answers four things and stops: which window it is, what it's worth, what odometer readings it rests on, and how far the vehicle went. Nothing is saved when you tap one — it's a read-only list.

3. Review the numbers. This is where the detail lives: days with driving, estimated entries, adjusted trips and a completeness score, sitting next to the two controls that move them.

4. Export. Opening this step runs a dry run — it shows the consent summary, the record count and every reconciled row that will be in the file, and saves nothing. The document is produced when you download or email it.

The two controls on the review step

The odometer pair is the denominator of the percentage above it. Correct a reading and watch the figure move — the numbers dim and update in place rather than disappearing behind a loading state, because the whole point is seeing what your correction did.

Continuous or raw switches which percentage is the headline. It costs nothing to flip: both figures are already calculated, so it only changes which one leads.

Why the number on the row is the number in the file

The candidate list shows one percentage, not two — the reconciled figure, which is what the exported document actually states. Showing the raw figure beside it would only raise the question of which one is real.

The same principle governs the trips. They're listed on the export step, not earlier, because what's listed there is the export's own reconciled row set — the literal contents of the file. In the old flow the trips were shown a screen sooner as raw logbook entries, which meant the list you approved wasn't the list you received.

What's holding an export up

Axlerun names the specific reasons a logbook isn't ready, worst first, and most rows take you straight to the fix:

• Period too short — the window doesn't reach twelve weeks.
• Business trips with no purpose — the most common blocker by a distance. It leads to a bulk-fix screen where you clear the whole set in one pass instead of opening trips one at a time.
• Large odometer variance — recorded kilometres and the odometer delta disagree, usually because tracking dropped out for part of the window.
• Sparse activity — the window contains days with no driving at all. This one can't be fixed after the fact; it's information for judging whether the window is worth using.

Unclassified trips and business trips missing a purpose are counted separately, because they're different jobs on different screens.

Periods you've already exported from

Windows you've produced a document from are kept, along with the file itself, so you can hand over the same document again later.

Past logbook periods and re-sending an export

Export your ATO logbook