2026-10-18 · Cost Audit

How Should a Shanghai Company Audit Corporate Vehicle Costs? Mileage Checks, Exception Flags and a Closing Loop

Most companies negotiate the rate and rarely look back at whether a given trip should have happened. The result is odd: the rate falls a little each year while total spend barely moves, because the leakage is not in the price but in the quantity and the basis. The same route reports two different distances, an eight-hour day is settled as ten, a vehicle appears in a residential district on a Sunday, and one journey shows up on both the provider invoice and an employee claim. None of it is large on its own, and together it is enough to unpick a budget. An audit is not a hunt for culprits; it is the practice of making whether a trip happened as agreed into something checkable. The four records that matter are the request, the dispatch note, the journey record and the invoice, and the gaps between them are where an audit begins.

1. What an Audit Is Preventing

Q1: Which kinds of leakage should a cost audit target?

In corporate transport auditing, three patterns dominate. Quantity inflation: mileage reported above the distance travelled, hours rounded up into the next band, waiting time counted twice, and cross-city trips billed as a return journey when only one leg ran. Purpose creep: private errands inserted into a business itinerary, such as collecting family on the way, weekend use, or regular passengers who are not company staff. Duplicate billing: the same journey appearing on both the provider invoice and an employee expense claim, or tolls and parking billed separately when the package already includes them. What these share is that each item is small, frequent and invisible to spot checks, so an audit cannot rely on impressions. It relies on whether four records agree: how many people the request named, how many days the dispatch note covers, how many kilometres the journey record shows, and what the invoice charges. Disagreement between them is the entry point.

Q2: Which records does an audit need?

Four sets, and missing any one leaves a blind spot. Demand side: the request, with requester, department, purpose, headcount, origin and destination, time window and grade. Delivery side: the dispatch note and journey record, with plate, driver, actual departure and arrival, and odometer or tracking data. Cost side: the invoice and settlement statement, with the billing basis, rate and add-ons such as waiting, overtime, tolls, parking and cross-city legs. Internal side: the transport ledger and employee expense claims, which is where duplicates surface. The granularity has to line up at trip level. If the provider only supplies a monthly total, the audit can compare aggregates but cannot locate a specific journey, so the contract should require trip-level statements with supporting time and distance records. Agreeing that at signature is far more effective than asking for data afterwards.

2. Which Records, and How to Test Them

Q3: How are mileage and hours tested in practice?

Mileage in three steps. First, is the baseline sensible: what is the ordinary route distance between the two points, how much deviation is normal, and beyond what point does it need an explanation; river crossings, district detours and roadworks are reasonable but should map to a specific stretch. Second, is the same route stable: drivers on a regular route should report very similar distances, and a line that consistently drifts deserves a closer look. Third, are there extremes: a single day far above comparable trips, or distance that does not fit the time, such as two hundred kilometres in two hours. Hours work the same way. Establish how the billing band is defined, whether per hour, half day or full day; check that actual departure and finish times are supported by a record; and confirm that waiting time matches the itinerary. The audit does not need to recompute every trip to the yuan, but it must make exceptions visible through thresholds run monthly rather than manual reading.

Q4: How should private use and unusual trips be identified?

Look at four dimensions. Time: late-night, weekend and public-holiday trips, and whether a request and purpose exist; a fixed daily slot over consecutive days with no clear business content also merits a look. Route: origins or destinations in residential areas, schools, shopping centres or hospitals that do not match the stated purpose. People: headcount differing from the request, or non-staff passengers travelling regularly. Documents: the same trip settled twice, add-ons overlapping a package, or the invoicing entity differing from the contracting party. None of these proves misconduct. Collecting a client family member or taking staff home after a late shift can be entirely legitimate. The right response is to flag and ask for an explanation, recorded and filed, rather than to conclude. Holding that line is what keeps business units willing to cooperate, and an audit that nobody cooperates with finds nothing.

3. Frequency, Sampling and Closure

Q5: What audit frequency and sampling rate are realistic?

Three layers work well for corporate vehicle spend. Monthly reconciliation across everything: every invoice matched to the ledger, with totals, trip counts and invoice counts agreeing, which does not require detail but must prove nothing is missing or duplicated. Quarterly sampling: take the departments with the highest volume, the highest-value trips and any new provider, and test mileage, hours and add-ons, starting at around ten per cent and widening where problems appear. Triggered review: an exception flag, a report from staff, a change of provider or a sharp month-on-month rise in one department justifies a targeted look. Together the layers keep cost manageable: full reconciliation prevents omission, sampling provides deterrence, and triggers stop a local problem from spreading. Frequency matters less than consistency; a fixed quarterly exercise beats an annual scramble.

Q6: How should findings be closed out?

Closure has four steps. Confirm the facts by putting documents, records and the business unit explanation into a one-page finding that states the amount, the cause and where the process failed, without characterising people. Categorise the response: a provider billing error is corrected under the contract and offset in the next settlement; an internal gap is fixed in the process, not just on that trip, for example by adding headcount and passengers to the request form and requiring actual mileage on the dispatch note; individual conduct is handled under company policy and kept out of the finding. Then take it to the provider: put repeated issues into the quarterly review and apply the contract where they continue. Finally review prevention twice a year, because a problem that keeps recurring usually means the rule needs changing. Keep the record, and align it with what internal audit and a tax review would expect, following your finance lead and the local tax authority.