Build a freight-claim file that both operations and finance can use
For customer service, transport operations and finance claims teams · Compare approaches
TL;DR — what you’ll learn
- Build a freight-claim file around the disputed units and the custody handoffs where they were observed.
- Preserve conflicting pickup and delivery counts instead of selecting the more convenient version.
- Record claimed loss, assessed amount, carrier response and actual recovery separately.
- Closing a physical investigation does not automatically close the financial claim.
Topics: freight claims · cargo damage claim evidence · shortage claims · logistics claims workflow

Illustrative logistics operations desk overlooking a warehouse floor; not a client facility.
All quantities, amounts, product codes and events are illustrative teaching examples.
A consignee reports three missing cartons from a wrapped pallet. The pickup record says forty cartons, the delivery count says thirty-seven, and the driver says the outer wrap was intact. Operations starts searching; finance receives a request to deduct the goods value from the next freight payment.
Build one shared case that connects the physical evidence to the commercial decision. An intact wrap is an observation about packaging. It does not, by itself, prove the original count, the location of a loss or which party owes compensation.
State the disputed fact precisely
Define the shipment, package identifiers, item and unit of measure. A shortage of three cartons means little if the sender counted cartons and the receiver counted inner boxes. Preserve the packing configuration and conversion applicable to that shipment.
Use the consignment or shipment reference to locate the journey, then link the handling-unit identities. GS1's Logistic Label Guideline describes using an SSCC to identify a logistic unit and connect physical movements with messages. An identifier supports linkage; it is not proof of a package's contents. GS1 Logistic Label Guideline — release 1.3, July 2019
Write the issue as a testable statement: “Sender's dispatch record lists forty cartons on pallet P-17; destination observed thirty-seven at opening.” Keep “three cartons lost in transit” as a hypothesis until the evidence supports it.
A case with a disputed pickup count
The following figures are illustrative. The dispatch pack sheet records forty cartons. A signed pickup note records thirty-nine. The destination records thirty-seven. All records refer to the same shipment, but the reason for the pickup discrepancy is unresolved.
Scroll horizontally to see all columns.
| Evidence | Quantity | What it establishes |
|---|---|---|
| Sender pack sheet | 40 cartons | Sender's recorded preparation |
| Pickup acknowledgement | 39 cartons | Recorded handover quantity, subject to its qualifications |
| Destination opening count | 37 cartons | Observed receipt quantity |
| Later carton located at destination | 1 carton | A receipt-side correction after identity confirmation |
Initially, the sender-to-destination difference is three cartons. The acknowledged-pickup-to-destination difference is two. Those are different questions; neither should be overwritten by the other.
After the identified carton is located, destination receipt becomes thirty-eight. The remaining difference is two against the pack sheet and one against the pickup acknowledgement. The case needs to explain the missing carton at the sender-to-carrier boundary as well as the remaining journey difference.
If the illustrative claimed goods value is ₹1,250 per carton, the initial gross claim is ₹3,750. Finding one carton reduces that gross claimed shortfall to ₹2,500 on the sender's basis. It does not establish that ₹2,500 is recoverable. Contractual valuation, scope, applicable terms and the accepted evidence still need the authorised commercial review.
Do not net salvage, replacement supply, insurance proceeds and carrier recovery together without distinct records. Otherwise the same loss can be counted twice or a customer replacement mistaken for money received.
Build a chronology that can survive disagreement
Collect source records in their original form: dispatch count, pickup acknowledgement, package and seal observations, hub handovers, delivery exceptions, photos, correspondence and later findings. Attach each to the event it supports, with event time, capture time, author and timezone.
A photo should identify the package and show what it was intended to demonstrate. A wide shot of a pallet may show visible damage but cannot prove an obscured count. Preserve the original file and any annotated derivative separately. Record that a seal was observed intact only when someone actually checked it.
Carrier portals may present different operational choices for a short multi-piece shipment. Delhivery's B2B guidance, for example, distinguishes delivery of available pieces from waiting for the missing pieces. Capture the chosen instruction and its acknowledgement. Delhivery — B2B exceptions management
That instruction changes the operational path. It does not settle the claim's liability or value. If the missing pieces are later delivered, append the receipt evidence and update the open quantity without erasing the initial exception.
Give each unresolved decision an owner
Scroll horizontally to see all columns.
| Decision | Owner to assign | Evidence needed for closure |
|---|---|---|
| Which quantity was handed over? | Dispatch and transport operations | Reconciled handover records |
| Where are the missing units? | Investigation coordinator | Located-unit identity or documented search result |
| What amount is being claimed? | Finance with commercial owner | Approved valuation basis and quantity |
| What does the carrier accept or dispute? | Carrier relationship owner | Written response tied to claim version |
| Has recovery actually occurred? | Finance | Bank, credit or authorised settlement reference |
Maintain a deadline register derived from the applicable contract, carrier procedure and qualified advice where needed. Enter the exact source, triggering event and due date. Do not assume that a portal submission extends another notice requirement. Assign an owner to a deadline even while the investigation remains open.
Use separate physical and financial closure states
A practical case may be “physical investigation complete, commercial review open” or “carrier accepts amount, recovery pending.” Those states are more useful than a single closed checkbox.
In an illustrative settlement, the carrier accepts ₹1,250 and finance receives a documented ₹1,000 credit. The accepted amount still awaiting settlement is ₹250. Any difference between the gross ₹2,500 claim and accepted ₹1,250 remains a separate disputed or written-off amount under approval; it is not a missing bank receipt.
A shared case folder with a structured register may serve a small operation. A case-management workflow becomes useful when ownership changes, deadlines overlap or recoveries span multiple documents. Require an export that includes attachments, decisions and relationships so the case remains understandable outside the application.
Evaluate the process by taking a closed case and reconstructing its quantity bridge, claim amount and recovery. Also test a reopened case after goods are found. Measure aged unresolved decisions and recovered amounts against accepted claims, without calling every submitted claim a saving.
Make the file useful to the next decision maker
A good claim file carries the disagreement forward accurately. Operations can investigate the units, the commercial team can assess entitlement and finance can reconcile the result without rewriting the history.
Next actions
- Write the disputed quantity at each custody boundary.
- Attach original evidence and retain conflicting versions.
- Assign owners and sourced deadlines to the remaining decisions.
- Reconcile claimed, accepted and recovered amounts before closure.
For a claim-workflow assessment, describe the handoff where evidence is usually lost and how finance currently records recovery.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Draft an assessment emailReferences
Sources checked 15 October 2026. Vendor documentation supports platform facts; the worked examples and diagrams are original.
- Delhivery — B2B exceptions managementAccessed 15 October 2026.
- GS1 Logistic Label Guideline — release 1.3, July 2019Accessed 15 October 2026.