Fuel Surcharge Reconciliation: A Method for Verifying Assessed and Paid Surcharges

Published: September 18, 2026.

A fuel surcharge is a commercial term, not a fuel measurement. It links a negotiated formula to a published diesel price so a carrier can recover part of the cost of fuel when prices move. Because the formula sits inside a contract and the price series sits in a public release, a billing team can test whether the two were applied consistently. That test is the subject of this brief.

Research question and scope

This study asks how a carrier can reconcile assessed and paid fuel surcharges against the formula it agreed to and the index it selected. It does not decide what a contract means, whether a rate is fair, who is at fault for a variance, or what a carrier should charge. Those are commercial and legal questions that belong to the parties and, where relevant, to counsel.

The method here is deliberately narrow. It tests whether a recorded surcharge can be recomputed from a named index value, a stated formula, and a defensible mileage or weight base. If it cannot, the record is unreconciled rather than wrong.

Why fuel surcharges resist simple reconciliation

Three inputs usually differ between the invoice and the contract. First, the index date. Carriers often peg the surcharge to the diesel price published for a specific week, and one calendar month can contain four or five weekly releases. Choosing a different release changes the result even when the formula is identical. Second, the base. Agreements frequently subtract a base price from the index before applying a peg, so a surcharge stated as a percentage and a surcharge stated as cents per mile are not interchangeable. Third, the denominator. Some formulas use loaded miles, some use total miles, some use weight, and some use a flat daily charge.

Federal records rules do not define a surcharge formula, but they do reinforce why the paper trail matters. The lease and interchange rules at 49 CFR Part 376 address the records that accompany leased equipment, including items that must be specified in a lease, and the preservation rules at 49 CFR Part 379 and Part 371 set retention expectations for carrier and broker records. Those provisions frame the documentation habit. They do not tell a carrier which index to use.

When any of the three inputs is missing, the recomputation is not reproducible. The correct output is a documented exception, not an estimate.

Define the reference formula before reviewing records

Write the formula in plain terms before opening a single invoice:

• the index series and its publisher;
• the specific index value and the publication date that applies;
• the base value to subtract, if the contract names one;
• the peg or multiplier;
• the unit the result applies to, such as mile, hundredweight, or day;
• the mileage or weight source;
• the effective date rule for the invoice period.

Freeze that written rule for the review. If a contract changes during the period, treat the change as a separate version with its own effective date rather than blending the two. A single blended formula will reproduce neither version and will manufacture variances that do not exist.

Build one observation record per surcharge line

Use a small, stable table with one row per assessed surcharge, and keep the original invoice attached. A workable record includes:

• carrier, customer, and contract reference;
• invoice number, invoice date, and service period;
• index series, index publication date, and published value;
• base value and peg as written in the contract;
• billed quantity and its source system;
• calculated surcharge, assessed surcharge, and paid surcharge;
• variance amount and variance direction;
• reviewer, review date, and resolution state.

Storing the paid amount beside the assessed amount matters. A dispute about a surcharge that was never paid is a different record from a surcharge that was paid at the wrong index value. Collapsing both into one variance column loses that distinction.

Recompute from the index, do not re-key from the invoice

The most common reconciliation error is copying the invoice total into a spreadsheet and calling the result a recomputation. Recompute independently: pull the index value from the publisher, apply the contract formula, and only then compare. Keep the publisher page or data file as evidence for the index value, with its retrieval date, because a published value can be revised after first release.

Round consistently and declare the rounding rule. A cent per mile multiplied across a fleet becomes a large number, and two reviewers who round at different points will report different variances for the same invoice. State the convention once and apply it to every row.

A worked example

Assume a contract sets the surcharge at one cent per loaded mile for every ten cents by which the weekly retail diesel price exceeds a base of three dollars per gallon, and the service week uses a published price of three dollars and sixty cents. The excess over the base is sixty cents, which is six ten-cent steps, so the formula produces six cents per loaded mile. On a one thousand-mile haul, the expected surcharge is sixty dollars. If the invoice assessed forty-eight dollars, the variance is twelve dollars under the same inputs.

