Freight audit and payment: compare quotes, PODs and invoices
Key Takeaways
Give the vendor a carrier invoice with one line that does not match the booking. Ask it to identify the difference, show the evidence and explain what happens before payment. In Wilson, one mismatched line sends the whole invoice to a person. Wilson does not make partial payments.
- Use a rate confirmation, shipment record, POD and invoice together.
- Test a disputed charge and a valid charge.
- Keep the full invoice waiting when a line does not match.
- Show who must decide and what information they receive.
- Test a corrected invoice without creating a second payment.
Why does a disputed bill make a useful demo?
A clean invoice shows whether freight audit and payment software can recognize an ordinary match. A disputed invoice shows whether the next action is clear when the bill differs from the shipment agreement. Both cases matter.
Use a small set of sample documents with names and private details removed. Keep the shipment facts consistent across the documents. The test should reveal a real comparison problem, not a confusing collection of unrelated files.
Write the expected result before the demo. For example: “The extra charge is identified, the invoice is not released automatically and the responsible person receives the booking terms and the supporting shipment records.” This is a proposed test condition, not a claim that every product works this way.
An AI logistics coordinator should not earn a pass only because it finds a price difference. The buyer needs to see what happens to that invoice, who owns the question and how the eventual decision stays connected to the shipment.
The invoice review guide explains the broader audit process. Use this article as a focused demonstration script for a disputed line.
What documents should you bring?
Bring the accepted rate confirmation, the carrier invoice, the shipment identity and the relevant service evidence. Include a POD if the delivery is complete. Add any later approved change that affects the price.
The rate confirmation shows the booked commercial terms. The POD shows delivery evidence. A signed POD does not by itself prove that every extra invoice charge was agreed. Keep those roles clear in the demonstration.
Use the same load number and billing party throughout. If the carrier references another number, include the mapping. A correct amount attached to the wrong load still needs attention.
If a document is missing, keep the gap visible. Ask what happens while the vendor requests it. A system should not turn “we have not received the rate confirmation” into “the billed rate matches.”
For a detention example, include arrival and departure records plus the agreed terms. For a delivery-service example, include the request and evidence of the service. The point is to test the relevant fact, not to send every document the company owns.
How can you create a simple disputed-line test?
Use a fictional booking with a $1,400 linehaul charge and $150 fuel charge. The accepted total is $1,550. Then add a $120 liftgate line to the invoice, giving a billed total of $1,670. State that all figures are illustrative.
| Record | Amount in the example | Question for the demo |
|---|---|---|
| Booked linehaul | $1,400 | Does the invoice use the accepted amount? |
| Booked fuel | $150 | Does the charge match the agreement? |
| Added liftgate | $120 | Was this service agreed or later authorized? |
| Invoice total | $1,670 | What waits while the extra line is reviewed? |
Do not tell the software that the liftgate line is automatically wrong. Give it the facts needed to check. In the first version, the load required no liftgate and there was no approved change. In a second version, provide a valid authorization and the agreed fee. The expected outcomes should differ.
Ask the presenter to open the shipment and show the exact evidence used. A color on a dashboard is not enough to explain the disputed amount. The person reviewing the bill should be able to understand the issue without rebuilding the shipment from an inbox.
Keep the test focused on the mismatch. Questions about tax treatment or legal liability belong with the company’s responsible specialists and actual agreements. This operating test does not decide them.
What should Wilson do before payment?
Before paying from the Wallet, Wilson audits each carrier invoice against the POD and the rate confirmation. Customers can require a signed POD before payment releases. Anything outside their rules goes to a person for approval.
If any line does not match what was booked, the whole invoice waits for a person. Wilson does not pay the undisputed amount while holding only the disputed line. In the fictional test, do not expect an automatic $1,550 payment against the $1,670 invoice.
Ask to see the human handoff. It should make the invoice, disputed line, booking terms, available evidence and requested decision clear. Confirm which notifications and review controls are available for the customer’s setup.
Keep booking approval separate from payment approval. A manager’s permission to book the original shipment does not automatically explain a new service fee on a later invoice. The reviewer needs the actual change and its authority.
Use the Cartage demo to test these steps with your rules. The demonstration should not release real funds. A simulated payment decision is enough to review the workflow.
What happens when the carrier corrects the bill?
Continue the demo after the first mismatch. Have the carrier send a corrected invoice removing the unsupported line, or provide the evidence and authorized decision that resolve it. Watch how the new document connects to the original bill.
The review should leave a clear current obligation. Two versions of one invoice should not look like two separate full amounts to pay. Ask how original references, revised amounts, credits and any prior payment are represented.
Check the total again after the correction. Removing a line may affect related calculations under the agreement. Do not assume that the corrected document is right simply because it has a new date or says “revised.”
Keep the evidence of the decision. A short note such as “carrier corrected invoice after unsupported liftgate charge” should link to the documents that explain it. If a person approves an exception instead, preserve that decision within the available workflow.
Do not assume a particular credit-processing or accounting feature. Ask Cartage to show the supported process for the customer’s invoice and Wallet arrangements. This article describes what the buyer should verify, not an untested accounting integration.
What should count as a pass?
A useful demo shows the right invoice matched to the right load, an explained difference, the correct payment boundary and an owned next step. It also shows how the case becomes resolved. A permanent red flag with no owner is unfinished work.
Run a clean invoice as a second test. The vendor should distinguish a genuine mismatch from an agreed fee. Otherwise the team may replace manual auditing with a large list of unnecessary reviews.
Add a missing signed POD when your policy requires one. The invoice should follow that rule even if all amounts match. Then add the POD and inspect what remains before release. Document collection and charge matching are separate checks.
Finish with a short result sheet: passed, failed or not demonstrated for each step. Save the exact question that remains open. “We can configure that later” is a scoping answer; it is not evidence that the configuration worked in the demo.
Freight audit is useful when it leads to a supported decision. Choose freight audit and payment software by the full review path, including exceptions, rather than by the number of fields on the first screen.
FAQs
Can Wilson pay only the undisputed amount?
No. If any line does not match what was booked, the whole invoice waits for a person. Wilson does not make partial payments.
Does a signed POD prove every charge is correct?
No. It provides delivery evidence. Wilson also checks the invoice against the rate confirmation. Extra charges need the relevant agreement and shipment facts.
What is the simplest disputed-invoice demo?
Use one accepted booking, one invoice with an added line and the related shipment records. Ask the vendor to show the mismatch, payment boundary, reviewer handoff and resolution.
Should the demo make a real carrier payment?
No real payment is needed to evaluate the workflow. Agree a safe test that shows the decision and required controls without releasing funds.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai