Freight claims management is the process of identifying, documenting, filing, and resolving claims against carriers for lost shipments, damaged goods, billing errors, and service failures. Done well, it returns real dollars to the P&L. Done poorly, it quietly erodes margin as overpayments, write-offs, and expired claim windows pile up unnoticed.
Most transportation teams know claims exist. Far fewer run claims as a disciplined, data-backed program. The result is the same pattern across industries: a small percentage of eligible claims get filed, an even smaller percentage get recovered, and the rest dissolve into the cost of freight.
This guide covers what belongs inside a modern freight claims program, the mechanics of filing and recovering, the rules that govern carrier liability, and the operating model required to scale claims management across thousands of shipments.
What a freight claim actually is
A freight claim is a formal demand for reimbursement made by the party financially responsible for a shipment, against the carrier that moved it. Claims fall into two broad categories.
Cargo claims cover physical loss, damage, or shortage of the goods themselves. These are governed in the US by the Carmack Amendment for interstate motor and rail freight, which makes the carrier liable for the actual loss or damage to property, subject to contractual limitations of liability.
Freight billing claims cover invoice errors: duplicate charges, incorrect accessorials, misapplied fuel surcharges, rate misapplications, weight or class discrepancies, and charges for services never rendered. These are contract and tariff disputes rather than liability claims, but they flow through the same workflow and the same recovery team in most organizations.
A mature claims program treats both categories as a single discipline. The data sources overlap, the carrier relationships are the same, and the financial mechanics are similar: you spot a discrepancy, you document it, you file within the required window, and you pursue resolution until the credit hits.
The main types of freight claims
How the freight claims process works
The underlying process is similar across carriers, though documentation requirements and portals vary.
1. Detect the exception. The trigger is an invoice that does not match expectations, a delivery receipt with a notation, a POD showing a shortage, or an ERP flag on a cost center. Detection is where most programs fail first. If the only people watching are the operators closing out shipments in the TMS, exceptions that fall outside a small set of obvious failures slip through.
2. Verify the claim is valid. Confirm the carrier moved the freight, the liability applies, the claim falls within the filing window, and the loss is documented. Carriers will reject claims missing any of these elements, and re-filing costs time.
3. Calculate the claim amount. For cargo claims, this is typically the actual invoice cost of the goods plus freight charges, minus any salvage. For billing claims, it is the difference between invoiced and contracted charges. Claim amounts above a carrier's released value limit require separately documented valuation.
4. Assemble documentation. Every claim requires the original BOL, the carrier invoice, proof of delivery, proof of value for lost or damaged goods, and any inspection reports or photos. Billing claims require the contract or tariff that establishes the correct charge. Missing documentation is the single most common reason claims get denied.
5. File within the claim window. Under the Carmack Amendment, carriers can require that cargo claims be filed in writing within a minimum of nine months from delivery or, for non-delivery, from the date delivery should have occurred. Many carrier contracts tighten this window significantly. Billing dispute windows are typically shorter, often 60 to 180 days from invoice date, and vary by carrier.
6. Work the claim to resolution. Carriers acknowledge the claim, investigate, and either pay, offer a reduced settlement, or deny. Denied claims can often be reopened with additional documentation. Settlements below full claim value should be evaluated against the cost of continued pursuit.
7. Post the recovery. The credit needs to land against the correct cost center, PO, or GL account. Without that final step, the money is recovered but the reporting still shows the original overpayment.
The rules that govern carrier liability
A few regulatory and contractual concepts show up in every cargo claim and are worth knowing cold.
Carmack Amendment (49 U.S.C. § 14706). The federal statute that makes motor and rail carriers liable for actual loss or damage to property transported in interstate commerce. It sets the minimum nine-month filing window and two-year suit window, and it preempts most state-law claims against carriers.
Released value. Most LTL and parcel carriers limit liability by commodity class or by a per-pound released value rather than paying actual invoice cost. A pallet of high-value electronics shipped under a carrier's standard class 60 released value will recover a fraction of its real cost unless excess valuation was purchased or a negotiated contract overrides the tariff.
Tariff and contract precedence. Where a carrier contract exists, its claim terms supersede the carrier's base tariff. Many disputes turn on which document governs and whether the claim falls under contract or tariff rules.
Notation requirements. Visible damage must be noted on the delivery receipt at the time of delivery. A clear POD on a damaged shipment is grounds for denial of a later damage claim in most jurisdictions.
Why manual claims management breaks down at scale
The mechanics above are not hard. What is hard is running them consistently across tens of thousands of shipments, dozens of carriers, and multiple ERPs and TMS instances.
Most claims programs break down in four predictable places.
Detection coverage. Manual review samples a fraction of invoices. The shipments that most need claim attention, like edge cases, concealed damage, and accessorial misapplications, are exactly the ones that do not trip standard TMS rules. If only 10% of invoices are audited, the other 90% of claim-eligible errors never surface.
Documentation assembly. Each claim requires pulling documents from multiple systems: BOLs from the TMS, PODs from the carrier portal, invoices from AP, contracts from procurement. Analysts spend more time assembling packets than working the claims.
Filing window expiration. When a claim sits in a queue for weeks, filing deadlines pass silently. Recovery goes from possible to impossible without any event marking the loss.
Carrier follow-up. Carriers do not proactively resolve claims. Every open claim requires periodic email and phone follow-up. Without disciplined cadence, the aged claims list grows and settlement rates drop.
The result is a program where claim recovery is a fraction of what it should be, and the team running it burns out on manual work that is mostly clerical.
Building a scalable freight claims program
A program that actually recovers at scale has four traits.
Complete detection. Every invoice is audited against the contract or tariff, and every shipment is checked for exceptions, not a 10% sample. Without 100% coverage, the claim pipeline starts with a leak.
Unified data. Shipment data, invoice data, contract data, and delivery events live in one place, linked at the shipment level. This is where most teams struggle. Without linked data, claim documentation has to be hand-assembled every time, which limits throughput no matter how many analysts are added.
Policy-driven prioritization. Not every claim is worth filing. A $40 reclass dispute on a carrier you file 50 weekly claims against may not clear a reasonable cost threshold. A program defines thresholds, de-minimis rules, and approval paths in policy, then lets those policies run consistently.
Automated filing and follow-up. Detection, packet assembly, submission, and status polling are heavily rules-based work. The operators who used to do that work move to exceptions only: complex disputes, concealed damage negotiations, and strategic carrier conversations.
Running this model manually is possible but expensive. Running it with the right data foundation and a set of agentic workflows changes the economics of claims recovery entirely.
How Loop supports freight claims management
Loop is a logistics data platform that unifies shipment, invoice, contract, and delivery data and layers AI agents on top of that data to automate high-volume operations work. For freight claims, two Loop capabilities do most of the work.
The Rate Audit Agent audits 100% of carrier invoices against contracted rates, surfacing overcharges, duplicate billing, accessorial misapplications, and contract deviations. This is the detection layer. Instead of sampling, every invoice is checked, and every exception is documented with the underlying contract clause that supports the dispute.
The Carrier Exception Agent takes those detected exceptions through the full claim lifecycle. It assembles the documentation packet, files the claim with the carrier through the carrier's preferred channel, tracks the claim through resolution, and escalates complex disputes to the team with all supporting documents already in place. It is email-native, so carriers do not need to change how they work.
Together, they convert claims management from a sampled, analyst-heavy program into a closed-loop system that catches and pursues every eligible claim, and routes only the judgment calls to people.
For a view of the broader freight audit capability that feeds this workflow, see What is freight audit and payment?. For how claims fit into the wider exception management picture, the upcoming guide on freight exception management will go deeper on the agentic workflow.
Ready to recover more of what you are owed?
If claim recovery at your organization looks more like sampling than a system, the fastest path forward is seeing what complete invoice coverage and automated exception handling look like on your actual data.
