Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Freight Audit in Your ERP: How to Check, Match and Recover Carrier Invoice Errors (2026 Guide)

How your ERP can audit carrier invoices: 7 typical errors, 3-way match, month-end accruals, EDI/API, build vs buy and a 90-day rollout plan.

Freight Audit in Your ERP: How to Check, Match and Recover Carrier Invoice Errors (2026 Guide)

A mid-sized company shipping several thousand parcels or pallets a month receives hundreds of carrier invoices, sometimes tens of thousands of lines. Almost nobody reads them line by line. Accounts payable checks the total, the logistics manager “knows” the carrier is roughly right, and the invoice is paid. That is exactly where the discrepancies hide: inflated chargeable weight, a misapplied surcharge, a duplicate, a delivery billed but never made.

This guide is for CFOs and logistics leaders who want to treat a carrier invoice like any other supplier invoice in the ERP: with matching, tolerances, exceptions and a month-end accrual. It does not revisit TMS selection, which we cover in our guide to ERP, WMS, TMS and demand planning. Here we stay on the procure-to-pay side of transport.

Why Freight Invoices Escape Control

Three factors compound.

Volume. A parcel or LTL invoice carries one line per shipment, often several lines per shipment (base rate, fuel, accessorials). No manual check scales to that. Control becomes sampling, or nothing at all.

Pricing complexity. The price of a shipment depends on a rate card (zone, weight band, service level), a chargeable-weight method, surcharges (fuel, energy, peak season, remote area) and accessorials (tail-lift, delivery appointment, floor delivery, pallet exchange). These rules live in PDF contracts and rate annexes that the ERP knows nothing about.

Siloed teams. Logistics knows the shipments, accounting knows the invoices, procurement knows the contract. Nobody owns the end-to-end match. In a standard procure-to-pay flow, 3-way match exists for goods purchases. For freight, it is rarely configured.

The result: transport is often the largest indirect spend category in the supply chain, and one of the least controlled.

The 7 Typical Discrepancies and How to Detect Them

These are the errors that show up repeatedly in carrier invoice audits, with the rule an ERP or a freight audit tool can apply.

DiscrepancyWhat happensDetection rule
Chargeable vs actual weightThe carrier bills a dimensional or scanned weight higher than what was shippedRecalculate chargeable weight from the dimensions and weight recorded in the ERP, apply the contractual rule (conversion factor, rounding) and compare
Wrong zone or weight bandWrong rate zone or postcode, hence a higher priceReplay the calculation from the delivery postcode and the versioned rate card
Fuel surchargeApplied rate differs from the contractual index for the monthCompare the invoiced rate with the indexation table, month by month
Unjustified accessorialsTail-lift, appointment, waiting time or pallet return billed with no matching requestRequire every accessorial to be linked to a transport instruction or a recorded customer requirement
DuplicatesSame shipment billed twice, or invoice reissued after a credit noteUnique key (carrier, waybill or tracking number, date) and a uniqueness check at entry
Undelivered shipmentShipment billed although refused, lost or returnedCross-check with delivery status (tracking, proof of delivery) before payment
Taxes and VATVAT misapplied, or an undue tax or duty on an export or intra-EU flowCheck the rate and the legal mention by origin and destination country, and by Incoterm

Fuel surcharges deserve particular attention. Most road freight contracts index the fuel component to a published diesel index (in France, the CNR indices; in the UK and elsewhere, the equivalent national or carrier-published indices). A surcharge rate that does not follow the contractual index is an easy discrepancy to catch, provided the index is master data in the ERP and not someone’s personal spreadsheet.

For guaranteed services, some large parcel integrators offer a refund when delivery is late, but only on the customer’s request and within a short claim window. Without systematic tracking, those credits are never claimed. Check the exact terms of each contract: they vary by carrier and by country.

Example tolerance rule. “If an invoiced line exceeds the recalculated amount by more than 2% or €3 (whichever is higher), the line goes to exception; below that, it is paid and the variance is logged for follow-up.” The thresholds are an example to adjust to your volume and risk appetite, not a standard.

Matching Architecture in the ERP

