Fleet is one of the most poorly managed cost centres in mid-size enterprises. Not because the fleet manager lacks data — if anything, they have too much — but because that data stays locked inside a Fleet Management System (FMS) that is never connected to the ERP. The result: finance rebuilds costs manually each month, fuel VAT is only partially recovered, assets are incorrectly depreciated, and the annual CO2 report eats up an extra week of work that could otherwise be avoided entirely.
This guide is written for the CFO or CIO of a company managing between 50 and 500 vehicles. It maps what needs to be connected, how to do it, and what measurable return you can expect.
Fleet and ERP: Two Systems That Rarely Talk
What the FMS Manages vs. What the ERP Manages
A Fleet Management System — such as Arval Business, Alphabet Fleet, or LeasePlan — is built around the operational life of the vehicle: ordering, delivery, fuel cards, mileage tracking, inspections, and end-of-contract return. The FMS knows everything about the physical life of the asset.
The ERP sees the fleet through a financial and balance-sheet lens: fixed asset or IFRS 16 right-of-use asset, monthly charges by cost centre, recoverable input tax, claims provisions. The ERP knows nothing about the physical life of the vehicle.
Both perspectives are essential. The problem is they rarely communicate in real time.
Five Daily Pain Points Without Integration
Fuel card re-entry: monthly statements from operators such as BP Fleet, DKV, UTA, or Fleetcor arrive as PDFs or CSVs. Someone manually re-enters them into the ERP, introducing errors along the way.
Partial fuel VAT recovery: without automation, the correct deductibility rate is not systematically applied per vehicle category. On a 150-vehicle fleet, the gap can represent tens of thousands in unrecovered input tax each year.
Incorrectly depreciated assets: a vehicle owned outright must be depreciated through the ERP fixed-assets module. A vehicle on a finance lease must appear on the balance sheet under IFRS 16 (mandatory for listed companies from 1 January 2019, increasingly adopted by subsidiaries reporting under IFRS). Without an automatic feed from the FMS, asset records are created late or incomplete.
CO2 reporting rebuilt from scratch each year: fleet emissions fall under Scope 1 (vehicles owned or controlled by the company) and Scope 3 Category 4 (business travel in vehicles not owned by the company) under CSRD. Manually collecting mileage and converting it to CO2 annually is time-consuming and produces inconsistencies year over year.
Unallocated repair invoices: a bodywork or tyre invoice arrives in accounts payable without a vehicle registration number. It is booked as a general expense. The true TCO per vehicle remains unknown.
The ERP Fixed-Asset Module: Managing Fleet as a Financial Asset
Creating Vehicle Records in the ERP
For each vehicle owned outright, the ERP needs a fixed-asset record with: registration plate, acquisition date, entry value, estimated residual value, and useful life. Standard practice is to depreciate passenger vehicles on a straight-line basis over five years (20% per year), subject to local tax rules and CO2-based caps that vary by jurisdiction and model year.
This record automates monthly depreciation charges and gives the finance team a live view of net book value at any point in the fleet lifecycle.
Operating Lease vs. Finance Lease (IFRS 16)
Before 2019, an operating lease stayed off balance sheet — lease payments were simply expensed. IFRS 16, effective 1 January 2019 for listed companies, changed this: any lease with a term exceeding 12 months and an underlying asset value above USD 5,000 must be recognised on the balance sheet.
In practice: a 36-month lease on a vehicle worth €30,000 generates a right-of-use asset and a lease liability in the ERP. The ERP must calculate the present value of future lease payments, then record the amortisation of the right-of-use asset separately from the interest charge on the lease liability.
Many mid-size companies have not yet correctly configured this treatment in their ERP. Auditing a fleet of 100 vehicles on long-term operating leases often uncovers several million euros of right-of-use assets missing from the balance sheet.
Vehicle Disposals
At return or sale, the ERP must close the asset record and book any gain or loss on disposal. Without an automatic feed from the FMS — which tracks the return date — this step is routinely missed, leaving “ghost assets” on the balance sheet for months.
Fuel Cards and Expense Claims: Closing the Accounting Loop
Automated Feeds from Fuel Operators
The main fuel card operators (BP Fleet, DKV, UTA, Fleetcor, and others) offer standardised exports: CSV, EDI, or — for more advanced integrations — REST APIs. Each transaction file contains: date, station, registration, volume, net amount, input tax, and fuel type (petrol, diesel, CNG, electric).
The ERP can ingest these feeds via a native connector (SAP Fleet Management, Dynamics 365 Expense, Odoo Fleet) or through a lightweight middleware. The outcome: each fuel transaction is automatically split by vehicle, charged to the correct cost centre, and processed with the right input-tax rate for that vehicle category.
Fuel Input Tax Recovery: The Parameterisation That Pays for Itself
Input tax deductibility on fuel varies by country, vehicle category, and fuel type. In most EU jurisdictions, commercial vehicles (light goods vehicles) are fully deductible, while passenger cars are partially or fully deductible depending on national rules. The key is to ensure the ERP applies the correct rate per vehicle category consistently — not a blanket default rate.
For a mixed fleet of 100 passenger vehicles spending an average of €150 per vehicle per month on fuel, even a 10-percentage-point difference in applied deductibility rate translates to more than €18,000 per year in unrecovered input tax. The automation pays for itself quickly.
Mileage Reimbursements
When employees use their own vehicles for business travel, the company reimburses them using a statutory mileage rate (the specific rate and engine-size brackets differ by country). The ERP or connected expense module applies the correct rate based on declared engine size and submitted mileage, then processes reimbursement either through payroll or a direct bank transfer. Electric vehicle mileage typically attracts a premium rate under most national schemes.
Maintenance and Claims: Getting Repair Costs Into the ERP
Work Orders and Maintenance Invoices
Preventive maintenance (oil changes, tyres, brake pads) is scheduled by the FMS based on mileage or time intervals. The invoice from the service provider needs to land in the ERP with the correct vehicle registration attached.
Two approaches, depending on system maturity:
- Native CMMS in the ERP: SAP PM, Infor EAM, or the Odoo maintenance module allow work orders to be created directly linked to the asset record. The supplier invoice is matched against the work order. Maintenance cost per vehicle is known to the cent.
- Delegation to the FMS: for fleets on full-service operating leases, the lessor often manages maintenance directly. In that case, only the consolidated monthly invoice passes through the ERP; per-vehicle detail stays in the FMS.
Claims: Accounting Treatment and Insurer Recovery
A claim generates several distinct accounting flows: repair cost, excess (a definitive charge), insurer reimbursement (income), and any potential third-party recovery (receivable). Without a workflow inside the ERP, these flows are managed manually and the open claims provision becomes impossible to calculate accurately.
Regulatory Compliance Tracking
The FMS manages alerts for MOT deadlines, scheduled services, and document renewals. These alerts can be exported to the ERP or a ticketing system to trigger purchase orders and prevent compliance failures.
Fleet CO2 Reporting in the ERP
The CSRD Framework for Fleet Emissions
For companies within scope of the Corporate Sustainability Reporting Directive (CSRD), fleet emissions must be reported under two categories:
- Scope 1: direct emissions from vehicles owned or controlled by the company (owned vehicles and finance leases).
- Scope 3 Category 4: emissions from business travel in vehicles not owned by the company (mileage reimbursements on private vehicles, taxis, short-term rentals).
The ERP is the only system that holds all the data needed: mileage from fuel cards, fuel type, mileage reimbursement transactions. The only additional input required is emission factors (grams of CO2 per litre or per kilometre by fuel type) to convert volumes into tonnes of CO2 equivalent.
Calculating Emissions from ERP Data
The standard method: for each fuel transaction, multiply volume consumed (in litres) by the emission factor for that fuel type. Well-established factors are published by national environmental agencies and the IPCC. As a reference, petrol produces approximately 2.28 kg CO2e per litre and diesel approximately 2.67 kg CO2e per litre (ADEME 2024 values, widely aligned with equivalent European databases). The ERP can automate this calculation and produce a monthly report by vehicle, by department, and by Scope.
According to the Arval Mobility Observatory 2026, 82% of companies surveyed are already committed to the energy transition of their passenger vehicle fleet or plan to act within three years, and 67% have already integrated electric or plug-in hybrid vehicles into their fleet. Accurate ERP/FMS integration is the prerequisite for calculating the real TCO of this transition — not the theoretical cost that leasing companies put in their proposals.
Thermal vs. Electric TCO Comparison
TCO (Total Cost of Ownership) is the only metric that matters for a thermal-versus-electric decision. It includes: lease payment or depreciation + fuel or electricity + maintenance + insurance + claims + parking, minus recovered input tax.
Without ERP integration, this calculation is done once a year in a spreadsheet using averages and vendor assumptions. With a correctly configured ERP, TCO per vehicle is available in real time, and the thermal-versus-electric comparison rests on actual company data rather than manufacturer hypotheses.
ERP/FMS Integration Architectures
Decision Framework
| Fleet size | Recommended architecture | Effort | Indicative cost |
|---|---|---|---|
| < 20 vehicles | Shared spreadsheet + manual entry | Low | Zero |
| 20 to 80 vehicles | Monthly CSV export from FMS + ERP import | Medium | €2,000–5,000 integration |
| 80 to 300 vehicles | API connector FMS → ERP (native or custom) | High | €10,000–30,000 |
| > 300 vehicles | iPaaS middleware (Boomi, MuleSoft) multi-FMS | Very high | €30,000–80,000 + maintenance |
Native Fleet Modules in Leading ERPs
SAP S/4HANA Fleet Management: PM (Plant Maintenance) module extended to vehicle assets. Asset records, work orders, fuel consumption, and CO2 reporting — all native in S/4HANA, no third-party connector required.
Microsoft Dynamics 365 Finance: fleet managed through Fixed Assets (for vehicle assets) and Expense Management (for fuel cards and mileage reimbursements). ISV connectors such as those offered by major fleet management software vendors are certified for Dynamics.
Odoo Fleet: native module, included in the Odoo subscription across all editions. Vehicle records, insurance contracts, mileage, maintenance alerts. Well-suited to fleets up to around 100 vehicles. The accounting functions (fixed-asset integration, IFRS 16) require expert configuration.
API Connection Between FMS and ERP
Major fleet management companies — Arval, Alphabet Fleet, LeasePlan, ALD Automotive (now Ayvens) — all offer REST APIs or enriched scheduled exports (JSON/CSV). These APIs provide real-time access to consumption data, mileage, maintenance alerts, and billing summaries. A typical integration development (on the ERP side) takes 15 to 40 days depending on the complexity of the accounting mapping.
iPaaS Middleware for Multi-Country Fleets
For groups managing fleets across multiple countries with local ERP instances, a middleware platform such as Boomi, MuleSoft, or Talend centralises the data flows: each local FMS feeds data to the integration platform, which normalises it and distributes it to the relevant ERP instances. This architecture makes sense above 300 vehicles or three distinct legal entities.
What ERP Integration Actually Delivers
ERP/FMS integration is not a comfort project. It is the prerequisite for managing the fleet as a financial asset rather than an opaque cost centre.
Measurable outcomes 12 months after integration:
- Fuel input tax correctly recovered on 100% of transactions (direct saving of tens of thousands per year depending on fleet size and national rules).
- Correct depreciation and IFRS 16 right-of-use assets on the balance sheet — audit-ready, no restatement required.
- Real TCO per vehicle available at any time to inform renewal decisions with actual data.
- Scope 1 and Scope 3.4 CO2 reporting automated, with consistent data year over year for the CSRD report.
- Faster month-end close: no more manual re-entry of fuel statements, maintenance invoices, or mileage expense claims.
The integration project itself typically pays back within 12 to 24 months for fleets of 50 to 200 vehicles, on fuel VAT recovery and reduction of manual processing time alone.
For related topics, see our complete guide to the ERP fixed-asset module (depreciation, disposals, inventory) and our transport and logistics ERP comparison for the distinction between in-house fleet management and TMS for external transport flows.
