What is contracted transport auditing?
Companies that offer charter transport to employees pay for a service that happens out of sight of the buyer: before dawn, on dozens of routes, with the carrier's vehicles and drivers. In most operations, the only source on what happened is the supplier's own report.
Contracted transport auditing is the practice of checking that service against your own reference. It answers simple questions that today often go unanswered:
- Did the 5:40 trip on Line 07 leave on time?
- Did the bus follow the agreed route or take a shortcut?
- How many people boarded, and at which stops?
- Does the mileage billed match the mileage driven?
- Were the extra trips on the invoice authorized?
Auditing does not presume bad faith. It exists because transport contracts have many variables and because differences happen for legitimate reasons: roadwork, authorized detours, vehicle swaps, equipment failure. What changes with auditing is that every difference gets an explanation and a record.
Why the trip is the unit of auditing
Charter spreadsheets usually separate information that should go together: the route is in one file, the passenger list in another, the contract in a PDF and the carrier's report in a fourth format. That makes it hard to answer any question without assembling the puzzle.
In Merus Tracker, each trip brings together everything known about it:
| Layer | What it contains | Where it comes from |
|---|---|---|
| Planning | Route, stops, schedules, vehicle, capacity | Routing and operation setup |
| People | Assigned employees, shifts, sites | HR and employee records |
| Execution | GPS positions, stop passages, observed times | Integrated telemetry or Merus equipment |
| Boardings | Who boarded, where and when | Validators and boarding flows |
| Contract | Billing rules, tolerances, amounts | Contract with the carrier |
| Supplier record | Trips and kilometers reported | Carrier reports or integrations |
With these layers on the same trip, auditing stops being a manual investigation and becomes a query.
What data is needed to audit charter transport?
There is no single package. The diagnosis of each operation defines what is needed and feasible. In general, auditing relies on four groups of data:
- Planned reference: routes, stops, planned departure and arrival times, vehicle and capacity.
- Independent measurement: GPS positions and virtual fence crossings. They can come from the tracker the carrier already uses, through native integration, or from telemetry sold and installed by Merus.
- Service delivered: boardings recorded per passenger, when the operation uses boarding validation.
- Rules and billing: contract clauses and the records the carrier presents at closing.
The Merus team loads this data together with the company's team during implementation and stays involved until the system is 100% functional.
How auditing works, step by step
1. Define what was contracted
Before comparing, you need to know what to compare. Merus organizes routes, schedules, fleet and contract rules as the reference. This step often reveals old inconsistencies, such as routes that changed in practice and were never updated in the contract.
2. Measure execution independently
During operation, position, time and boarding events are tied to the corresponding trip. This is the independent measurement: your own reading of execution, which does not depend only on the supplier's version.
3. Compare planned with actual
Each trip is compared with its reference: did it leave on time? Did it pass through the stops? Did it complete the route? Did it serve the expected passengers? The guide to planned versus actual details this comparison.
4. Investigate the differences
A discrepancy is the start of the analysis, not the conclusion. The team consults the history, incidents and justifications before classifying the case: service problem, authorized change, source failure or incomplete data.
5. Reconcile with the invoice
At closing, measured trips and kilometers are placed side by side with what the carrier charges. The operational reconciliation shows the differences trip by trip, so the company can review them before paying.
6. Record the decision
Each analysis is recorded with the reason, the responsible party and the date. This history is what gives confidence when renegotiating the contract or answering an internal audit.
The most common problems auditing finds
Without promising results, because every operation is different, these are the types of difference auditing usually makes visible:
- Recurring delays at certain times or on certain lines, which only show up when you look at the history.
- Route deviations, authorized or not, that change the mileage.
- Incomplete trips, when the vehicle does not pass through all planned stops.
- Trips not completed or made with a vehicle different from the one contracted.
- Extra trips charged without a recorded authorization.
- Mismatched occupancy with the vehicle: large buses with few passengers or overcrowded vehicles.
What auditing is not
For auditing to work, the limits must be clear:
- It is not automatic invoice approval. Merus shows the evidence; the company decides.
- It is not automatic punishment. A missing record does not prove missing service. Inconclusive cases stay open for analysis.
- It does not replace the contract. Tolerance rules, fines and deductions are those of the signed contract.
- It does not turn Merus into a carrier. Vehicles, drivers and execution remain with the contracted supplier. According to the contract, the Merus team can operate the platform for the company: routing, monitoring and checking.
Who takes part in auditing inside the company
| Area | What it gains |
|---|---|
| Facilities and operations | Daily view of execution and same-day handling of incidents |
| Procurement and contracts | Evidence base to check billing and renegotiate |
| Finance | Invoice checked before payment |
| HR | Service and punctuality data that affect employees |
| Compliance and internal audit | Traceable history of decisions |
How to get started
The starting point is a diagnosis of the operation: sites, shifts, routes, contract and the data sources that already exist. From there, the Merus team defines equipment or integrations, loads the data, validates the flow with the people who will use it and stays involved until everything is working. There is no single timeline: it depends on the size of the operation and the integrations needed.
If the company is still choosing a tool, see the criteria in how to choose charter transport management software.
The planned reference comes from the route; see how to build routes from addresses and shifts.
