POD (Proof of Delivery) is the document or record — physical or electronic — that evidences goods reached the consignee: who received, when, how much, and in what condition. Digital versions (ePOD) add geolocation, a timestamp, and photo attachments. On the Mexico–U.S. corridor POD is not a courier formality: it is the piece that closes the trip file for shipper, 3PL, and accounts payable.
The invoice arrived. The carrier bills handling and detention. You ask for the POD and get a blurry photo of a folded sheet with no readable time. Do you pay or dispute? With that file, disputing is shouting. This guide locks the definition, minimum fields, paper vs digital, the Mexican stack versus European eCMR, and how to bind evidence to the trip ID before releasing payment.
- real delivery evidence
- Closes trip
- sign · time · geo · photo
- 4+ fields
- CFDI + Carta Porte + POD
- MX trilogy
- dispute before release
- Pre-pay
Cluster: ePOD · OTD · OTIF · Carta Porte vs POD · Delivery / POD
What POD is (usable answer)
A useful POD answers six questions: was it delivered?, to whom?, when?, how much?, in what condition?, were there incidents? If any answer is missing, the document is decorative. In Mexican B2B operations it is matched to the delivery note, purchase order, and often the customer DC dock check-in.
The weak version (illegible signature only) cannot support a shortage or a detention charge. The strong version hangs off the trip ID in the transportation management system (TMS) and reaches accounts payable in hours, not days. That is what separates a lost delivery note from a file that survives audit.
Fields of a defensible POD
There is no “ISO POD” and no single SAT form for proof of delivery. What exists is a strong commercial practice: minimum checklist + digital capture bound to the shipment + accounts payable hold when evidence is missing. Fields that usually decide a dispute:
| Field | Why it matters | Typical failure |
|---|---|---|
| Trip / shipment ID | Hang evidence off the file | Orphan PDF in chat |
| Identifiable receiver | Who received or refused | Generic “warehouse signature” |
| Timestamp | When delivery happened | Illegible time or no timezone |
| Quantity / condition | In Full and agreed quality | Only “delivered” with no detail |
| Signature or typed refusal | Acceptance or exception | Scribble with no name |
| Photo / attachments | Damage, seal, door, pallet | Truck selfie with no freight |
| Geo or geofence | Where it was captured | No GPS or dock fence |
| Incidents / accessorials | Detention, handling, partial | Charge with no timestamp |
Paper vs digital (ePOD)
Paper remains valid if complete · but it gets lost, delayed, and does not scale. ePOD forces fields, geo, and timestamp and reaches the system in minutes. Digitizing a photo of a sheet is not ePOD: it is paper with an extra step.
Paper POD / chat
- Lost in a box or WhatsApp
- Incomplete, illegible fields
- Arrives days after the CFDI
- Cannot filter shortages or detention
Structured ePOD
- Hangs off the trip ID
- Signature + time + geo + photo
- Available in hours
- Supports pre-pay dispute
| Dimension | Paper / chat photo | Bound ePOD |
|---|---|---|
| Speed to accounts payable | Days · sometimes weeks | Hours (typical local SLA <4 h) |
| Audit | Manual sampling | 100% match per shipment |
| Accessorials | Conversation | Timestamps + geo |
| Retention | Box / personal phone | File recoverable by ID |
| Risk | Lost note = blind pay | Typed exception if a field is missing |
POD vs eCMR vs OTD vs OTIF
European competitors sell eCMR as if it were the only standard. On the Mexico–U.S. corridor it is not. Distinguish what each piece proves:
POD / ePOD
What it measures / proves: Physical delivery: who, when, what, condition
Scope: Commercial / ops (global)
If missing: No In Full or strong dispute
eCMR
What it measures / proves: Electronic consignment note
Scope: Europe (EU framework)
If missing: Irrelevant as “MX law”
OTD
What it measures / proves: % on time vs window/appointment
Scope: Punctuality KPI
If missing: Clock only · not completeness
OTIF
What it measures / proves: On time AND complete (AND)
Scope: Service scorecard
If missing: Without POD, In Full is invented
Carta Porte + CFDI
What it measures / proves: Fiscal move / invoice
Scope: Mexico (SAT)
If missing: Fiscal gap · not dock proof
For punctuality see what is OTD; for the service AND, what is OTIF. POD feeds both: it is evidence, not the percentage.
Mexico–U.S.: CFDI + Carta Porte + POD
For fiscalized shipments on Mexican territory, a defensible file usually needs three legs: CFDI (what is billed), Carta Porte / 3.1 complement when applicable (what moved and how), and POD (what was delivered and when). SAT sees the documented move; accounts payable needs delivery proof and rate to release payment.
At corridor DCs and docks (Monterrey–Laredo, Bajío–border, Mexico City–north) POD is captured at the dock: receiver signature, door seal, pallet or damage photo, and often marks for detention. Do not confuse that with parcel lockers or consumer chat. Transfer fiscal guide: CFDI traslado guide · glossary what is CFDI traslado.
CFDI
Answers: What is billed fiscally
If missing: No payment formality
Typical owner: Finance / carrier
Carta Porte
Answers: What moved and how
If missing: SAT risk + operations gap
Typical owner: Operations / carrier
POD / ePOD
Answers: What was delivered and when
If missing: No In Full or strong dispute
Typical owner: Operations / consignee
Full trilogy
Answers: Defensible file
If missing: Audit and SLA weakened
Typical owner: 3PL / shipper
Dock accessorials and disputes
Handling, detention, redelivery, and partials are born at the dock. Without a timestamp and geo on the POD, the charge is a conversation: the carrier says “I waited three hours”; you have no mark. With bound evidence, accounts payable disputes before releasing payment · not after the wire.
Catalog and control: what accessorials are · what detention is. Audit checklist: CFDI + Carta Porte + GPS + POD. Healthy rule: without a usable POD (or a typed exception), there is no automatic pay.
From dock to accounts payable
Do not start with the pretty app. Start with the fields accounts payable and the customer require · then bind them to the trip ID.
Capture at dock
Sign · photo · time
Bind to trip
ID in the TMS
Type exception
Shortage or refusal
Payment gate
Pre-pay match
Retain the file
By ID, not chat
Expensive POD mistakes
Elige un paso para ver el detalle
Detalle del paso · 01
Accepting a sheet photo as ePOD
OCL and the trip file
OCL Cargo is an autonomous TMS with AI agents (computer use): it captures dock evidence, binds photo/signature/geo to the trip ID, and puts POD in front of accounts payable before release. Scope: own fleet and workshops, dynamic last-mile routing, multimodal; WhatsApp when the external provider cannot use the native app. Dedicated product: Delivery / POD · POD capture agent. It coexists with your stack on day one.
Who decides exceptions? Your team. Agents bring the file ready; they do not invent commercial criteria. When applicable, OCL can stamp invoices and Carta Porte · it does not “stamp POD.” Typical pilot 6–8 weeks on one corridor; 5–7% recovery pattern when auditing 100% of the pilot flow · pricing signal from ~$50 MXN per shipment depending on scope.
Key takeaways6 points
- POD = proof of delivery that closes the trip file: who, when, what, condition · and digitally geo + attachments.
- Defensible = photo + signature + timestamp + geo + trip ID · not a scribble in WhatsApp.
- In Mexico the stack is CFDI + Carta Porte (when applicable) + POD. eCMR is a European framework, not Mexican law.
- Without a usable POD you lose accessorial disputes, OTIF In Full, and pre-pay audit.
- Healthy target: ePOD in hours, bound to the shipment in the TMS · not days later on a driver’s phone.
- Convention playbook: POD guide for shippers. Product: Delivery / POD.
Does your POD defend… or only decorate the file?
Related reading
Frequently asked questions
POD (Proof of Delivery) is the document or record — paper or digital — that evidences goods were delivered to the consignee: who received, when, quantity/condition and, in digital versions, where (geo) plus attachments. It closes the trip file; it does not replace the Mexican digital tax invoice (CFDI) or Carta Porte.
Not always. A remittance describes what was dispatched; POD proves reception (who signed, when, condition). They may be signed together at the dock, but they play different roles in the file. Detail: POD convention for shippers.
eCMR is the European electronic consignment note (EU framework). In Mexico the real stack is CFDI + Carta Porte (when applicable) + POD. Do not treat eCMR as Mexican law; use it only as a European digitization reference.
CFDI documents the fiscal operation; Carta Porte documents the move for SAT; POD proves physical delivery. One without the others leaves gaps for accounts payable, the customer, or audit. Compare: Carta Porte vs POD.
At minimum: trip ID, identifiable receiver, date-time stamp, quantity and condition, signature (or typed refusal), photo when policy requires it, geo or geofence, and dock incidents/accessorials. Without structured fields, it is decoration.
As an emergency channel, sometimes. As the official record, almost never: it gets lost, cannot be filtered, and does not hang off the trip ID. Digitizing a blurry sheet is not ePOD. The system of record is the TMS/file, not the driver’s chat.
OCL captures and binds POD to the trip file (photo, signature, timestamp, geo), puts it in front of accounts payable before release, and types exceptions. Product: Delivery / POD. Who decides exceptions? Your team. When applicable, it can stamp invoices and Carta Porte. Typical pilot 6–8 weeks; 5–7% recovery pattern when auditing 100% of the pilot flow.