Fuel Surcharge Verifier: Catch Overbilled FSC Before You Pay the Freight Invoice

The problem this kills

Your carriers bill a fuel surcharge (FSC) on top of the linehaul, and it's supposed to follow a simple, agreed rule: take the published fuel index for the week of the shipment, look it up in the surcharge schedule in your contract, and that's the percentage. Simple — except nobody actually checks. The carrier's billing system uses whatever index it used, the effective date might be off by a week, the schedule tier might be stale, and the surcharge gets applied to charges it shouldn't touch. Pennies on a single shipment, but across thousands of invoices a year it's real money quietly leaking out the door.

The maddening part is that the correct number is completely knowable. The fuel index is published. Your schedule is in the contract. The ship date is on the invoice. You just need something that does the lookup the carrier was supposed to do, compares it to what they actually billed, and shows you exactly where they diverge — so you can dispute with the math in hand. You do not need to be a developer to build that something.

What you'll build

A simple internal web tool for your freight-audit team. You import three things: your freight invoices (with the billed fuel charge and ship date), your fuel-surcharge schedule (the index-to-rate table from your contract), and the weekly index values (the DOE diesel price or whatever index your contract names, effective-dated by week). For every invoice, the tool finds the index value in effect on the ship date, looks up the correct surcharge percentage in your schedule, applies it to the right base (linehaul only, by default), computes the surcharge that should have been billed, and compares it to what was billed. Every variance is flagged with the full calculation laid out. Your auditor reviews each flag and clicks Dispute or Accept — with a reason. On release, the tool exports a dispute log in the columns your claims process needs, plus a running savings total of what you've recovered.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your audit process, the carriers and contracts involved, which fuel index each contract uses and how its effective dates work, the exact columns and naming in your invoice and schedule files, your typical and peak invoice volumes, and your real rules for what counts as a disputable variance. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the three CSV imports, the effective-dated index lookup, the surcharge-recalculation engine, the variance flagging, the review-and-decide screen, the human approval gate, and the dispute-log and savings exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real audit function needs: login so only your team can use it, row-level security so people only see their own organization's invoices and contracts, a complete audit trail of every dispute/accept decision and override (who, what, when, and why), a hard human-approval gate so nothing becomes a dispute until a person decides, and duplicate guards (keyed on invoice number + ship date) so the same invoice can't be audited and counted twice. The whole tool exists to make a careful human decision easy — the AI does the math, a person makes the call.

Who it's for

Freight-audit analysts, logistics cost managers, and transportation controllers who pay carrier invoices and suspect the fuel surcharge isn't always right. If you can point at your contract's surcharge schedule and name the index it uses, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be recalculating your first real batch of fuel surcharges this weekend.