The problem to investigate
The same service label or charge code may mean different things across carriers. Standardization must preserve source meaning instead of assuming all records are interchangeable.
Common causes to check
- Carrier codes mapped inconsistently
- Account numbers colliding across providers
- Different rate bases forced into one comparison
What your organization should review
- Use carrier plus account and shipment identity
- Maintain mappings for service and charge codes
- Apply each carrier's own agreement and date basis
Verification and supporting evidence
Retain source-to-standard mappings and carrier-specific evidence. Flag ambiguous mappings before aggregating findings so a portfolio view does not amplify interpretation errors.
Illustrative review example
Two carriers use the same short code for different additional services. The team preserves separate definitions and verifies each charge under its own fee schedule.
How this fits the AuditRes workflow
Use Freight audit and reporting with carrier-specific source references, preserving each verified exception's agreement and shipment context in recovery records.
AuditRes Freight supports invoice audit, exception visibility, evidence preservation, recovery tracking, and reporting inside a company workspace. Use these review stages to keep shipment facts, the disputed charge, and the documented case outcome connected.
Frequently asked questions
Can all carrier invoices use one expected-rate formula?
Only where the applicable agreements support it. A shared workflow should allow different rating rules and evidence requirements.
Are the examples actual customer recoveries?
No. The examples illustrate a review decision; they are not customer case studies, measured savings, or promised results. A real finding requires the relevant shipment, invoice, and agreement evidence.