Freight invoice and accessorial audit
What an invoice has to agree with before it is paid, which of those checks is arithmetic and which is judgement, and the charges that quietly leave margin on the table in both directions. Written from published standards and the statutes that set the clocks.
The deadlines that decide what you can still recover
- 180 daysA carrier must issue any bill for charges in addition to those originally billed within 180 days of receipt of the original bill in order to keep the right to collect them.49 U.S.C. § 13710(a)(3)
- 180 daysA shipper must contest the original or a subsequent bill within 180 days of receiving it in order to keep the right to contest those charges.49 U.S.C. § 13710(a)(3)
- 18 monthsA carrier must begin a civil action to recover freight charges within 18 months of the claim accruing; a party must begin an action to recover overcharges in the same window.49 U.S.C. § 14705(a), (b)
To issue an additional bill, or to contest one — 49 U.S.C. § 13710(a)(3)
To bring an action for freight charges or overcharges — § 14705
Distinct ways a fuel surcharge is computed wrong
Fixed-price pilot: one invoice flow, three weeks, instrumented
Eight steps, and which of them a machine should actually own.
The arithmetic belongs to an engine and the judgement belongs to a person of record. A vendor who blurs the two is describing a demo, not a system your controller will sign off.
- 01 · deterministicIntake and normalise210, emailed PDF, carrier portal, API — or a factor billing on the carrier's behalf. One canonical invoice object whatever the channel.
- 02 · engine + ownerResolve load, carrier, payeeWhich load, which carrier actually hauled it, and who is lawfully owed. Submitter, carrier and payee are three different parties.
- 03 · deterministicPaperwork gateSigned BOL, clean POD, lumper receipt, scale ticket, in and out times. Terms run from a complete packet, not from the invoice date.
- 04 · engine + ownerDuplicate and cancellation screenDuplicate, corrected invoice and balance-due bill look identical and are not. B3-08 and the 180-day rule separate them.
- 05 · engine + ownerDecompose and map to authorityLinehaul, fuel, accessorials, pass-throughs, tax — each line mapped to the document that authorises it.
- 06 · deterministicRecalculate from first principlesRate times miles, fuel from the correct index week, accessorial units net of free time, LTL in the contract's order of operations.
- 07 · human decidesAdjudicate the judgement chargesDetention, layover, TONU, driver assist. Evidence and time maths, and a person of record who decides.
- 08 · engine + ownerDisposition and releaseApprove, short pay with a coded reason, hold for documents, or deny with a rebuttal packet — and pay the remit-to on file, not the carrier by default.
The X12 210 segments that carry the money.
Element names are stable; their positions move between versions and every trading partner constrains them further in their own implementation guide. Anyone who tells you the mapping is universal has not onboarded a partner.
| Segment | What it is | Why it matters to an audit |
|---|---|---|
| B3 | Beginning segment for carrier's invoice | Invoice number, PRO, method of payment, invoice date, net amount due, SCAC — and the correction indicator that tells a corrected invoice from a duplicate. |
| C3 | Currency | Currency code and exchange rate. The cross-border hook: the contract has to say when the rate locks. |
| ITD | Terms of sale | Discount percent, discount due date, net days. Quick-pay terms live here, not in a side letter. |
| N9 | Reference identification | BM bill of lading, CN carrier reference, PO purchase order, SI shipper's number. The join keys, and the reason matching is multi-key. |
| G62 | Date / time | Carries a time-code element that is routinely omitted. Omit it and every detention calculation inherits a timezone bug. |
| L0 | Line item quantity and weight | The rated-as basis — the quantity and weight the charge was actually computed on, which is not always what shipped. |
| L1 | Rate and charges | The money segment. Rate, rate qualifier (per mile, flat, per CWT), the charge, and the special-charge code that is supposed to say which accessorial this is. |
| L7 | Tariff reference | Tariff number, item number, freight class. Where an LTL reclass argument is won or lost. |
| L3 | Total weight and charges | The totals to reconcile the lines against. They disagree more often than anyone expects. |
The accessorial code is half free text
The special-charge code on L1 is where the accessorial type is supposed to live. In practice partners map it inconsistently and half the meaning ends up in the free-text description beside it. Real normalisation is a curated, versioned mapping per carrier — not a lookup against the standard. That is the problem, and it is the product.
The 210 cannot evidence detention
Arrival and departure times are not in the invoice. They come from 214 status events, from telematics geofence dwell, or off the proof of delivery. Detention audit is structurally not an EDI-only problem, and a tool that only parses invoices will never settle a detention argument.
Where an invoice and the agreement disagree.
In rough order of how often each occurs, which is deliberately not the order of dollar impact — the costliest classes are not the commonest, and treating them as one list is how audits chase the wrong thing.
| What ops sees | What is actually happening | How it gets handled |
|---|---|---|
| Invoice is $75–$400 over the rate confirmation, with a line reading DET, LAYOVER or DRIVER ASSIST. | An accessorial that may be entirely real — the driver did wait — but was never authorised in writing, so no price was agreed and there is no path to rebill the customer. | Flag deterministically: a charge line with no authorising document. Route to the account owner with the evidence attached. The durable fix is upstream — pre-authorisation in the agreement and an approval in the moment. |
| Linehaul on the invoice does not equal linehaul on the rate confirmation. | Usually the carrier billed their original quote rather than the agreed rate, a keying error, a verbal increase for a late appointment that never reached a revision — or you are auditing against a superseded revision. | Deterministic, but check revision lineage first. A large share of apparent rate mismatches are stale-revision false positives, and chasing those is how an audit loses the carrier's goodwill. |
| A fuel surcharge line that will not reconcile, or a fuel line on an all-in load. | Six distinct failure modes, set out in the next section. In aggregate this is the largest number on most audits. | Fully deterministic, provided the dated index series and the contractual schedule are stored. The highest-return rule in the whole audit. |
| “DET 3.5 HRS @ $50” and no arrival or departure time anywhere in the packet. | A real wait with lost paperwork, or free time counted from the wrong clock start. | Hold for evidence — a facility-stamped in and out, 214 status events, or geofence dwell — then recompute against free time, the rounding increment and the daily cap. Expect genuine ambiguity and record who decided. |
| A second invoice for a load already paid, often months later, under a new number. | Re-submission after a short pay, a factor and a carrier both billing, or a legitimate balance-due bill. | Deterministic screen on SCAC plus PRO, BOL plus amount, and load id. The three cases look identical and must be separated — the 180-day additional-bill rule decides the third. |
| Same lane, same rate per mile, different total. | Mileage engine version drift, or practical versus shortest versus toll-discouraged routing, or ZIP-to-ZIP against point-to-point, or out-of-route miles billed unauthorised. | Deterministic only if the contract names the engine, the version and the routing option. Where it does not, the dispute is unwinnable and the fix is contractual, not technical. |
| A corrected LTL invoice well above the quote, plus an inspection or reweigh fee. | The carrier scaled or inspected the freight and found weight or density different from the bill of lading — often a stale NMFC item, or dimensions that excluded pallet height or overhang. | Demand the weight and inspection certificate, the certified scale ticket, photographs and measured dimensions, then recompute density on the actual cubed footprint. Detected and disputed, never silently re-classed. |
| An invoice that will not match anything at all. | The reference landed in the wrong field, digits transposed, or a customer PO given where the shipper's BOL was expected. | Multi-key matching with a persistent alias table a human confirms. Almost no direct leakage, and usually the single largest driver of days-to-approve. |
| An invoice for a cancelled load, or from a carrier whose remit-to matches nothing on file. | At best a TONU billed under the wrong code. At worst double-brokering, carrier identity theft, or a fraudulent remit-to change. | Never auto-pay. Verify the carrier against the tender and the remit-to against the notice of assignment, and verify any banking change out of band — never by replying to the message that requested it. |
| Nothing. Ops sees nothing at all. | A legitimate lumper, detention or extra stop was paid to the carrier and never added to the customer invoice. No exception is raised because nothing is wrong with the carrier's bill — the margin simply leaves. | Reconcile every paid accessorial against the customer rebill and report unrebilled pass-through as its own exception class. For a broker this is often the biggest number on the page, and almost nobody audits for it. |
Six ways a fuel surcharge is computed wrong.
One line on the invoice, six independent ways to get it wrong, and in aggregate the largest recoverable number on most audits. All six are deterministic once the dated index series and the contractual schedule are stored.
Wrong index week
The contract says the week of pickup; the carrier used the week of delivery, or the week they invoiced. On a moving index that is a different number every time.
Wrong index
A national average applied where the contract specifies a regional one, or the reverse. Same source, different series.
Wrong peg or wrong step
The base price the schedule pegs to, or the wrong row of the cents-per-mile table.
Wrong efficiency assumption
Cents-per-mile schedules derive from an assumed MPG. It is a contract term, not a law of nature, and it is frequently assumed rather than read.
Fuel applied to accessorials
The schedule says linehaul only; the surcharge was computed on the invoice total.
The double dip
An all-in rate was agreed, and the invoice carries the all-in rate plus a separate fuel line.
The index itself is public — the weekly retail on-highway diesel series published by the U.S. Energy Information Administration, released on Mondays. What is not public is which week your contract points at, and that is the element most often assumed rather than read.
What each charge has to evidence.
Conventions, not standards — every figure here is a contract term that varies by carrier, lane and facility. What does not vary is what the argument turns on.
| Charge | Usual convention | What evidences it | Where the dispute turns |
|---|---|---|---|
| Detention, with power | Commonly around two hours free per stop, then an hourly rate, usually capped per day. | Facility-stamped in and out on the POD, gate records, 214 status events, geofence dwell. | When the clock starts. Free time runs from the appointment, not from arrival — a driver two hours early does not accrue detention for his own choice. |
| Layover | A flat daily figure when the load is held overnight. | Dispatch notes, the next day's appointment, the driver's hours record. | Whether it is layover or capped detention. Never both for the same hours. |
| TONU | Flat, agreed in the master agreement rather than per load. | The accepted tender, the cancellation timestamp, and proof the driver was dispatched. | How much notice was given, and whether the driver had already departed or arrived. |
| Lumper | Third-party unload, passed through at cost. | A legible receipt showing facility, date, amount and who paid. | Double billing — the driver was funded by express code and the carrier invoices it again — and markup where the contract says at cost. |
| Driver assist | Flat, per occurrence. | A notation on the POD, ideally initialled by the receiver. | One of the most contested charges there is, because there is usually no independent evidence it happened. |
| Reconsignment | The extra miles plus a flat fee. | A written instruction with an author and a timestamp. | Who authorised it, and whether the new miles were recomputed on the contractual mileage basis. |
| Reweigh, reclass, inspection | LTL, per event. | The weight and inspection certificate, scale ticket, photographs, measured dimensions. | Whether the certificate was produced at all, and whether the right NMFC item and sub were applied. |
| Demurrage and per diem | Drayage: free days, then per day. | Terminal and ocean-carrier statements. | That these are two different charges — demurrage is the container sitting inside the terminal, per diem is equipment held outside beyond free days. |
Free time runs from the appointment
Not from arrival. A driver who shows up two hours early does not accrue detention for his own choice, and a system that counts from the geofence will overpay on every lane.
Who signs decides the outcome
An in and out time with no facility stamp, signature or initial is close to unwinnable. The cheapest investment in the whole audit is getting a signed in and out at every stop.
Notice windows are real terms
Many agreements require detention to be reported while the driver is still on site. Late-reported detention is denied routinely — not because it did not happen, but because the clause was not met.
The deadlines an audit exists to never miss.
These are not conventions. They are the limits set in the United States Code and the Code of Federal Regulations, and they are the boundary on what you can still bill, still contest, and still recover.
A carrier must issue any bill for charges in addition to those originally billed within 180 days of receipt of the original bill in order to keep the right to collect them.
49 U.S.C. § 13710(a)(3)
A shipper must contest the original or a subsequent bill within 180 days of receiving it in order to keep the right to contest those charges.
49 U.S.C. § 13710(a)(3)
A carrier must begin a civil action to recover freight charges within 18 months of the claim accruing; a party must begin an action to recover overcharges in the same window.
49 U.S.C. § 14705(a), (b)
A broker must keep a record of each transaction — including the freight charges collected and the date the carrier was paid — and every party to the transaction has the right to review that record.
49 CFR § 371.3
What a pilot reports back.
Half of these are honesty metrics. A pilot that reports only savings is a pilot nobody in accounts payable believes twice.
Straight-through rate
Share of invoices matched, recalculated and dispositioned with no human touch — reported per mode and per carrier, because truckload and LTL behave nothing alike and a blended number hides it.
Exception rate by class
The breakdown above, with dollars attached. The most useful artefact of a pilot, because it says which contract to fix rather than which invoice to short pay.
False-positive rate
Share of flagged exceptions later confirmed as valid charges. Published prominently, because a noisy auditor costs more in carrier goodwill than it recovers.
Prevented versus recovered
Kept strictly apart. Prevented is caught before payment and nearly all of it is realised; recovered is clawed back afterwards and much of it is not. One blended savings number conceals the mix.
Dispute outcome and days to resolve
Share of adjustments the carrier accepts without escalation, and the time from short pay to closure. A low acceptance rate means the evidence packets are weak.
Cycle time and discount capture
Days to approve, share approved inside the early-pay window, and — as the counterweight — the carrier's days to pay. An audit that improves accuracy by delaying payment has failed.
One invoice flow, three weeks.
Fixed scope and a fixed price: $4,500. We take one carrier or one customer's invoice flow, stand up the deterministic rules — rate against the rate confirmation, fuel against the dated index, accessorials net of free time — and instrument them from the first day, so the result is measured rather than argued.
What we need: the carrier agreement and the accessorial schedule, the fuel schedule, about fifty recent invoices with their paperwork, and one person in operations or accounts payable who answers questions.
- Charge decomposition with every line mapped to its authorising document
- Deterministic recalculation for linehaul, fuel and accessorials
- An evidenced short-pay packet the carrier can actually reconcile
- Exception queue for the judgement charges, with an approver of record
- The exception breakdown by class — which contract to fix, not just which invoice
Questions a controller actually asks.
Do you pay our carriers?
No. We are the audit and approval layer, and we hand off to your accounts payable or your payment provider. What we do is decide what should be paid, evidence it, and route it to the remit-to actually on file.
What if a carrier has factored its invoices?
Then the factor is the lawful payee under the notice of assignment, and paying the carrier directly does not discharge the debt — the factor can still collect, and you have paid twice. Remit-to verification against the assignment on file is a hard gate in anything we build, and a mid-stream change is verified out of band, never from the message that requested it.
How much of this can actually be automated?
The arithmetic, almost entirely: rate against the rate confirmation, fuel against the dated index, accessorial units net of free time, LTL in the contract's order of operations. The judgement charges — detention, driver assist, layover — need evidence and a person of record. We would rather claim a high straight-through rate on the deterministic half than pretend the other half is solved.
What recovery percentage should we expect?
We will not quote one. The figures that circulate — a given percent of bills in error, a given percent of spend recovered — trace back to vendor marketing rather than to any method you could check. We instrument your invoice flow and report what we actually find, by class, within the first weeks. That number is yours and it is real.
Our carriers do not all send EDI. Does that break this?
No, and assuming otherwise is the usual mistake. Most small carriers invoice by emailed PDF, and 210 coverage skews to large asset carriers and LTL. More to the point, the agreed price often lives on a rate confirmation rather than in the EDI stream at all, because a 204 tender frequently carries no rate. Invoice audit is a document problem that happens to involve EDI.
Can you audit detention from our EDI alone?
Not reliably, and anyone who says otherwise has not done it. The 210 does not carry arrival and departure times. Those come from 214 status events, from telematics, or off the proof of delivery — which is why detention is the charge that most needs evidence capture rather than better parsing.
What does a pilot cost?
A pilot is $4,500 fixed: three weeks, one carrier or one customer's invoice flow, the deterministic rules switched on and instrumented from the first day. The scope is written down before anything starts.
What do you need from us to begin?
The broker–carrier agreement and the accessorial schedule, the fuel surcharge schedule, around fifty recent invoices with their rate confirmations and paperwork, and one person in operations or accounts payable who can answer questions.
Book a 30-minute call with our expert
Bring one carrier and a month of invoices. You will leave the call knowing which of your charge classes is leaking, what a pilot would cover, and what it would cost — $4,500 fixed, three weeks.
Reply within 1 business day · India & USA
Charge conventions on this page are typical contract terms, not industry standards, and vary by carrier, lane and facility. Statutory references are to the United States Code and the Code of Federal Regulations as cited and are given for orientation, not as legal, tax or accounting advice. X12 element names are stable but their positions vary by version and by each trading partner's implementation guide. No customer data, configuration or code appears here.
Also in this blueprint: freight EDI onboarding and repair, and the rest of the AI TMS Blueprint.