TMS Multi-Index Fuel Surcharges: EIA Peg Scales, Regional PADD Variance, and Hybrid Hedging Formulas

Fuel volatility and carrier margin architecture

Fuel remains one of the largest variable cost lines for asset based carriers and one of the least controlled without deliberate design. Carriers choose among pass through fuel surcharges pegged to public indices, negotiated all in rates with implicit fuel risk, financial hedging instruments, bulk tank programs, and hybrid policies by customer or lane. Each choice shifts risk between carrier, shipper, and driver. The architecture job is to make that shift visible in SQL models leadership can stress test before diesel spikes erase a quarter of operating income.

Scott Elliott founded Strong Tower Consulting, LLC on July 29, 2008 (Minnesota File 2948628-2) and has spent eighteen years modeling fuel recovery alongside dispatch and rating systems. Carriers evaluating surcharge tables versus hedging programs may begin with a historical backtest workshop by calling 763-244-1373.

Dynamic fuel surcharge mechanics

Dynamic fuel surcharges adjust linehaul or total charges based on a benchmark index and a fleet specific formula. Formulas include base index price, incremental cents per mile per penny change, caps, floors, and rounding to nearest tenth of a cent. Some customers accept weekly updates. Others require monthly averages or regional index splits.

Operational success depends on synchronizing rating engines, TMS fuel tables, EDI 210 outputs, and driver settlement pass through rules. When surcharge updates lag index publication, carriers either under recover or trigger customer dispute batches. Automate effective datetime activation with audit logs showing who approved each table version.

DOE pegging and publication timing

The United States Department of Energy publishes weekly retail diesel benchmarks commonly used in North American trucking contracts. Pegging language in contracts names the exact series, geographic area, and which week’s value applies to which pickup week. Misinterpretation of lag rules creates systematic mismatch with customer payment systems.

SQL jobs should import index values on publication schedule, store historical series immutably, and join loads by pickup datetime and origin region rules. Never overwrite prior index rows. Corrections belong in adjustment rows with reasons.

Weekly index adjustments in practice

Weekly adjustments require a calendar table mapping pickup dates to index weeks. Customer exceptions exist for holidays when publication shifts. Rating procedures must read the mapping table rather than hard coding offsets in scattered reports.

• Index import with validation against prior week delta thresholds
• Customer specific base price and multiplier stored as versioned rows
• Preview report showing miles affected and revenue delta before activation
• Driver pass through percentage applied consistently with billing
• General ledger accounts separating surcharge revenue from linehaul

Finance should reconcile surcharge revenue to index movement times billable miles times formula derivatives within tolerances each month. Unexplained variance indicates wrong miles, wrong effective dates, or loads billed on obsolete tariffs.

Fuel hedging versus surcharge recovery

Hedging uses financial contracts or structured purchases to lock in all or part of future fuel exposure. Surcharge recovery passes index movement to customers contractually. Hedging protects margin when indexes rise faster than surcharge formulas allow recovery, or when customers delay acceptance of updates. Hedging introduces basis risk when fleet purchase geography, card network pricing, or bulk tank costs diverge from the DOE benchmark used in customer contracts.

Carriers sometimes hedge physically through bulk storage while still surcharging customers on DOE pegs. Basis between rack, taxes, and DOE retail must appear in risk models or leadership misreads hedge effectiveness.

Hedging risk models carriers should maintain

A practical risk model estimates net fuel expense under scenarios: index up ten percent, index down ten percent, lagged surcharge recovery, and customer mix with frozen all in rates. Monte Carlo simulation is optional. Deterministic scenario tables are mandatory minimum discipline.

Model inputs include forecast miles by region, purchase channel mix, surcharge coverage ratio, hedge notionals and tenors, and timing of cash settlement versus invoice collection. Outputs include expected operating ratio fuel slice, worst case weekly cash need, and breakeven index levels where hedge gains offset surcharge shortfalls.

Build and validate these models with SQL data mining on historical fuel tickets, card data, and billed surcharge lines. Align reporting with carrier rate matrix optimization when contract renegotiations change peg language or caps.

Comparison of fuel risk approaches

Driver pass through and settlement alignment

Drivers often receive fuel surcharge pass through on loaded miles or all miles per contract. Settlement engines must use the same surcharge dollars billed to customers when pass through is percentage based, or document intentional differences when driver programs use flat bonuses instead. Misalignment creates silent margin leakage or driver disputes when diesel spikes.

Owner operators under lease agreements may have fuel purchase responsibilities that differ from company drivers. Lease fuel clauses should appear as explicit settlement line categories in SQL outputs.

