An AI agent that audits freight invoices with Carta Porte does not "just read the invoice": it matches it against five evidence sources, approves what checks out, and holds what does not with a case file.

  • Agreed rate
  • CFDI
  • Carta Porte complement
  • Trip GPS
  • POD

In Mexican operations, that 100% match typically recovers 5-7% of freight spend in a 6-8 week pilot.

Clear from the first paragraph: OCL Cargo verifies and audits; it does not issue or stamp as a PAC. The CFDI and complement are generated by your carrier (or their Authorized Certification Provider). We read them, match them, and build the payment case file.

If you are coming from AP, pair this with how to automate freight accounts payable and what freight audit is.

Answer: the 5 matching sources

Every freight invoice claims there was a trip, at a rate, with tax backing and a delivery. The agent does not trust that claim: it compares it to external evidence. These are the five sources and the role of each.

1. Agreed rate

What it contributes: Price by lane, unit, and current carrier

What a mismatch detects: Inflated base freight, missed discount, wrong unit billed

2. CFDI

What it contributes: Valid tax XML for the SAT

What a mismatch detects: Wrong RFC, duplicate UUID, invoice that does not cover the trip

3. Carta Porte

What it contributes: Transfer complement (locations, goods, vehicle)

What a mismatch detects: Inconsistent origin/destination, broken SAT codes, poorly documented trip

4. GPS

What it contributes: Real trip path and times

What a mismatch detects: Inflated detention, deviation, ghost trip, geofence with no arrival

5. POD

What it contributes: Proof of physical delivery to the receiver

What a mismatch detects: Delivery not credited, shortage, refusal without evidence

Five sources. One invoice. The agent only approves when the match closes.

What each source checks

Agreed rate

Compares base freight and accessorials against the current rate sheet by lane, unit type, and carrier. If the contract says one thing and the invoice another, the gap is flagged before the money leaves. This is the core of freight audit.

CFDI

Reads the XML: RFC, amounts, UUID, link to the service. A valid CFDI is not enough if it does not correspond to the trip you think you are paying. The full tax frame is in Mexico transport invoicing 2026.

Carta Porte complement

Checks that the 3.1 complement documents the same move as the shipment: locations, goods, vehicle, and coherence with the CFDI. Typical errors that reject or weaken the voucher are listed in Carta Porte 3.1 errors. Again: verify is not issue.

Trip GPS

Matches real times and route. A "3 hour" detention is not paid if the geofence shows 1 hour 13 minutes. If there is no signal the trip happened, the agent does not let a ghost trip through.

POD

Confirms delivery: signature, stamp, ePOD, or acknowledgment. Without POD, you have a documented move but no receipt. The difference between Carta Porte and POD is in the document triad.

What gets approved and what gets held

Approved

  • Rate and accessorials match what was agreed
  • CFDI and Carta Porte are coherent with the trip
  • GPS confirms path and times
  • POD credits the delivery

Held with case file

  • Freight or detention off-contract / without evidence
  • Inconsistent complement or errors that weaken the CFDI
  • GPS does not support the charge or the trip
  • Missing POD or contradiction with what was billed
The analyst stops keying data and only decides exceptions with a case file.
Rate, CFDI, Carta Porte, GPS, POD
5 sources
Typical recovery of freight spend
5-7%
Pilot length against baseline
6-8 wks

OCL verifies: it does not issue or stamp as a PAC

This distinction matters in RFPs and finance conversations: we do not promise to replace the tax issuer. We promise 100% coverage of invoice-trip matching, with a defensible case file.

The same rule holds across dozens of carriers: the agent does not depend on every carrier using the same PAC; it depends on the XML arriving and being matchable.

Typical recovery: 5-7% of spend

When you move from sampling to auditing 100% before paying, the typical leak that shows up in Mexico is in the 5-7% of freight spend range. It is not "magic savings": it is off-contract rates, detention without GPS, duplicate accessorials, and deliveries without POD that used to be settled by inertia.

Reference case: a logistics operator audited 2,250 invoices and detected $3.6M MXN in unsupported charges in 6 weeks. The full story is in how a 3PL detected $3.6M MXN. The AP flow that sustains that result is in freight accounts payable automation.

6-8 week pilot

You do not need to migrate TMS to see if the match works. The OCL Cargo pilot lasts 6-8 weeks, connects to SAP, Oracle, CargoWise, Magaya, GM Transport, or Excel, and runs on your real invoice flow. It is measured against baseline: % audited, MXN detected, and analyst hours per invoice. Market context in best TMS in Mexico 2026.

1-2

Focus: Data connection, rate sheet, and business rules

Output: Baseline and pilot scope defined

3-6

Focus: Agent auditing 100% of the pilot flow

Output: Real approvals, holds, and case files

7-8

Focus: Measurement vs baseline and expand decision

Output: Numbers finance can defend

Short pilot, real operation, before-and-after metrics. No endless project.

Want to see the 5-source match on your flow?

In a demo we show how the agent reads CFDI and Carta Porte, matches rate, GPS, and POD, and holds what does not check out. Verifies and audits; does not stamp. 6-8 week pilot.

Sources and further reading

Key takeaways5 points
  1. The AI agent matches every freight invoice against 5 sources: rate, CFDI, Carta Porte, GPS, and POD.
  2. What checks out is approved; what does not is held with a case file ready for dispute.
  3. OCL Cargo verifies and audits. It does not issue Carta Porte, stamp CFDI, or act as a PAC.
  4. Auditing 100% of the flow typically recovers 5-7% of freight spend.
  5. The pilot lasts 6-8 weeks on your current stack, with no migration project.

Frequently asked questions