The Mexico freight journey is the full order-to-pay cycle: planning, booking and assignment, tax documents (CFDI and Carta Porte), control tower, delivery with proof of delivery (POD), audit, and settlement — measured with indicators such as OTIF (on time in full).
Generic TMS (transportation management system) guides stop at plan–execute–optimize. This map ties systems (ERP, WMS, TMS), Mexico documents, tracking, KPIs, and lean/JIT to the same trip file. If you already run 300+ shipments a month and accounts payable still pays by sampling, the pattern when auditing 100% of the pilot flow is recovering 5–7% of freight spend — because the trip stopped living in chat.
- order to pay (physical + document)
- 8 stages
- rate · CFDI · CP 3.1 · GPS · POD
- 5 docs
- pattern auditing 100% of the pilot
- 5–7%
- pilot on one corridor, no big bang
- 6–8 wk
Cluster context: what a TMS is · pre-pay audit · fake digitization (human bridge).
What the freight journey is (order to pay)
For Mexico–US shippers and logistics operators, “trip” often means three different things by role: the unit on the road (traffic), the status in the TMS (tower), and the invoice in the inbox (finance). The useful hub is the union of all three under one shipment ID.
We expand acronyms as we go: TMS = transportation management system; WMS = warehouse management system; ERP = enterprise resource planning; CFDI = Digital Tax Receipt by Internet; POD = proof of delivery; OTIF = on time in full; KPI = key performance indicator; AP = accounts payable.
This article does not replace the 8 processes with agents guide: that lists automatable work; this draws the buyer map — where each decision lives even if you still use Excel.
Map of 8 stages
Eight stages cover the operable cycle. Short diagram names are milestones; detail — owner, evidence, and typical failure — sits in the table below.
Cycle
Order to pay
Booking
Demand ready
Planning
Capacity and route
Assignment
Tender closed
Documents
Rate and tax
Tower
Milestones and alerts
Delivery
Usable POD
Audit
Pre-pay cross-check
Pay
Release or hold
1. Booking / demand
What it decides: What moves, when, and where
Minimum evidence: Order or load with ID, window, weight/volume
Typical failure: Incomplete order; ambiguous SKU
2. Planning
What it decides: Capacity, consolidation, corridor
Minimum evidence: Load plan; equipment constraints
Typical failure: Plan in chat; no appointment owner
3. Assignment (tendering)
What it decides: Who hauls and at what rate
Minimum evidence: Offer/acceptance with a trail
Typical failure: WhatsApp with no rate confirmation
4. Documents
What it decides: Legality and payment base
Minimum evidence: Rate + CFDI + Carta Porte 3.1
Typical failure: Loose XML; CP with stale catalog
5. Tower / tracking
What it decides: Trip status and exceptions
Minimum evidence: Milestones + GPS with alert owner
Typical failure: Map pin with no protocol
6. Delivery / POD
What it decides: Complete, usable delivery
Minimum evidence: POD bound to the trip ID
Typical failure: Photo in chat; unreadable signatures
7. Audit
What it decides: Does it balance for pay?
Minimum evidence: Cross rate + CFDI + CP + GPS + POD
Typical failure: 1-in-10 sampling; blind payment
8. Pay
What it decides: Release, hold, or dispute
Minimum evidence: Decision with cause and deadline
Typical failure: Pay without a file; recurring leakage
Go deeper by stage in planning, tendering, control tower, and POD.
Trip documents
In Mexico the document trip is not optional: SAT requires CFDI 4.0 with Carta Porte complement version 3.1 (standard since July 2024; catalogs update — verify on the SAT portal). Accounts payable needs the same operating cross-check.
Rate confirmation
What it proves: Agreed price and terms for the trip
Who uses it: Traffic / freight procurement
Risk signal: Accessorials “from memory” with no trail
CFDI (income or transfer)
What it proves: Tax receipt for the service or transfer
Who uses it: Finance / accounts payable
Risk signal: UUID not bound to the shipment ID
Carta Porte 3.1
What it proves: Origin, destination, goods, and transport mode
Who uses it: Tax + in-transit operations
Risk signal: Obsolete catalog keys; stamp rejection
GPS evidence
What it proves: The unit was where the trip claims
Who uses it: Tower / security / audit
Risk signal: Carrier-only account; alerts with no owner
POD (proof of delivery)
What it proves: Accepted delivery (complete / damage / reject)
Who uses it: Customer service / accounts payable
Risk signal: Loose photo; no link to the same ID
Operating rule (not a tax opinion): do not release trip payment until you cross all five pieces to the same ID. Cross-check guide: freight invoice audit. Carta Porte walkthrough: Carta Porte guide.
ERP · WMS · TMS
Three layers, three jobs. The expensive mistake is asking the ERP to “run freight” or the WMS to “pay the carrier.” The table fixes who decides what.
ERP
Its job: Orders, masters, costs, accounting
Not its job: Minute-by-minute routing or dock POD
Healthy handoff: Issues the order with ID and clean masters
WMS
Its job: Location, picking, inventory, ready to ship
Not its job: Assigning carriers or stamping freight CFDI
Healthy handoff: Marks ready with a timestamp to the TMS
TMS
Its job: Assignment, tracking, trip evidence, pay base
Not its job: Located DC inventory
Healthy handoff: Returns status and file to ERP/finance
Warehouse compare: ERP vs WMS. Stack guide: WMS + ERP in Mexico. TMS definition: what a TMS is.
SKU and master data
The SKU (stock-keeping unit) is the atom of the order. If the master lies — weight, dimensions, hazardous UN, pack, customer mapping — OTIF “In Full” breaks even when the truck arrived “on time.”
- The WMS picks what the master says. A bad conversion factor turns “complete in system” into a dock short.
- CFDI and Carta Porte inherit keys and descriptions. Bad SKU-to-SAT mapping means stamp rejection or XML that does not cover what moved.
- The customer measures OTIF with their catalog. If your internal code does not translate to theirs, the reject or retail chargeback starts in master data, not on the highway.
Practical rule: freeze the master-data owner (who changes weight/UN), validate the ERP–WMS–TMS handoff on a pilot corridor, and measure OTIF with the same definition finance uses to release payment. Related KPIs: distribution indicators · glossary what is OTIF.
Tracking methodologies
“Visibility” is not a map pin. Operable tracking combines milestones, GPS with a mirror account, and typed exceptions with an owner.
Trip milestones
What it adds: Agreed states (appointment, in transit, border, delivery)
When it is enough: Low volume; simple corridors
When it falls short: No timestamp or owner; endless “in transit”
Mirror GPS
What it adds: Signal independent of the carrier portal
When it is enough: Mixed fleet; risk or tight OTIF
When it falls short: Alert with no protocol; nobody acts in 10–15 min
Typed exceptions
What it adds: Categories (delay, diversion, detention, missing POD)
When it is enough: Tower with volume
When it falls short: Everything becomes “urgent” in chat
Tower and volume: logistics control tower. Mirror GPS accounts: monitoring with a mirror account.
Quality indicators
Measure service and cash in separate columns. OTIF without a file is theater; audit coverage without OTIF is finance blind to the customer.
OTIF
Operable definition: % trips on time and in full (formula written down)
Typical owner: Operations / service
Alert signal: On time but incomplete; or complete with document reject
Fill rate
Operable definition: % lines or units delivered vs ordered
Typical owner: WMS / DC
Alert signal: High fill in system, low OTIF at customer
% audited pre-pay
Operable definition: % corridor invoices crossed at 100% before paying
Typical owner: Accounts payable
Alert signal: Sampling under 20% at high volume
Time to useful alert
Operable definition: Minutes from GPS/milestone event to named owner
Typical owner: Tower
Alert signal: Unread alerts; median over 15–30 min
Cost / km or / trip
Operable definition: Freight spend of the universe vs km or closed trips
Typical owner: Finance / procurement
Alert signal: Rises with no mix change; accessorials without rate
KPI hub: distribution indicators in Mexico.
JIT, lean, and pressure on the file
Just-in-time (JIT) and lean reduce inventory and waiting — and raise pressure on every trip: there is no stock buffer to hide a late POD or an incomplete CFDI.
- JIT demands tight windows: a missed appointment or a dock without evidence hits OTIF and often chargebacks.
- Lean attacks waste (waiting, empty miles, double entry, document defects). Without a file, “lean” is only headcount cuts.
- 5S in the warehouse orders the node; freight still needs a unique ID and pull-based payment.
Read: what is just-in-time · lean supply chain · 5S methodology.
How to map the real process
Before buying another screen, draw the journey that already exists. Two parallel lines — physical and document — are enough to see the human bridge.
Use one customer or lane with real volume. Do not map the whole network on day one.
Elige un paso para ver el detalle
Detalle del paso · 01
Choose the universe
Where it breaks (human bridge)
The process breaks where a person is the cable between two systems: offering the load in a portal, pasting the rate into Excel, chasing POD in chat, and forwarding the XML to accounts payable. That does not scale with Mexico–US volume.
Symptoms: saturated tower, OTIF that “looks fine” on a dashboard while the customer complains, and payments that leave without a cross-check. The full thesis is in fake freight digitization: you bought licenses; the work is still a human bridge.
Checklist by stage
Use this list in the weekly pilot-corridor meeting. If an item fails, the trip does not advance a stage — even if the truck already moved.
Elige un paso para ver el detalle
Detalle del paso · 01
Booking
What OCL executes without a big bang
OCL Cargo is an autonomous TMS: it does not ask you to shut down Magaya, CargoWise, SAP, Oracle, GM Transport, or Excel on day one. Agents operate the screens and portals your tower already uses, close work, and leave your team on exceptions with a file.
On the freight journey, that means assignment with a trail, tracking with typed exceptions, POD bound to the ID, and pre-pay audit. When fiscal scope applies, OCL can stamp invoices and Carta Porte. It also cross-checks the file on the shipper / freight buyer side so accounts payable releases or holds with criteria — without guaranteeing deductibility (confirm with your tax advisor).
Execution
Work on the trip
Assign
Tender with trail
Monitor
Exceptions
Bind POD
To the same ID
Audit
Before paying
6–8 week pilot
The pilot for this hub is not “install TMS across the network.” It is closing the order-to-pay cycle on one corridor with frozen metrics.
- Weeks 1–2: baseline capture hours, % audited, corridor OTIF, MXN in dispute; physical + document map.
- Weeks 3–6: execution in the pilot universe (assignment, mirror GPS, POD, 100% pre-pay cross-check).
- Weeks 7–8: compare vs baseline; decide scale. When auditing 100% of the flow, the published pattern is recovering 5–7% of spend — reference: logistics operator case, $3.6M MXN / 5.7% in 6 weeks.
Sister playbook: stop capturing shipments.
Key takeaways5 points
- The Mexico freight journey is the order-to-pay cycle: it does not end when the truck arrives, but when the file balances and accounts payable releases or holds with cause.
- Eight operable stages: booking, planning, assignment, documents, tower, delivery/POD, audit, and pay — each with an owner and evidence.
- Minimum documents per trip: rate + CFDI + Carta Porte 3.1 (when applicable) + usable GPS + POD; same ID in tower and finance.
- ERP, WMS, and TMS do not replace each other: they hand off the order with a shared ID; bad SKU master data breaks OTIF “In Full.”
- No big bang: 6–8 week pilot on one corridor; auditing 100% of the flow shows the 5–7% spend pattern (published case). OCL can stamp invoices and Carta Porte.
Does your freight journey still end in chat?
Related reading
Frequently asked questions
It is the full order-to-pay cycle: planning and booking (tendering), documents (rate confirmation, Digital Tax Receipt by Internet — CFDI —, Carta Porte 3.1 complement), control tower, delivery with proof of delivery (POD), pre-pay audit, and KPIs such as OTIF (on time in full). It is not “just moving the truck.”
The 8 business processes with AI agents maps work agents can already close. This hub is the buyer journey map: systems, Mexico tax documents, SKU master data, KPIs, and where the human bridge breaks — even before you automate.
At minimum: rate confirmation, CFDI (income or transfer as applicable), Carta Porte 3.1 complement when domestic movement requires it, usable GPS evidence, and usable POD. Accounts payable should not release payment without crossing them to the same shipment ID. Guide: freight invoice audit CFDI + Carta Porte + GPS + POD.
No. The ERP is the company system of record (orders, masters, finance). The WMS runs the warehouse or DC. The TMS runs the transport trip. A healthy handoff uses a shared ID. See ERP vs WMS and what is a TMS.
Because OTIF (on time in full) requires the unit ordered, the unit picked, and the unit declared in documents to match. If SKU master data is wrong (weight, UN, pack, customer mapping), the WMS can “complete” an order the customer DC rejects or that CFDI/Carta Porte does not cover.
Not at the outset. OCL is an autonomous TMS: agents operate screens and portals, build the trip file, and can stamp invoices and Carta Porte when fiscal scope applies. It coexists with your system of record. Typical pilot: 6–8 weeks on one corridor; when auditing 100% of the flow, the published pattern is recovering 5–7% of spend (3PL case).
Draw two lines for the same trip:physical flow (order, dock, and route to delivery) and document flow (rate, assignment, and GPS to POD, CFDI/Carta Porte, and pay). Mark every human hop. That map shows where to automate first — not the software brochure.