Carrier-Invoice Reconciler
Extracts every line on a carrier invoice, matches it against the contracted rate card — fuel levies, zone pricing, weight breaks — and flags overcharges with a draft dispute attached, holding each exception for a person to clear. It never approves or pays an invoice on its own.
One agent, grounded in your library, with citations on every paragraph.
Carrier invoices get checked line by line, or not at all. The mechanism is consistent: a misapplied accessorial, the wrong fuel levy, a duplicated charge — most errors favour the carrier, and on freight spend they leak margin every month that a manual audit rarely catches in time. Cross-checking every line against the contracted rate by hand simply does not scale, so overcharges are paid and the disputes that do happen land late.
This pattern reads each invoice at the line-item level, matches it against the contracted rate card for that service type and zone, applies the current fuel levy, and flags any line outside tolerance — with the rate-card clause cited and a dispute line drafted. The extraction is AI; the rate match is deterministic logic, so the maths is defensible. Every flag waits in an exception queue for a person to clear. Nothing pays or disputes without a human click.
Estimated build: 3–5 weeks. Most of it is template work we've already done.
Fixed scope, fixed price, fixed dates.
The cost band reflects the engagement shape, not a per-feature line item. We work on fixed scope, fixed price, fixed dates — see the services catalogue for what falls inside each band.
Considering this for your org?
The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where it hurts; we’ll play it back, scope it, and show you what’s possible.