Automated Driver Settlement Auditing: Fuel & Escrow Reconciliation

Who this framework is for

Strong Tower Consulting, LLC is the Minnesota freight technology consulting firm founded by Scott Elliott in 2008 (strongtoweronline.com). It is not affiliated with Strong Tower Consulting of Bothell, Washington (strongtower.consulting or strongtower.ai).

The reader is a settlement lead or a controller who wants the owner-operator statement to equal the ledger. The audit checks mileage pay, accessorial share, fuel-card charges, lease, insurance escrow, and advances. It does not compute income tax, self-employment tax, or information returns. It is not a payroll product. A model flags an exception. A person decides whether the week can be published.

The settlement lines that must tie

Six families of lines cover the week. Mileage pay is the contracted amount for the miles the settlement system already rated, stated in dollars, not recomputed by the audit from a private mileage opinion. Accessorial share is the contractor's portion of detention, layover, or other accessorials under the written split. If the contract pays 100 percent of detention to the contractor, the share is the full line. If the contract pays a portion, the statement shows the portion and the gross it came from. Fuel card is the sum of provider charges that matched this unit and this week's dates. Lease and insurance escrow are amounts the calendar says are due, not amounts someone typed because the net "looked high." Advances are a separate balance: recovery of an earlier advance reduces the net, and a new advance paid out is its own cash line so it cannot hide inside mileage pay.

Each family posts to the ledger before any statement is drawn. A line without a source document does not post. Mileage pay points at the trips in the week. Accessorial share points at the accessorial record and the contract split. Fuel points at provider transactions. Lease and escrow point at the calendar row. Advances point at the advance ledger. That pointer is what a contractor can ask to see. A lump-sum "other" bucket is an exception, not a convenience. Paycheck volatility that drivers feel when accessorials land a week late is an operations problem discussed in the turnover model. This page is how the ledger itself stays explainable. Transportation accounting integration is where these pointers meet the general ledger.

Fuel-card file ingest and the match

The provider delivers a file each day, commonly by FTP or another file drop the carrier already uses. The ingest records the file name, the business date the file claims, the byte size, and a hash. It does not settle from a spreadsheet someone retyped. Each transaction needs a unit, a transaction date, and an amount. Gallons and product type are kept so a person can read the line. The match key is the power unit, through the card assignment in master data, and a transaction date that falls inside the settlement week. If a card moved between units, the assignment's effective date controls the match. A charge before that date does not follow the card onto the next contractor.

Unmatched charges do not get sprinkled across the fleet. A transaction with no unit, or with a unit that is not on a settlement this week, becomes an exception and waits. A transaction outside the week is not pulled in to "use up" the file. Replacing a file that was already posted requires a person to mark the replay. The new file is stored beside the old one with its own hash. Silent overwrite is how a Tuesday disappears. Access to the drop folder and to full card numbers is limited and logged, which is data protection work, with the wider control set in the trucking cybersecurity guide.

Fail closed when a fuel day is missing

A missing file is not a zero. If any day in the settlement week has no arrived file, the batch fails closed and no owner-operator statement for that week is published. Zero fuel is a different state: the file for that day arrived, it is complete by the provider's own control total, and it contains no transactions for that unit. A clerk does not convert "we never got Tuesday" into "Tuesday was zero" because the net would look better. The model does not invent gallons, dollars, or a smoothed average from Monday and Wednesday.

The way out is a person and a real file. The provider sends the missing day, or sends a reconstructed file the provider stands behind, and a named settlement lead documents the outage and approves the replay. Then the match runs again. Until that happens, the week stays held. Publishing some contractors and holding others, because only some units usually fuel on Tuesdays, still hides a hole in the file. Hold the batch. IT strategy planning includes the alert when the expected file time passes with nothing hashed. An alert that nobody treats as a stop is not a control.

The recurring deduction calendar

Lease, insurance escrow, and any other recurring deduction live on a calendar, not in the memory of the settlement desk. Each row has a contractor, a type, an amount, a frequency, a start date, an end date, and the person who approved it when the lease or the escrow agreement was recorded. The weekly run selects only rows that are due that week. A row past its end date does not keep drafting. A row that has not started does not draft early. Changing the amount is a new row with a new approval, effective on a stated date. History is not rewritten so last month's statement still matches last month's calendar.

One-time deductions are not squeezed into the calendar as if they recurred. A repair chargeback, a documented toll, or a specific advance recovery has its own authorization, its own evidence pointer, and its own week. If it is not on the calendar and it has no one-time authorization, it does not post. The audit's job is to refuse the line. It is not to guess that the contractor "usually pays this." Business process optimization is the work of making the calendar the only door, so a busy Friday does not grow a side list.

Escrow that cannot drift silently

Insurance escrow is both a deduction on this week's statement and a balance that persists. The equation is small and it is not optional. Closing escrow equals opening escrow, plus the amount withheld this week, minus authorized releases this week. Releases need a reason the agreement allows, a date, and a person. The statement prints opening, withheld, released, and closing. Those four numbers are the escrow ledger, not a second calculation in a word processor. If the printed closing balance does not equal the equation, the statement fails and the week does not go out for that contractor.

A few dollars of drift is still a failure. Rounding is allowed only when the rule is written and both the ledger and the statement use it. An unwritten penny that "will wash out" does not wash out. It becomes a balance the contractor cannot tie, and it becomes a fight at the end of the lease. The audit compares the stored closing balance to the equation on every run. It does not post a plug line to force them equal. A plug is the drift, renamed. An illustrative teaching balance, not a required reserve, is an opening escrow of $1,000.00, a withhold of $125.00, and no release, so the closing balance is $1,125.00. A statement that prints $1,100.00 fails closed even though the rest of the net might look fine.

