Why Shippers Cannot Verify Their Freight Bills
Freight is usually the largest line in logistics spend, yet many shippers pay carrier invoices almost exactly as billed. The reason is not a lack of will but a lack of means.
Consider the scale. For a shipper spending ₩300 million a month on freight, an overbilling rate of just 2% means ₩6 million a month, or ₩72 million a year. Most of it is clerical error on the carrier's side and not bad faith, but if the shipper does not find it, it simply becomes cost.
The Three Data Sets That Define "Correct"
Freight audit is less about reading invoices and more about having something to compare them against.
These three must be tied together by a common key at the shipment level. The most reliable approach is to make the shipper-issued dispatch number (transport order number) the primary key and require, in the contract, that carriers quote it on every invoice line. For lines that arrive without it, keep a fallback key built from loading date, vehicle number, and origin–destination.
Making Rate Contracts Machine-Readable
A rate written in a contract PDF can only be read by a person. Automated audit requires turning it into rule data.
Contract versions and effective dates have to be managed alongside these rules. Billing at the old rate in the month a rate changed is the most common error of all, and the system must be able to decide which version applies based on the shipment's loading date.
Automated Matching and Exception Handling
Once the reference data is in place, the flow is simple. Calculate the expected charge first from the shipment record, compare it with the billed amount, and auto-approve anything within tolerance.
Suppose an 11-ton truck on the Seoul metropolitan area–Busan lane has a base rate of ₩450,000, a 5% fuel surcharge (₩22,500), and ₩20,000 in detention for one hour beyond the one free hour. The expected charge is ₩492,500. If the invoice says ₩520,000, the difference is ₩27,500 (about 5.6%), and with a tolerance of "1% or ₩1,000 per shipment," this line goes to the exception queue.
Each exception gets a reason code: duplicate billing, rate version mismatch, truck class mismatch, accessorial without evidence, billing with no matching shipment, and so on. The discussion with the carrier and the final adjusted amount are recorded per shipment. Only when that history accumulates can you identify carriers that repeat the same type of discrepancy.
Extending Settlement Data into Logistics Cost Analysis
Audited settlement data is also shipment-level freight cost data, already cleaned.
With these figures, rate renegotiation and carrier reallocation rest on evidence, not on impressions. The data also shows when the problem is not the rate at all: a delivery point that keeps generating detention charges needs a different receiving appointment process, not a cheaper carrier.
Scoping the Build: TMS Features vs. a Dedicated Settlement System
If you already run a TMS, the practical approach is to pull dispatch and shipment records from it and build only the rate engine and matching logic separately. Standard TMS settlement modules often struggle to express a shipper's more complex accessorial rules. The integration point with ERP is where approved settlement amounts are posted as payable entries.
We recommend a phased rollout.
Freight Settlement Systems Built by POLYGLOTSOFT
POLYGLOTSOFT builds custom freight settlement systems, covering a rate engine shaped to your contract structure, automated invoice matching, exception workflows, and TMS and ERP integration. With our subscription development service, you can start small with rate digitization and widen the scope step by step. If you need a baseline to check your freight invoices against, contact POLYGLOTSOFT.