The principle is a 3-way match adapted to freight: you match the transport order (or shipping instruction), the shipment actually carried out (delivery note, proof of delivery, tracking status) and the carrier’s invoice.

The target flow:

  1. Transport order: created automatically from the sales order or stock transfer, with the carrier, service and terms selected.
  2. Shipment and delivery note: the WMS or logistics module confirms dispatch, with weight, packaging, dimensions and date.
  3. Expected price: the ERP computes the theoretical cost from the rate card.
  4. Invoice: received by EDI, API, file or OCR, then matched line by line.
  5. Decision: compliant line, paid; out-of-tolerance line, sent to exception; line with no matching shipment, blocked.

The Carrier Rate Card as Versioned Master Data

The weak point of most projects is the rate card. For the expected price to be reliable, it must be ERP master data, just like a purchase price:

  • one rate card per carrier, service and validity period, versioned: you never delete a card, you create a new one with an effective date;
  • chargeable-weight rules (volume-to-weight conversion factor, rounding, minimum weight);
  • the monthly fuel indexation table;
  • the accessorials catalogue and its tariff;
  • a link to the signed contract, so that a dispute points to the right document.

Without versioning, you cannot check a March invoice against April rates. This data has an owner: the transport buyer, who updates it at each amendment or annual review.

Tolerances and Exception Workflow

Matching without tolerances produces too many exceptions and ends up ignored. Define:

  • thresholds by carrier and line type (tighter on fuel, looser on accessorials);
  • an exception queue assigned to a named person, with a coded reason (weight, zone, duplicate, accessorial, fuel, delivery);
  • a payment rule: pay the undisputed part, block the disputed part;
  • a claims loop: the discrepancy leads to a credit note request to the carrier, tracked until the credit note is received and applied.

Tracking through to the credit note is what turns a control into real recovery. Many teams detect discrepancies but never chase them.

Month-End Accruals: Delivered but Not Yet Invoiced Freight

Freight is invoiced with a lag: a shipment delivered on the 29th may be invoiced the following month. If you do not accrue, the transport cost lands in the wrong period and margin per order is distorted.

In the ERP, the freight accrual works like this:

  • list the shipments delivered in the period with no matched invoice;
  • value each at the expected price from the rate card (a second use of the versioned rate card);
  • post an accrued expense (goods received not invoiced), automatically reversed when the next period opens;
  • when the invoice arrives, match it and measure the variance between accrual and actual invoice.

That variance is a useful indicator: if the accrual is systematically lower than the invoice, your rate card or accessorial rules are incomplete. For annual closings, this mechanism ties in with accruals and year-end closing entries.

EDI/API Integration of Carrier Files and E-Invoicing

Matching only works if the data reaches the ERP cleanly. Three routes coexist:

  • EDI (invoice and status messages): suited to high volumes and to carriers that offer it; stable, but heavy to set up.
  • API and detailed files: large parcel and LTL carriers often provide a detailed billing file, line by line, richer than the PDF. It is this file, not the PDF, that you should match.
  • PDF and OCR: a last resort for small carriers, with a higher risk of misreads.

The choice between EDI and API follows the same logic as for other partner flows, detailed in our EDI vs REST API decision guide. The practical test: can the carrier provide, with every invoice, a structured file containing the shipment number, the billed weight, the zone and each surcharge?

On e-invoicing, a carrier is a supplier like any other. Across Europe, B2B e-invoicing mandates (France’s reform, Peppol-based regimes in Belgium and elsewhere, and the EU’s ViDA initiative) are progressively making structured invoice receipt the norm. That improves the quality of the data you receive, but it does not replace matching: a compliant e-invoice can still be wrong on substance. Check that your receiving platform passes the detail lines to the ERP, not just the header.

Build vs Specialist Tool: Which Option by Volume

