Freight audit and payment software: the buyer’s control checklist

Key Takeaways

Freight audit and payment software should be bought on its controls: the rules that stop a wrong payment and show why a right one was released.
Require nine controls: a shipment match, a four-way comparison, approval limits, a duplicate check, holds, dispute handling, a named release authority, recorded rule ownership and a payment record.
The comparison should cover the booked rate, documented shipment changes, supporting evidence and the carrier invoice, not the invoice against a rate table alone.
Operations confirms what happened on the shipment; finance owns who can release money. Software that blurs the two weakens both.
Wilson, by Cartage, audits and reconciles each carrier invoice against what was booked and pays carriers from the Wilson Wallet under customer-configured approval rules.

Which controls should a buyer require from freight audit and payment software?

A buyer should require controls at three points: what the invoice is compared to, what stops a payment, and who can release it. If a vendor can show each control working on a real invoice, the software is reducing payment risk. If it can only show a dashboard of flagged charges, the controls still live in someone's inbox.

Most evaluations focus on detection. But a flag that nobody owns doesn't stop a payment. When a charge doesn't match, does the payment stop automatically? Who can override it? Is the reason written down where the next reviewer will find it?

There is also a placement question: whether audit happens inside the software, through an outside service or as a step in freight execution. That trade-off is covered in freight audit software or an outsourced audit service. The checklist here applies whichever model a buyer picks, because the payment still needs the same controls.

The control chain from carrier invoice to released payment

Each invoice should pass through six stages, and each stage should have a control that can stop it.

Match. The invoice is tied to one shipment by PRO number, bill of lading, load reference or carrier invoice number. No match, no payment.
Compare. The charges are checked against the booked rate and the services that were agreed.
Explain. Any difference is tied to a documented shipment change and supporting evidence, or it stays open.
Decide. Approval rules decide whether the invoice can be paid as billed, needs a person or goes to dispute.
Release. Only the people or rules the company has authorized can release payment.
Record. The match, the comparison, the decision and the payment stay on the shipment.

Software that lets a payment be approved before the comparison is complete has the chain backwards.

What the comparison and the stops look like in practice

The audit is a four-way comparison, and a two-way one misses most of what goes wrong.

The booked rate comes from the rate confirmation or the agreed quote, including any accessorials that were accepted at booking. Documented shipment changes are things like an approved redelivery, a reweigh, a reclassification or a carrier change after a cancellation. Supporting evidence is what proves a charge: the POD, weight or inspection documents, arrival and departure times behind a detention charge. The carrier invoice is the claim. A charge is payable when all four line up; the work of assembling that evidence is laid out in make the invoice prove what the carrier charged.

The duplicate check needs more than an exact invoice-number match. Rebills often arrive with a suffix on the invoice number, a different amount after a correction, or the same PRO number on a second invoice. Require the software to check the shipment as well as the number, and ask what happens to a corrected rebill when the original was already paid. That seam is where duplicates usually get through.

Holds should be specific. "On hold" is not a control unless the hold carries a reason, an owner and a condition that releases it, such as missing POD, a charge awaiting evidence or an open carrier dispute. Dispute handling should keep the carrier's response, the evidence sent and the outcome on the shipment, so a credit or a revised invoice is matched to the original.

Decision rules: where a buyer should draw the lines

Set the limits before the software arrives, and make the vendor configure them in front of you.

Approval limits by variance, not only by invoice total. A large invoice that matches the booking exactly may need less review than a small one with an unexplained accessorial. Illustrative example: a load booked at $1,850 arrives invoiced at $2,090, with a $240 detention line. Under an illustrative rule, a variance with complete evidence under $150 is paid; anything above waits for a logistics manager. This invoice waits.
Release authority separate from rule-setting. The person who changes approval limits should not be the only person who can release an exception payment.
No booking, no auto-pay. An invoice for a load that has no booked shipment, such as a spot move arranged by phone, goes to a person every time.
Carrier changed mid-shipment. The final invoice is matched to the rate agreed with the carrier that actually hauled it, and the cancelled booking is closed.
Invoice before proof of delivery. Hold until delivery is confirmed, unless the company's rules say otherwise for that carrier or mode.
Rule changes are recorded. When a limit changes, the record should show the new value and when it changed.

A buyer with formal compliance requirements should confirm with finance and internal audit how the software's records map to those requirements before relying on them.

The buyer's control checklist

Use one real invoice that didn't match its booking, and mark each control pass or fail during the evaluation.

Control	Require	Ask the vendor to show	Red flag
Shipment match	Every invoice tied to one shipment	An invoice with a wrong PRO number	Unmatched invoices go to a general queue
Four-way comparison	Booked rate, changes, evidence, invoice	A charge added after booking	Comparison against a rate table only
Approval limits	Variance-based limits the company sets	The limit changed and enforced live	Limits fixed by the vendor
Duplicate check	Shipment-level, not number-only	A rebill with a suffixed invoice number	Duplicates found after payment
Holds	Reason, owner and release condition	An invoice held for missing POD	"On hold" with no reason
Disputes	Evidence and carrier reply on the shipment	A disputed accessorial through to credit	Disputes tracked in a separate sheet
Release authority	Named people or rules release payment	Who can override a held payment	Anyone with a login can pay
Rule ownership	Rule changes are recorded	The record of the last limit change	No record of who changed a rule
Payment record	Payment tied to invoice and shipment	The full history behind one payment	Payment visible only in the bank file

A vendor that passes the first three rows but can't show holds, disputes and release authority is selling detection, not payment control. Operational controls for invoices already in flight are covered in freight invoice controls to test before carrier payment.

How Wilson, by Cartage, applies these controls

Wilson audits, reconciles and pays as the final steps of shipments it already ran, so the comparison starts from the booking Wilson made. Wilson quotes, books, tracks and delivers freight across LTL, FTL, parcel, ocean, drayage and cross-border, and it replaces the TMS for freight execution while connecting to the company's ERP.

When a carrier invoice arrives, Wilson matches it to the shipment and compares it to the booked rate, documented shipment changes and supporting evidence such as the POD. Charges that don't match go to review under the company's rules. Once the 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 the rules, wait for a person. The company decides who approves and where the limits sit.

Messages, confirmations and changes are recorded in shipment history, so the reason behind a held or paid invoice stays with the load. Wilson starts with assisted execution, and the scope of what runs within the rules can expand step by step. Wilson does not present its records as a compliance-grade approval ledger; buyers with formal requirements should review that with their finance team.

Bring a carrier invoice that didn't match its booking last quarter, along with the approval limits you'd want enforced, and see Wilson audit it, hold it and route the payment decision under those rules.