FTFleetmesh Tech
Guides › Freight & TMS

Mexico's Carta Porte and Your TMS: CFDI Rules, Penalties, Costs and Go-Live Timelines

A truck in Mexico without a valid Carta Porte risks fines, inspection holds and freight costs your customers can't deduct. Here's what your TMS has to capture, what PAC integration costs and how long go-live typically takes.

Fleetmesh Tech editorial team · November 2026 · 8 min read

Why Carta Porte is a TMS problem before it's a tax problem

If you move goods on Mexican federal highways, each load needs an electronic invoice (CFDI) carrying the Carta Porte complement, stamped through a certified provider before the truck leaves. For most shippers, carriers and 3PLs, compliance isn't the open question. Data is. Can your transportation system produce a valid complement on every load, or will dispatchers keep retyping shipment details into an invoicing portal at 2 a.m.?

That's why choosing TMS software Mexico operations can rely on is mostly a data decision. The complement asks for things that live in your TMS (routes, distances, departure and arrival times, vehicles, drivers) and things that live in your ERP or WMS (product codes, weights, customs documents). If those systems don't feed one clean record to the invoicing layer, you get rejected stamps, held trucks and an operations team doing compliance work by hand.

Advertisement

Who issues the document depends on your role. In general:

  • For-hire carriers issue an income-type CFDI (Ingreso) for the freight charge, with the complement attached.
  • Shippers moving their own goods in their own fleet issue a transfer-type CFDI (Traslado) with the complement.
  • Intermediaries, forwarders and transport agents fall under specific rules in SAT's annual Miscellaneous Tax Resolution. Those rules have changed more than once, so reconfirm your position every year.

SAT revises the complement version and its catalogs periodically, so check which version is current before you scope anything. Favor vendors who ship those updates as routine releases, not paid projects. And have a Mexican tax advisor (contador or tax attorney) confirm which obligations apply to your entity and routes.

The data fields your TMS must capture before dispatch

A Carta Porte complement can run to dozens of fields. Most rejections and roadside problems trace back to a handful of field groups, each with a natural owner system. Map them before you talk to vendors.

Field groupTypical contentsUsual sourceCommon failure
LocationsOrigin and destination IDs, full addresses with SAT postal, state and municipality codes, RFC of sender and recipientTMS location masterFree-text addresses that don't match SAT catalogs
Timing and distanceDeparture and arrival date and time, distance traveled per legTMS planning and routingDistance left at zero or guessed; multi-stop legs collapsed into one
GoodsSAT product key from the Carta Porte catalog, description, quantity, unit key, weight in kg, hazardous-material flag and UN number, packagingERP item master or WMSGeneric product keys; weights missing for mixed pallets
Customs (cross-border)International transport flag, entry or exit, country, customs regime, pedimento number, tariff classificationCustoms broker feed or trade-compliance modulePedimento not available when dispatch needs it
VehicleFederal transport permit type and number, vehicle configuration, plate, model year, trailer detailsTMS fleet or asset moduleSubcontracted trucks with no data in the system
Insurance and crewLiability insurer and policy number (cargo and environmental where required), driver RFC and license numberCarrier onboarding recordsExpired policies; driver swapped at the yard

Later versions of the complement also require a unique Carta Porte identifier (IdCCP) on each document. Your TMS or middleware should generate it and keep it with the shipment record for audits.

The hardest data for most 3PLs is vehicle and driver detail for subcontracted capacity. If you broker loads, onboarding must collect permits, insurance and driver details before tender, or the complement can't be built on time. On cross-border freight into Mexico, pedimento timing is just as common a snag. The drayage leg from the crossing often can't be documented until the customs broker releases the number, so the broker's system should connect to your TMS, not to a shared inbox.

Where the certified PAC sits between your TMS and SAT

SAT doesn't accept CFDIs straight from your TMS. Every invoice must be validated and stamped (timbrado) by a Proveedor Autorizado de Certificación, which checks the XML against SAT's rules, adds the digital stamp and returns the fiscal folio (UUID). Without that stamp the document isn't valid, whatever your system printed.

For PAC integration TMS projects, you'll see three architectures:

  1. TMS-native localization. Large international platforms such as SAP TM, Oracle Transportation Management, Blue Yonder and Manhattan generally offer Mexican localization or certified partner connectors. The TMS builds the XML and calls a PAC through a partner integration. Best when Mexico is one country in a global rollout.
  2. Middleware or e-invoicing hub. A multi-country e-invoicing provider (Edicom is a widely used example) takes shipment data from your TMS and ERP, builds the complement and stamps it. Good if you already handle mandates elsewhere, such as India's e-way bill or Brazil's CT-e, through one hub.
  3. Mexican TMS with built-in stamping. Local platforms built for Mexican carriers often include Carta Porte and a bundled PAC. They deploy quickly and track SAT changes closely, but can be harder to connect to a global ERP.

