Key Takeaway
A freight audit tool that reads every carrier invoice and checks it against your rates, BOLs and PODs catches overcharges before payment, so your AP team only handles exceptions.
Your AP team has a stack of carrier invoices to get through this week. Some came in as EDI 210s. Some are PDFs attached to emails. A few regional carriers still send spreadsheets, and one sends a scanned image of a printed invoice. Every one of them needs to be checked against a rate agreement, a bill of lading and a proof of delivery before it gets paid.
Nobody has time to check them all. So most teams check a sample, approve the rest, and accept that some overcharges will get through.
That trade-off made sense when the only way to audit an invoice was a person reading it line by line. It doesn’t anymore.
Why freight billing errors keep getting paid
Freight invoices are hard to audit for structural reasons, not because anyone is careless.
The formats don’t match. A 210 from a large LTL carrier is structured data. A PDF from a small drayage provider is a document with whatever layout they chose. Your team has to normalize all of it before they can compare anything.
The rules live in different places. Contracted linehaul rates sit in one agreement. Fuel surcharges follow a table tied to the weekly DOE diesel index. Accessorial rules for liftgate, residential delivery, detention and reweighs are buried in a tariff or an addendum. Checking one invoice correctly means pulling from three or four sources.
The evidence lives somewhere else again. Was the shipment actually 2,400 pounds or did the carrier reweigh it to 3,100? Was detention real? The answer sits in the BOL, the POD and maybe the 214 status messages in your TMS. Matching them takes time.
The errors are small one at a time. A wrong fuel percentage costs a few dollars on one shipment. A duplicate invoice looks like a legitimate charge unless someone remembers paying it. Individually, none of these feel worth chasing. Across a year of freight spend, they add up to a number your CFO would care about.
Freight audit and payment providers exist, and some companies use them well. But they often work on a percentage of recovered spend, sit outside your systems, and apply their own rules instead of the specific terms you negotiated. Generic AP automation tools read invoices but don’t understand freight. They can extract a total. They can’t tell you the accessorial was never authorized.
What a custom freight audit tool does
The tool we build sits between invoice intake and payment approval. Every invoice passes through it. Here’s how it works with your existing setup.
Reading invoices in any format
The first job is extraction. The tool takes in EDI 210s directly and reads PDFs, scans and spreadsheets with document models tuned to freight invoices. It pulls out the fields that matter: PRO number, ship date, origin and destination, weight, class, linehaul charge, fuel surcharge, each accessorial line, and the total.
Each extracted field is tied back to where it came from on the source document. When a reviewer opens a flagged invoice, they see the original next to the parsed data.
Matching against rates and shipment records
Once an invoice is structured, the tool looks up what the charge should have been. It pulls the contracted rate for that lane and carrier, applies the fuel surcharge table for the right week, and checks each accessorial against the approved list for that shipment.
Then it matches the invoice to the shipment itself. It finds the corresponding load in your TMS, whether that’s MercuryGate, Blue Yonder, Oracle OTM or something built in-house. It compares billed weight to BOL weight, checks the delivery date against the POD, and reviews 214 status events to see if a detention claim lines up with actual dwell time.
Flagging specific errors
Instead of a generic “mismatch” warning, the tool flags the exact problem:
- Duplicate invoices, including the same PRO billed twice under slightly different invoice numbers
- Fuel surcharge applied at the wrong percentage or against the wrong base
- Accessorials that weren’t requested or approved on the shipment
- Linehaul rates above the contracted rate for the lane
- Weight or class changes with no reweigh or inspection record
- Charges on shipments that don’t exist in your TMS at all
Each flag comes with the expected amount, the billed amount and the evidence behind the difference.
A review queue with dispute drafts
Clean invoices move to approval. Flagged invoices go to a queue for your team. For each one, the tool drafts a dispute to the carrier with the PRO number, the charge in question, the contract reference and the supporting documents attached. Your team reviews it, edits if needed, and sends it.
Where your team stays in control
The tool doesn’t pay or dispute anything on its own. You set the rules:
- Which invoices can be auto-approved, for example clean matches under a set dollar amount
- Which carriers or charge types always go to a person
- Who approves disputes before they go out
Every decision the tool makes is logged. If a carrier pushes back on a dispute, your team has the full trail: what was billed, what was expected, and which document proved it.
What it takes to build this properly
A demo version of this is easy. Upload a PDF, extract the total, compare it to a number in a spreadsheet. That version breaks the first week it meets real invoices.
The production version has to handle the messy parts.
Contract logic. Rate agreements have minimums, tiered discounts, lane exceptions and effective dates. Fuel tables change weekly. The tool needs to apply the right version of each rule for the ship date, not today’s.
Shipment matching. Carriers reference shipments by PRO, BOL number, PO number or your load ID, and not always consistently. Matching has to work across all of them and handle partial or missing references without guessing.
Low-confidence extraction. A blurry scan or an unusual layout will produce fields the model isn’t sure about. A production tool knows when it isn’t sure and sends that invoice to a person instead of approving it on a bad read.
Integration with your AP flow. The output has to land where payment happens, whether that’s NetSuite, SAP, Dynamics or a dedicated AP platform. An audit result your team has to copy over by hand isn’t automation.
Security. Invoices contain pricing you negotiated and don’t want shared. The tool runs in your environment or a dedicated one, with access limited to the people who need it.
What you need to provide
Your involvement is small and concentrated at the start:
- Your carrier rate agreements and fuel surcharge tables
- A batch of recent invoices, ideally including a few you know had errors
- Read access to your TMS shipment records
- Someone from AP or freight ops who can answer questions about edge cases and review the first round of results
How the build works
You describe the problem. We turn it into a clear scope: which carriers, which invoice formats, which systems the tool connects to and what counts as done.
You get a fixed price based on that outcome. You pay for a working audit tool, not for hours.
The build is done by AI agents supervised by senior engineers. The engineers own the architecture, review the code and test every integration against your real data. That’s how the work moves at AI speed and still holds up in production.
You get a production-grade tool, deployed and connected to your systems, in days to weeks. The code is yours.
Frequently asked questions
Does this replace our freight audit and payment provider?
It can, or it can work alongside one. Some companies use it to audit everything in-house. Others use it to check their provider's results or to cover carriers the provider doesn't handle.
What if our carriers send invoices in formats you haven't seen?
That's expected. Part of the build is testing against your actual invoice mix. New formats after launch get handled by the same extraction approach, and anything the tool can't read confidently goes to review instead of approval.
How do you handle rate changes and contract renewals?
Rates are stored with effective dates. When you sign a new agreement, it's loaded with its start date, and invoices are checked against whichever terms applied on the ship date.
Can it handle parcel as well as LTL and truckload?
Yes, though parcel has its own surcharge structures and usually its own data feeds. We scope that explicitly if you want it included.
