Real-Time Visibility and Freight Invoice Validation: You Are Checking Carrier Charges With Carrier Data in 2026

Freight invoice validation checks charges against a contracted rate card, and for rate-based charges that works. Event-based accessorial charges are different: waiting time, failed delivery attempts, redelivery and re-consignment are billed on events the carrier itself reports, so a shipper without independent observation can dispute the rate applied but not whether the event happened. In fragmented European carrier networks that covers a material share of accessorial spend. Locus, the world’s first Decision-Intelligent, Agentic TMS, records execution events from its own plan and tracking alongside carrier-reported ones, which is what turns validation into verification.

Why Accessorial Validation Is a Different Problem From Rate Audit

Freight audit is usually described as one activity. In practice it contains two, and only one of them is solved.

Rate validation compares a charged amount to a contracted rate for a known service. The inputs are a rate card, a lane, a weight or volume and a service level, all of which the shipper holds independently. Disagreements are resolvable because both parties can compute the correct answer from documents neither controls exclusively.

Accessorial validation for event-based charges works differently. The charge depends on something that happened during execution, and in a conventional arrangement the only record of what happened is the carrier’s. The shipper receives an invoice line stating that a vehicle waited two hours at a delivery point, or that an attempt failed because the receiver was absent, and the evidence supporting that line is the carrier’s own event data.

This is not an allegation about carrier conduct. Reasonable parties disagree about dwell start times, about whether a wait was caused by the receiver or by the driver arriving outside the booked window, and about whether an attempt was genuinely made. The point is narrower and structural: where the only record belongs to one party, the other party cannot form an independent view, and disputes resolve on relationship rather than on fact.

Our own freight audit and settlement buyer’s guide identifies accessorial and surcharge validation as the area where most disputes live. This article addresses the part that guide leaves open, which is how the underlying event is established at all.

Also Read: Freight Audit and Settlement Software Buyer’s Guide 2026

Why the Exposure Is Larger in Europe

Two structural features of European road freight widen the gap between what is charged and what the shipper can independently verify.

The first is carrier fragmentation. AlixPartners’ 2026 Home Delivery Survey found more than 90% of executives run a mix of last-mile carriers and 32% use four or more, and European networks commonly sit at the higher end because national carrier markets remain distinct. Each carrier brings its own event definitions, its own dwell measurement convention and its own reporting cadence, so there is no single standard against which a charge can be read.

The second is subcontracting depth. A charge raised by the contracted carrier frequently describes an event observed by a subcontractor, sometimes several layers down. The contracted party is passing through a record it did not create and often cannot substantiate in detail, which makes a factual dispute slow even when both parties are acting in good faith.

The financial stakes justify the attention. McKinsey’s out-of-home delivery work puts the last mile at 60% to 70% of total parcel delivery cost, and accessorials are the fastest-moving component of that base because they scale with exception volume rather than with contracted volume. Conditions are pushing exception volume up: INRIX’s 2025 Global Traffic Scorecard recorded congestion increasing across the large majority of cities it measures, and congestion produces exactly the late arrivals and missed windows that generate event-based charges.

What Can and Cannot Be Contested

The distinction that matters is between charges whose basis the shipper can reconstruct and charges whose basis only the carrier holds.

Charge type	Basis of the charge	Can the shipper verify it independently
Linehaul rate	Lane, weight, service level	Yes, from the rate card and the consignment
Fuel surcharge	Published index and formula	Yes, from the index and the contract
Weight or volume correction	Measured at a terminal	Partly, if the shipper measured at origin
Waiting or detention time	Arrival and departure timestamps at the stop	Only with an independent record of both
Failed delivery attempt	Attempt occurred, receiver unavailable	Only with an independent record of presence and timing
Redelivery	A prior attempt failed	Inherits the evidence problem of the attempt
Re-consignment or address correction	Instruction received during execution	Only with a record of what was instructed and when

The top three lines are where most audit effort goes and where least money is genuinely at risk, because both parties can compute the right answer. The bottom four are where disputes concentrate, and they are exactly the lines a conventional audit cannot reach on the facts.

The practical consequence is that a freight audit programme reporting a healthy recovery rate may be recovering well on the charges it can reach while never testing the ones it cannot. A recovery rate computed only over contested lines describes the audit’s performance on its own chosen scope.

Also Read: Real-Time Tracking and Visibility for 3PLs

Sizing the Exposure Before Spending Anything

The argument only justifies work if the number is material, and it is calculable from data most finance teams already hold.

Start with total accessorial spend for the year, then split it by charge type using the table above. The event-based lines, waiting and detention, failed attempts, redelivery and re-consignment, form the exposed pool. In most road operations this is a meaningful minority of accessorials rather than a rounding error, and it is the fastest-growing part because it scales with exception volume.

