The problem it solves
Freight disputes are where money goes to die. A carrier bills for a 4-hour detention; the GPS trail shows 90 minutes. A 3PL claims a failed delivery was customer-refused; the driver app shows no attempt was made. An accessorial is charged at the peak rate; the contract specifies off-peak. Each case is small — a few hundred dollars, sometimes a few thousand. Individually, they’re not worth chasing. Collectively, they’re tens of millions per year at an enterprise operator, and they represent the margin leak no one has the bandwidth to close.
The deeper pain is cycle time. A disputed invoice sits in a suspense account. Procurement emails the carrier. The carrier asks for evidence. Someone digs out the POD, the GPS trail, the contract clause. Weeks pass. By the time the case resolves — often as a partial credit negotiated on volume — the working capital is long gone and no pattern has been learned.
What it is
Vera is the Dispute Resolution Agent inside AgentFleet — the component that owns the full dispute lifecycle from flag to settlement. She works in lockstep with Nexa, which flags the exception, and executes the resolution: pulls the contract clause, assembles the evidence packet, builds the carrier-facing case, negotiates within configured policy bounds, and either auto-settles, auto-escalates, or routes to a human commercial owner with everything pre-built.
What’s new-age about Vera is that she treats every dispute as a reasoning problem, not a ticket. She parses the carrier’s claim, compares it to the operator’s evidence, identifies the specific clause in dispute, and reasons about which party is correct based on contract language and actual shipment data. The reasoning is exposed — every settlement carries a traceable chain of logic from contract clause to GPS event to POD to final amount. That traceability is what lets the agent operate at tens-of-millions of dollars of scale without losing auditability.
Core capabilities
| Capability | What it does |
|---|---|
| Invoice-to-contract matching | For every disputed line, Vera fetches the relevant contract object — rate card, accessorial clause, dwell-time grace, fuel linkage — and locates the exact clause the dispute turns on. |
| Evidence assembly | Pulls GPS trail, geofence entry/exit timestamps, ePOD, signature, photo proof, driver app events, and weather/traffic context — packaged as a carrier-facing case file. |
| Automated reasoning | Given the claim, the clause, and the evidence, Vera computes the defensible amount and generates a plain-language rationale: “Carrier billed 4h detention; GPS shows 1h 28m inside geofence; contract grace is 2h. Defensible detention: 0.” |
| Settle-vs-escalate decision | Confidence-tiered: high-confidence cases auto-settle within policy; medium cases auto-draft the carrier response; low-confidence cases route to a commercial owner. |
| Negotiation policy engine | Operators set policy bounds (e.g., accept up to 10% settlement if cycle time exceeds 30 days) and Vera negotiates inside them. |
| Multi-party dispute handling | For disputes involving a shipper + carrier + 3PL + end customer (common in cross-border), Vera manages each leg of the case. |
| Chargeback & credit-note generation | Where the resolution is a credit or a chargeback, Vera drafts the instrument, routes for approval, and pushes to ERP. |
| Pattern recognition & systemic flags | Recurring dispute categories at a carrier — repeated detention over-claims, accessorial misapplications, fuel-surcharge mis-indexing — are surfaced as systemic issues for renegotiation, not just line-item fixes. |
| Carrier scorecard feedback | Every dispute outcome feeds the carrier performance layer used by Multi-Carrier Intelligence — so repeat offenders get deprioritised in future allocation. |
| Audit-grade trail | Every Vera decision carries the claim, the clause, the evidence, the rationale, the confidence, the action, and the approval chain — immutable and exportable. |
| Working-capital release | Disputed invoices don’t linger in suspense. Cycle times typically move from 30–60 days to 7–14 days after go-live. |
| Regulatory-grade exposure | Deployed under 21 CFR Part 11 and GDP for pharma, SOX controls for listed operators. |
How it works
Vera is architected as a reasoning component on top of a structured contract store, a shipment event store (fed by Atlas), and a POD repository. When Nexa flags a variance, Vera picks up the case, retrieves the three source-of-truth objects, runs the reasoning pass, and executes — settle, escalate, or route.
clauses, grace, accessorials] --> D[Reasoning engine] E[Shipment events
GPS, geofence, dwell] --> D F[POD repository
signatures, OTP, photos] --> D B --> D D --> G{Confidence tier} G -->|high| H[Auto-settle within policy] G -->|medium| I[Draft carrier response → approve] G -->|low| J[Commercial owner queue] H & I & J --> K[Outcome → ERP + carrier scorecard]
Below is the sequence for a detention dispute — the single highest-volume category at most FMCG and parcel operators.
The reasoning chain — clause → evidence → computation → outcome — is exposed in the audit record. If a regulator or auditor asks why a specific dispute settled at a specific amount, the answer is a clickable trail, not a human memory.
Why this is different from a freight audit service
A freight audit service is a forensic function. It reviews past invoices, produces a list of suspected variances, and hands them back to your team to chase. The chasing is where the economics break down — the cost of recovering a $400 detention over-charge often exceeds the recovery itself, so the smaller cases get dropped and only the big ones get fought.
Vera inverts the economics. Because reasoning is automated, evidence assembly is automated, and the carrier-facing case is drafted by the agent, the marginal cost of pursuing a $400 case is close to zero. That’s how the long tail of small disputes — the ones traditionally abandoned — gets fully captured. At a global alco-bev leader operating across 70+ countries, that long-tail capture is a meaningful portion of the $25M+ Vera has autonomously resolved. The headline number isn’t a handful of big settlements; it’s tens of thousands of small ones that no human-powered team would have had the bandwidth to chase.
Proven outcomes
| Customer type & scale | Outcome |
|---|---|
| Global alco-bev leader, 70+ countries, 2M+ annual trips | $25M+ in carrier/vendor disputes autonomously resolved; 28% reduction in LSP payments for excessive stay at customer location; route settlement automation from 70% to 90%+ |
| Global biotech, rare-disease therapeutics, 30+ countries | 50–70% manual effort reduction in settlement & dispute handling; rate-card enforcement across fragmented multi-carrier landscape |
| One of Asia’s largest quick-commerce arms, 5M+ orders/month | ~82% reduction in COD loss; carrier scorecards feeding allocation; ~21% reduction in cost-per-delivery |
| Premium Indian B2B express network, 49 cities, 3,500+ pincodes | 100% e-way bill & reconciliation coverage; appointment-delivery disputes resolved autonomously with Clara handoff |
| Latin America’s largest airline group, $12–13B revenue, 500K+ tonnes | Shift from reactive to proactive ops; ~50–60% reduction in control-tower manpower, freeing commercial teams to focus on dispute patterns rather than case-by-case |
Integrations
- ERP & finance: Oracle ERP · SAP · NetSuite · Microsoft Dynamics · Tally · Xero
- Contract & legal systems: CLM platforms · Veeva QMS (pharma) · custom contract stores
- Shipment telemetry: Wialon · Wheelseye · carrier APIs (240+) · IndiGo cargo API · native GPS
- POD & evidence: Shipsy ePOD · driver app · photo & signature repositories · OTP systems
- Carrier portals & EDI: EDI 210/214 · carrier dispute portals · email-based dispute inbox
- Workflow & approvals: ServiceNow · Jira · Microsoft Approvals · native AgentFleet approvals
- Analytics: Snowflake · BigQuery · Redshift · BI dashboards for dispute trends and recovery
Deployment
Most enterprises go live with Vera in 10–14 weeks alongside or shortly after Nexa; standalone Vera deployments are faster (8–10 weeks) when the contract and invoice data is already structured.
Phase 1 — Discovery (weeks 1–3). Dispute taxonomy workshop — what types, what values, what carriers, what cycle times today. Audit of historical disputes for pattern extraction. Commercial policy mapping — what can Vera settle autonomously, what requires human approval.
Phase 2 — Configuration (weeks 3–7). Contract digitisation alongside Nexa (shared contract store). Evidence source mapping — GPS telemetry provider, POD format, geofence setup. Negotiation policy bounds per carrier.
Phase 3 — Pilot (weeks 7–11). Shadow mode on 30–60 days of historical disputes — Vera resolves, humans verify. Then assisted mode on live cases (Vera drafts, humans approve). Success criteria: resolution accuracy vs. human benchmark, cycle-time reduction, recovered-dollar value, carrier relationship health.
Phase 4 — Scale (weeks 11–14+). Autonomous mode with policy bounds, rolled out by carrier tier. Governance: weekly dispute review (finance + ops + legal), monthly carrier performance review, quarterly policy and contract audit.
Success criteria locked pre-go-live are always dollar-denominated: recovered value, working-capital release, manual-touch reduction, cycle-time compression.
Security & compliance
- SOC 2 Type II · ISO 27001 · GDPR
- SOX controls: segregation of duties between reasoning and payout; immutable audit log on every decision
- 21 CFR Part 11 · GDP · GMP for pharma-relevant deployments — validated system, electronic signatures
- Three-tier confidence scoring on every Vera action
- Human-in-the-loop mandatory above configurable thresholds (dollar value, carrier tier, dispute category)
- Full traceability — every outcome carries the contract clause, evidence chain, reasoning, and approver
- Data residency options for contract, shipment, and evidence data
Case study callouts
Global alco-bev leader · 70+ countries, 2M+ annual distribution trips
$25M+ in carrier and vendor disputes autonomously resolved. Payments to logistics service providers for excessive stays at customer location cut by 28%. Fully automated route settlement moved from 70% to over 90% — a direct consequence of Vera and Nexa matching actual shipment behaviour to contract terms across every country of operation.
Global biotech · rare-disease therapeutics, 30+ countries
Rate-card enforcement and automated dispute resolution across a fragmented, multi-carrier, multi-CDMO footprint. Manual effort down 50–70% while SLA compliance moved past 95%. Integrated with Oracle ERP and Veeva QMS for batch-linked audit trails.
One of Asia’s largest quick-commerce arms · 5M+ orders/month
~82% reduction in COD loss and ~21% reduction in cost-per-delivery. Carrier scorecards — fed by Vera’s dispute outcomes — flowed into the allocation engine, so repeat over-claimers got deprioritised in real time. The feedback loop between dispute resolution and allocation is the compounding margin gain.