OptionPrincipleStrengthsLimitsWhen to consider it
ERP module (build / configuration)Rate card, matching and exceptions inside the ERPData and accounting already integrated, no extra licence costConfiguration effort, rate card maintenance, few claims toolsModerate volume, few carriers, ERP already well mastered
TMS (with freight audit module)Cost computed at planning time, checked at invoiceConsistency between planned and billed price, better carrier selectionBroader project, licence and integration costMultimodal flows, many carriers, TMS already in place or planned
Third-party freight audit serviceA provider audits, disputes and recoversFast start, expertise in each carrier’s rules, chasing done for youFees often tied to recovered amounts, dependency, data sharingHigh parcel volume, few internal resources, need for quick results

Recommendation by volume (orders of magnitude, to adapt):

  • Under a few thousand shipments a month and 2 to 3 carriers: start with the ERP module, with the rate cards of your two main carriers and the three most frequent discrepancies.
  • Intermediate volume, several carriers: ERP plus TMS, or ERP plus a third-party service in parallel for a quarter to measure what the third party finds that you do not.
  • High parcel volume, heavy exposure to accessorials and surcharges: a specialist service or a TMS with native audit pays off fairly quickly, because the internal development cost exceeds that of the tool.

In every case, keep the accounting in the ERP: the external tool detects, the ERP pays, accrues and allocates.

Incoterms and Customer Re-Invoicing

Two links that are too often forgotten:

  • Incoterms: depending on the sale’s Incoterm, freight is for your account or the customer’s. A carrier invoice on an EXW or FCA sale, for example, should not weigh on your margin: it must be re-invoiced or rejected. The match therefore needs to know the order’s Incoterm.
  • Customer re-invoicing: when freight is re-invoiced at cost or at a flat rate, the validated carrier invoice feeds the re-invoicing. An undetected discrepancy lands either on your margin or on the customer, with a dispute risk.

Business Case: How to Calculate the Gain

We do not quote an average over-billing rate: the figures in circulation often come from freight audit vendors and depend heavily on sector and carrier mix. Calculate your own, with a simple method:

  1. Pull a sample: three months of invoices from one or two main carriers.
  2. Recalculate each line with the contractual rate card.
  3. Classify the discrepancies into the 7 categories above and sum them.
  4. Divide the total by the invoiced amount in the sample to get your discrepancy rate.
  5. Apply that rate to annual volume, removing the share you will not be able to dispute (expired claim windows, missing evidence).

Net gain is that amount minus the implementation cost (configuration, licences or third-party fees) and the time spent handling exceptions. This sample calculation takes a few days and is worth more than any industry average when convincing a finance director.

KPIs to track:

  • discrepancy rate: detected discrepancies over invoiced amount;
  • % recovered: credit notes obtained over disputed discrepancies;
  • freight cost per order (or per parcel, or per pallet);
  • exception handling time;
  • variance between month-end accrual and actual invoice.

90-Day Rollout Plan

Days 1 to 30: scope and measure

  • Pick 1 to 2 carriers representing the largest share of volume.
  • Collect contracts, rate cards, amendments and fuel tables.
  • Run the sample audit and quantify the business case.
  • Name the owner of the rate data and the owner of the exception queue.

Days 31 to 60: configure

  • Create the versioned rate cards and chargeable-weight rules in the ERP.
  • Set up structured invoice receipt (detailed file, EDI or API).
  • Configure matching, tolerances and exception reasons.
  • Set up the month-end accrual on delivered, uninvoiced shipments.

Days 61 to 90: operate and extend

  • Go live on the pilot carriers, with systematic chasing of credit notes.
  • Measure the KPIs and compare them to the business case.
  • Decide on extension (other carriers) or on a specialist tool.

Launch checklist

  • Rate cards entered, versioned and linked to contracts
  • Reliable weight, dimensions and packaging at dispatch
  • Monthly fuel indexation table
  • Unique anti-duplicate key at invoice entry
  • Delivery status available before payment
  • Tolerances approved by finance and logistics
  • Exception queue with an owner and known claim deadlines
  • Freight accrual automated and reversed
  • Order Incoterm accessible to the match
  • KPIs published every month

Going Further

Freight invoice control is a special case of supplier matching. To structure your approach, download our ERP checklist and evaluation grid and read our guide to procure-to-pay in the ERP. If you want to scope a pilot on your own carrier invoices, contact DigitsLane.