Module

FreightAudit AI

Check the freight invoice against what was actually contracted.

Beta — live for pilot tenants₹20,000 / month
See pricing

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 figures. 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 is not finished.

BETA rather than AVAILABLE. Shipment weight and volume, carrier invoice numbers and contracted tariffs all import now, so weight-priced contracts audit and duplicate-invoice detection can fire. What remains is a data-quality dependency rather than a missing feature: an invoice can only be audited against a tariff somebody uploaded, and a lane with no rate card on file returns NO_RATE_CARD — correctly, and to a customer who may not know why.

Where this sits

One of 16 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 15 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.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.