Freight accruals trailed invoices; Transportation Management System (TMS)–Oracle rules by lane/carrier with fuel/accessorial review queue stabilized close

Overview

A logistics provider’s freight accruals were routinely understated because transportation data reached Finance late. The Transportation Management System (TMS) held shipment status, planned rates, and accessorials, while Oracle held the ledger, and the two were reconciled only after invoices arrived. Intelligex integrated the TMS with Oracle, built estimate rules tied to lanes and carriers with fuel and accessorial logic, and introduced a review queue for high?impact accruals. Accruals aligned more closely with actuals, post?invoice adjustments dropped, and period?end entries stabilized—without changing the TMS, carrier portals, or the ERP.

Client Profile

• Industry: Third?party logistics and freight management
• Company size (range): Multi?site operations with domestic and cross?border lanes
• Stage: Mature TMS for planning and execution; Oracle for ERP; accruals estimated in spreadsheets and reconciled after carrier invoices
• Department owner: Finance & Accounting (Cost Accounting and Controllership)
• Other stakeholders: Transportation Operations, Procurement/Carrier Management, Billing/AP, FP&A, IT/Integrations, Internal Audit

The Challenge

Shipment activity moved quickly, but accruals lagged. Operations planned loads and tracked moves in the TMS, including base rates and accessorials. Finance received actual carrier invoices through EDI or portals on a different cadence, so accrued freight at period?end reflected partial information. When invoices posted, variances appeared due to missed accessorials, fuel changes, or lane exceptions, and teams booked corrections that reopened prior periods.

Data fragmentation created blind spots. Lane, carrier, and service level attributes were not standardized between the TMS and Oracle. Fuel surcharge tables changed with market conditions, and accessorial charges (detention, lumper, liftgate, reweighs) were captured in notes rather than structured fields. Multi?stop and mode changes mid?route were hard to estimate consistently. Accrual workbooks grew complex, and AP reconciled after the fact when carrier vouchers arrived.

Audit support was time?consuming. The basis for accruals lived in spreadsheets and emails, invoice tie?outs were manual, and approvals for large variances were scattered. Close meetings focused on explaining swings rather than on preventing them. The team needed timely TMS signals, consistent estimation rules, and a governed exception process to reduce rework.

Why It Was Happening

Root causes were delayed data flow and ungoverned estimation logic. The TMS was the system of record for shipments and contracted rates, but Finance relied on carrier invoices and summaries to validate costs. Without a canonical schema that tied loads to lanes, carriers, fuel tables, and accessorials, accruals were built from partial data. Estimation rules varied by analyst and lane, and changes were not versioned or reviewed centrally.

Ownership and timing were misaligned. Operations updated shipments in the TMS as events occurred, AP processed carrier invoices when received, and Finance estimated accruals at period?end. There was no shared pipeline to turn shipment signals into consistent accruals, monitor variances, and route exceptions with evidence and approvals.

The Solution

Intelligex implemented a freight accrual pipeline that synchronized TMS data with Oracle and applied finance?owned estimate rules by lane, carrier, and service. The pipeline normalized load attributes, referenced contracted rates and fuel tables, estimated accessorials based on shipment events, and generated proposed accruals daily. High?impact or low?confidence items landed in a review queue for Finance and Operations. Variances to carrier invoices were tracked with reason codes, and adjustments required maker?checker approvals. The integration followed Oracle Financials patterns (see Oracle Financials Cloud) and leveraged industry transaction concepts used by carriers and TMS platforms, including EDI standards described by X12 Transportation & Logistics; where the TMS was Oracle Transportation Management, platform guidance aligned with Oracle Transportation Management.

• Integrations: Shipment, rate, and event data from the TMS; carrier invoice feeds via EDI or portal files; accrual and AP voucher activity from Oracle; fuel table updates and accessorial configurations; notifications to collaboration tools.
• Canonical freight schema: Standard fields for load ID, lane (origin/destination), carrier, mode/service, contracted rate, fuel table reference, accessorial events, stops, status, and delivery timestamps; crosswalks to Oracle entities and cost centers.
• Estimate rules engine: Finance?owned rules by lane/carrier/service; fuel surcharges applied by table and effective date; accessorial estimation from shipment events (detention thresholds, lumper at specific facilities, reweigh signals); overrides with rationale.
• Accrual generation and posting: Daily proposed accruals by entity and cost center; safeguards to prevent double counting; linkbacks to shipments and rule versions; automated journal creation in Oracle after approval.
• Variance tracking: Comparison of accruals to carrier invoices at voucher posting; reason codes for differences (rate mismatch, missing accessorial, fuel delta, mode change, data timing); auto?release or true?up logic.
• Exception review: Queue for high?impact or low?confidence accruals; maker?checker approvals with comments and attachments; routing to Operations for shipment context when needed.
• Dashboards and alerts: Period posture by lane and carrier, accrual vs. actual variance patterns, rule impact, and feed health; alerts for spikes and stalled shipments.
• Audit and permissions: Role?based access; immutable logs of rules, estimates, postings, and approvals; evidence packs linking journals to shipments, rates, and invoices.

Implementation

