Proof of delivery: what makes a PoD defensible, and why yours is hard to find
A proof of delivery records who received a consignment, when, how many pieces, and in what condition. It decides whether a freight claim survives, whether an invoice gets paid, and whether a customer's deduction sticks. Here is what belongs on the document, the notice and filing windows that govern it by mode, and why retrieval — not capture — is the problem that bites multi-carrier shippers.
This is one document type inside a wider problem. The parent module, Document Management, covers customs readiness and claims evidence across the documents a shipment carries. If you need the shipment-side signal that a PoD is now due, that is Shipment Visibility; last-mile delivery events come from Parcel Visibility.
What proof of delivery means
Proof of delivery (PoD) is the document that records a consignment being handed over: who received it, when, how many pieces, and in what condition. Electronic proof of delivery (ePOD) is the same record captured digitally at the point of delivery instead of on a paper delivery receipt. Both are evidence, and evidence is the whole point — a PoD only matters on the day someone disputes something.
Three parties come looking for it. Your carrier's AP process wants it before releasing a freight invoice. Your customer's AP process wants it before releasing yours, or cites its absence as grounds for a deduction. And a claims adjuster wants it when $18,000 of product arrives crushed. All three arrive on different clocks, and all three are satisfied or defeated by the same sheet of paper.
A PoD is closer to a witness statement than a receipt. What is written on it at the dock — and what is left blank — determines who carries the burden of proof for the next twelve months.
| Field | What it proves | What its absence costs you |
|---|---|---|
| Signature plus printed receiver name | Someone with authority accepted the goods | “Left at door” or an illegible mark. Carrier says delivered, consignee says nothing arrived, you reship and eat it |
| Date and time of delivery | Whether the delivery hit the appointment or window | No way to prove on-time. Detention, late-fee and OTIF disputes resolve in the carrier's favour |
| BOL / PRO / order reference | Ties the document to the shipment, order and invoice | The PoD exists and nobody can find it — functionally identical to no PoD |
| Pieces or pallets received vs. tendered | The shortage happened in transit, not in your DC | A transit shortage becomes an internal warehouse argument you lose |
| Condition notes and exception codes, written at delivery | Damage was visible on arrival | A clean signature is the carrier's strongest defence. See the worked example below |
| Photos at the tailgate | Nature and extent of damage, pallet and wrap condition | Adjusters discount or deny for want of contemporaneous evidence |
| Seal number and, for reefer, the arrival temperature reading | Chain of custody and cold-chain integrity | Load-integrity, tampering and spoilage claims collapse |
| Refused or returned quantity | What actually stayed with the consignee | Credit memos, reverse logistics and inventory records diverge from reality |
A PoD that cannot be produced within your shortest dispute window is not evidence. It is a filing problem with a legal consequence.
ePOD capture is not the same problem as PoD retrieval
These get conflated constantly, and they have different owners and different fixes.
Capture — at the tailgate
Someone puts a device in the driver's hand, the receiver signs, the app timestamps and geotags it, photos attach, the record syncs. Capture is a field-operations problem. If you run your own fleet or your own final mile, that is you. If you tender to forty carriers, it is emphatically not you — you are buying transportation, and the PoD is captured in someone else's system on someone else's app.
Retrieval and matching — afterwards
The document exists. It is in a carrier portal, behind an image link referenced off the freight invoice, in an emailed scan from a regional dispatcher, or in a 3PL's document store. Your job is to get it, read the references off it, and attach it to the right shipment, order line and invoice — before the deduction window closes and before the carrier's retention policy archives the image.
The two get bought interchangeably, and they solve different halves. An ePOD app improves the documents you capture yourself — if you run your own fleet or your own final mile, it is the right tool and it works. What it cannot do is reach into a document a third party captured in their system. If most of your volume moves on carriers you do not employ, capture tooling leaves that volume exactly where it was.
If most of your freight moves on carriers you do not employ, the PoD gap is a data problem, not a devices problem.
The document is written by someone who does not work for you
The person who decides whether your claim is winnable is a receiving clerk with two more trucks in the yard and a driver waiting on a signature. They are not weighing your exposure. They are clearing the door.
Which is why the fields that matter have to be ones a clerk can complete without stopping to think: pieces received, damage seen, photo taken. Anything that needs interpretation gets left blank — and blank is what the carrier defends with.
Why PoDs go missing in a multi-carrier network
Nobody sets out to lose the document. It goes missing structurally, for five reasons that compound.
It lives in the carrier's system, not yours
Forty carriers means forty retrieval workflows, forty credential sets, forty image formats and forty retention policies. Image availability windows vary widely by carrier — some publish scans through an API and keep them a long time, others archive or purge on a rolling schedule. You find out which kind you hired on the day you need it.
It arrives without metadata
A scan named IMG_0345.pdf, attached to a mail from a shared dispatch inbox, is not a record. It is a file. Nothing joins it to the shipment.
Multi-leg moves split ownership
The PoD belongs to the last leg. Cross-dock, transload, interline and final-mile agent moves mean the party who captured the signature is two contracts removed from you, and their reference number is not your reference number.
References do not reconcile
Your PO, the carrier's PRO, the 3PL's job number, the customer's store and appointment number. Without one shared key per shipment, matching is manual.
No one owns the follow-up
Missing PoDs get discovered reactively — at the moment of dispute, which is the moment it is too late to chase.
PoD capture rate = (delivered shipments with a legible PoD linked within N days ÷ delivered shipments) × 100
Set N to the shortest dispute window you are actually contractually bound by — read it out of the supplier agreement rather than assuming an industry norm.
Trigger the clock off whichever delivery event you already receive, and pick one per carrier rather than one for the network. On EDI feeds that is usually 214 status code D1 (completed unloading at delivery location); some carriers send only X1 (arrived at delivery location) or CD (carrier departed delivery location), and API and connector-based feeds carry their own delivered status. The rule that matters is that the same shipment cannot be measured off two different events.
What drives the spread is carrier mix, not effort. Parcel and national LTL carriers with document APIs support a high rate. Regional carriers, interline partners, final-mile agents and owner-operators are where the number collapses — and in most networks that tail is small in volume relative to the exposure it carries.
What a deduction actually looks like when it lands
The PoD gap does not announce itself as a document problem. It arrives as money.
A remittance advice comes in with the invoice short-paid and a reason code against it. The code is three characters. Behind it is a deadline set by your supplier agreement, and behind that a rebuttal packet you now have to assemble.
On the remittance
The rebuttal packet
- The signed delivery receipt, with printed receiver name and delivery time
- The BOL or PRO
- The packing list or ASN
- Evidence of what was tendered (shortage codes only)
That packet is the whole fight. Assembled inside the window, most documentation-coded deductions are recoverable. Assembled after it, none are — the deduction is closed regardless of what the PoD says, because you missed a contractual deadline, not an evidentiary one.
So the practical question is not whether you can eventually find the PoD. It is how many hours of a person's week go into finding it, and what share of deductions expire in the queue while they do. Run the number on one quarter's remittances.
Unrecovered documentation deductions = (deductions coded for missing or inadequate PoD, never disputed or disputed late) × their dollar value
That figure, not a capture-rate percentage, is what gets this problem funded. It is also the figure most claims teams have never been asked for, because it sits in the write-off account rather than in a freight report.
The customer service version of the same problem is quieter and larger. “Did they receive it?” is one of the highest-volume questions a CS desk handles, and today the answer usually requires an escalation into supply chain and a wait measured in hours. The document exists. The person who needs it cannot reach it.
Fourteen pallets left Toronto in good order and reached Columbus with cartons crushed on three of them. Whether that invoice value gets recovered or written off is settled in the fifteen seconds the receiver spends on the condition block. Both versions of that delivery are below.
Worked example: the same damage, two documents
Fourteen pallets of packaged goods, Toronto to Columbus, LTL with one cross-dock. Invoice value $18,400. On arrival, cartons on three pallets are crushed. Two versions of the same delivery.
Fourteen pallets, Toronto to Columbus, one cross-dock. Invoice value $18,400. Same freight, same damage — one notation apart.
| PoD A — clean-signed | PoD B — exception-noted | |
|---|---|---|
| Delivery receipt | Signed “received”, no notations | “3 pallets crushed, top 2 tiers — photos taken”, driver initialled |
| When damage was recorded | At put-away, two days later | At the tailgate, before the driver left |
| Photos | After the pallets were broken down for put-away | On the trailer, load intact, wrap and stack visible |
| OS&D report | Filed day 3, no carrier witness | Filed same day, driver acknowledged |
| Burden of proof | Yours — you must prove the damage occurred in carrier custody | Carrier's — the delivery receipt records damage on arrival |
| Claim character | Concealed damage claim | Visible damage claim |
| Likely outcome | Denied, or settled at a fraction | Paid at invoice value less salvage |
Same freight. Same damage. Same dollar value. The difference is fifteen seconds of notation at the dock — and a document your team can produce on demand.
The clocks you are actually racing
A clean signature is not a formality. Under the US domestic framework — the Carmack Amendment, 49 U.S.C. § 14706 — a clear delivery receipt is treated as prima facie evidence that the goods arrived in good order. That flips the burden onto you. Concealed damage claims are still winnable, but you are now proving a negative against a signed document, and carrier tariffs typically require notice of concealed damage within a short window (commonly five to fifteen days, tariff-specific) as a condition of consideration.
Under 49 CFR Part 370, a carrier receiving a written claim owes you a fixed cadence — but that cadence is only available to you if the claim was filed cleanly, with the PoD attached, inside the window.
30 days
acknowledge the claim
120 days
pay, decline, or make a firm settlement offer
every 60 days
report status until it resolves
The notice and filing windows differ by mode, and the shortest one governs your process.
| Mode / regime | Damage notice | Claim filing | Time to sue |
|---|---|---|---|
| US road & rail — Carmack Amendment49 U.S.C. § 14706; handling rules 49 CFR Part 370 | Note visible damage on the delivery receipt at delivery; concealed damage per carrier tariff | Minimum 9 months — carriers may not contract for less. Runs from delivery for damage; from a reasonable time for delivery where the goods were lost or never delivered. | Minimum 2 years from claim denial |
| Europe road — CMR ConventionConvention on the Contract for the International Carriage of Goods by Road | Reservations at delivery for apparent loss or damage; within 7 days (excluding Sundays and holidays) for non-apparent | Written, referencing the CMR consignment note | 1 year (3 years for wilful misconduct) |
| Ocean — COGSA / Hague-VisbyUS COGSA; Hague-Visby Rules as adopted in the governing jurisdiction | In writing before or at the time of removal for apparent damage; 3 days for concealed | Against carrier per bill of lading terms | 1 year from delivery |
| Air — Montreal Convention (as revised effective 28 December 2024)Convention for the Unification of Certain Rules for International Carriage by Air | Written complaint within 14 days of receipt for damage; 21 days for delay | Written complaint is a condition of action | 2 years |
Windows and caps summarised from the convention and regulatory texts named above — verify against the governing contract and tariff for your lane. Not legal advice.
Liability caps are per-weight or per-package, not per-invoice: roughly 8.33 SDR/kg under CMR; 26 SDR/kg for air cargo under Montreal since the revision effective 28 December 2024, up from 22; and, at sea, 666.67 SDR per package or 2 SDR/kg under Hague-Visby, against a flat $500 per package under US COGSA. Which one applies depends on the bill of lading and the trade, and the difference is often larger than the claim. A defensible PoD gets your claim considered; declared value and cargo insurance determine what it is worth. Retail deduction and chargeback windows are separate from all of this and purely contractual — they live in your supplier agreement, they are usually far shorter than any statutory window, and they vary by programme. Find yours before you design a process around it. Miss that one and the deduction is permanent no matter what the PoD says.
Evidence decays faster than the deadlines do
Every window above is written down somewhere — a tariff, a convention, a supplier agreement. The clock that decides most files is written down nowhere. It is the rate at which the evidence stops existing. The carrier's image ages out of the portal. The driver who initialled the receipt moves to another carrier. The receiver who signed has left the site. The crushed pallet was broken down and binned the same afternoon.
So a file assembled in week one and the same file assembled in month four are not the same file, even when both land inside the deadline. One has photographs, a named receiver and a driver who remembers the stop. The other has a signature and a hope.
What a working PoD process looks like
Five things, in order.
Define the document contractually
Put the required PoD fields in the routing guide: printed receiver name, delivery time, piece count received, mandatory notation of visible damage, photos on exception. Make notation at delivery a carrier obligation with a named consequence, not a courtesy.
Go and get it before you need it
Retrieval should be a standing routine keyed to the delivery event, not a reaction to a dispute — days after delivery, while the carrier's image is still live and the freight invoice has not yet reached AP. On-demand retrieval is how a short contractual dispute window becomes a three-week chase.
Index against the shipment, not into a folder
One record keyed to BOL/PRO plus PO plus order line, so the document is reachable from the shipment, the order and the invoice. A searchable drive is not indexing.
Reconcile against what you tendered
The exceptions that matter are delivered-with-no-PoD, PoD-with-no-order match, and a received piece count that does not equal the tendered count. Matching the PoD against the freight invoice as well is worth doing, but it belongs to whoever owns freight audit and AP — different owner, different system, different meeting. Do not make your document programme wait on it.
Age the gaps with owners
A missing-PoD list, sorted by dispute-window urgency and dollar exposure, with a named owner per line. Everything above exists to produce that list.
Start with the one step you can run alone
None of the five steps above sit inside one job. Steps 1 and 2 need whoever owns the carrier contracts. Steps 3 and 4 need whoever owns the shipment data. Step 5 is the only one a claims or customer service desk can start alone, and it is the one that makes the case for the rest.
So start there, and start small. Take one quarter of remittances, pull the deductions coded for missing or inadequate proof of delivery, and split them into recovered, disputed late, and never disputed. Put a dollar figure on the last two columns. Then take that one number to whoever owns logistics or the carrier relationships, and ask a single question.
Which of our carriers can send us delivery documents automatically, and which ones are we chasing by hand?
That question is answerable in a week, it costs nothing, and it turns a filing frustration into a funded problem. Most PoD programmes that work started with someone in claims or customer service producing that number.
Where Orkestra fits, and what it doesn't do
Orkestra sits above the systems you already run — ERP, TMS, WMS and your carrier feeds — and works the retrieval side of the problem rather than the tailgate.
Start with the part that needs no documents at all. Because the platform already receives the delivery event across your carriers, it knows which shipments are delivered, and it tracks which of those still have no proof of delivery against them. That is Missing PoD Tracking, and on its own it converts a discovery you make when a deduction letter arrives into a list you work from while the window is still open. Delivery documents that reach us through a connected feed — EDI 210, 214 and 856 are supported, alongside 200+ pre-built carrier connectors — are held against the shipment and order record, so the document is reachable from the shipment and from the order rather than out of a folder.
Where a PoD sits only in a carrier's portal or a partner's document store, be blunt with us in the demo: ask which of your specific carriers and partners we can ingest from today, and which ones stay a manual pull. That answer is per-carrier, not per-platform, and you should have it in writing before you buy anything.
Routing a missing-document list to named owners with an SLA is the exception board in Shipment Visibility, not the document module — worth knowing if ownership, not detection, is your bottleneck. Claims Evidence Builder, in the parent module Document Management, assembles the documentation set for a claim once the pieces exist. Last-mile delivery events, where parcel is the mode, come from Parcel Visibility.
95%
PoD capture rate
module-level figure, measured our way — not the N-day formula defined above
3x
Faster claims processing
module-level figure, measured our way — not the N-day formula defined above
On numbers, so you can hold us to the right ones. The document management module reports a 95% PoD capture rate and 3x faster claims processing — module-level figures, measured our way, not under the stricter N-day formula defined earlier on this page; ask us to restate them against your window and your carrier mix. Separately, the Defense Logistics Agency consolidated dozens of carrier feeds into one normalised data layer with real-time data-quality monitoring, and saw an 83% increase in proof-of-delivery visibility across thousands of shipments a week, live in four weeks. That result is about seeing delivery status reliably across every carrier — the signal that tells you a PoD is now due. It is not a claim about retrieving document images, and we would rather you knew the difference before the demo than after it.
What Orkestra does not do
We do not put a device in your driver's hand. There is no Orkestra driver app and no signature-capture screen — we do not create the PoD at the tailgate, and we cannot notate damage or take the photo on your behalf. We do not file, negotiate or adjudicate freight claims with carriers, we do not replace the carrier's system of record for the signed original, and nothing here is legal advice on a claim.
Two more limits worth stating plainly, because pages like this usually blur them. We do not read a scanned image and lift the references off it for you — matching relies on the identifiers carried in the connected feed, so a bare untagged scan from a shared inbox is still a bare untagged scan. And we do not audit or match freight invoices; three-way matching against carrier billing sits with your AP or freight-audit tooling.
If a carrier never created a PoD, no software can retrieve one. What we can tell you is exactly which shipments that applies to, while you still have time to do something about it.
Four weeks from kickoff, DLA had 83% more proof-of-delivery visibility — and every duplicate tracking record gone.
“Orkestra consolidated shipment visibility across carriers into one reliable platform with real-time data quality monitoring.”— DLA, Defence Logistics
Proof of delivery questions, answered
Back up a level: Document Management — customs readiness, claims evidence, and document tracking across every shipment.
