At a glance
- A three-way match compares the carrier invoice with the BOL and the POD, using the rate confirmation as the price reference, keyed by PRO number or load reference.
- Four discrepancies anchor the routing logic: duplicate invoice, unapproved accessorial, weight or class mismatch, and missing POD. Each has a flag and a named human decision.
- The agent flags and shows both values. Approving a disputed charge or a borderline carrier for payment stays with the broker's own AP staff.
- The hard part is the POD itself: a scan or phone photo has to be read before it can be matched, and a read that is not trustworthy has to reach a person.
Freight invoice audit automation checks each carrier invoice against its POD and BOL before payment. That matters to a broker or 3PL because an overpaid invoice can come out of the broker's own margin. This article starts at invoice receipt; carrier onboarding is upstream and not covered.
Why carrier invoices don't always match the rate confirmation
A rate confirmation is the broker's document for one load. It records the agreed rate, and one trade publication lists accessorials such as detention and layover among the items a rate con outlines[1]. The invoice, by contrast, is built later by the carrier's billing process, after the load has moved.
When the invoice and rate confirmation differ, check whether:
- a charge was added after the rate confirmation was signed;
- a revised rate confirmation never reached settlement;
- the carrier's billing system applied its own default rate or fee.
Unplanned events are one reason. A 2011 Logistics Viewpoints article reports a shipper's manager saying that "you can never totally get your hands around unplanned accessorials"[2]. The remedy is to compare the documents, not to assume either side is wrong.
The three-way match: invoice, BOL and POD
A three-way match compares a carrier invoice with two shipment documents: the bill of lading (BOL), which describes the freight handed to the carrier, and the proof of delivery (POD), which shows the receiver took it. The PRO number, the carrier's shipment reference, or your own load number ties the three together; the rate confirmation supplies the agreed price.
How do you check that a carrier invoice matches the bill of lading?
Compare the fields the two documents share: shipper and consignee, pieces, weight, and reference numbers. Then check the delivery against the POD. We recommend the order below, so every packet gets the same checks.
- Key the packet to one load
Use the PRO number or load reference to group the invoice, BOL, POD and rate confirmation. If no reference matches, the packet is an exception before any other check runs.
- Check the price
Compare linehaul and fuel on the invoice with the rate confirmation and any revision.
- Check the freight
Compare pieces, weight and class on the invoice with the BOL, and shipper and consignee names with the load.
- Check the delivery
Confirm the POD shows delivery to the right consignee, with a date and a signature or other receipt mark, and note any exceptions written on it.
- Check every other line
Each non-linehaul charge needs a basis on the rate confirmation or documented support. Compare the invoice against invoices already received to catch repeats.
- Route the result
A clean packet goes to the payment queue under your approval policy. Anything else goes to the exception table's owner, with both values shown.
None of this is new logic. A 2011 Logistics Viewpoints article describes a TMS freight audit engine that "looks at the total bill, as well as the linehaul and accessorial costs," with tolerances set "by dollar amount or as a percentage of the total bill variance"[2]. What an AI agent adds is reading the BOL and POD that reach you as documents, so those comparisons can run at all.
The exception table: what gets flagged, and who decides
The table lists four core discrepancies plus two that follow from the same checks. The middle column is what the agent shows; the last is a decision that stays with your AP staff.
| Discrepancy | How an AI agent flags it | Human decision before payment |
|---|---|---|
| Duplicate invoice | Compares carrier, PRO or load reference, invoice number, amount and date with invoices already received, and holds the newer one beside the first. | AP decides: duplicate to reject, corrected invoice that replaces the first, or a legitimate second bill. Nothing is paid until a named person picks. |
| Unapproved accessorial | Marks any non-linehaul line that is absent from the rate confirmation or its revisions, and lists the support it found, such as timestamps, a notice, or a note on the POD. | Approve, request more support, or reject that one line. The settlement lead sets whether the clean lines wait or are paid. |
| Weight or class mismatch | Shows the invoice's weight, piece count and class beside the BOL's, with the difference and the field each came from. | AP decides which figure stands, and whether to ask the carrier for a weight ticket or corrected invoice before paying. |
| Missing or unusable POD | Reports no POD in the packet, or a POD with no date, no receipt mark or an unreadable image, and says which. | AP decides whether to hold, chase the carrier or the consignee for a better copy, or accept other evidence of delivery under your policy. |
| Linehaul differs from the rate confirmation | Shows invoiced linehaul and fuel beside the agreed figures, and checks whether a revised rate confirmation exists for the load. | Accept a documented revision, or return the invoice for correction. Paying a higher figure without a revision is an AP-lead decision. |
| Reference or consignee mismatch | Flags the document that disagrees: a PRO number, consignee or date that differs between invoice, BOL and POD. | AP decides whether the packet belongs to a different load, a typo explains it, or the carrier must resubmit. |
The agent never pays, rejects or short-pays on its own. This is the pattern in checking each invoice line against policy terms, a pattern that suits carrier invoices too. The approval step follows document review with human approval.
Auditing accessorial charges: detention, liftgate and layover
Audit each accessorial as its own line with its own evidence: what it is, where the rate confirmation allows it, and what proves it happened. The definitions below come from one payments blog; your rate confirmation terms govern.
| Charge | What it covers | Evidence to require |
|---|---|---|
| Detention | "If a carrier is delayed for any reason (over 2 hours) at a shipper/receiver, detention charges may apply."[3] | Arrival and departure times, any notice the rate confirmation requires, and the detention terms on that load's rate confirmation. |
| Liftgate | "When shipments are being delivered to locations with no loading dock, they must use liftgate equipment."[3] | A liftgate request on the booking or rate confirmation, and a delivery location without a dock. |
| Layover | "A charge will apply if the truck is unable, for whatever reason, to be unloaded/loaded during its slated delivery day."[3] | Proof the delivery day was missed and why, plus the layover term on the rate confirmation. |
Why this is harder than it looks: PODs as scanned and photographed documents
Yes for a clear POD; a poor scan needs a person. EDI invoices arrive as structured fields; a POD may not. Shipwell's help center lists the formats its shipment document upload accepts as "Supported formats: PDF, PNG, JPG."[4] A POD uploaded as an image can be a flatbed scan or a phone photo taken at a dock, with creases, glare and a signature across the date.
Shipwell describes processing a packet of an invoice plus related settlement documents, including POD and BOL, through "a document classifier followed by an information extraction model"[5]. It also states that "like any technology it is not perfect and there is the possibility of mistakes"[5], and offers the ability to reclassify documents believed to be incorrect[5]. This is how the product describes itself, not evidence of performance.
Reading is a source of exceptions, not only matching. We recommend that a field the agent cannot read with confidence becomes the "unusable POD" flag, and that the reviewer sees the image beside the extracted fields. A guessed delivery date that silently passes is worse than a visible miss.
- Classify each page first, so a lumper receipt is not read as a POD.
- Show the original image next to every extracted value the match relies on.
- Treat a missing date, a missing receipt mark and an unreadable page as three different flags.
What stays human: borderline carriers and disputed charges
Approving a disputed charge, or paying a borderline carrier, is the organization's own operating choice and stays with the broker's AP staff. The agent prepares the file: both values, the evidence found, and the relevant rate confirmation clause.
Write the decision rights down: who may approve an exception, who may release a held payment, and who reviews approvals afterward. An agent that proposes a payment should never authorize it.
When this doesn't apply
- If your TMS audit engine already matches your carriers' EDI invoices to rate confirmations within tolerance, adding an agent for those invoices adds little. Use it for documents the TMS cannot read.
- At low invoice volume, a checklist and a second pair of eyes may cost less than any tooling.
- If you outsource audit-and-pay to a freight audit provider, the matching is theirs. Your decision rights over disputed charges still need writing down.
- Nothing here fixes a missing rate confirmation. If loads are booked by phone with no written terms, there is nothing to match the invoice against.
Frequently asked questions
How do I know if a carrier invoice matches the actual bill of lading?
Compare the fields both documents carry: shipper, consignee, pieces, weight, class and reference numbers. Then check the delivery against the proof of delivery. Show both values side by side, and send any difference to a named person in AP. We recommend running the same checks in the same order on every packet.
What's the best way to catch freight billing errors before paying carriers?
Match every carrier invoice to its rate confirmation, bill of lading and proof of delivery before it enters the payment queue. Flag duplicates, unapproved accessorials, weight mismatches and missing delivery proof, and let a named person decide each flagged item. Catching errors before payment avoids recovering money from the carrier afterward.
How do freight brokers audit accessorial charges like detention and liftgate fees?
Treat each accessorial as its own line. Check that the rate confirmation or a revision allows it, then ask for evidence that it happened: arrival and departure times for detention, a booked request and a dockless delivery for liftgate. A person decides whether to approve, query or reject the line.
Can AI automatically match PODs to invoices without manual data entry?
It can read a clear POD and key it to the invoice by PRO or load reference, which removes the keying for that document. It cannot be trusted on every scan, so a blurry or incomplete POD should become a visible flag and reach a reviewer who sees the original image beside the extracted fields.
Why do carrier invoices so often not match the original rate confirmation?
The invoice is produced after the load moves, from the carrier's own billing process. A charge may be added after the rate confirmation was signed, a revision may not reach settlement, or a default may apply. Comparing the two documents line by line shows which side the difference came from.
Related reading
- Insurance invoice analysis describes the invoice-checking pattern this article applies to carrier invoices.
- Document review with human approval covers the approve-or-escalate step used for exceptions.
- Our AI agent implementation service covers design, a staged build with acceptance gates, and handover for one chosen workflow.
- See the logistics industry page for the wider set of broker back-office workflows.
Sources
- [1] — FreightWaves, How to Read Your Rate Con Like a Pro (2025-05-15) (accessed 2026-10-29)
- [2] — Logistics Viewpoints, Auditing Freight Bills with a Transportation Management System (TMS) (2011-04-18) (accessed 2026-10-29)
- [3] — RoadSync, Definitions of Common Accessorial Charges (2021-12-14) (accessed 2026-10-29)
- [4] — Shipwell Help Center, Uploading and Deleting Documents on a Shipment (2026-06-25) (accessed 2026-10-29)
- [5] — Shipwell Help Center, Settlement: In-App Uploaded Rendition and Invoice Packet (2024-03-01) (accessed 2026-10-29)
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsGroup and Folio Billing Audit: Catching the Leak Types a Normal Error Check Misses
A group and folio billing audit for hotel management companies: a leak-type table of rate code mismatches, missing closes, adjustments, orphaned charges.
Hotel Management Companies