PDF rate cards and varied invoices to TMS/X12 pre?payment rating, audit?ready disputes

Overview

A logistics company was routinely overpaying carriers and spending hours on after-the-fact reconciliations because rate cards lived in PDFs and spreadsheets, while invoices arrived in many formats with inconsistent codes. Intelligex implemented a contract repository that structured carrier rate tables and accessorial rules, and matched them against shipment details from the Transportation Management System (TMS) and carrier invoices. Discrepancies were flagged before settlement, disputes were supported by clear evidence, and Accounts Payable moved from manual checks to governed, pre-payment reviews.

Client Profile

• Industry: Logistics and transportation services (multi-mode)
• Company size (range): Multi-region network with diverse carrier base
• Stage: Established TMS and carrier integrations across parcel, LTL, and truckload
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Carrier management, Finance/Accounts Payable, Operations planning, Legal, IT applications, Customer service

The Challenge

Carrier contracts were detailed and varied by mode, lane, and service level. Rate cards for parcel, Less-Than-Truckload (LTL), and truckload included base rates, zone or lane matrices, class-based tariffs, minimum charges, accessorials, and fuel surcharge formulas. Many contracts were stored as PDFs with different layouts, and exceptions were hidden in footnotes. Invoices arrived through Electronic Data Interchange (EDI), carrier portals, or email PDFs. The TMS held shipment facts, but translating contracts into executable rules and comparing them to billed amounts was largely manual.

Accounts Payable and carrier managers relied on spreadsheets and tribal knowledge to check charges. Accessorials were coded inconsistently, fuel surcharges used varying baselines, and package dimensions or freight class sometimes differed between the TMS and the carrier bill. Disputes took time to assemble and often lacked a clear audit trail, which strained relationships and delayed payments. Replacing the TMS or renegotiating every contract was not feasible; the team needed a way to structure what they had, connect it to shipment and invoice data, and institutionalize the audit in a way carriers would trust.

Why It Was Happening

The core issue was unstructured and fragmented data. Contracts lived as documents, not data, and each carrier expressed similar concepts differently. The TMS, invoice formats, and internal cost codes were not aligned to a shared set of definitions, so apples-to-apples comparisons were hard. Without a canonical model for rates and accessorials, rules were reinterpreted with each payment cycle and by each reviewer.

Process gaps compounded the mismatch. Invoices were processed on tight timelines, and discrepancies were found late, after accruals or payments were in motion. There was no consistent pre-payment audit, no shared tolerance bands by category of charge, and no simple path to create a well-evidenced dispute. Ownership for edge cases—like class changes, reweighs, or dimensional adjustments—was unclear, which led to inconsistent outcomes.

The Solution

Intelligex delivered a contract repository and rating service that sat above the existing TMS and Accounts Payable systems. Carrier contracts were ingested and modeled as structured rate tables and rules, including base rates, zones, classes, accessorials, and fuel surcharge logic. The service matched shipment facts from the TMS with invoice lines and recalculated the expected charge. Variances beyond defined tolerances triggered a human-in-the-loop review and, when confirmed, generated dispute packages with references to the contract clause and shipment data.

• Integrations: Bi-directional connection to the TMS for shipment legs, weights, dimensions, service levels, and events; ingestion of carrier invoices via EDI (for example, ANSI X12 freight invoices) or API; synchronization with Accounts Payable for pre-payment holds and releases; optional PDF ingestion with structured extraction for non-EDI carriers. General EDI guidance aligned with X12 transaction sets, and fuel surcharge logic referenced the U.S. Energy Information Administration’s diesel benchmarks from EIA.
• Contract modeling: Canonical schema for modes, zones, lanes, classes, service levels, base rates, minimums, discount matrices, accessorial rules, and fuel surcharge formulas with effectivity dates and versioning.
• Rating engine: Rule-driven calculation that reproduced contract math for parcel, LTL, and truckload, including dimensional weight, class/FAK logic, detention/demurrage, liftgate, residential, and other accessorials.
• Invoice matching: Line-level comparison between expected charges and billed amounts with tolerance bands by category; reason classification for common variances such as reweigh, reclass, redelivery, and address corrections.
• Exception workflow: Human-in-the-loop review for out-of-policy variances with links to shipment events and contract clauses; dispute package generation with attachments and commentary for carrier portals or EDI response.
• Review gates: Approvals required for write-offs, overrides, and tolerance adjustments; segregation of duties between creators and approvers of disputes.
• Dashboards: Real-time visibility into variance types by carrier and mode, dispute backlog and outcomes, contract coverage gaps, and accessorial trends.
• Permissions: Role-based access for AP, carrier managers, and operations; audit logs for contract changes, tolerance edits, and dispute actions.