Then apply two adjustments. The first is the share of that pool for which you already hold an independent timestamp, which for operations running their own driver application on part of the network may be substantial and for purely contracted networks is often close to zero. The second is the dispute rate you currently achieve on those lines, which in the absence of independent evidence is usually low and negotiated rather than evidenced.

What remains is the unverifiable pool: spend that is charged on a basis you cannot examine. That figure, not the total accessorial number, is what an observation programme is competing against.

It is worth being honest about what recovery from that pool looks like. Most of it is not fraud and will not be recovered as refunds. The larger effect is compositional: once a shipper can evidence dwell and attempt outcomes consistently, the marginal lines stop being raised, and the saving appears as charges that never arrive rather than as credits that do. That is harder to attribute in a business case and it is usually the bigger number, so a programme justified only on recovered credits will understate its own return.

Also Read: ePOD Explained: Electronic Proof of Delivery

What an Independent Record Has to Contain

1. Arrival and departure timestamps generated by the shipper’s system

Dwell is the difference between two timestamps, so both must come from a source the shipper controls. A geofence crossing recorded by the shipper’s platform, or a driver app event on a shipper-operated application, establishes the interval independently of the carrier’s own report.

2. The booked window alongside the actual arrival

Most waiting-time disputes turn on whether the vehicle arrived inside its booked slot. Holding the booking and the arrival in the same record makes that answerable, and it frequently reverses the direction of the charge.

3. Attempt outcome with supporting evidence

An attempt record needs a timestamp, a position and ideally a photograph or receiver interaction. Electronic proof of delivery is the mechanism, and its value in disputes depends on it being captured by a system the shipper can produce in evidence.

4. The instruction trail for changes during execution

Re-consignments and address corrections are charged because someone changed something. A record of what was instructed, by whom and when, resolves most of those lines without argument.

5. Data retained past the dispute window

Accessorial disputes surface on an invoice cycle, which means the underlying event may be weeks old before it is questioned. Retention shorter than the contractual dispute window makes the record useless at the moment it is needed.

6. Event definitions agreed in the contract

An independent record only settles a dispute if both parties measure the same thing. Agreeing what starts dwell, what constitutes an attempt and what counts as receiver unavailability converts a factual disagreement into an arithmetic one.

Conventional Audit and Observation-Backed Audit Compared

Dimension	Conventional freight audit	Observation-backed audit
Source of event data	Carrier’s reported events	Shipper’s execution record, compared to the carrier’s
What can be contested	The rate applied to the event	The rate and whether the event occurred as described
Typical dispute resolution	Negotiated, on relationship	Evidenced, on record
Coverage of accessorial spend	Rate-based lines only	Rate-based and event-based lines
Effect on carrier behaviour	Charges tested inconsistently	Charges tested consistently, which changes what is raised
Requirement	A rate repository	A rate repository plus an execution record

The behavioural row is the one that compounds. Where a shipper can evidence dwell and attempt outcomes, the composition of what gets invoiced tends to change, because marginal lines that would not survive examination stop being raised.

What to Check in Your Own Operation

What share of accessorial spend is event-based? Split last year’s accessorials into rate-based and event-based lines. The second group is the portion currently being validated against the carrier’s own account of what happened.

Do you hold an independent timestamp for arrival and departure at customer sites? If dwell is only ever known from the carrier’s feed, waiting-time charges are unverifiable in principle, regardless of how thorough the audit is.

Are event definitions written into the carrier contract? Ask what starts and stops dwell under each agreement. Where it is unspecified, disputes cannot be settled on facts even when both parties hold records.

Can you produce the evidence in the format a dispute requires? Holding the data is not the same as being able to present it. A timestamped record that takes three days to extract will not be used inside a dispute cycle measured in weeks, and the practical test is whether the responding team can retrieve it from a system they already have open.

Does your retention period exceed your dispute window? Compare how long execution data is kept against how long you contractually have to raise a claim. A shorter retention makes the record unavailable exactly when the charge is questioned.

When You Cannot Observe, Change the Contract

Independent observation is not available everywhere. Pure parcel networks, long subcontracting chains and carriers who will not accept a shipper application on their drivers’ devices all limit what can be captured directly. Where observation is impossible, three contractual moves recover part of the position.

Define the event, not just the rate. Most carrier contracts specify what a waiting hour costs and leave what starts the clock to the carrier’s own terms. Specifying that dwell begins at the later of booked slot start and actual arrival, and that arrival means gate or geofence entry, removes the most common source of disagreement without any new data.

Require evidence to accompany the charge. A contractual obligation to supply the supporting timestamp, position or attempt photograph with the invoice line shifts the burden without requiring the shipper to observe anything. Lines that cannot be evidenced are then disputable on the contract rather than on the facts.

Set a rebuttal window that matches your data. Dispute periods are negotiable and are frequently shorter than the time it takes an invoice to be questioned internally. Aligning the window to your own close and audit cycle is a cheaper fix than accelerating the cycle.

