Transportation Management / Freight Audit is where ERP discipline either begins or breaks.
Freight Bill Audit and Carrier Invoice Reconciliation looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Freight overcharge recovery rate above 95%; freight audit savings exceeding 3% of total freight spend; invoice processing time reduced from 5 days to 1 day
The control flow a finance team actually needs.
Step 1
Auto-Match Carrier Invoices To Shipment...
Step 2
Flag Weight/Dimension Discrepancies...
Step 3
Validate Accessorial Charges Against...
Step 4
Generate Dispute Letter With Supporting...
Step 5
Track Dispute Status Through Resolution
The ERP surface involved.
Module
Transportation Management / Freight Audit
Actors
Freight Auditor, Accounts Payable Clerk, Carrier, TMS Audit Engine
Tier
Tier 2
Finance area
Supply Chain, Demand Planning & Logistics
Region lens
US and UK finance teams
Publication date
May 19, 2026
Auto-match carrier invoices to shipment records by PRO number, tracking number, or BOL; flag weight/dimension discrepancies above 1 lb or $5; validate accessorial charges against pre-negotiated accessorial schedule; generate dispute letter with supporting evidence automatically; track dispute status through resolution; calculate freight audit savings monthly; integrate with AP for approved invoice posting; support EDI 210 freight invoice intake and EDI 214 status
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Auto-match carrier invoices to shipment records by PRO number, tracking number, or BOL | Given carrier submits a freight invoice with PRO number and line-item charges |
| Control 2 | flag weight/dimension discrepancies above 1 lb or $5 | when the audit engine auto-matches it against the shipment booking and rate-shopped rate confirmation |
| Control 3 | validate accessorial charges against pre-negotiated accessorial schedule | then discrepancies in weight, zone, or accessorial charges above $5 or 1 lb are flagged with tariff rule citation, valid invoices are forwarded to AP, and disputes are tracked through resolution |
| Control 4 | generate dispute letter with supporting evidence automatically | negative) when a carrier invoice cannot be matched to a shipment record by PRO, tracking number, or BOL then the system must return 422 SHIPMENT_MATCH_NOT_FOUND. |
| Control 5 | track dispute status through resolution | Freight overcharge recovery rate above 95%; freight audit savings exceeding 3% of total freight spend; invoice processing time reduced from 5 days to 1 day |
| Control 6 | calculate freight audit savings monthly | Freight overcharge recovery rate above 95%; freight audit savings exceeding 3% of total freight spend; invoice processing time reduced from 5 days to 1 day |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | When a carrier submits a freight invoice, the TMS audit engine automatically matches it against the original shipment booking and the rate-shopped rate confirmation. It checks for discrepancies in weight, dimensions, zone, accessorial charges, and rate applied. Disputed line items are flagged with the expected vs. billed amount and the applicable tariff rule citation. The freight auditor reviews flagged items, accepts valid charges, and raises formal disputes for invalid ones via the carrier's dispute portal or EDI. Valid invoices are approved and forwarded to accounts payable for payment within terms. Dispute resolution amounts are tracked and recovery rates measured. |
| Control rules | Auto-match carrier invoices to shipment records by PRO number, tracking number, or BOL; flag weight/dimension discrepancies above 1 lb or $5; validate accessorial charges against pre-negotiated accessorial schedule; generate dispute letter with supporting evidence automatically; track dispute status through resolution; calculate freight audit savings monthly; integrate with AP for approved invoice posting; support EDI 210 freight invoice intake and EDI 214 status |
| Acceptance proof | Given carrier submits a freight invoice with PRO number and line-item charges; when the audit engine auto-matches it against the shipment booking and rate-shopped rate confirmation; then discrepancies in weight, zone, or accessorial charges above $5 or 1 lb are flagged with tariff rule citation, valid invoices are forwarded to AP, and disputes are tracked through resolution; (negative) when a carrier invoice cannot be matched to a shipment record by PRO, tracking number, or BOL then the system must return 422 SHIPMENT_MATCH_NOT_FOUND. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`freight_invoice` { invoice_id: string, carrier_id: string, pro_number: string, invoice_amount_minor: int64, invoice_currency_code: char(3), received_at: timestamp, status: enum(RECEIVED/MATCHED/DISPUTED/APPROVED/PAID) }; `freight_audit_line` { audit_line_id: string, invoice_id: string, charge_type: string, billed_amount_minor: int64, expected_amount_minor: int64, currency_code: char(3), dispute_status: enum(NONE/FLAGGED/DISPUTED/RESOLVED) }; (reference, product may differ).API and events
`POST /v1/freight-invoices` { carrier_id, pro_number, lines[] } -> 201 { invoice_id, match_status, flagged_line_count }; `GET /v1/freight-invoices/{invoice_id}/audit`; `POST /v1/freight-invoices/{invoice_id}/dispute-lines` { line_ids[], dispute_reason } -> 200; `POST /v1/freight-invoices/{invoice_id}/approve` -> 200; emits `freight.invoice.approved` and `freight.dispute.filed` events; idempotent via `external_id`.State transitions
`RECEIVED -> MATCHED -> DISPUTED | APPROVED`; `DISPUTED -> RESOLVED -> APPROVED`; `APPROVED -> PAID`; guard: APPROVED blocked if any unresolved flagged audit lines remain.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.