A coach operator with 60 vehicles does not sell kilometres. It sells availability: a legally fit driver and an inspected vehicle, in the right place, at 6:40 in the morning, for a school contract whose price was set three years ago and indexed by a formula nobody rereads. When one of those three links fails (a driver over their driving-time limit, a coach off the road, a fuel index never applied), the margin on the route disappears without any screen ever flagging it.
That is why owners and finance directors in passenger transport quickly hit the limits of accounting software backed by planning spreadsheets. This guide maps the specific needs of the trade, the families of solutions available, and how to choose according to fleet size. It does not rank vendors exhaustively: the market moves fast, and the right choice depends on your activity mix.
Why passenger transport is not freight transport
Many readers arrive from a freight TMS project and instinctively transpose it. Our comparison of transport and logistics solutions covers freight forwarding, route planning and carrier invoice audit: a world where the unit of management is the shipment. In passenger transport, the unit of management is the service: a route, a school run, a transfer, a trip.
Contracts, public service obligations and tenders
A large share of a regional coach operator’s revenue rests on long-term contracts with public authorities: school services, scheduled lines under public service contracts, demand-responsive transport. These contracts have three direct consequences for the ERP:
- Contractual invoicing: a flat fee per route, a price per kilometre, a daily minimum, with different rules for each contracting authority.
- Delivery tracking: days actually run, cancelled services (strikes, bad weather, school closures), possible penalties.
- Documents to produce: delivery statements, monthly summaries, evidence for public tenders.
A general-purpose ERP can issue a recurring invoice. It rarely reconciles that invoice with the service actually delivered, day by day and route by route.
Seasonality
Activity follows the school calendar, the tourist high season and event peaks. In July the fleet goes out on tours and transfers. In September the return to school ties up most vehicles on fixed timetables. The system therefore has to handle two logics at once: recurring, predictable schedules (school, scheduled lines) and one-off missions priced by quote (private hire, tourism). Deciding whether a vehicle goes to a profitable quote or to a route already sold is the daily call that creates or destroys margin.
What about taxis and private hire?
Taxis and private hire vehicles (PHV, or “VTC” in France) run on a different model: smaller fleets, light vehicles, individual fares, and for some taxis a large share of contracted medical transport (billed to a health insurer or public body). Compliance centres on driver licences, operator permits and insurance rather than on EU driving-time rules. Real-time dispatch needs are close to those of booking tools. Beyond about twenty vehicles, the issues of cost price, maintenance and payroll converge with those of coach operators, and the logic of this guide applies.
Driver and vehicle scheduling
Driving and rest times: EU Regulation 561/2006
Regulation (EC) No 561/2006 governs driving times for vehicles carrying more than nine persons including the driver. Its rules shape schedules directly:
- daily driving limited to 9 hours, extendable to 10 hours twice a week;
- a maximum of 56 hours of driving per week and 90 hours over two consecutive weeks;
- a break of at least 45 minutes after 4.5 hours of driving (which can be split into 15 then 30 minutes);
- a daily rest of 11 hours, reducible to 9 hours three times between two weekly rests.
The text excludes regular services on routes of 50 km or less: these fall under national rules, which means the applicable regime must be configured per service, not per driver. The same driver may work a school run outside the regulation and an airport transfer inside it in the same week.
What an ERP must concretely do: project cumulative driving and rest at the moment of assignment, and refuse or warn before the mission is confirmed, not afterwards. A spreadsheet schedule checked after the fact against tachograph files detects the infringement once it has been committed.
Assignment and replacements
The real difficulty is not the ideal September schedule but the 7:15 replacement: a driver off sick, a coach broken down, three routes affected. The criteria for choosing a replacement are multiple: legal availability, licences and qualifications (Driver CPC, child transport requirements where relevant), proximity to the depot, cost (overtime, premiums). A useful solution exposes these criteria in an assignment screen rather than offering a simple drag-and-drop calendar.
Tachograph, scheduling and payroll: the chain to connect
The digital tachograph records driver and vehicle activity. The downloaded data feeds three processes that many companies treat separately:
- Regulatory control: analysis of infringements, archiving of files within the required deadlines.
- Scheduling: comparison of planned against actual.
- Payroll: driving hours, spread of duty, service time, allowances, premiums, under the applicable collective agreement.
If these three flows do not share the same time base, payroll re-keys what scheduling has already calculated, and discrepancies are settled at month end. At selection stage, ask to see a real case: a driver file imported, compared with the schedule, then turned into payroll variables. Our guide on timesheets and project cost billing details this single-entry logic, which transposes to driver hours.
Contracts, quotes and invoicing
Scheduled, school and private-hire services
Three product families coexist, with three invoicing logics:
| Activity | Invoice trigger | ERP point of attention |
|---|---|---|
| Scheduled service / public contract | Monthly, per contract | Delivery tracking, penalties, evidence |
| School | Monthly or quarterly, per route | School calendar, cancelled services, price indexation |
| Private hire / tourism | By quote, deposit then balance | Costing per vehicle, actual mileage, extras |
The private-hire quote deserves particular attention: it must rest on the actual cost price of the vehicle and driver (see below), not on a per-kilometre rate frozen in a file. Charter contracts with travel agencies often add deposits, cancellations and re-invoicing of tolls or parking.
Fuel price indexation
Transport contracts must provide for price revision as costs change. Most countries publish cost indices for road passenger transport (in France, the CNR publishes dedicated indices covering professional diesel, school transport, maintenance, driver and overhead components) that serve as indexation references. Good practice on the ERP side:
- store the revision formula per contract (fixed share, fuel share, wage share);
- import the index every month rather than re-keying it;
- automatically generate the adjustment invoice or the revised unit price.
Many companies lose margin not because of a missing formula but because revision is only applied when the customer asks or during an audit. An ERP that calculates the revision at every billing period removes this risk.
Cost price per vehicle and per route
This is the subject that financially justifies the project. A coach operator generally knows how much it invoices. It knows less well what a specific route or a given vehicle really costs. The analysis requires allocating four cost blocks:
- Fuel: actual consumption per vehicle, fed by fuel cards and tank readings, not by a fleet average.
- Maintenance: workshop labour, parts, tyres, downtime for breakdowns, reported per vehicle and per kilometre.
- Depreciation or lease: a 2015 coach and a 2024 coach do not have the same cost of ownership, which is what makes uniform pricing misleading.
- Payroll: drivers assigned to the service, with employer costs, overtime, waiting time and set-up time.
The expected result is an operating account per route and per contract, reconciled with invoiced revenue (indexation included). The first financial years regularly reveal an unexpected result: a small school route with tight timetables, tying up a vehicle and a driver for two rotations a day, loses money, while a poorly priced tourist mission consumes margin without anyone noticing. To go further on cost allocation mechanics, our article on ERP for engineering firms explains how to link time spent, costs and billing per project, a logic directly reusable here (the route plays the role of the project).
Fleet maintenance and regulatory inspections
A vehicle off the road costs twice: the repair, and the service not delivered. Maintenance must therefore be integrated into scheduling, not managed in a parallel tool. The expected functions:
- Maintenance plan per vehicle: by mileage, calendar or engine hours, with work order generation.
- Regulatory inspections: roadworthiness tests, tachograph and speed limiter, safety equipment, with due-date alerts, because a coach with an expired certificate cannot leave the depot.
- Workshop slots integrated into the schedule: a vehicle in service must disappear from availability before assignment, not after.
- Cost history per vehicle, which feeds the replacement decision.
The logic resembles that of equipment rental, where availability depends on maintenance: see our equipment rental ERP comparison for how the availability engine and periodic checks work.
Solution families: adapted general ERP, industry software, ERP plus specialist tool
Three approaches coexist. Rather than naming a winner, here is how to position them.
| Criterion | Adapted general ERP | Passenger transport industry software | ERP + specialist tool (scheduling / TMS) |
|---|---|---|---|
| Driver scheduling and driving times | To develop or integrate | Native | Native in the specialist tool |
| School contracts and price indexation | Heavy configuration | Often native | Depends on the tool |
| Accounting, purchasing, fixed assets | Native and solid | Sometimes limited | Native in the ERP |
| Cost price per route | Possible via analytical accounting | Variable | Good if flows are synchronised |
| E-invoicing | Native or via certified platform | To check with the vendor | Depends on the architecture |
| Main risk | Development debt | Lock-in, weak accounting | Interfaces to maintain |
| Suitable profile | Multi-activity groups, strong finance | Single-activity fleet, fast need | Mid to large fleet, demanding management |
Adapted general ERP: you start from a business management ERP (solutions such as Odoo or Business Central are regularly considered by SMEs) and add trade-specific features through configuration or development. Advantage: solid accounting, purchasing and analytics. Risk: turning the ERP into a development project to fill the scheduling gap, which remains the heart of the business.
Industry software: designed for passenger carriers, it covers scheduling, tachograph, quotes and contract tracking. It suits fleets whose main challenge is operations. Check accounting depth and the openness of interfaces: that is where projects stall.
ERP + specialist tool: the ERP carries finance, purchasing, analytics and fixed assets; the specialist tool carries scheduling and telematics, with synchronised flows (contracts, actual hours, costs). It is the most complete architecture, and the most demanding in data governance.
Recommendation by fleet size and selection checklist
20 to 50 vehicles: prioritise industry software or a light ERP, with reliable driver scheduling and a clean payroll link. A complex ERP would be disproportionate.
50 to 150 vehicles: analytics per route becomes central. The choice lies between industry software with a good accounting bridge, and an ERP paired with a scheduling tool.
150 to 300 vehicles, or a multi-activity group (coach, taxi, medical transport, rental): the ERP + specialist tool architecture is generally the most coherent, because consolidation, intercompany and e-invoicing become subjects in their own right.
Selection checklist
- Does the schedule refuse (or warn about) an assignment that exceeds driving and rest limits?
- Can the regulatory regime be configured per service?
- Do tachograph files feed control, actuals and payroll?
- Is the price revision formula stored per contract, with monthly index import?
- Is the operating account per route and per vehicle produced without reprocessing?
- Does the maintenance plan block the availability of a vehicle that is off the road?
- Do the fleet’s regulatory inspections generate due-date alerts?
- Is e-invoicing covered (see below)?
- Are the interfaces (accounting, payroll, telematics, fuel cards) documented APIs?
- Does the five-year total cost include interfaces and custom development?
Accounting integration and e-invoicing
For operators in France, the national calendar requires all companies to be able to receive electronic invoices from 1 September 2026, with issuing mandatory from 1 September 2027 for SMEs and micro-businesses (September 2026 for large companies and mid-caps). Other EU countries are following their own timetables. For a passenger carrier that often invoices public authorities, this is a concrete issue: public customers already receive their invoices electronically. Check that the ERP or industry software produces structured formats (Factur-X, UBL, CII), connects to a certified platform and handles e-reporting for trips invoiced to individuals. The control point: the export to accounting must keep the analytical dimension per route, otherwise you lose at invoicing what you built at scheduling.
5 common implementation mistakes
- Starting with accounting and postponing scheduling. The project delivers a clean ERP, and dispatchers carry on with their spreadsheets.
- Neglecting the contract master data. Revision formulas, calendars and minimums are entered in a hurry, then never maintained.
- Not linking the tachograph to payroll. Payroll re-keys the hours, and discrepancies are argued over every month.
- Underestimating fleet data migration. Without maintenance and cost history per vehicle, analytics start empty for a year.
- Forgetting replacements and extras. Seasonal staff, subcontractors and agency drivers are missing from the model, and the schedule no longer reflects reality at peak times.
Going further
To structure your approach, download our ERP evaluation scorecard: a set of weighted criteria to compare three solutions side by side. And if cost price is your priority, read our article on timesheets and project cost price.