Before freight software pays a carrier, make it explain the invoice

Key Takeaways

Before a carrier is paid, the person releasing payment should receive a written invoice explanation: one plain-language line per charge saying what it is, how it compares with the booked rate, what supports it and whether it is paid, held or disputed.
The explanation should open with a short summary: booked total, invoiced total, amount ready to pay, amount held and amount disputed.
Every hold should name what is missing, who owes it and what releases the payment.
Wilson, by Cartage, audits and reconciles each carrier invoice against the booked rate and the changes recorded on the shipment, then pays approved amounts from the Wilson Wallet under the company's configured rules.

What should freight software tell you before it pays a carrier?

Before any payment leaves, the software should hand the payer a short invoice explanation that states, line by line and in ordinary words, why each charge is on the invoice, why it differs from the booked rate if it does, which recorded change or document supports it, and what is being held. If the person approving payment has to open an inbox or call the coordinator to understand a line, the software has not finished its job.

The reader matters. The coordinator who ran the load knows why a second stop was added. The accounts payable reviewer who releases payment usually does not, and often sees the invoice weeks later. An explanation written for that reader avoids carrier codes, turns every difference into a sentence and ends each line with a status.

Finding the difference is one step (how AI catches freight invoice errors); proving the evidence chain is another (make the invoice prove what the carrier charged). The explanation is what comes out of both: the document a payer reads and signs off.

The four parts of an invoice explanation

A useful invoice explanation has four parts, in the order a payer reads them.

Header. Carrier, invoice number, the references the invoice carries (PRO, BOL, PO or order number) and the shipment it was matched to.
Summary. Booked total, invoiced total, the difference, then how that difference splits: amount ready to pay, amount held and amount disputed. These figures must add up to the invoice total.
One line per charge. For each invoice line: the charge in plain words, billed amount, booked or expected amount, the reason for any difference in one sentence, the supporting record and the status.
Payment instruction. What will be paid now, under which configured rule, and what has to happen before the held amount moves. If the payment needs a person's approval because it is above a limit, the explanation says so and names the limit.

What goes into each explanation line

Each line is built from records the software already holds, not from the invoice alone.

Start with the booked basis, broken into linehaul, fuel and any accessorial requested at booking. Compare each invoice line with its own booked part, not only the total, since a matching total can hide offsetting errors.

Then translate the carrier's wording. Carrier invoices use codes such as "DET" or "STOP OFF." The explanation line should read "Detention at delivery, 2 hours beyond free time" or "Second delivery stop added after booking," never the code alone.

Next, state the cause of any difference in one sentence that names the change, when it happened and who agreed to it. "Second stop in Dayton added on March 4 at the customer's request; carrier quoted $150 by email; approved by the logistics manager the same day" is an explanation. "Accessorial added" is not.

Then point to the record: the rate confirmation, a carrier message, the bill of lading, the POD, a receipt or a change recorded in shipment history. A payer should be able to open it from the line.

Finally, assign a status: ready to pay, held or disputed. A disputed line states the amount and the reason the carrier will receive.

When should a payer reject the explanation?

Reject the explanation, not just the invoice, when it would leave a reasonable payer guessing. Five patterns are worth refusing in an evaluation:

The reason restates the charge. "Detention: detention billed" explains nothing. The line needs the event and the time.
No record behind a difference. A line marked ready to pay at a higher amount than booked, with no change, message or document attached, should not pass, even if the charge later turns out to be valid.
A hold with no owner. "Needs review" is a status, not a hold. The line should say what is missing (arrival times, a receipt, a confirmation) and who is expected to send it.
Unnamed tolerances. If small fuel differences are accepted below a set amount, the explanation should cite that rule. "Close enough" with no rule is a hidden decision.
Explanation after payment. If the software pays first and explains later, the payer is reviewing history, not approving money.

Two edge cases are telling. A corrected invoice should replace the original, with a line saying what changed between versions. And when a change was agreed by phone and never recorded, the honest line is "agreed verbally, not recorded; confirm before paying," not a guess.

To judge the software, hand its explanation for a past invoice to someone in finance who never saw the load. If they can say what will be paid, what is held and why without asking logistics, it passes. For loads where cost drifted from the original quote, start with where the extra cost came from.

Template: the invoice explanation a payer should receive

Below is the template filled in for one illustrative FTL load. The load was booked at $2,400 linehaul plus fuel on the carrier's schedule, with one delivery stop. The invoice arrives at $3,335. All figures are illustrative.

Summary: booked $2,760 · invoiced $3,335 · difference $575 · ready to pay $2,910 · held $225 · disputed $200.

Charge, in plain words	Billed	Booked or expected	Why it differs	Supporting record	Status
Linehaul, origin to first delivery	$2,400	$2,400	No difference	Rate confirmation	Ready to pay
Fuel surcharge	$360	$360	No difference; matches the schedule at ship date	Rate confirmation, fuel basis	Ready to pay
Second delivery stop added after booking	$150	$150	Customer added a stop; carrier quoted $150; approved before pickup	Carrier email and recorded approval in shipment history	Ready to pay
Lumper fee at the second stop	$225	Not booked	Unloading service at the consignee; no receipt on file yet	Carrier message; receipt requested	Held: carrier owes the lumper receipt
Detention at pickup, 2 hours	$200	Not booked	Carrier claims a wait; pickup arrival and departure times show loading within free time	Pickup confirmation and recorded times	Disputed: $200, times sent to carrier

Payment instruction: pay $2,910 now under the configured rules. Release the $225 when the lumper receipt arrives and matches. Send the $200 dispute to the carrier with the recorded pickup times.

How Wilson, by Cartage, explains an invoice before paying

Wilson audits the invoice against the shipment it booked and ran, then pays from the Wilson Wallet only what the company's rules allow. Wilson, by Cartage, is an AI logistics agent that replaces the TMS for freight execution and connects to the company's ERP.

Because Wilson books with approved carriers, sends the rate confirmation, tracks the load from the best source available and collects the POD, the records an explanation needs already sit on the shipment. Messages, confirmations and changes are recorded in shipment history.

When the carrier invoice arrives, Wilson audits and reconciles it against the booked rate, the documented shipment changes and the supporting evidence. Differences go to review under the company's rules. Once an invoice is audited and reconciled, Wilson pays the carrier from the Wilson Wallet under the customer's configured rules. Payments above approval limits or outside those rules wait for a person, and dispute decisions stay with the team.

Wilson starts with assisted execution, and the company decides how far payment runs within the rules as the workflow earns trust.

Bring a carrier invoice your AP team had to send back to logistics with questions, and see Wilson audit it against the booking before anything is paid.