Carrier Invoices: Reconciling Rates Before You Pay

A carrier invoice lands on Friday with a charge the team does not recognize: a liftgate fee on a load that did not need one. The rate confirmation says nothing about liftgates. The accounts payable clerk has two choices: pay it and move on, or spend an hour finding the original agreement and the proof of delivery. Most weeks, the clerk pays it.

How common are carrier invoice errors?

An audit of nearly 250,000 LTL invoices found that about 4.5% carried errors. Accessorial charges made up about 42.8% of those errors, and fuel surcharges about 14.4%. The data comes from a Q1 2023 audit, so it is dated, but it shows where the money goes wrong. Other estimates vary widely, and many come from vendors who sell audit services, so treat them as a range rather than a rate.

Why reconciliation is hard

The rate confirmation is a single document, but the charges it governs are spread across several sources. The base rate is in the confirmation. Accessorial rules may be in the carrier contract, and the fuel index changes by week. Weights and classes come from the bill of lading. Invoices arrive as PDFs, as EDI 210 files, or as photos sent by email, and each format needs its own reading step before any comparison can start.

Signs you have this problem

• Accessorial charges are paid without a link to the rate confirmation or proof of delivery.
• The same carrier is billed for the same charge on several invoices in one month.
• Fuel surcharges are applied with a date or index that does not match the load.
• A person spends most of an invoice review finding the right document, not checking the charge.
• Disputes start only after the carrier sends a reminder.

How to measure your own errors

Sample 100 carrier invoices from the last quarter. For each charge, record whether you can match it to a rate confirmation term, a proof of delivery, or a fuel index for that date. Count the unmatched charges and add up their value. Note how many minutes a clerk spends on each invoice. Those three numbers tell you the size of the exception queue and the cost of checking it by hand.

The tools that read invoices, and where they stop

docTR, PaddleOCR and Tesseract are open-source OCR libraries. They read printed text from PDFs and scans, and some of them extract tables. The EDI parsers in the open-source community read EDI 210 files into fields. All of these produce text or structured fields. None of them knows your rate terms, so none of them can say whether a charge is correct.

Best practice for invoice reconciliation

• Store the rate terms as data when the rate confirmation is signed, so a check can run against them.
• Write accessorial rules as explicit conditions, such as liftgate only when the rate confirmation says so.
• Keep the proof of delivery and the rate confirmation attached to each charge.
• Set a rule for what is paid automatically, what is disputed automatically, and what goes to a person.
• Review the exception rules each quarter against the disputes that were actually resolved.

How Asauvia helps

We build the reading, matching and exception steps for freight teams. A typical setup reads each invoice, matches every charge to the rate terms and the proof of delivery, and presents the evidence with each exception. Clear matches are cleared automatically, and a person approves the rest.

Dispute rules and payment terms depend on each carrier agreement, so have your legal or compliance adviser review the final process before it runs without a person in the loop.