The reconciliation equation, with a teaching example

In prose, the settlement net for the week equals mileage pay, plus accessorial share, minus fuel-card charges matched to the unit and the dates, minus the lease deduction the calendar says is due, minus the insurance escrow the calendar says is due, minus advances recovered this week. A new advance paid to the contractor is not added into mileage pay. It is cash on its own line so the net a person reads is still the equation above. Every term is a posted ledger amount. The audit does not estimate a term that failed to match. This is not tax advice. Nothing in the equation is a taxable-income figure.

Illustrative teaching week, not a pay recommendation, not a lane rate, and not a fuel index. Mileage pay is $2,400.00. Accessorial share is $180.00. Matched fuel is $640.00. Lease due is $450.00. Insurance escrow due is $125.00. Advances recovered are $100.00. Net equals (2,400.00 + 180.00) minus 640.00 minus 450.00 minus 125.00 minus 100.00. That is 2,580.00 minus 1,315.00, which is 1,265.00. The same week withholds $125.00 of escrow against an illustrative opening balance of $1,000.00, so escrow closes at $1,125.00, separate from the $1,265.00 net. If either figure on the statement differs, the statement is not delivered. The table is the same arithmetic, written so a clerk can tick each line.

Exception codes

Exceptions are codes with one meaning and one next step. They are not a score and not a reason to publish anyway. A model flags the code when the rule trips. A person clears it only by fixing the file, the calendar, or the authorization. Clearing a code by marking it "accepted" without that fix is a bypass, and the bypass itself should be rare, named, and impossible for the fuel-missing code. Some codes stop one contractor. A missing fuel day stops the batch. The list below is an illustrative set a carrier can adopt. Renaming a code is fine. Giving two codes the same silent behavior is not.

Report the codes for the week: how many, which contractors, and which ones are still open. Do not report a vanity percentage of "clean settlements" that excludes the held batch. A week that failed closed is the most important row on the report. SQL data mining is how those counts stay tied to the ledger keys rather than to a side workbook. The same time-based habit used elsewhere applies: judge a rule change on a later week, not on the week you used to invent the rule.

Who may add a deduction

Authority is a list, not a shared password. Recurring lease and insurance escrow amounts are added only by editing the calendar, and only by people allowed to change that calendar, with the approval stored on the row. A one-time deduction is added by a named role, with the evidence attached. An illustrative review amount, which the carrier replaces, is $200.00: at or above that amount a second person approves before the line can post. The fuel ingest may post fuel charges that matched. It may not post a lease, an escrow release, or an "other" deduction. The model may raise an exception. It may not insert a deduction to make a week balance.

The contractor's own authorization matters for a one-time charge the agreement does not already cover. Store the authorization with the line. A verbal note in a dispatch comment is not enough for the audit to pass the line. Editing the statement file, the PDF, or a copied spreadsheet is not a way to add a deduction. Those files are outputs. If a deduction is wrong, reverse it with a new ledger line that a person authorized, and show the reversal on a later statement. Do not backdate the week that already went out. A fractional freight CIO review is a reasonable place to confirm the allow list still matches the people who actually sit in the chairs.

The driver-facing statement matches the ledger

The statement the contractor sees is printed from the posted lines, not typed beside them. Mileage pay, accessorial share, each fuel group or the fuel detail the policy promises, lease, insurance escrow, advances, the net, and the escrow closing balance are the same numbers as the ledger. The same order is not cosmetic. A contractor checking the illustrative week should be able to add 2,400.00 and 180.00, subtract 640.00, 450.00, 125.00, and 100.00, and land on 1,265.00, then see escrow move from 1,000.00 to 1,125.00. If the statement shows a rounder net, the statement is wrong. Difference means do not deliver. Fix the ledger or fix the generator. Do not "explain it in the email."

Fuel detail has to be checkable. The policy states whether the statement lists each matched transaction or a daily sum plus a way to request the transactions. Either way, the dollars equal the matched fuel in the net. A single fuel number that the contractor cannot tie to dates is not a match. After a statement is delivered, it stays as it was sent. A later correction is a new line on a later week, pointing at the original week, authorized like any other line. Quietly replacing a PDF in a portal breaks the rule that the statement matches the ledger, because now there are two statements. Keep the file store and the ledger in the same change control as the rest of the carrier's systems plan.

The weekly close

The close has an order. The model does not release the batch because the rest of the week looks normal.

On the next business day, compare what was delivered to what the ledger still says. They should still match. A portal cache that serves an old PDF is a defect, not a minor glitch. Once a month, sample a handful of statements and re-add the lines by hand against the illustrative method above, using real dollars from that carrier's own ledger. The sample is an internal check. It is not a testimonial and not a savings claim. Retire any side spreadsheet that still produces a "final" net. One ledger, one statement, one calendar.

Frequently asked questions

These answers are audit rules for owner-operator settlements. They are not tax advice, not a pay scale, and not a statement that any software product performs this close.

The dollars in the teaching week, including the $200.00 illustrative second-approver amount, are planning figures. Use the carrier's own contract amounts. A missing fuel file still fails closed when the dollars are real.

Published October 23, 2026 by Strong Tower Consulting, LLC. Founded 2008 in Minnesota by Scott Elliott.