Rebuilding the year in a spreadsheet
Year end comes, and each client's payroll team or accountant asks for company car data. Your team rebuilds the year: which cars each driver had, from when to when, the list price with options, CO2 figures, fuel type, whether fuel was provided for private use, capital contributions and any periods the car was unavailable. Drivers swapped cars mid-year, some had a temporary car during a repair, and a few left.
The fleet system has the current picture, not the history. So the team pieces it together from delivery notes, emails and old reports.
Why car benefit data is hard to produce
The data needed is simple in principle, but it changes through the year and is rarely captured when it changes.
- Car changes, temporary replacements and gaps are not recorded with exact dates.
- List price with options is on the order, not in the fleet system.
- CO2 figures differ by specification and are sometimes entered wrongly.
- Driver contributions are agreed with the client's HR and not shared.
- Each client's payroll team or accountant wants the data in a different layout.
What a year-end scramble costs
Days of team time at the busiest point of the client's year. Data that is incomplete or wrong, which the client's payroll team then has to correct. Late submissions to the client. And clients who reasonably expect their fleet manager to have this at their fingertips.
The benefit data record we build
- When a car is ordered, its list price with options, CO2, fuel type and registration are captured from the order and the leasing company's data.
- Every allocation change is recorded with exact dates: new car, swap, temporary replacement, return, driver leaving.
- Driver contributions and private fuel arrangements are recorded as the client's HR team confirms them, through a simple form.
- The record is checked monthly for gaps, overlaps and missing facts, and questions go to your team or the client while they are recent.
- At year end, each client's dataset is produced in the layout their payroll team or accountant wants, with every period and value listed.
- In-year changes can also be sent to the client's payroll as they happen, if the client handles benefits through payroll.
| Fact | Captured when | Source |
|---|---|---|
| List price and options | Order placed | Order and leasing company data |
| CO2 and fuel type | Order and delivery | Vehicle specification |
| Driver and dates | Every allocation change | Your team, recorded at the time |
| Contributions and private fuel | Agreed with the client | Client HR form |
The data, not the tax calculation
We do not calculate tax or advise on benefit in kind. The client's payroll team or accountant does that, using the rules that apply. What we provide is the underlying data, complete and checked, with every period and value traceable to where it came from. If something is uncertain, it is flagged for the client rather than guessed.
Year end without the rebuild
Consider a driver who had one car until the summer, a courtesy car for ten days while it was repaired, and then a new electric car. Under the old process, that year is a puzzle in December. With the record, each change was captured with its date when it happened, the new car's list price and CO2 came from its order, and the driver's contribution was confirmed by the client's HR team in the autumn. At year end the three periods are simply listed.
The dataset for each client builds itself through the year from changes recorded at the time. At year end, your team reviews and sends it rather than reconstructing it. Clients' payroll teams get what they need in the layout they asked for. And when a driver or HMRC asks about a particular period, the record answers.
Is year end a rebuild every time?
- Company car data for P11D returns is rebuilt every year.
- Car swaps and temporary cars are not recorded with dates.
- List prices with options have to be found from old orders.
- Driver contributions are held by the client's HR, not you.
- Each client's payroll team wants a different format.