Definition
The OCL Cargo freight audit agent is AI software with computer use that, in the OCL Portal, matches every transport invoice against the agreed rate card, CFDI, Carta Porte complement, GPS evidence, and POD before authorizing payment; when it does not match, it builds a dispute or deduct file. It verifies on the buyer side; it can stamp and also verifies before pay — it does not replace your fiscal criteria.
If you audit 1 in 10 invoices, 90% is paid on faith. On the OCL landing, Agent 04 («Audit freight») changes the denominator to 100%: every invoice enters the OCL Portal and is matched against CFDI, Carta Porte, rate, GPS, and POD before release.
Do not confuse this agent with generic freight audit or with a PAC. This is the OCL product agent: computer use + your rules + human exceptions.
What the freight audit agent (OCL) means in practice
On the landing this module is «Audit freight» (Agent 04): Finance and AP match every invoice in the OCL Portal against CFDI, Carta Porte, rate, GPS, and POD. The demo shows the typical pattern: a detention mismatch caught before payment, with an amount to deduct and a dispute ready.
It is not a chatbot that summarizes the invoice. It operates the stack (email, XML, TMS, portal) with computer use, applies your rules, and leaves a trail on the trip ID. Your team only see exceptions already diagnosed.
Neighbors: freight audit is the process; this agent is who runs it at 100%. Pre-pay validation is the control; the agent automates that control.
Why it matters (shipper / 3PL / carrier / AP)
1.Shipper / AP
Stop paying by sample. Every accessorial (detention, layover, TONU, fuel) needs evidence before cash out. Typical 5–7% leakage recovered when leaving sampling.
2.3PL / operator
Scale volume without linear reconciler headcount. The 3PL case went from ~30 min to ~3 min per invoice and 90% without human intervention.
3.Carrier
Disputes with a file (UUID, IdCCP, geofence, POD), not «we do not see it». Get paid faster on what matches.
4.Tax / compliance (buyer)
CFDI and Carta Porte are verified before pay; OCL can stamp invoices and Carta Porte. Playbook: Mexico freight tax.
How it works / when it applies
Landing cycle: invoice lands in OCL Portal, CFDI + Carta Porte match (+ rate, GPS, POD) y discrepancy found a amount to deduct / dispute. Manual today: match by hand, sample, pay errors at volume. With OCL: 100% matched, CP/CFDI verified, ready to dispute.
It fits hardest at ~300+ shipments/month, multi-carrier Mexico–US, parallel capture, and AP that cannot read every XML. It is not step one without a rate card and document checklist: without rules you only accelerate chaotic holds.
Rate card / confirmation
What it proves: Agreed price and accessorials
Typical failure if missing: You pay what the carrier invents on the invoice
CFDI (UUID)
What it proves: Valid tax voucher
Typical failure if missing: Payment without deductible support / SAT risk
Carta Porte 3.1
What it proves: Goods, route, trip parties
Typical failure if missing: Pretty CFDI without a defensible trip
GPS / geofence
What it proves: On-time, detention, deviation
Typical failure if missing: Accessorials without timestamps
POD / ePOD
What it proves: Delivery, signature, condition
Typical failure if missing: You pay incomplete or invented delivery
What it is not (vs PAC, RPA, sampling)
1.Who stamps vs who audits
OCL can stamp invoices and Carta Porte when your stack needs it, and also verifies CFDI + Carta Porte + evidence on the buyer side before pay. See PAC.
2.Not CFDI-only SAT validation
A live UUID ≠ correct rate ≠ real delivery. Guide: what the AI agent checks.
3.Not brittle RPA
RPA breaks on every portal. The agent uses computer use with shipment context. See RPA vs agents.
4.Not sample-based audit
1 in 10 leaves 90% on faith. The agent moves coverage to 100% of the AP inflow.
AP checklist before releasing payment
1.Same trip unit
Invoice, CFDI, CP, GPS, and POD hang off the same ID.
2.Rate and accessorials
Line by line vs rate card or rate confirmation.
3.CFDI + Carta Porte
Type, UUID, IdCCP, origin/destination, goods coherent.
4.GPS / mirror
Geofence and times support detention/deviation. See mirror account.
6.Hold owner
Who acts in minutes when the agent stops payment.
Zen flow: from invoice to pay or dispute
Invoice
Enters Portal
Match
Rate CFDI CP
Evidence
GPS and POD
Close
Pay or dispute
Common mistakes in Mexico
1.Believing «valid XML» is enough
Tax form ≠ price or delivery. Accessorials sneak in there.
2.Auditing without a rate card
Without a rate card the agent has no contractual truth.
3.Splitting tax and operations files
On Mexico–US they must be the same object per trip.
4.Asking OCL to stamp
OCL can stamp invoices and Carta Porte. Confirm with your tax advisor; this is an operating playbook, not a legal opinion.
5.Ignoring accessorials
Detention, layover, TONU, fuel: accessorials guide.
OCL and the shipment file (light)
OCL is an autonomous TMS: this agent closes the finance leg of «assign, track y POD a audit» (plus MVE and tower). It coexists with your system of record; day-one migration is not required.
Full product agent map: what are freight agents. Typical 6–8 week pilot measuring % invoices at 100%, MXN recovered, and dispute cycle time.
Sources and further reading
- Case: 3PL audit agent.
- Checklist: CFDI+CP+GPS+POD audit.
- What it checks: AI agent on the invoice.
- Tax: Mexico freight tax.
- POD: what is POD · Accessorials: guide.
- Agents hub: freight agents.
Key takeaways6 points
- OCL freight audit agent = matches 100% of invoices in the OCL Portal against rate, CFDI, Carta Porte, GPS, and POD before pay.
- It verifies; it can stamp invoices and Carta Porte; it also verifies CFDI/Carta Porte. The carrier issues; AP owns exceptions.
- Leaving sampling in Mexico often recovers 5–7% of freight spend (3PL case: $3.6M MXN in 6 weeks).
- Without a written rate card, POD, or defensible GPS the agent holds with a file; it does not invent evidence.
- Coexists with CargoWise, Magaya, SAP, or Oracle: the TMS records; the agent runs pre-pay matching.
- OCL agents hub: freight agents.
Still paying 90% blind?
Frequently asked questions
Product Agent 04: computer-use software that matches every invoice in the OCL Portal against rate, CFDI, Carta Porte, GPS, and POD before pay, and builds a dispute when it does not match. It can stamp; it also verifies.
In typical Mexico operations, 5–7% of freight spend. The public 3PL case documented $3.6M MXN in 6 weeks across 2,250 invoices (5.7%).
Yes. OCL can stamp invoices and Carta Porte; it also verifies and leaves a pre-pay file for AP.
No. The hybrid pattern keeps the system of record and adds the audit agent. See TMS vs agents.
The agent can hold payment and open an exception; it does not invent evidence. That is why GPS tracking and POD capture agents exist.
Yes: the demo’s typical mismatch is detention. Without geofence/POD the dispute is weak. See detention.
The business-process AI agent glossary defines the category. This agent is OCL’s concrete AP/freight module with Mexico tax sources.