Carta Porte 3.1 errors that reject your CFDI (Comprobante Fiscal Digital por Internet / Mexican e-invoice) or let you pay a ghost trip are caught on the buyer side before you authorize payment , not after cash has left, and not when the SAT notice arrives.
Fines punish the issuer. In Finance and accounts payable (AP) the damage is different: objectionable deduction or settlement without a file. Match the XML to the real trip; hold with cause what does not check out. OCL Cargo is an autonomous TMS that can stamp invoices and Carta Porte, and audits that match at 100% with a typical recovery of 5-7% of freight spend.
- Carta Porte checks before paying
- 10
- only valid version since Jul 2024
- 3.1
- recovery when auditing 100% of flow
- 5-7%
- pre-pay verification pilot
- 6-8 wks
Cluster: Carta Porte guide · what is Carta Porte · freight accounts payable.
Verify before paying (not only fines)
The usual conversation about Carta Porte 3.1 centers on SAT fines to the issuer. That angle matters, but shippers and 3PLs live a different risk: authorizing payment of a CFDI whose complement does not support the deduction or the trip. When accounts payable settles without matching, the cash has already left.
That is the same logic as freight audit and the POD + Carta Porte + invoice triad. POD (proof of delivery) proves delivery; Carta Porte documents the tax-side move; the invoice bills. Without all three, Finance operates blind.
Only watching SAT fines (issuer)
- Focus is punishment of the carrier for stamping errors
- The buyer finds out late, after paying or when the SAT looks
- Does not stop cash leakage or non-deductible CFDIs
- Does not build a case file to dispute with operational evidence
Verify before paying (buyer)
- Focus is not paying a CFDI with a broken complement or ghost trip
- Rejection happens in accounts payable, with a ready case file
- Protects tax deduction and recovers a typical 5-7% of freight spend
- Matches CFDI, Carta Porte, GPS, POD, and rate on every invoice
10 errors that kill deduction or payment
Use this list on every freight invoice with a Carta Porte 3.1 complement. It is not compliance theory: these are the points that killed deductions or stopped payments in operations that started auditing 100% of the flow. Check them before you schedule payment.
Elige un paso para ver el detalle
Detalle del paso · 01
Issuer and receiver RFC
If you want the full audit frame (rate, accessorials, GPS, and POD), combine this checklist with the 15-point freight invoice audit checklist. Carta Porte is one layer; a healthy payment needs all five evidence sources.
| Error | What you see in the XML | What the buyer does |
|---|---|---|
| Broken RFC | Empty, typo, or inactive RFC | Hold payment; request a corrected CFDI |
| SICT permit | Expired number or wrong modality | Validate validity before settling |
| Coordinates | Lat/long out of geofence or invented | Match against GPS and shipment address |
| CP key | Generic or incorrect commodity | Compare with what the order declared |
| Misaligned UUID / IdCCP | Complement from another CFDI or trip | Unique invoice-trip matching |
SAT 2026 catalogs: stamped ≠ payable
Complement version 3.1 is the only valid one since 17 July 2024 (confirm effective dates on the SAT portal). In 2026 the schema stays on 3.1; what moves are the catalogs PACs validate at stamping , 2026-exercise pedimentos, shipping authorizations, commodity keys, and dangerous goods, among others. Calibrate dates and cuts with SAT / DOF; do not invent fines or deadlines.
| 2026 fact | What it means for the buyer |
|---|---|
| 3.1 schema in force since Jul 2024 | Require complement 3.1; do not accept older versions in the file |
| Updated catalogs (typical Jan 2026 cut) | Stale keys can reject stamping; demand XML with the current catalog |
| Pedimentos / 2026 exercise | On foreign-trade moves, check that the pedimento number matches the exercise |
| Successful stamp | Only proves the PAC accepted the XML , not that the trip happened or that you should pay |
A CFDI stamped with a current catalog can still be a ghost trip, invented weight, or an IdCCP that does not bind to the shipment. That is why pre-pay verification is not “did we get a UUID?”.
Who stamps vs who verifies
There is an expensive confusion: assuming the shipper's system “produces” Carta Porte for the carrier. In the Mexican model, whoever issues and stamps the CFDI with the complement is whoever provides the service (almost always the carrier, via their PAC). The buyer receives, validates, and decides whether to pay.
Carrier / issuer
What they do: Builds CFDI + 3.1 complement and stamps with their PAC (or issuing system)
What they do not do: Does not approve the shipper’s payment
Freight buyer (Finance)
What they do: Receives XML, verifies the file, and decides to pay or hold
What they do not do: Does not “issue for” the carrier the CFDI they are billed
OCL (when it runs the flow)
What they do: Can stamp invoices and Carta Porte; audits 100% pre-pay
What they do not do: Does not replace every external carrier’s PAC
That honesty matters when you choose a stack. In best TMS platforms in Mexico 2026, native tax compliance is one filter; the other is knowing who issues and who audits.
Buyer pre-pay flow
The PDF in email is only the printed representation. The evidence for payment is the stamped XML matched to the agreed trip and a usable POD. Below: five verification stages (select a step for detail) and the zen order in four milestones.
Select a step to see detail
Step detail · 01
Intake
XML + rate
The same order, short version for Control Tower and Finance: from inbound XML to release or hold with cause.
Pre-pay
From XML to decision
Ingest XML
CFDI + 3.1
Tax validate
UUID · IdCCP
Match trip
GPS · weight · POD
Decide payment
Release or hold
Expanded method: CFDI + Carta Porte + GPS + POD audit.
What OCL does on Carta Porte
Running the 10 points by hand on every invoice is correct and exhausting. An operation with hundreds or thousands of CFDIs per month cannot sustain that pace without sampling, and sampling is where the leak hides. OCL applies the checklist to 100% of the pilot flow.
- Reads the XML on arrival: CFDI + Carta Porte 3.1 complement, with no manual keying.
- Validates the 10 checklist points and flags exceptions with the exact field that failed.
- Matches against the real trip: rate, GPS (including origin/destination geofence), POD, and invoice-shipment uniqueness.
- Builds a case file: what checks out is approved; what does not is held with evidence for the carrier. Humans on exceptions.
When the trip runs in the OCL flow, the same autonomous TMS can stamp invoices and Carta Porte. When the carrier stamps with their own PAC, OCL still verifies on the buyer side before payment , coexistence without migrating your ERP on day one.
A Mexican logistics operator audited 2,250 invoices and detected $3.6M MXN in unsupported charges in 6 weeks (100% of the flow). The detail is in how a 3PL detected $3.6M MXN.
6-8 week pre-pay verification pilot
You do not need to migrate your ERP or wait for the next tax close. The pilot measures Carta Porte 3.1 verification before paying on your real operation , 6-8 weeks, connected to SAP, Oracle, CargoWise, Magaya, GM Transport, or Excel.
Elige un paso para ver el detalle
Detalle del paso · 01
Coverage baseline
At the end you have numbers Finance and tax can defend: 100% coverage, typed exceptions, and a cycle that does not sacrifice control. Sister playbook: stop capturing shipments in 6-8 weeks.
Key takeaways5 points
- Carta Porte 3.1 errors do not only generate issuer fines: on the buyer side they kill CFDI deductibility or release a payment that should not have gone out.
- Check RFC, SICT permits, coordinates, CP commodity key, weight, insurance, transport figure, UUID, and IdCCP before you schedule payment.
- Stamping with current catalogs does not authorize payment: Finance still needs the trip, GPS, and POD match.
- OCL can stamp invoices and Carta Porte; it also audits the buyer file (CFDI + Carta Porte + GPS + POD) before pay. It does not replace every carrier PAC.
- Auditing 100% of the flow typically recovers 5-7% of freight spend; the pre-pay verification pilot runs 6-8 weeks on your current stack.
How many CFDIs with Carta Porte do you pay today without running the checklist?
Related reading
- SAT: Carta Porte complement · official requirements of the complement for goods transport.
- What is Carta Porte · operational definition of the complement.
- Carta Porte guide · full frame for shippers and 3PLs.
- POD + Carta Porte + invoice · the documentary triad of the shipment.
- Freight accounts payable · automated invoice-trip-payment cycle.
- 15-point freight invoice audit checklist · full layer (rate, accessorials, GPS, POD).
- CFDI + Carta Porte + GPS + POD audit · five signals before releasing payment.
- What is IdCCP · unique complement identifier in the XML.
Frequently asked questions
On the buyer side, the most common are incorrect or inactive RFC, expired SICT permits, coordinates outside the geofence, wrong CP commodity key, incoherent weight, incomplete insurance, poorly built transport figure, UUID (CFDI tax folio) misaligned with the complement, and IdCCP (unique Carta Porte complement ID) that does not match the trip. Any of these can kill the deduction or stop payment.
SAT fines punish the issuer. On the shipper side the damage is different: you pay a CFDI (Comprobante Fiscal Digital por Internet / Mexican e-invoice) you cannot deduct, or you pay a trip with a broken file. Verifying before payment stops the cash out; it does not leave you chasing money months later. More in freight accounts payable.
Yes. OCL can stamp invoices and Carta Porte when that fits the trip flow. It also audits on the buyer side: it matches CFDI, Carta Porte complement, rate, GPS, and POD (proof of delivery) before payment. It does not replace every carrier’s PAC (Proveedor Autorizado de Certificación / authorized stamp provider) when they invoice outside the OCL flow.
Whoever builds the CFDI (almost always the carrier) stamps via their PAC or an issuing system. The freight buyer receives the XML and verifies that the file matches the real trip before authorizing payment. Issuance and verification are different roles; mixing them leaves the risk in Finance and accounts payable (AP).
No. Stamping validates structure and catalogs with the SAT. Paying requires matching that XML to rate, GPS, POD, and the trip IdCCP. A stamped CFDI can still be non-deductible or not match the service received. Calibrate catalogs and effective dates on the SAT / DOF portals.
In Mexico, typical recovery from auditing 100% of the flow is 5-7% of freight spend. A 3PL detected $3.6M MXN in unsupported charges in 6 weeks. The case in how a 3PL detected $3.6M MXN.
With a 6-8 week pilot on your real operation: the agent reads every invoice on arrival, validates the Carta Porte 3.1 complement, and matches it to the trip. It connects to SAP, Oracle, CargoWise, Magaya, GM Transport, or Excel, without migrating your TMS on day one.