Implementation

• Discovery: Collected representative contracts across parcel, LTL, and truckload; mapped how the TMS captured weights, dimensions, NMFC classes, zones, and service levels; reviewed invoice sources and coding; identified frequent variance categories and current dispute practices.
• Design: Defined the canonical rate and accessorial schema; established mapping between carrier codes and internal service definitions; set tolerance bands and reason codes; designed event schemas for shipment rating, invoice receipt, variance detection, and dispute lifecycle.
• Build: Implemented the contract repository, parsers, and rating engine; built connectors to the TMS, EDI feeds, and AP; configured fuel surcharge models and effectivity management; created the exception workflow and dashboards.
• Testing/QA: Back-rated historical shipments and compared against invoices to validate contract math; ran parallel audits in observe-only mode; conducted human-in-the-loop reviews for edge cases like dimensional adjustments and reclassifications to refine rules and tolerances.
• Rollout: Started with a subset of carriers and one mode; kept the legacy AP process as a fallback; progressively expanded coverage as variance detection stabilized and dispute outcomes aligned with expectations.
• Training/hand-off: Scenario-based sessions for AP analysts and carrier managers; quick-reference guides on common variance types; runbooks for dispute submission and follow-up; transitioned daily operations to finance and carrier management with IT support on call.

Results

The team shifted from reactive reconciliation to proactive, pre-payment auditing. Expected charges were computed consistently from structured contracts, and mismatches surfaced early with clear explanations. AP no longer combed through spreadsheets to verify invoices; instead, they reviewed flagged exceptions with shipment context and contract citations, releasing clean bills straight through.

Carrier relationships improved because disputes were backed by transparent, reproducible calculations. Overpayments were caught before settlement, and recurring issues—like ambiguous accessorial triggers or inconsistent codes—were documented and addressed in contract updates. Leaders gained visibility into where charges deviated from plan and used that insight to prioritize negotiations and operational fixes.

What Changed for the Team

• Before: Contracts lived in PDFs and were interpreted differently each time; After: Rate tables and rules were modeled in a shared repository with version control.
• Before: AP manually reconciled invoices line by line; After: The system auto-rated shipments and flagged only true exceptions for review.
• Before: Disputes relied on email threads and screenshots; After: Dispute packages pulled shipment facts and contract clauses into a single, shareable record.
• Before: Accessorials were inconsistently coded; After: Standardized mappings and validations aligned carrier codes with internal categories.
• Before: Fuel surcharge calculations varied by carrier and week; After: A common model referenced the same benchmark source and effectivity dates.

Key Takeaways

• Turn carrier contracts into data, not documents—structured rate tables make audits repeatable and trustworthy.
• Anchor pre-payment audits to shipment facts from the TMS, and compare against invoices with clear tolerance bands.
• Standardize codes and definitions across carriers to reduce noise, especially for accessorials and service levels.
• Use a governed workflow with human-in-the-loop approvals for ambiguous cases and write-offs to maintain control and credibility.
• Start with the highest-volume carriers and modes to prove the math and refine tolerances, then scale coverage.

FAQ

What tools did this integrate with?
The rating service connected to the existing TMS for shipment data and to Accounts Payable for holds and releases. Carrier invoices were ingested via EDI aligned with X12 transportation transaction sets or through carrier APIs and portals. The approach worked alongside common TMS platforms such as Oracle Transportation Management and SAP Transportation Management, without replacing them.

How did you handle quality control and governance?
Contracts were versioned with effectivity dates, and changes required approvals. Tolerance bands were managed centrally and adjusted through controlled changes. Every variance carried a reason code, and exceptions moved through a human-in-the-loop review with audit logs that captured who approved what and why. Sensitive overrides and write-offs required dual review.

How did you roll this out without disruption?
We ran the audit in observe-only mode first, back-rating shipments and comparing results privately against invoices. The legacy AP process remained in place while we tuned mappings and tolerances. Once results were stable and stakeholders were comfortable, we enabled pre-payment holds and expanded by carrier and mode.

How were fuel surcharges and accessorials modeled?
Fuel surcharge formulas were configured per contract using shared baselines referenced from the EIA diesel benchmarks. Accessorials were mapped to a canonical set of codes with rule triggers tied to shipment events, dimensions, service levels, and delivery attributes, ensuring consistent calculation and comparison.

What about non-EDI invoices and unstructured contracts?
For carriers without EDI, invoices from portals or PDFs were ingested through API connectors or structured extraction templates, with stewards reviewing any fields below confidence thresholds. Contracts in PDF were translated into the repository using templates by mode and carrier, with human review for exceptions and unusual clauses before activation.