2026-03-16
The first of a three-part series on freight audit. The five source documents every audit depends on, and how billing errors enter the chain.
Loading article...
Freight Audit Intelligence - 3-Part Series
Freight audit is the process of verifying carrier invoices against contractual rates and shipment records before payment is approved.
The need for it is more pervasive than most finance teams expect. Industry estimates suggest freight billing errors and overcharges can consume 3–10% of annual freight spend. For a company spending ₹100 crore annually on freight, that translates to ₹3–10 crore in potential overcharges. Most of it goes undetected and gets paid.
Every shipment produces a chain of documents - a Purchase Order, a Rate Card, a Bill of Lading, an e-Way Bill, a Proof of Delivery and each one captures a different piece of the operational record. A freight audit is the act of systematically comparing those documents against the carrier's invoice before any payment is released.
This article covers what that process looks like from first principles: the shipment lifecycle, the five source documents every audit depends on, and how billing errors enter the chain.
A shipment is not a single event, it is a sequence of ten handoffs, each owned by a different team, each producing at least one document. Understanding this sequence is the foundation of freight audit, because the evidence for every billing dispute originates somewhere within it.
Phase 1 - Operational: goods in motion
Phase 2 — Finance / AP: invoice to payment
The diagram below maps this full lifecycle. Freight audit sits at the boundary between the two phases — the point where the operational record meets the financial claim.
Shipment lifecycle flowchart: 10 verification checkpoints from purchase order to payment in a freight audit workflow.
Each box above marks where a document is created. The five that matter most for audit — PO, Rate Card, BOL, e-Way Bill, and POD — are all produced in Phase 1, before the invoice arrives.
By the time a freight invoice arrives, five source documents should already exist. Each one captures a different layer of the shipment record — and together they cover every dimension of what a carrier can legitimately charge.
| Document | What It Is | What Auditors Check Against It |
|---|---|---|
| Purchase Order (PO) | Raised by the buyer before the shipment. Defines what is being moved, agreed price, and delivery terms. | Does the invoice align with what was contracted in the PO? Are quantities and service levels correct? |
| Rate Card / Contract | The agreed freight rates between shipper and carrier for each lane — base rate, fuel surcharge formula, free detention time. | Is the billed rate the contracted rate? Has the carrier applied an expired or incorrect rate? |
| Bill of Lading (BOL) | Signed at pickup by both shipper and carrier. Confirms what was collected, from where, the weight, and origin timestamps. | Does the billed weight match the BOL? Do origin timestamps disprove detention charges? |
| e-Way Bill | Mandatory GST-compliance document for goods above ₹50,000 in India. Generated before transit begins. | Does the declared value and route match what was invoiced? Is the transit time consistent with the route? |
| Proof of Delivery (POD) | Signed by the consignee at the destination. Confirms delivery time, quantity received, and condition. | Do destination timestamps disprove detention charges? Was the invoice raised before delivery was confirmed? |
In practice, most AP teams verify one or two of these documents at most. A freight audit cross-references all five — against every line item on the invoice — before approval.
Think of a freight invoice as a claim. The carrier is asserting: we moved your goods, this is what we did, this is what you owe. A freight audit is the process of checking whether that claim holds up — not by reviewing invoices when something looks off, but systematically, for every invoice, before any payment leaves the account.
The formal industry term is Freight Audit and Payment — FAP. It is broader than error-catching. FAP covers the complete operational cycle from invoice receipt to payment clearance, running through four sequential stages.
The four stages of the Freight Audit and Payment (FAP) cycle
Invoice ingestion is where the process starts — and where most manual workflows first run into trouble. A freight invoice does not arrive as a clean, standardised record. Large national carriers send EDI X12 210 files. Registered Indian transporters issue GST e-Invoice JSON. Regional carriers send PDFs over email. Last-mile portals like Delhivery and Blue Dart export CSVs. Small transporters send a WhatsApp photograph of a handwritten bill. Before any audit logic can run, each invoice has to be extracted and normalised into a consistent structure. At volume, the variety of formats alone is enough to overwhelm any manual intake process.
Line-item verification is the core of the audit — matching each charge against what the operational record shows. Four checks run in parallel:
Of these four checks, accessorial legitimacy is where the most money is quietly lost. Verifying a base rate is binary — it either matches the rate card or it does not. Accessorial charges work differently. Detention, demurrage, liftgate fees, and peak surcharges are all calculated using the carrier's own systems, driver logs, and definitions of when the free-time window begins. The shipper has no visibility into any of that unless it pulls the source timestamps and runs the comparison itself. Gartner's FAP market research identifies accessorial fee auditing as the primary driver of cost recovery — precisely because base rates are locked in advance and increasingly transparent, while accessorial charges remain opaque and inconsistently applied. The detention overcharge example later in this article shows exactly how this plays out on a real invoice.
These are the error categories that line-item verification most commonly surfaces:
| Error Type | What Happens | Document That Exposes It |
|---|---|---|
| Inflated detention charges | Carrier measures dwell time from city gate arrival, not dock arrival | BOL + POD timestamps |
| Expired rate applied | Rate card was updated but carrier continues billing the old rate | Rate Card / Contract |
| Duplicate invoice | Same shipment billed from two carrier branches or in two billing cycles | Invoice history |
| Weight discrepancy | Carrier bills dimensional weight; BOL records actual weight | Bill of Lading |
| Invalid accessorial | Liftgate billed for a dock-to-dock delivery; residential surcharge on a commercial address | POD / delivery notes |
| Fuel surcharge error | Surcharge calculated against wrong index date or incorrect base rate | Rate Card formula |
| Invoice before delivery | Carrier raises invoice before POD is received or signed | Proof of Delivery |
| Route deviation | Carrier takes a longer route and bills the additional mileage without authorisation | e-Way Bill declared route |
No single error type dominates. In practice, accessorial inflation and expired rate carry-forward are the highest-frequency issues; weight and route disputes tend to be lower in frequency but larger per incident.
Dispute resolution is where findings become recoveries — and where most organisations fall short. Catching an error is step one. Getting the money back requires documentation, formal dispute submission, and consistent follow-through over a cycle that typically runs from 30 days to six months. Without a structured dispute workflow, audit findings stay as findings. They never become credit memos.
Payment and intelligence closes the loop. Approved invoices are released for payment. Every audited invoice also feeds a data layer — rates by lane, error rates by carrier, accessorial patterns by mode — that becomes the input for contract renegotiations and logistics cost benchmarking over time. The audit pays for itself twice: once in recovered overcharges, and again in better contracts the next renewal cycle.
Each of the four stages is manageable for a single invoice. At scale — hundreds of invoices per month, dozens of carriers, multiple modes — executing all four manually with any consistency becomes unrealistic.
But the harder obstacle is not volume. It is fragmentation. The five source documents an audit depends on do not live in a single system. The PO sits in an ERP. The Rate Card is buried in a contract folder or an email thread. The BOL arrives as a PDF attachment. The e-Way Bill lives on the GST portal. The POD may be a paper scan, a carrier portal entry, or a photograph from the dock. Each is siloed — and connecting all five, for every invoice, before the carrier's dispute window closes, is where freight audit breaks down in practice. Most teams are not failing at the audit. They are failing at the assembly.
The following simulation shows how a single detention error passes through a standard AP workflow undetected — and what the documents reveal when they are actually checked.
The setup. ABC Manufacturing ships a truckload from Mumbai to Delhi with FastFreight Logistics. The contract allows 2 hours of free loading/unloading time at both origin and destination. After that, a detention charge of ₹75 per hour applies. This is standard.
What the invoice says. When the carrier's invoice arrives, it includes:
| Charge | Billed |
|---|---|
| Base freight (820 kg × ₹18.50) | ₹15,170 |
| Fuel surcharge (8.5%) | ₹1,289 |
| Detention at origin (2.5 hrs × ₹75) | ₹187.50 |
| Detention at destination (3.0 hrs × ₹75) | ₹225 |
| Total | ₹16,871.95 |
The detention charges look unremarkable. Most AP teams would approve this invoice without question.
What the documents show. The Bill of Lading records that the driver arrived at origin at 09:15 and departed at 10:45 — exactly 1 hour 30 minutes. The Proof of Delivery shows the driver arrived at the destination at 14:30 and departed at 16:00 — again, 1 hour 30 minutes. Both are inside the 2-hour free time window.
Neither detention charge is valid. The carrier's driver log system recorded dwell time from city gate arrival rather than dock arrival, inflating the time spent at each facility. The ₹412.50 in detention charges should never have appeared on the invoice.
The impact. ₹412.50 is 2.4% of this invoice. On 500 invoices per month at this scale, that compounds to over ₹2 lakh per month in uncaptured overcharges. Across a full freight program, these discrepancies can add up to 5–10% of annual freight spend if they are not caught before payment. Without the BOL and POD timestamps, this would have been paid without question, and the carrier would have continued billing this way on every subsequent shipment.
Freight errors are rarely one-off mistakes. They are structural, built into how carrier billing systems record dwell time, how driver logs are timestamped, and how AP workflows are designed to process volume, not to investigate it. The only reliable fix is to check every invoice against every document, every time.
In Part 2 of this series, we dive into the complete taxonomy of freight invoice errors — from detention and demurrage overcharges to dimensional discrepancies and expired rates — across every freight mode: motor, parcel, ocean, air, and rail.
Cubesite is built for this fragmented reality. It ingests documents from ERPs, TMS systems, email attachments, carrier portals, and paper scans — and connects them automatically before the audit runs. If you move freight at scale and want to see what your current billing error rate looks like against your actual source documents, book a demo with the Cubesite team.
Cubesite