For mid-size carriers and 3PLs operating mainly in Mexico, a Mexican TMS with built-in stamping is the faster, lower-risk choice, because their whole customer base depends on keeping up with SAT. Multinational shippers already running a global TMS should usually extend it through a hub rather than run a separate Mexican stack.

Either way, you'll need a Mexican taxpayer ID (RFC), a digital seal certificate (CSD) for signing invoices, and a process for renewing that certificate before it expires. An expired CSD stops stamping, and it's an easy way to strand a fleet on a Monday morning.

Penalties, red flags and what compliance add-ons cost

The fine is only part of the risk. Under the Federal Tax Code, issuing a transport CFDI without the complement, or with incorrect data, can draw penalties per noncompliant document. Amounts are updated periodically, so get current figures from your advisor. Day to day, the consequences look like this:

  • Roadside holds. Authorities can detain goods that lack valid documentation. For imported goods without proof of legal entry, that can escalate to seizure under customs rules.
  • Lost deductions. Customers may be unable to deduct freight backed by a defective CFDI, so expect them to reject your invoices.
  • Customer audits. Large shippers often audit carrier compliance and drop carriers with repeat errors.

Typical 2026 market ranges are below. They vary widely by contract, volume and region, so confirm them with vendors.

Cost itemIndicative range (USD)Main driver
PAC stampingAbout $0.02 to $0.15 per stampAnnual volume commitment
Mexican TMS with built-in Carta PorteAbout $40 to $150 per user or truck per monthFleet size, modules
Localization add-on for a global TMSAbout $500 to $3,000 per monthNumber of legal entities, transaction volume
Integration project (TMS, ERP, PAC, customs broker)About $10,000 to $80,000 one-timeNumber of source systems, data cleanup
Catalog and master-data cleanupAbout $5,000 to $30,000 one-timeNumber of SKUs and locations

Red flags during vendor evaluation:

  • The vendor treats SAT version changes as change orders instead of maintenance.
  • The system can't show a rejected stamp, the reason and the fix on one screen.
  • It can't prepare the complement offline at the yard and stamp it once connectivity returns.
  • There's no automated check of carrier insurance and permit expiry before tender.
  • Every reference is a cross-border shipper, with no domestic carriers among them.

A realistic go-live timeline and how to decide

Rollout time depends more on master data than on software. Here's a hypothetical example: a 3PL running 60 trucks and 200 SKU families across two Mexican warehouses, with one cross-border lane.

PhaseMexican TMS with built-in PACGlobal TMS plus localization or hub
Requirements and advisor review1 to 2 weeks2 to 4 weeks
Master data: SAT product keys, locations, vehicles, drivers2 to 4 weeks4 to 8 weeks
Integration and PAC test environment1 to 3 weeks6 to 12 weeks
Parallel run on live loads2 weeks3 to 4 weeks
Total to go-liveAbout 6 to 11 weeksAbout 4 to 7 months

Don't skip the parallel run. Stamp real loads through the new flow while the old process keeps running, and compare rejection rates by field group. Go live only after a full week with no errors on your highest-volume lanes.

Here's the decision rule. If most of your loads are domestic Mexican moves and you don't run a global TMS, buy a Mexican TMS with built-in stamping and connect it to your ERP. If Mexico is one market inside a multi-country network, extend your global TMS through a certified localization or e-invoicing hub, and plan on a full quarter or more. Either way, your first step this month is the same: pull 50 recent loads, try to fill every field group above from your current systems, and count the gaps. That number tells you how long the project will really take. Take the gap list to your Mexican tax advisor before you sign a vendor contract.

Quick answers

Does a foreign carrier or shipper need its own Mexican RFC to issue Carta Porte?

In general, CFDIs can only be issued by entities registered with SAT and holding a digital seal certificate. That's why foreign companies usually work through a Mexican subsidiary, a Mexican carrier or a registered intermediary. How this applies to you depends on your structure and whether you have a permanent establishment in Mexico, so confirm it with a Mexican tax advisor.

Who issues the Carta Porte on a cross-border import move?

Usually the Mexican carrier doing the drayage or line-haul inside Mexico issues it, with the international transport fields and the pedimento number filled in. Responsibilities can shift when intermediaries or forwarders are involved. Agree in writing with your carrier and customs broker who issues the document and who supplies each data element.

Can we keep using a separate invoicing portal and skip the TMS integration?

You can, and many small fleets do at first. The cost is retyping, which causes data errors and delays dispatch once you're past a few dozen loads a day. Most operations find integration pays for itself within months, through fewer rejected stamps and held trucks.

How often does SAT change the Carta Porte requirements?

SAT has released several versions since the complement became mandatory, and it updates its catalogs and the annual Miscellaneous Tax Resolution more often than that. Plan for at least one meaningful change a year. Write vendor contracts so that regulatory updates are covered by standard maintenance.

Written by the Fleetmesh Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.