A nota de remisión (packing slip / delivery note) is the commercial document that lists what merchandise left the warehouse or distribution center (CEDIS) for a consignee: folios, SKUs, quantities, and often who acknowledged the count. In Mexico–US logistics it supports dock matching — it does not replace the electronic invoice (CFDI), the Carta Porte complement, or proof of delivery (POD).
- Not a fiscal invoice effect
- ≠ CFDI
- Shipped contents ≠ signed receipt
- ≠ POD
- Does not cover fiscal goods movement
- ≠ CP
- Same trip folio as the file
- 1 ID
Trip-file cluster: POD convention · Carta Porte vs POD · freight journey.
What a packing slip (nota de remisión) is
In Mexican ops, the remisión is the sheet (paper or digital) that travels with the freight and answers: what left the DC, and for whom? Shipper, carrier, and consignee dock use it to count lines and catch shortages before the fight reaches accounts payable.
There is no single SAT-mandated “nota de remisión” form. It is a commercial/internal document. That does not make it optional in a serious DC: without a usable remisión, OTIF “In Full” (On Time In Full) becomes opinion.
What it includes (minimum fields)
A weak remisión is a PDF with no folio or a blurry photo. A usable Mexico–US remisión has fields the dock and accounts payable can cross with the order and the trip.
Unique folio + date
Why it matters: Trace outbound and avoid duplicates
Typical failure: Same sheet reprinted with no control
Shipper and consignee
Why it matters: Who ships and who should receive
Typical failure: Generic legal name with no plant/DC
PO / order / trip ID
Why it matters: Link to TMS and rate confirmation
Typical failure: Orphan remisión with no shipment number
Lines: SKU, description, qty, UOM
Why it matters: In Full count and shortage disputes
Typical failure: “Assorted” or boxes with no breakdown
Lot / expiry (when required)
Why it matters: Traceability and recalls
Typical failure: Lot in WMS that never hits the remisión
Count acknowledgment
Why it matters: Who accepted quantities at the dock
Typical failure: Illegible signature or “received” with no name
If you run foreign trade, do not confuse this domestic remisión with the customs packing list: the latter crosses with commercial invoice and transport document (B/L, AWB). Here the focus is DC outbound and Mexico truck freight.
Remisión vs invoice, Carta Porte, POD, and waybill
The expensive Mexico mistake is treating one sheet as if it closed fiscal, movement, and delivery. Each document proves something different.
Nota de remisión
What it proves: Shipped contents (what / how much)
SAT fiscal?: Not as CFDI
Who uses it: Warehouse, dock, operations
Invoice / CFDI
What it proves: Fiscal event (income or other types as applicable)
SAT fiscal?: Yes (stamp)
Who uses it: Issuer, accounts payable, tax
Carta Porte complement
What it proves: Goods movement in Mexico (when required)
SAT fiscal?: Yes, as CFDI complement
Who uses it: Issuer; buyer checks pre-pay
POD / ePOD
What it proves: Who received, when, what, condition
SAT fiscal?: No (ops evidence)
Who uses it: Consignee dock + tower / accounts payable
Waybill / PRO / knowledge
What it proves: Carrier contract or shipment reference
SAT fiscal?: Does not replace CFDI/CP
Who uses it: Carrier, tower, claims
For Carta Porte vs delivery proof, use Carta Porte vs POD. Short POD definition: what POD is.
What it is for in Mexico DCs and freight
A remisión does not “close the trip” alone. It closes the contents link in the freight map: order, pick, and outbound to transport, receipt, and payment.
On the journey
Where the remisión sits
Pick
Lines vs order
DC outbound
Remisión issued
Haul
CFDI + Carta Porte
Dock
POD + count
Pre-pay
File cross-check
- Inventory and pick control: evidence of what left vs PO or order.
- Consignee dock: base for count and partial reject without arguing from memory.
- Basis for later invoicing: many credit sales ship on remisión then issue CFDI — the remisión does not replace that CFDI.
- Freight accounts payable input: cross quantities and folio with POD and the carrier invoice (pre-pay audit).
Benefits when the remisión is done right
The benefit is not “another PDF.” It is fewer shortage disputes, faster trip-file close, and OTIF defended with evidence — not WhatsApp screenshots.
| Benefit | What changes Monday |
|---|---|
| Fewer ghost shortages | Dock counts against clear lines; claims cite folio and SKU |
| Defendable OTIF | “In Full” is proven with remisión + POD, not a chat “delivered” |
| Cleaner invoicing | Later CFDI inherits quantities already reconciled at outbound |
| Faster pre-pay | Accounts payable crosses remisión · POD · CFDI without rebuilding the trip |
| Usable traceability | Lot/serial travel on the same thread as the trip (see traceability hub) |
In Mexico the remisión records what left the DC; the CFDI stamps the fiscal event; Carta Porte covers the goods movement when SAT requires it; proof of delivery (POD) shows who received and in what condition. When those four documents share folio and trip ID, accounts payable does not rebuild the shipment from WhatsApp screenshots.
A retail shipper on a Mexico–US lane that reconciles remisión against dock picking and requires legible line-level POD usually closes shortage disputes in days — not a chargeback cycle. “In Full” OTIF holds because outbound quantity (remisión) matches received quantity (POD), not because someone typed “delivered” in chat.
Dig into order, remisión, and lot on what traceability is.
Digital remisión and ePOD (without mixing roles)
Digitizing the remisión (WMS, TMS, or portal) helps if folio, lines, and trip link survive the PDF. An illegible chat scan is not “digital transformation.”
Avoid the European shortcut of calling any photo a “packing slip.” Define minimum fields, unique user, and trip ID link — the same discipline as the shipper POD convention.
Common mistakes in Mexico
These failures repeat in tower, DC, and accounts payable. Fixing them costs less than fighting a chargeback or accessorial without a file.
Using remisión as “the invoice”
Why it hurts: No CFDI means weak fiscal support
Fix: Remisión for outbound; CFDI for the fiscal event
Confusing remisión with POD
Why it hurts: You know what left, not who received or condition
Fix: Require POD (or ePOD) tied to the same folio
Thinking remisión = Carta Porte
Why it hurts: Fiscal goods movement is not covered
Fix: Carta Porte complement when SAT requires it
WhatsApp photo with no folio
Why it hurts: Not auditable; fails ALCOA
Fix: PDF/system with folio + trip ID
“Assorted” lines / no UOM
Why it hurts: Cannot prove In Full
Fix: SKU, quantity, and unit per line
Remisión with no PO/order
Why it hurts: Cannot cross rate or trip
Fix: Same ID as TMS / tower
The costliest mistake is not a typo on a line: it is treating the remisión as if it were the other documents. Without CFDI there is no fiscal support for AP; without Carta Porte the move may be exposed even if the box arrived; without POD you do not know whether the customer rejected for damage or shortage. Each piece has a role — merging them into one “multi-purpose” PDF feeds audits and holds.
A useful tower/dock mnemonic: remisión = outbound; POD = receipt; CFDI = fiscal invoice; Carta Porte = covered movement. If the carrier sends only POD to bill detention, accounts payable must cross arrival time (GPS), contractual window, and remisión lines — same ID, four distinct evidences.
Operable checklist
Use this at pick, dock, and accounts payable. If a material item fails, do not release freight payment “because the truck arrived.”
Elige un paso para ver el detalle
Detalle del paso · 01
Folio and date
What OCL executes with remisión and the trip file
OCL is not selling you a European multi-carrier WMS. It is an autonomous TMS with AI agents (computer use: they operate screens and portals under rules) that build the trip file and audit it before pay.
- Capture and cross delivery evidence (POD/ePOD) with the same ID as remisión and rate.
- Can stamp invoice and Carta Porte when fiscal scope applies; also audits the pre-pay cross-check.
- Coexists with your TMS/ERP: no day-one migration. Your team on typed exceptions.
- Typical pilot 6–8 weeks; when auditing 100% of the flow, the published pattern is recovering 5–7% of freight spend (3PL case).
Work done
From folio to payment
Register
Remisión + trip
Capture POD
Usable evidence
Cross CFDI
Carta Porte if needed
Audit
Exceptions to your team
Key takeaways5 points
- Nota de remisión (packing slip) = outbound content list from warehouse/DC: what shipped — not the fiscal voucher and not POD alone.
- It does not replace CFDI (invoice), Carta Porte complement, or POD; each document answers a different question in the trip file.
- Accounts payable closes cleanly when remisión + POD + CFDI (and Carta Porte when required) match the same trip ID.
- Typical Mexico mistakes: treating remisión as “the invoice,” confusing remisión with POD, WhatsApp photo with no folio or TMS link.
- OCL audits 100% of the pilot trip file, can stamp invoice and Carta Porte, and captures delivery evidence — without forcing a European WMS on day one.
Does your remisión close the file — or only ride in the truck?
Related reading
Frequently asked questions
It is the commercial document that lists what merchandise left the warehouse or DC (CEDIS) for a consignee: folio, SKUs, quantities, and often who acknowledged the count. It is not a Mexican electronic invoice (CFDI) and it does not replace proof of delivery (POD).
No. A remisión has no SAT fiscal effect as a CFDI. If the buyer needs deductibility or the issuer must document the fiscal event, that is the electronic invoice (CFDI). Confirm with your tax team — this is an ops playbook, not a legal opinion.
No. The packing slip describes what was shipped. POD (Proof of Delivery) proves who received, when, what, and in what condition. They may be signed together at the dock, but they play different roles in the trip file. See the POD shipper guide and POD glossary.
No. The Carta Porte complement on the CFDI covers goods movement in Mexico when SAT rules require it. A packing slip is not that complement. Cross-read: Carta Porte vs POD.
Unique folio, date, shipper and consignee, PO/order reference, lines with SKU/description, quantity and unit of measure, and space for count acknowledgment. Ideally the same trip ID as your TMS (Transportation Management System).
Similar idea (shipment inventory), but the foreign-trade packing list crosses with commercial invoice, B/L or AWB, and customs filing. The domestic remisión closes warehouse outbound and dock count. Glossary: packing list.
OCL builds and audits the trip file (rate · CFDI · Carta Porte · GPS · POD), can stamp invoice and Carta Porte when fiscal scope applies, and coexists with your stack. Your team on exceptions. Typical pilot 6–8 weeks; 5–7% pattern when auditing 100% of the flow.