None of these produce an independent record, and they are not equivalent to one. They convert an unanswerable question into an answerable one by narrowing what the parties can reasonably disagree about, which for the portion of the network you cannot instrument is the realistic ceiling.

Also Read: Order to POD: Handover Visibility Blind Spots

Common Mistakes in Freight Invoice Validation

Treating recovery rate as a measure of audit quality. A high recovery rate on rate-based lines says nothing about the event-based lines the audit never tested.

Assuming an integration gives you independent data. Receiving carrier events through an API makes them faster and better formatted. It does not make them independent, because the source is unchanged.

Relying on proof of delivery alone. Delivery confirmation establishes that the delivery happened, which is rarely the disputed fact. The disputed fact is usually the timing or the attempt that preceded it.

Leaving event definitions to the carrier’s terms. Where dwell measurement is defined only in the carrier’s documentation, the shipper is contesting a figure computed under rules it did not agree.

Justifying an observation programme only on recovered credits. The larger saving is in charges that stop being raised once they can be examined, which appears as a lower run rate rather than as refunds and is easy to leave out of a business case.

How Locus Supports Independent Event Evidence

Locus, the world’s first Decision-Intelligent, Agentic TMS, holds the plan and the execution record in one system, so the events that drive accessorial charges are captured by the shipper’s platform rather than received from the carrier. The Control Tower records arrival and departure against the booked window, and electronic proof of delivery captures attempt outcomes with timestamp and position, which together cover the categories where event-based disputes concentrate.

ShipFlex normalises carrier-reported events into the same model, which means the carrier’s account and the independently observed account sit side by side in one record rather than in two systems compared by hand. The Settlement agent evaluates invoice lines against both, and the DiSCO governance mechanisms, particularly Traceability, preserve the chain behind each figure, so a disputed line can be evidenced with the observations that produced it.

An Indian paint manufacturer processing more than 1,500 carrier invoices a month across 160 depots identified variance of 5% to 6% above contracted rates and reduced payment cycles from 30 to 45 days down to 7 to 10 days through automated freight reconciliation, moving all local-movement invoices to digital processing. A Fortune 50 enterprise running more than 4,500 drivers across captive and third-party capacity surfaced more than $14M in capacity it already owned through centralised dispatch, on a network where owned and contracted execution run side by side.

Locus has been recognised by Gartner for seven consecutive years across multiple research categories, including the 2026 Gartner Market Guide for Multicarrier Parcel Management Solutions, where ShipFlex is featured as a Representative Vendor, and Representative Vendor status in the 2026 Gartner Hype Cycle for Supply Chain Execution and Logistics Technologies. QKS Group positions Locus as the Leader in its SPARK Matrix for Transportation Management Systems 2025, and G2 ranked Locus number one in Route Planning in its 2026 Best Software Awards. The platform has run more than 1.5 billion deliveries for 360+ enterprise customers across 30+ countries at 99.99% uptime.

In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

The reframing this argues for is modest and it changes what a freight audit can reach. Rate validation is a documents problem and it is largely solved. Event-based accessorial validation is an observation problem, and no amount of audit rigour substitutes for holding a record of what happened. Split your accessorial spend, establish which portion is currently unverifiable, and decide whether that number justifies capturing execution events yourself. Locus records execution alongside carrier-reported events in one system across 30+ countries and more than 1,000 carriers. Schedule a demo to see it against your own carrier base.

Also Read: Real-Time Shipment Visibility Platforms: A Complete Enterprise Buyer’s Guide

Frequently Asked Questions

Why can freight audit not validate accessorial charges? Because event-based accessorials depend on something that happened during execution, and in a conventional arrangement the only record of it belongs to the carrier raising the charge. A rate can be checked against a contract, but whether a vehicle waited two hours cannot be checked against anything the shipper holds.

Which freight charges can a shipper verify independently? Linehaul rates, fuel surcharges and index-linked charges, because the inputs sit in documents both parties hold. Waiting time, failed attempts, redelivery and re-consignment cannot be verified without an independent record of the underlying event.

Why is this a bigger issue for European carrier networks? Because carrier bases are fragmented and subcontracting chains are long. Each carrier applies its own event definitions and measurement conventions, and a charge raised by the contracted party often describes an event observed several layers down the chain.

What does an independent execution record need to contain? Arrival and departure timestamps generated by the shipper’s own system, the booked window alongside actual arrival, attempt outcomes with position and evidence, the instruction trail for changes during execution, and retention that exceeds the contractual dispute window.

Does receiving carrier tracking data through an API solve the problem? No. An integration changes how the data arrives, not where it comes from. Independence requires an observation the shipper’s own system generated, which is why geofence events and driver-app records are different in kind from carrier feeds.

Is proof of delivery sufficient evidence for accessorial disputes? Rarely on its own. Delivery confirmation establishes that the delivery occurred, while disputes usually concern the timing that preceded it or an attempt that did not result in delivery. Those require arrival, dwell and attempt records rather than a completion record.