A calm FBT season: organising the annual fringe benefits workflow
Build a repeatable FBT season workflow from data collection to lodgement, with client chasing and review handled so the deadline stops being a scramble.
Every year the FBT season arrives at the same time, and every year it seems to catch a few practices off guard. The 31 March fringe benefits year ends, the lodgement deadline looms, and suddenly the team is emailing clients for car logbooks and credit card statements they should have asked for weeks ago. The good news is that FBT is one of the most predictable obligations on the calendar. With a repeatable process, you can turn the annual panic into a steady, calm run.
This guide sets out an FBT season workflow that moves from data collection through review to lodgement, with the client chasing and partner sign-off built in rather than bolted on at the end.
Start with a clean FBT client list
The first job is knowing exactly which clients are in scope. Not every client provides fringe benefits, and you do not want to chase the ones who do not. Before the year ends on 31 March, build your list of FBT-liable clients: those who provide cars, pay for entertainment, offer car parking, make loans to employees, or cover expenses on behalf of staff.
In Finye you can tag or group these clients and treat FBT as a recurring obligation. Because the FBT year and the lodgement window repeat every year, this is exactly the kind of work that suits templated recurring jobs. Set up an FBT project template once and let it auto-generate the job for each in-scope client at the right time, so nobody has to remember to start the file manually.
It is worth confirming scope each year rather than assuming last year's list still holds. A client who bought their first work ute, started salary packaging, or held a staff Christmas function may have crossed into FBT territory for the first time.
Make data collection a structured request, not an email thread
Most of the pain in FBT season is data collection. You need logbooks, odometer readings at 31 March, declarations, novated lease statements, entertainment records, and details of any expense payment or loan benefits. Chasing these by email creates long threads where it is impossible to see what has arrived and what is still outstanding.
A document and PBC request handles this far better. Send each client a structured list of the FBT records you need, and let them upload directly through the client portal. You get a clear, item-by-item view of what is in and what is missing, and the client gets one tidy place to respond instead of a scattered inbox. For benefits that need a signed declaration, such as the reduction for otherwise deductible expenses, you can attach the form to the same request.
A few practical inclusions for the request list:
- Motor vehicles — purchase or lease details, opening and closing odometer readings, and logbooks where the operating cost method applies.
- Entertainment — records of meals, functions and events, with attendee splits between staff and clients.
- Expense payments and reimbursements — credit card statements and details of anything paid on an employee's behalf.
- Loans and debt waivers — balances, interest rates and any amounts forgiven.
- Car parking and housing — where these benefits are provided.
Chase systematically so nothing drifts
The difference between a calm season and a frantic one is usually how the chasing is handled. Left to memory, follow-ups happen unevenly and the slow responders get away with it until late March. The fix is to make every FBT client a tracked work item with an owner and a due date.
In Finye, each FBT engagement can sit on a board with a clear status workflow: requested, partially received, complete, in preparation, in review and lodged. A quick look at the board tells you who is holding things up and where the bottlenecks are. Because the records arrive through the portal against a structured request, the status updates as items come in rather than relying on someone to mentally track twenty separate email chains.
For early reminders, a short, friendly nudge well before the deadline almost always beats a stressed phone call in the final week. Reminders that go out on a predictable cadence train clients to respond on time, and the staff and individual contacts attached to each client record keep the right person in the loop.
Build review into the workflow, not the last hour
FBT calculations carry real risk. Choosing the statutory formula over operating cost, getting the entertainment apportionment wrong, or missing a reportable fringe benefits amount on an employee's payment summary can all create problems. Review should be a deliberate stage in the workflow, not something squeezed in once the return is already half lodged.
Move each file into an in review status once the preparer is done, and assign it to the reviewing accountant or principal. Comments, checklists and subtasks on the work item keep the review trail in one place: confirm the calculation method for each car, check the minor benefits exemption has been applied correctly, verify gross-up rates, and reconcile reportable amounts back to payroll. Because the working papers and source documents are attached to the same item, the reviewer is not hunting across folders to check the numbers.
Where you have an engagement letter covering the FBT work, having it signed and on file before lodgement keeps the scope clear and protects the practice. Engagement letters and e-signing live alongside the rest of the client record, so the agreement and the work sit together.
Lodge, record, and set up next year
With data complete, calculations done and review signed off, lodgement is the easy part. Move the work item to lodged, record the lodgement date, and where the work is billable, draft the invoice straight from the time and WIP captured against the job. Tracking time as you go means the FBT fee reflects the actual effort rather than a rushed estimate.
The final, easily skipped step is to set up next year while the detail is fresh. Note which clients were slow, which records were hardest to get, and whether any client moved in or out of scope. Feed that back into your recurring FBT template so next season starts from an even cleaner base. The compliance dashboard keeps the FBT obligation visible alongside BAS, IAS and income tax deadlines, so the whole lodgement calendar sits in one view rather than scattered across spreadsheets.
FBT does not have to be the obligation that ruins April. A clear in-scope list, structured data requests, systematic chasing and a built-in review stage turn it into a predictable run you repeat every year. If you would like to see how Finye brings recurring jobs, document requests, the client portal and a compliance dashboard together, start a free trial or take a look at our plans to find the right fit for your practice.