Module
FreightAudit AI
Check the freight invoice against what was actually contracted.
Watch demo
The carrier's invoice is on the desk. The rate card is a PDF from last year.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- Expected charge rebuilt from the rate card, line by line
- Variance against the invoice, with the evidence for each difference
- Duplicate invoices and duplicate charges
- Potential recovery, with a confidence and a source reference
A worked example
INV-99213 — potential discrepancy ₹84,200
fuel surcharge invoiced 18.5%, rate card 14.0%
chargeable weight 2,140 KG invoiced, 1,980 KG on the AWB
one accessorial charge not present in the contract
→ evidence attached; raise with the carrier
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Carriers invoice against a rate card agreed months earlier that lives in a PDF. The overcharge is rarely a fabricated line. It is a fuel surcharge applied to the wrong base, a minimum chargeable weight rounded the wrong way, or a detention day counted from the wrong date — each small, each defensible, none of them caught. Checking a hundred invoices by hand against a contract is a job nobody has time for, so they are paid. The work is reading the rate card properly and applying it line by line, every time.
Opened by the logistics manager and the finance director — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
An invoice is audited against the tariff you uploaded and nothing else: SIAARU holds no market rate table and no benchmark to score your carrier against, because the only rate that settles a dispute is the one in your contract. A lane with no rate card on file comes back as NO_RATE_CARD by name, which tells you exactly which tariff to load.
Where this sits
One of 36 modules, on one engine.
FreightAudit AI reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.