Every carrier invoice checked against what you actually agreed to pay.
LogAI compares each line on the carrier invoice to the rate confirmation and the accessorials that were actually incurred on the load. Discrepancies are flagged with evidence before any AP bill is created. Carrier pay equals agreed rate plus approved accessorials, minus advances and quick-pay discount — nothing more.
How Audit works
Carrier invoices enter. Verified AP bills leave. Customer invoices go out with documents attached.
Carrier Invoice vs Rate Confirmation Comparison
Every line on the carrier invoice is matched against the signed rate confirmation. Line-haul rate, fuel surcharge, and stop charges are compared automatically. Any amount that does not match the confirmation is flagged with the delta and the specific line at issue.
Accessorial Audit
Carrier-billed accessorials are validated against what actually occurred on the load. Detention is verified against the detention clock timestamps. TONU is verified against the tender-no-show event. Lumper charges require a lumper receipt. If the accessorial cannot be verified, it is flagged — not approved.
Delta Flagging with Evidence
Every discrepancy surfaces in the audit queue with the evidence: the rate confirmation rate, the invoiced rate, the difference, and the load event that supports (or contradicts) the carrier's claim. Auditors see exactly what to dispute and why.
AP Bill Emission
Once a carrier invoice passes audit, an AP bill is emitted to the connected finance module or ERP. Quick-pay discount, advance deductions, and any approved claims are factored into the net payable before the bill is created.
Customer Invoice Emission
The customer invoice is generated from the agreed customer rate plus approved accessorials. All freight documents — signed POD, BOL, rate confirmation — are attached. The invoice is emitted to the finance module or sent directly to the customer, depending on your billing configuration.
Short-Pay Signal to Pey
When a customer pays less than the invoiced amount, LogAI emits a short-pay signal to the Pey (accounts receivable) module for follow-up. LogAI never matches payments — that is Pey's domain. The load record shows the open AR balance until Pey closes it.
Every rate line is traceable to its source
No invoice line is approved on faith. Each charge is compared to the agreement and the load events that verify whether the charge was actually incurred.
| Line Item | Source of Truth | Audit Check |
|---|---|---|
| Line-haul rate | Rate confirmation | Matches invoiced line-haul exactly |
| Fuel surcharge (FSC) | Rate confirmation or FSC table | Calculated correctly per the agreed FSC schedule |
| Detention | Detention clock timestamps | Minutes verified against free-time window in rate confirmation |
| TONU | Tender no-show event | Load was actually tendered, carrier did not cover |
| Lumper | Lumper receipt in document pipeline | Receipt present and amount matches invoiced charge |
| Stop charge | Rate confirmation stop terms | Correct number of stops, correct per-stop rate |
| Quick-pay discount | Quick-pay terms in carrier profile | Deducted only when payment is within the agreed window |
How LogAI calculates net carrier pay
Agreed rate confirmation rate
+ Approved accessorials (detention, lumper, TONU, etc.)
− Advances paid
− Approved claims deductions
− Quick-pay discount (if applicable)
The AP bill is emitted to your connected finance module or ERP after the audit is approved by a dispatcher. The Carrier Invoice Audit agent flags discrepancies — a human reviews and approves before any bill is created.