• Discovery: Mapped TMS shipment and rate structures, lane hierarchies, and accessorial events; inventoried carrier invoice feeds and AP workflows; reviewed Oracle posting patterns; sampled variance drivers and audit comments from recent periods.
• Design: Defined the canonical freight schema and identity crosswalks; authored estimate rules by lane/carrier/service and fuel table references; specified accessorial detection logic; designed variance reason codes and exception routing; planned dashboards and audit exports.
• Build: Implemented TMS connectors and normalization; integrated carrier invoice feeds; built the rules engine for rates, fuel, and accessorials; developed accrual generation and Oracle posting; created variance tracking and exception queues; assembled dashboards and notifications.
• Testing/QA: Ran in shadow mode: generated daily accruals while existing spreadsheets and methods continued; reconciled against eventual carrier invoices; tuned rules and thresholds; piloted maker?checker with Finance and Operations.
• Rollout: Enabled automated accruals for selected lanes and carriers first; retained manual accruals as a controlled fallback; expanded by mode and region as stability improved; enforced approvals for high?impact entries after training.
• Training/hand?off: Delivered sessions for Finance, Operations, and AP on reading accruals, handling exceptions, and interpreting variance dashboards; updated SOPs for rule maintenance, fuel table changes, and accessorial evidence; transferred ownership of rules and dashboards to Controllership under change control.
• Human?in?the?loop review: Established a recurring forum to review exception trends, rule updates, carrier rate changes, and fuel impacts; decisions captured with rationale and effective dates.

Results

Accruals reflected current shipment reality instead of trailing invoices. Lanes and carriers followed consistent estimate rules, fuel and accessorial logic was transparent, and high?impact items received timely review. When invoices posted, variances were explained with reason codes and resolved through governed adjustments rather than ad hoc entries.

Close activities stabilized. Journal entries carried links to shipments, contracted rates, and rule versions, so reviews focused on true exceptions. AP, Operations, and Finance worked from the same view of expected costs, and variance dashboards highlighted where rate maintenance or accessorial capture needed attention. The TMS, carrier connections, and Oracle remained; the addition was a governed estimation and reconciliation layer that reduced rework.

What Changed for the Team

• Before: Accruals were built from spreadsheets at period?end. After: Daily accruals were generated from TMS signals with governed rules.
• Before: Fuel and accessorials were easy to miss. After: Fuel tables and event?based accessorial logic were applied consistently.
• Before: Variances surfaced after invoices posted. After: Variance patterns were monitored with reason codes and routed for action.
• Before: Large accruals lacked clear approvals. After: High?impact entries flowed through a maker?checker queue with evidence.
• Before: Audit trails were reconstructed. After: Journals linked to shipments, rates, and rule versions with immutable logs.
• Before: Operations and Finance debated estimates. After: Shared dashboards and rule ownership aligned expectations by lane and carrier.

Key Takeaways

• Connect TMS to ERP; timely shipment and rate data are prerequisites for credible accruals.
• Encode estimation policy; finance?owned rules by lane/carrier/service with fuel and accessorial logic reduce variance noise.
• Monitor and explain variances; reason codes and dashboards turn clean?up into targeted fixes.
• Use a review queue for impact; maker?checker on large or low?confidence accruals strengthens control.
• Tie entries to evidence; link journals to shipments, contracted rates, and invoices for audit readiness.
• Integrate, don’t replace; layer governance on your TMS, carrier feeds, and Oracle.

FAQ

What tools did this integrate with? Shipment and rate data flowed from the TMS, carrier invoices arrived via EDI or portal files aligned to concepts in X12 Transportation & Logistics, and accrual and AP activity posted in Oracle Financials Cloud. Where the TMS was Oracle Transportation Management, platform integration followed Oracle Transportation Management guidance.

How did you handle quality control and governance? Estimate rules for lanes, carriers, and services lived under Finance change control with effective dating. Fuel tables and accessorial logic were versioned. High?impact or low?confidence accruals required maker?checker approval with rationale. Every estimate, variance, and posting was immutably logged with links to shipments, rates, and invoices.

How did you roll this out without disruption? The pipeline ran in shadow mode first, producing daily accruals while spreadsheets remained the source for postings. Results were compared to eventual invoices and tuned. Rollout started with select lanes and carriers, expanded as stability improved, and approvals were enforced for larger entries after training.

How were fuel and accessorials estimated? Fuel surcharges referenced tables with effective dates tied to lane or carrier. Accessorials were inferred from shipment events and facility attributes (for example, detention thresholds or lumper requirements). When signals were incomplete, the item entered the review queue with shipment context for confirmation.

What drove variances between accruals and invoices? Common drivers included rate updates not yet reflected in the TMS, missed accessorial events, fuel table deltas, mode or stop changes mid?route, and timing differences. Variances were reason?coded and either auto?released or routed for true?up with approvals and evidence.

How did AP and Operations participate? AP supplied invoice feeds and validated voucher mappings; Operations provided shipment context for exceptions and maintained contracted rates and accessorial configurations in the TMS. Finance owned rules and approvals. Dashboards showed shared metrics so teams could address root causes rather than repeat corrections.