Definition
Carta Porte XML is the structured complement file stamped with the CFDI. It holds goods, locations, transport-party, and autotransport nodes. It is what AP and the SAT can validate; the PDF is only a representation.
If your process is “the PAC will fix it”, you already accepted double capture and rejection.
The TMS should map trip a nodes; AP should store the XML for the UUID.
What Carta Porte XML means in practice
It is the machine-readable form of complement 3.1. It lives in the same tax package as CFDI XML and is identified by the UUID.
Ops guides: Carta Porte and 3.1 step by step.
Why it matters (shipper / 3PL / carrier)
1.Shipper / AP
Parse locations, goods, and unit vs the real trip before paying.
2.3PL / intermediary
Require carrier XML on the client file; PDF does not scale.
3.Carrier
Generate XML from trip data. PAC re-keying = 3.1 rejection.
Which XML nodes to match
Errors: Carta Porte 3.1 rejections.
| Node | Vs trip | Failure signal |
|---|---|---|
| Locations | Origin/destination | Different ZIP or coords |
| Goods | SKU/weight | Wrong SAT code |
| Auto transport | Plates/permit | Stale config |
| Figures | Driver | Incomplete RFC |
CP XML pre-pay checklist
File
XML present
UUID
CFDI match
Version
Complement 3.1
Nodes
Vs trip
POD
Delivery separate
Common mistakes
1.Regenerating XML by hand
Breaks trip–stamp traceability and multiplies rejection.
2.Auditing PDF only
Failing nodes do not show on the printout.
3.Ignoring catalog versioning
A stale catalog kills stamping even when the business “looks fine”.
OCL and the trip file
OCL can stamp invoices and Carta Porte. Agents parse nodes, match them to trip/GPS/POD, and leave exceptions with a file.
Sources and further reading
- Glossary: Carta Porte · complement 3.1.
- Guide: Carta Porte.
- Errors: 3.1 rejections.
- SAT (official): Carta Porte complement.
Key takeaways5 points
- CP XML = complement nodes inside/with the stamped CFDI.
- The expensive mistake is regenerating or editing XML by hand off the trip.
- Version SAT catalogs (3.1) and test changes before production.
- AP should parse nodes, not “read the PDF”.
- OCL can stamp invoices and Carta Porte; it also reads the XML in the file.
Is AP still auditing Carta Porte on PDF?
Frequently asked questions
The structured complement file stamped with the CFDI: goods, locations, auto transport, and figures.
The complement travels in the CFDI. CFDI XML is the voucher; Carta Porte XML is the complement nodes.
The issuer (usually the carrier) from its system; the PAC certifies it at stamping.
Yes. OCL can stamp invoices and Carta Porte; it also verifies the buyer-side file before pay.
No. It proves tax documentation of the move. Delivery is POD.
Complement 3.1 in current ops. See complement 3.1.