What should a freight audit check before an invoice reaches payment?

The freight invoice adds up. The lorry receipt, or LR, matches a completed trip. Yet accounts payable cannot explain why the carrier used the new lane rate or charged three hours of waiting. Approving the invoice because its total looks reasonable turns an unresolved commercial question into a payment decision.

A freight audit should establish which shipment was billed, which rule governs each charge, what evidence supports the service and whether the calculation follows that rule. These checks have different owners. Bringing them together makes approval easier to explain without asking finance to reconstruct every trip.

Establish the shipment before examining the price

Match the supplier and shipment references before applying a rate. An invoice number can identify a document without identifying all the work it covers. One bill might consolidate several LRs; one LR might also appear on an original invoice and its replacement.

Keep the invoice identity, supplier account, LR or consignment reference, trip leg and customer or cost-centre allocation together. Where a carrier group invoices through another legal entity, use an approved relationship rather than a name similarity.

Oracle's match-rule documentation provides a product example: it uses service-provider and reference-number criteria to connect invoices with shipments. Those matching criteria establish a relationship; the commercial review still needs the governing charge rules. Oracle Transportation Management 26C — Match Rule.

Separate the four questions behind a charge

A useful review moves through four questions:

An empty field should not become a zero charge or an automatic rejection. It may mean the evidence has not arrived, the charge is outside the agreed rule, or the record cannot be matched. Those outcomes need different actions.

Work through a bill line by line

Consider this illustrative example, before any applicable tax. The fictional agreement permits ₹12,000 base freight, ₹1,000 supported waiting and a 5% surcharge on base freight only.

The invoice's arithmetic is correct: 5% of ₹13,500 is ₹675. The problem is that it applies the surcharge to waiting as well as freight. The supported total is ₹12,000 + ₹1,000 + ₹600 = ₹13,600.

The waiting calculation needs its own inputs. In this example, the agreed clock runs from gate arrival at 10:00 to release at 13:00 on the same day, in the same timezone. The fictional terms allow one free hour and charge ₹500 for each subsequent full hour. Three elapsed hours minus one free hour gives two chargeable hours: 2 × ₹500 = ₹1,000. The invoice charged all three hours.

If the carrier disputes either timestamp, keep that evidence question open instead of treating the example's result as established fact. The surcharge error is independent: even if another hour of waiting is later supported, the example agreement still excludes waiting from its surcharge base. Separate the causes so correcting one does not automatically approve the other.

The supported amount is a review result, not an instruction to make a partial payment. Finance must decide payment and dispute treatment under the agreement and its approved controls.

Make the exception queue useful to the owner

A good exception record contains the disputed line, amount, rule version, missing or conflicting evidence, accountable owner and next review date. Preserve the original invoice and the reviewer’s decision. A later credit should explain how the dispute was resolved, rather than silently replacing the bill that triggered it.

Use separate reasons for an absent rate, an overlapping rate, missing POD, disputed waiting, arithmetic error and possible duplicate. The owner should see enough context to act without opening five unrelated systems. An AP reviewer can then distinguish “waiting for operations” from “waiting for a credit note”.

Start with a controlled spreadsheet if the population is small and ownership is clear. Use native TMS or ERP matching when it can reproduce the required rules. An integration becomes useful when records are repeatedly copied between systems or corrections cannot be traced reliably. OCR can prepare invoice fields, but an extracted waiting amount does not establish that waiting was chargeable.

Follow the decision through to closure

Measure how much billed value has a reproducible rule and service record, alongside the age of unresolved differences. Count false duplicate flags and reviewer corrections too. A high automatic-match rate is unhelpful if disputed lines are hidden inside matched invoices.

Before enabling a tolerance, specify its currency, amount or percentage basis, and which error categories it may cover. A small rounding difference is different from an unapproved service, even when both amounts fall below the same threshold. Keep the detected difference visible after an authorised tolerance decision.

Make approval explainable

The useful output of a freight audit is an explanation of each material charge and the work needed to settle any difference. Shipment matching, entitlement, evidence and arithmetic should support one approval record without becoming one indistinct pass/fail flag.

Next actions

1. Select a completed carrier billing period and gather invoices, LRs, rate versions and service evidence.
2. Reproduce a few bills manually, separating commercial, operational and arithmetic differences.
3. Assign an owner and closure record to each recurring exception.
4. Automate the repeatable checks only after finance can reproduce their results.