Accounting, tax, and hedge documentation

Hedge accounting rules and tax treatment depend on instrument type and documentation at inception. Carriers should involve qualified accountants before marking hedge programs as operational fixes. Even non hedge accounting carriers need treasury minutes approving notional limits and counterparty exposure.

Surcharge revenue recognition may differ from cash collection when customers short pay fuel lines. Pair fuel risk models with accounts receivable aging segmented by surcharge disputes.

Operational telemetry and fraud controls

Fuel cards and bulk tanks generate transaction feeds useful for anomaly detection. Sudden gallon spikes off route, duplicate purchases, and mismatches between purchased gallons and miles driven trigger investigations. Telematics MPG models support bonus programs but should not replace card level audits for theft.

Integrate ELD odometer snapshots with fuel events where policy allows privacy compliant use. Exceptions feed both driver coaching and billing integrity when reefer fuel is billed separately.

Customer contract renegotiation triggers

1. Sustained basis risk above tolerance for two quarters
2. Customer refusal to accept weekly updates within contract language
3. Cap hit frequency above threshold on high mile lanes
4. Hedge collateral calls stressing liquidity
5. Driver pass through exceeding billed surcharge on major accounts

Renegotiation data packs should include SQL backtests showing dollars at stake under recent index paths. Sales teams armed with math close better than sales teams armed with anger about diesel prices.

Implementation on Truckmate, McLeod, and TMW

Rating and billing modules store fuel tables differently, but external fuel engines can write approved surcharge amounts to staging tables consumed by invoicing. McLeod fleets often automate with SQL Agent schedules after index import. TMW fleets may combine table updates with automated rate audit checks before 210 generation. Truckmate environments frequently integrate card data through middleware into the same SQL warehouse used for surcharge analytics.

Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Fuel architecture specifications remain independent of any optional hosted execution environment.

Governance cadence

Weekly fuel council with finance, pricing, dispatch, and treasury when hedges active reviews index import, table activation, exception loads, and hedge mark to market summaries. Monthly reconciliation ties purchased gallons, billed surcharge dollars, and GL fuel expense. Quarterly board summaries explain basis risk and contract coverage ratio without jargon walls.

Carriers that treat fuel as a gas station problem stay surprised. Carriers that treat fuel as a indexed financial exposure with optional hedges and synchronized TMS tables regain predictability in operating ratio conversations.

Next steps

Run a twelve month backtest comparing actual net fuel expense to simulated scenarios with alternate surcharge lags and hedge notionals. Identify customers and lanes that drive majority of basis risk. Then update rating tables and contract language with evidence. Scott Elliott’s Strong Tower Consulting team documents fuel engines and risk dashboards carriers own. Call 763-244-1373 to schedule a fuel architecture session grounded in your TMS and card data extracts.

Dynamic surcharges and hedging are complements, not rivals. Surcharges recover contractually allowed dollars from customers. Hedges cap catastrophic variance when contracts lag reality. SQL discipline connects both to the same mile and index facts so leadership never debates two different fuel truths in the same meeting.

Regional diesel spread and lane level recovery

National DOE benchmarks smooth regional rack volatility. Carriers hauling consistently in high spread regions may systematically under recover unless contracts allow regional tables or lane specific base prices. SQL lane profitability should include fuel net of surcharge using actual purchase geography when card data provides station location, not only load origin state averages.

During refinery outages or pipeline disruptions, spread widening can occur faster than weekly surcharge cycles capture. Treasury and pricing need a pre approved escalation playbook for temporary table updates or hedge layer additions when spread exceeds modeled bands for more than two consecutive weeks.

Reefer and auxiliary fuel separately

Temperature controlled units burn diesel on reefer engines independently of tractor fuel economy. Billing reefer fuel surcharges or per hour charges requires telematics run hours or gallon estimates tied to commodity requirements. Audit rules should verify reefer charges against bill of lading temperature instructions and unit settings logged at pickup.

Blending reefer fuel into generic linehaul when contracts require itemization creates the same silent loss as missed detention. Separate charge codes, separate audit policies, and separate GL lines keep reefer margin visible in operating ratio fuel slice reviews.

Board and lender reporting clarity

External stakeholders want plain language on fuel risk. Provide a single page quarterly fuel appendix showing index path, surcharge coverage ratio, hedge notionals at quarter end, and realized basis versus plan. Tie appendix numbers to the same SQL warehouse tables used internally so external and internal narratives cannot diverge accidentally.

When lenders include fuel adjusted covenants, document formula alignment with their templates early. Retrofitting covenant calculations after hedge programs start wastes legal fees and erodes trust.

Frequently Asked Questions