When a company has two cars, "fleet management" is an Excel file and whatever the bookkeeper remembers. When it has ten, that same Excel starts costing three days of work a month and the occasional fine for a missed inspection. That's the moment to stop and think about it differently.
Fleet is rarely a priority in an SME. Cars run, invoices get booked, and if someone's insurance is about to lapse — usually someone spots it in time. Until they don't. Then suddenly nobody knows who drove which car in April, why a salesperson's fuel card is buying diesel when the car runs on petrol, and why three routes in last quarter's travel expenses overlap. On top of that come audits from the tax office and the annual personal income tax adjustment for private use of company vehicles.
Good news: this is a problem that integration mostly solves. Bad news: every vendor (GPS, fuel cards, insurer, workshop) has their own portal, their own reports, and their own export format. They need to be tidied up.
What actually hurts in a 15-person firm with 12 cars
Before picking tools, it's worth writing down on paper what specifically costs time. At one of our clients — a 22-person HVAC service company with 14 cars — the bookkeeper spent about three working days each month on "closing the fleet": manually keying in 340 lines from bundled fuel invoices, reconciling them against the mileage log, calculating the personal income tax adjustment for private use for seven salespeople, and checking that nobody had tanked up on the company's dime over the weekend.
Three days a month times twelve months is nearly two months of a bookkeeper's job. Add two incidents a year where a car went out without a valid inspection — one fine, one breakdown on the road with a PLN 1,800 tow bill. These costs rarely show up on the "ROI of a fleet management system" slide, and yet they're what the real figure is made of.
Three layers that need to talk to each other
Fleet management in an SME is, in practice, three layers of data that live separately and need to start communicating.
- Vehicle technical layer — inspection date, insurance validity, tire condition, service history, mileage. Usually in an Excel file kept by whoever handles admin.
- Usage layer — who drove, when, where, how many kilometers. From GPS (if any) or from a manual driver log. Plus the split between private and business trips.
- Cost layer — fuel from the fleet card, car washes, parking, toll charges (viaTOLL/e-TOLL), repairs, leasing. Scattered across several vendors, each with a separate bundled invoice.
Goal of integration: for any car and any month, be able to answer in a minute — who drove it, how much fuel it burned, what the repairs cost, when the next inspection is, how much tax to book for private use.
GPS — when it's worth it and when it's wasted money
GPS in fleets up to 20 cars makes sense when the company delivers services in the field (service, construction, transport) or when salespeople visit clients and need to log routes. It doesn't make sense when a car sits in the office car park 90% of the time and only leaves for meetings.
The realistic cost is around PLN 35–60 per vehicle per month (Webfleet, Auto Plaza, Autowizja and similar — each supports an API integration into ERP). In return you get an accurate kilometer log (needed for the private-use tax calculation), automatic reports of arrivals at client sites (feeding the service invoice), and alerts on "unusual" routes.
The classic mistake is buying GPS "because you're supposed to" and not using a single one of its reports. If the bookkeeper still manually types in the odometer reading from the fuel receipt — GPS pays back at zero.
Fuel cards — one source, one export
A company with 10 cars usually has 10 fuel cards from a single operator (Orlen Flota, Circle K Routex, BP Plus, Shell Card). That's good — one bundled invoice a month, one portal, one export format. It gets unpleasant when there are three ("because there are more Orlens on the road than BPs") — then every month means three separate reconciliations.
Practical recommendation: one operator, all cards assigned to specific plates (not drivers), a monthly CSV/XML export imported directly into the accounting module. In Comarch Optima, enova365 or Subiekt GT this is a straightforward mapping — a one-off integration usually takes 6–12 developer hours.
Result: 340 fuel lines get booked in 20 minutes instead of a day and a half. That difference is precisely what adds up to two months of a bookkeeper's salary per year.
Servicing, insurance, and inspections — a calendar, not an Excel
An Excel of inspection dates stops working the moment the person handling admin changes (which happens on average every 2–3 years). Workshop contacts, repair history and scheduled inspections should live in one place with email alerts 30, 14, and 3 days before the deadline.
Three approaches tend to work in practice:
- a simple Airtable/SharePoint base with Power Automate reminders (cost ~PLN 100/month, one day to set up),
- a "fixed assets" module in the ERP extended with fleet-specific fields,
- a dedicated fleet management system (Fleet Complete, Autowizja Flota) — reasonable from 15–20 cars upwards.
Which one to pick depends on how many cars you have and whether accounting already runs an ERP where a module can be added comfortably. There is no single right answer. There is, however, one wrong one: "we'll keep an eye on it in Excel and nobody will forget anything".
Tax on private use — where the numbers most often don't add up
The flat rate for private use of a company car is PLN 250 (up to 1600cc) or PLN 400 (above) per month, added to the employee's income. Sounds simple, until it turns out that in April the salesperson had a loaner of a different engine size, in May they were on holiday and the car sat still, and in June they lent it to a colleague for two weeks.
Without a "who drove what, and when" log, every such mistake is a potential tax correction and a possible tax office letter. With a log (even a simple one, as a table with electronic signatures), the whole thing closes in 15 minutes at month end. Introducing that log is the "boring change" worth making before buying any system at all.
Where to start in your company
A simple three-month path to walk on your own or with a consultant:
- List every car (plate, model, engine size, ownership — leased or owned, permanent driver or "pool").
- Pick one place to keep the deadlines: inspections, insurance, tire changes. Turn on alerts.
- Consolidate fuel cards to a single operator (if you have several).
- Integrate the fuel card export with the accounting module.
- Only now decide whether GPS is worth it — based on how much salespeople actually drive.
Order matters. Buying GPS on day one, before getting the calendar and the bookkeeping under control, is a classic implementation trap. Foundations first, electronics later.
If you'd like to see what such an integration would concretely look like in your business — half an hour of conversation is usually enough to spot where the biggest hole is and what should be tackled first.
Fleet management is not a "let's buy GPS" project. It is a "let's stop booking fuel by hand" project.