POD (Proof of Delivery) is evidence that goods reached the consignee: who received them, when, how much, and in what condition, tied to the same trip ID as the rate and tracking. On Mexico–US freight, a last-mile app is not enough: accounts payable needs the POD inside the shipment file before releasing payment.
- commercial convention, not a SAT form
- No ISO POD
- minimum dock checklist
- 6 fields
- rate · CFDI · CP · GPS · POD
- 5 pieces
- evidence hung on the trip
- 1 ID
Context: short definition · Carta Porte vs POD · audit CFDI + Carta Porte + GPS + POD · freight journey
What POD is in logistics
This section answers the direct search: what proof of delivery is and how a freight shipper uses it — not only a parcel doorstep operator.
POD · minimum fields
What closes the trip
1
Identity
Trip / shipment ID bound to the receiver.
2
Time + place
Timestamp and geo or dock check-in.
3
Condition
Quantity, photo/signature, exceptions, and accessorials.
4
Payment
Match to rate + CFDI before release.
An orphan photo with no ID is not POD · it is noise for accounts payable.
A useful POD answers six questions: delivered?, to whom?, when?, how much?, in what condition?, under which trip ID? If any answer is missing, the document is decorative for payment, claims, or a customer scorecard.
On the corridor, POD is part of the shipment file with rate confirmation, CFDI, Carta Porte, and GPS — the same thread as the freight journey. Short definition: glossary: what is POD.
What a POD is not (definition mistakes)
Last-mile competitors sell signature and door photo. Here we clarify what does not replace a defensible proof of delivery in B2B freight.
Carta Porte / CFDI
What it really is: Fiscal document for the move (SAT)
Why it is not enough as POD: Does not identify who signed at the dock or received condition
Delivery note or packing list alone
What it really is: List of what shipped or traveled
Why it is not enough as POD: No receipt acknowledgment with receiver and exceptions
EDI 214 “delivered”
What it really is: Carrier status
Why it is not enough as POD: Milestone ≠ file with quantity, photo, and exceptions
eCMR (Europe)
What it really is: EU digital consignment note
Why it is not enough as POD: Not the Mexican Carta Porte frame or your dock convention
Sheet photo in WhatsApp
What it really is: Loose image
Why it is not enough as POD: Orphaned from the ID; cannot filter shortages or scale to AP
CEDIS gate stamp
What it really is: Access event
Why it is not enough as POD: Does not prove quantity, condition, or identifiable receiver
Fiscal vs delivery compare: Carta Porte vs POD.
Minimum fields of a defensible POD
Here we fix the minimum a dock, CEDIS, or plant delivery must leave on record. If any answer is missing, the document cannot support a hold or a dispute.
Six minimum fields
Elige un paso para ver el detalle
Detalle del paso · 01
Trip reference
If the pain is the claim after the dock: damage or shortage claim.
Paper vs digital: POD and ePOD
The goal is not to idolize the app or romanticize paper: it is intact evidence, on time, and searchable by ID. ePOD (electronic Proof of Delivery) is not “a photo of the sheet”: it is capture with required fields and integrity.
Paper POD
Strength: Accepted at traditional docks
Typical risk: Loss, illegibility, delay to accounts payable
When to use: Backup + immediate structured capture
ePOD in app or TMS
Strength: Fields, geo, photo, timestamp
Typical risk: Dock that will not sign on a device
When to use: Internal standard for the carrier panel
WhatsApp photo
Strength: Fast
Typical risk: Orphaned from the ID; does not filter shortages
When to use: Only if structured and tied to the trip
EDI 214 “delivered”
Strength: Automatic status
Typical risk: No condition or dock photo
When to use: Complement, not a substitute for the file
Capture
From dock to shipment file
Deliver
Dock or site
Capture
Sign + fields
Attach
Photo / GPS
Bind
ID in TMS
POD vs Carta Porte: what each proves
This is the wedge against European eCMR guides: in Mexico the Carta Porte complement and the POD answer different questions. Both often coexist on the same trip.
CFDI (invoice)
Proves: What is billed fiscally
Typical owner: Finance / carrier
If missing: No payment formality
Carta Porte
Proves: What moved and how (the move)
Typical owner: Operations / carrier
If missing: SAT risk + gap in the file
POD / ePOD
Proves: Who received, how much, and condition
Typical owner: Operations / consignee
If missing: No In Full or strong dispute
GPS / geofence
Proves: Where the unit was and when
Typical owner: Tower / carrier
If missing: No “was on site” match
OCL can stamp CFDI invoices and Carta Porte when fiscal scope requires it; POD is not “stamped” with SAT — it is captured and matched in the file. Three-piece guide: POD + Carta Porte + invoice trilogy.
Mexico: CEDIS, dock, and OTIF chargebacks
Here we land the convention in Mexican operations: distribution centers (CEDIS), dock appointments, and the cost of a weak POD against retail or customers with contractual OTIF.
At many CEDIS, delivery goes through appointment, ASN (advance ship notice), and receipt documents. A stamp or counter-receipt helps, but your convention must require an identifiable receiver, timestamp, quantity received vs scheduled, and exceptions. Without that, “we delivered at the CEDIS” cannot support a shortage or a handling accessorial.
OTIF (On Time In Full) and chargebacks: “In Full” without quantity or condition on the POD is a vanity metric. When a retail customer debits for shortage or refuse, the POD (or the WMS receipt acknowledgment) is the typical source to fight or accept the charge. Without evidence tied to the ID, you lose the argument before you open email.
Shipper convention: what counts as a valid POD
Without a convention, every team invents its own “we have a POD”. This section is the standard procurement, operations, and accounts payable must sign together and annex to the carrier panel.
A strong convention has five pieces: minimum fields, ePOD availability SLA (for example under 4 hours for local delivery and 24 hours for long haul), payment-hold rule, typed exceptions (no signature, partial refuse, closed dock), and document retention with search by ID.
Adoption
Four compliance fronts
Define
Fields and SLA
Contract
Carrier annex
Capture
ePOD to ID
Govern
Payment hold
Accounts payable and pre-pay audit
The same file feeds payment, claims, and OTIF — with different criteria. This section is the handoff to the team that releases freight pay.
Accounts payable (freight pay)
Question it answers: Is there service evidence coherent with rate, GPS, and CFDI/Carta Porte?
What it prevents when complete: Paying blind and fighting later without leverage
Claims
Question it answers: Was the exception noted at receipt (shortage, damage, refuse)?
What it prevents when complete: “Arrived OK” winning by default against the carrier
OTIF (On Time In Full)
Question it answers: Was it on time and complete, with quantity and condition?
What it prevents when complete: A vanity KPI that only says “delivered”
Healthy playbook: if the POD is missing or contradicts the trip, document the exception, ask the carrier to correct, and hold payment with a readable reason. Once paid, you lose leverage. Scale in accounts payable pre-pay audit.
Sheet photo with no fields
Why it fails: No quantity, condition, or ID
Fix: Structured capture (ePOD or form) tied to the trip
POD orphaned in chat
Why it fails: Accounts payable cannot find it in time
Fix: Archive by ID in TMS or shipment file
Pay first, claim later
Why it fails: You lose leverage
Fix: Hold with cause until a defensible POD exists
Confusing Carta Porte with POD
Why it fails: The complement does not prove dock signature
Fix: Require both when the leg warrants it
Action checklist for this week
Close the loop with concrete actions for the process owner (tower, procurement, or accounts payable) who wants to stop depending on chat.
Elige un paso para ver el detalle
Detalle del paso · 01
Publish the six fields
OCL: delivery agent and the trip file
OCL Cargo is an autonomous TMS with agents that operate screens and portals (computer use: the agent uses the UI the way a person would). The delivery / POD agent captures or binds evidence to the trip ID; audit matches it with rate, CFDI, Carta Porte, and GPS before pay.
You decide with the file on the table. OCL escalates to operations and finance when a usable POD is missing or the match fails. If you already run MercuryGate, SAP, or another system of record, the pattern is to coexist: the agent closes shipment-file work without a day-one migration. Glossary: POD capture agent.
Exceptions
You decide with the file
Capture
POD to ID
Match
Rate and docs
Hold
If mismatch
Escalate
Team exception
On pilot lanes, teams that stop sampling and audit 100% of the flow often see a 5–7% recovery pattern on audited spend when the file (including POD) supports holds and disputes.
Key takeaways6 points
- POD (Proof of Delivery) is physical-receipt evidence: who, when, how much, condition, and trip ID — not a SAT form.
- Do not confuse POD with Carta Porte, a loose delivery note, EDI “delivered”, or a sheet photo in chat.
- Six minimum fields + a recoverable archive by ID support payment, claims, and OTIF (On Time In Full).
- In Mexico the strong file is rate + CFDI + Carta Porte + GPS + POD; a CEDIS stamp alone is not enough.
- The shipper convention defines a valid POD and when accounts payable holds with cause.
- ePOD wins with fields, geo/photo, and system arrival; OCL binds evidence to the trip without a day-one TMS migration.
Does your POD defend payment… or only decorate the chat?
Related reading
Frequently asked questions
POD (Proof of Delivery) is evidence that goods reached the consignee: who received them, when, how much, and in what condition, tied to the trip ID. It is not a single SAT form and not an “ISO POD”.
No. There is no “ISO POD” and no single SAT (Mexican tax authority) form for proof of delivery. POD is commercial and operational evidence. Fiscal documentation for the move, when it applies, is the CFDI (Mexican digital tax invoice) with the Carta Porte complement. Adopt an internal convention and put it in carrier contracts.
No. Carta Porte documents the move for SAT; the Bill of Lading or CMR documents the contract of carriage; POD proves physical receipt. On Mexico–US corridors they often coexist by leg.
Both can be defensible if complete, intact, and tied to the trip ID. Electronic proof of delivery (ePOD) wins on speed, required fields, geolocation or photo, and a recoverable archive. A blurry photo of a sheet with no fields is the worst of both worlds.
It can, but you lose leverage on shortages, damage, detention, and OTIF (On Time In Full). The healthy playbook is to hold payment or flag an exception when a defensible POD is missing — aligned to your pre-pay audit policy.
A stamp helps, but it is not enough if it does not identify the receiver, date/time, quantity/condition, and exceptions, and if it is not tied to the same ID as the rate and trip. At distribution centers (CEDIS) with appointments, the POD should reflect received vs scheduled — not only “passed the gate”.
The delivery / POD capture agent binds evidence to the trip ID; audit matches rate, CFDI, Carta Porte, GPS, and POD before pay. Your system of record can stay where it is; your team close the judgment call on the exception. See the delivery POD product and the agent glossary.