The example is not a recommendation. It shows that every number can be traced to a public value plus a written rule, and that a second reviewer can reproduce the result without seeing the first reviewer's spreadsheet.

Handle the denominator honestly

Report the full population, not only the lines that produced a variance. A useful summary includes:

• total surcharge lines in the period;
• lines with a complete recomputation;
• lines that could not be recomputed, with the missing input named;
• lines with a variance above the materiality threshold;
• lines still under review;
• net variance and absolute variance.

Reporting only matched lines hides the records that could not be tested. Show both the count and the dollar value so a reader can see whether a large variance comes from one invoice or from many small ones. A materiality threshold should be set in advance and stated in dollars per line or as a percentage of the assessed amount.

A boundary case

Suppose an invoice covers a service week in which the index moved between pickup and delivery. One analyst uses the value published before pickup; another uses the value published after delivery. The two analyses produce different numbers from the same contract language.

Retain both index values and label which one each analysis used. The disagreement signals that the effective date rule is ambiguous. It should be escalated as a contract interpretation question rather than resolved silently in the spreadsheet or by choosing whichever value produces a zero variance.

Reviewer agreement and reproducibility

Have a second reviewer independently recompute a sample that includes clean lines, unmatched lines, mid-period contract changes, and lines with missing mileage evidence. Compare the index value, the arithmetic, the rounding rule, and the exception classification. Resolve differences against the frozen formula and record the adjudication in a dated analysis note. If the reviewers cannot agree, the formula as written is not yet precise enough for automated reconciliation, and that is a finding worth reporting on its own.

Interpretation boundaries

A reconciliation measures agreement between a document and a formula. A variance does not prove that anyone intended to overcharge or underpay, that the contract was breached, that a customer acted in bad faith, or that a carrier is owed money. It shows only that the recomputation and the invoice differ under the reviewer's stated rules.

A zero variance for a period proves that the selected index values and formula reproduce the invoice. It does not validate the underlying linehaul rate, the mileage, or the commercial agreement. Neither outcome should be presented as an audit opinion.

Limitations

Fuel surcharge programs vary widely, and this method can only test the formula the reviewer can document. Index values may be revised, contracts may be amended informally, and mileage may come from more than one system. Where the original contract is unavailable, the review should stop and record the gap rather than substitute an assumed formula.

The findings apply to the named carrier, customer, period, and index series. They should not be presented as an industry benchmark or as a measure of a customer's practices. Fuel surcharge treatment can also carry tax and accounting consequences that are outside the scope of an administrative reconciliation.

Source treatment

The U.S. Energy Information Administration publishes the weekly retail diesel prices that many programs reference. The Code of Federal Regulations addresses records that accompany leased equipment at 49 CFR Part 376, broker records at 49 CFR Part 371, and record preservation at 49 CFR Part 379. Those sources provide context and a documentation boundary. They do not supply a carrier's contract formula, and nothing here should be read as tax, legal, or accounting advice.

Evidence-led conclusion

Fuel surcharge reconciliation becomes defensible when the index series, index date, base, peg, unit, and mileage source are written down before the review begins. The result is a reproducible comparison between an invoice and a contract with unresolved lines left visible. It is a documentation control, not a judgment about fairness or fault.

References

1. U.S. Energy Information Administration. Gasoline and Diesel Fuel Update. https://www.eia.gov/petroleum/gasdiesel/. Retrieved 2026-09-18.
2. U.S. Energy Information Administration. Weekly Petroleum Status Report. https://www.eia.gov/petroleum/weekly/. Retrieved 2026-09-18.
3. Electronic Code of Federal Regulations. 49 CFR Part 376, Lease and Interchange of Vehicles. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-376. Retrieved 2026-09-18.
4. Electronic Code of Federal Regulations. 49 CFR Part 371, Broker Records. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-371. Retrieved 2026-09-18.
5. Electronic Code of Federal Regulations. 49 CFR Part 379, Preservation of Records. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-A/part-379. Retrieved 2026-09-18.
6. National Archives and Records Administration. Records Management Policy. https://www.archives.gov/records-mgmt/policy. Retrieved 2026-09-18.