Accountable Plan Rules for Mileage Reimbursement

Ask an operator about mileage and you hear some version of the same sentence: "We already pay mileage. It is on every check. What more does the IRS want?" It is a fair objection, because from the outside the two versions look identical: the driver gets paid, the shop eats the cost, the money leaves the account. But the IRS does not grade you on whether you paid. It grades you on how the payment was documented, and the payment can land in only one of two boxes. This article names both boxes, walks the three tests that decide which one you are in, models what failing costs a six-driver shop, and names the structure that fails most often.

Name the two boxes: accountable or non-accountable

The rule is Treasury Regulation 1.62-2. In plain operator language: a reimbursement arrangement is either an accountable plan or a non-accountable plan, and there is no third box. The label is not something you pick. It is something your records earn, test by test, and it gets decided after the fact by whoever opens your file.

Under an accountable plan, the money is a reimbursement of the driver's own expense. It is not wages. No income tax withholding, no Social Security or Medicare on either side, no federal unemployment tax, and it never appears in Box 1 of the W-2. Under a non-accountable plan, every dollar you paid is wages. It is withheld on, both sides pay payroll tax on it, it lands in Box 1, and a W-2 driver generally has no way to deduct the expense back off their own return; our driver write-off guide covers what is and is not deductible today. Same payment, same intent, two very different outcomes, decided entirely by paperwork.

The three tests, in operator language

Three conditions, all required. Miss one and the arrangement fails as a whole, not in part.

1. Business connection

The payment has to cover expenses your driver actually paid or incurred while doing your work, in the course of employment. The run from the shop to the customer and back is business mileage. The drive from home to the shop is commuting, and commuting is not reimbursable business mileage, no matter how far your closer lives. This is also why the log has to be per run rather than per shift: a shift total quietly mixes the two categories together. Our delivery mileage primer covers what counts and what does not.

2. Substantiation within a reasonable time

The driver has to document the expense: date, miles driven, and business purpose, close enough in time that the record still means something. The IRS publishes a safe harbor for what "reasonable time" means, and the usable version of it is substantiation within 60 days of the expense. A reconstructed spreadsheet built in March for the previous October is not substantiation; it is a guess with a font. Putting the ticket number next to the miles ties the drive to a real delivery and turns a claim into a record.

3. Return of amounts in excess

Anything you paid above what the driver substantiated has to come back, and the safe harbor there runs to 120 days after the expense. This is the test almost nobody thinks about, because it only bites arrangements that pay a fixed amount up front. If you advance or flat-pay and never true it up against substantiated miles, there is no mechanism to return excess at all, so the test fails by design rather than by accident.

What failing costs, modeled once with every input named

Here is the model, with every figure illustrative and modeled. Take a shop running 6 drivers who average 220 delivery miles a week each, reimbursed at the IRS standard mileage rate of $0.76 per mile, effective July 1 2026, the change we broke down in our July rate increase piece. That is 1,320 miles a week, 68,640 miles a year, and $52,166 a year in mileage payments, modeled.

If the arrangement is accountable, none of that $52,166, modeled, is wages. If it is non-accountable, all of it is. Not the excess over some reasonable amount: the entire payment. On the employer side that means Social Security and Medicare at 7.65 percent, about $3,991 a year, modeled, plus federal and state unemployment tax on the wage base, plus whatever your workers' compensation premium does when reported payroll jumps. On the driver side, another 7.65 percent, roughly $3,991, modeled, comes off their checks, along with income tax withholding on money they never got to keep, because they already spent it on gas, tires, and brakes. Multiply that across a franchise group and you get the pattern we mapped in the franchise mileage tax burden.

Notice what did and did not matter. The rate did not matter: paying the full IRS rate does not buy you an accountable plan, and paying under it does not automatically cost you one. Volume did not change the character of the payment; it only changed the size of the bill. What decided the whole thing was two records: a log and a reconciliation. Both are cheap. Neither is optional.

The flat per-run fee is where most shops fail

The most common structure in delivery is a flat fee per run: $1.50 a delivery, illustrative. It is easy to explain at hiring, easy to push through payroll, and it is the single most common way an accountable plan quietly stops being one.

A flat fee is not automatically fatal. A per-run or per-mile allowance can sit inside an accountable plan if it is compared against substantiated mileage on a regular cycle and any excess actually comes back. It becomes non-accountable the moment nothing reconciles it, because then two of the three tests fail at once: nothing was substantiated, so nothing can be returned. The same logic applies to a flat monthly car allowance, which is the version we take apart in car allowance vs mileage reimbursement.

There is a second problem stacked on the first. A flat fee that lands under a driver's real cost per mile pushes their effective hourly wage down. That is a wage and hour exposure rather than a tax one, and it is the exposure that turns into class actions. How to pay delivery drivers legally walks the pay structure side of the same decision.

Wage law and tax law fail separately, and you can lose both

Passing the three tests is a tax result. It does not answer whether you reimbursed enough under wage law, and those are the cases that produce checks. Parker v. Battle Creek Pizza, Inc. (6th Cir. 2024) rejected both bright lines, the strict IRS rate on one side and any reasonable approximation on the other, and pointed courts back toward the driver's actual costs; it is binding only in the Sixth Circuit (Michigan, Ohio, Kentucky, Tennessee) and persuasive everywhere else. Its companion, Bradford v. Team Pizza, Inc. (6th Cir. 2024), carries exactly the same scope: binding in those four states, persuasive elsewhere. West v. BAM! Pizza Management (D.N.M., January 2026) shows the same under-reimbursement theory being litigated well outside the Sixth Circuit. And in California, Labor Code 2802 requires indemnification for necessary business expenses; you cannot contract around 2802, and our California guide covers what that means for a delivery roster. All of this is general information and not legal advice; take the specifics to your own counsel and your CPA.

The practical read is that the two bodies of law point the same direction. A rate documented well enough to satisfy the substantiation test is also the rate you would want to put in front of a wage claim, and a per-run flat fee with no log is weak evidence in both rooms.

What a passing plan looks like on Monday morning

None of this needs a new department. It needs a habit and a file. Five things, in order:

• One written rate per location, with a basis behind it. Write down the rate, the date it took effect, and why it is that number, whether that is the IRS standard rate or a documented local cost build. Our state rate table is a starting point for the local piece.
• A per-run log with date, miles, and ticket number. Per run, not per shift, so commuting never gets swept in. The ticket number is what makes the line auditable a year later.
• A 60 day cutoff you actually enforce. Mileage submitted after the window is not substantiated, and an exception you grant every month is not a policy. Enforcing it is easier than defending it.
• A reconciliation line on every payroll run. Compare what you paid against what was substantiated, and recover or offset the difference inside the 120 day window. This is the test that flat-fee shops skip entirely.
• A file someone else could open cold. Rate basis, policy, logs, and reconciliations in one place, not spread across a POS export, a text thread, and a manager's memory. Our driver reimbursement compliance audit is the checklist version of this, and reimbursement software for restaurants covers what to automate.

RatesReady was built for the two records that decide this. It sets and documents a defensible per-mile rate for each of your locations, updates that rate when the IRS number or your state's rules move, and keeps the rate basis, the driver logs, and the reconciliation in one place you can hand to an auditor, a CPA, or opposing counsel without a week of scrambling. It is $49 per location per month. If you want to see what your current arrangement would look like sitting in that file, request a demo and we will walk your numbers with you.

This article is general information for delivery operators and is not legal or tax advice. Rules vary by state and change over time, and your facts matter; consult counsel or a tax professional licensed in your jurisdiction before acting on anything here.