How to Build a Vehicle Service History Your Accountant Will Thank You For

Published · Last updated

Nobody gets excited about service records. But I'd put good ones near the top of the list of boring things that quietly save a small business money, and the person who benefits most is usually your accountant.

I'll explain why, then show you how I'd set it up so it takes minutes, not hours.

Why your accountant cares about your service history

When your accountant sits down to do your year-end, every repair and service bill needs to land in the right place. Which van was it for? Was it a routine service or a bigger repair? What was the date? Was it paid by the company or by you personally?

If the answers are scattered across a glovebox of crumpled receipts, a WhatsApp thread with your mechanic, and your own memory, your accountant has two options: chase you for the details (which costs you billable time) or make their best guess (which is how mistakes creep into accounts).

A proper service history answers all of that before they've even asked.

The records limited companies are expected to keep

If you run your van fleet through a limited company, GOV.UK is clear that you must keep financial and accounting records for six years from the end of the last company financial year they relate to. Vehicle repair and servicing costs are normally part of that picture, because they're business expenses that need supporting evidence behind them.

I'm not an accountant, and the detail of what's allowable (and how repairs are treated compared with bigger improvements) is something your accountant should confirm for your situation. But the practical point is simple: if a cost went through the company, you should be able to show what it was, which vehicle it was for, and when it happened.

What each service entry should capture

Whatever system you use, every entry needs the same handful of details:

  • Which vehicle (the registration, not "the white van")
  • The date the work was done
  • What was done, in plain English ("front brake pads and discs," not just "repair")
  • The cost, split between parts and labour if the invoice shows it
  • Who did it, meaning the garage or mechanic
  • The mileage at the time
  • A copy of the invoice or receipt, attached to the entry rather than living in a separate pile

That last one is the bit that makes the difference. A cost with no proof behind it is the one your accountant ends up chasing.

Three habits that keep it tidy

1. Log it the same day. Not at the end of the month, and definitely not at the end of the year. By then, nobody remembers which van needed which tyres.

2. One record per vehicle, not one big list for the whole fleet. When something goes wrong with a specific van, or when you sell it, you want that van's full history in one place without picking through everyone else's.

3. Keep the paper trail attached to the entry. A photo of the invoice, taken on your phone at the garage counter, is far better than a promise to find it later.

The side benefit nobody mentions

A clean service history isn't only for tax. It also helps when you come to sell a van, because a documented history is something buyers will genuinely pay more for. It helps if there's ever a dispute after an accident, because you can show the vehicle was properly maintained. And it helps you spot patterns, such as the van that's eaten three sets of brake pads in a year, which might mean something else is wrong.

How I set it up in FleetGuv

I built the maintenance log in FleetGuv around exactly this problem. Each vehicle has its own log, work due and work done sit together, and the costs are captured as you go. At the end of the year there's a CSV export formatted for Xero and QuickBooks, so your accountant gets the figures in a layout they can import rather than retype.

You don't need software to start, though. A simple spreadsheet with one tab per van and the columns above beats a pile of receipts every time. The point is to do it consistently, and to do it in one place.


Written by Chris, Founder of FleetGuv. I built the maintenance log because I was tired of hunting for invoices every time year-end came round, and I'd rather you didn't have to.

Related reading: