Compliance · August 22, 2026

Employee reimbursement laws by state: who must pay business expense reimbursement, and by when

That gap between "no federal mandate" and "no exposure" is where most employers get into trouble. A company headquartered in Texas with six remote engineers in California is operating under California law for those six people, and California is by some distance the most expensive of the seven. The statutes below were read from the statute text on 22 August 2026 rather than from a summary, because the details that decide cases live in the subsections that summaries drop.

The federal floor is not a reimbursement rule

The Fair Labor Standards Act does not tell employers to reimburse anything. What it has instead is the anti-kickback rule at 29 CFR 531.35, which requires that wages be paid "finally and unconditionally or free and clear." The regulation says the wage requirements are not met where the employee "kicks-back" to the employer, directly or indirectly, part of the wage delivered to them.

The example the regulation itself gives is tools. If an employer requires an employee to supply tools of the trade used for the employer's particular work, there is a violation in any workweek where the cost of those tools cuts into the minimum wage or the overtime pay the employee is owed. Read that carefully, because the mechanism matters: the expense is not unlawful in itself. It becomes unlawful only when it drags effective pay below the federal floor in a given week.

The practical consequence is uneven. For a warehouse worker near the minimum wage, a $90 pair of required boots can be a federal violation. For a salaried engineer buying a $90 monitor stand, the same expense is nowhere near the floor and the kickback rule never engages. Federal law protects the lowest paid and nobody else.

The states with an express statutory duty

Below is the set verified directly from statute text for this article. It is not a claim that no other jurisdiction imposes any duty: other states reach similar results through wage-deduction rules, wage-supplement provisions or case law, and municipal ordinances exist. Treat this as the group where the obligation is written plainly in a statute you can read yourself.

Four of these seven share almost identical wording, because California, Montana, North Dakota and South Dakota all trace back to the same nineteenth century civil code language about indemnifying an agent. That is why they read alike and why California case law gets cited in the others. The two modern statutes, Illinois and Iowa, look completely different: they read like procedures, with deadlines, documentation requirements and employer defenses.

Three states say 30 days and mean three different things

This is the detail that catches multi-state employers, and no summary I have read spells it out. All three deadlines are 30 days. The clock runs on a different party in each one.

• Illinois runs against the employee. The statute requires the employee to submit the expenditure with appropriate supporting documentation within 30 calendar days after incurring it. Miss it and the claim is at risk. An employer may grant more time, but only in a written expense reimbursement policy.
• Iowa runs against the employer. Authorized expenses must be reimbursed either in advance of the expenditure or no later than 30 days after the employee submits an expense claim. Submission starts the clock, and the employer is the one racing it.
• New Hampshire also runs against the employer, but from a different trigger: 30 days from the employee's presentation of proof of payment. Proof of payment, not the date of the expense and not the date of an internal approval.

If you run one reimbursement process nationally, it has to satisfy the strictest reading of all three at once: prompt the employee well inside 30 days of the expense, timestamp the submission, and pay within 30 days of that timestamp. A single monthly batch run on the first of the month can quietly breach Iowa or New Hampshire for anything submitted early in the prior month.

Why California is in a category of its own

Section 2802(a) is the famous part, and it is broad: all necessary expenditures or losses in direct consequence of the discharge of duties, including obedience to unlawful directions the employee believed to be lawful. But the two subsections underneath are what make California expensive.

Subsection (b) says awards for reimbursement carry interest at the civil judgment rate, and that interest accrues from the date on which the employee incurred the expenditure. Not from the date of the claim, not from judgment. A cell phone stipend shortfall from three years ago accrues interest for three years.

Subsection (c) is the one that changes the economics entirely. It defines "necessary expenditures or losses" to include all reasonable costs, expressly including the attorney's fees the employee incurs enforcing the section. The fees are not a separate award subject to the usual American rule. They are folded into the thing being reimbursed. That is how a dispute over $40 a month of personal phone use becomes a matter no employer wants to litigate, and it is the mechanism behind the wave of class actions over unreimbursed remote work and personal device costs. Subsection (d) adds that the Labor Commissioner may issue a citation directly, so a private lawsuit is not the only route.

Section 2804 closes the obvious escape route: any contract, express or implied, to waive the benefits of the article is null and void. You cannot paper over 2802 in an offer letter or a policy acknowledgment.

Two California cases set the practical boundaries. In Cochran v. Schwan's Home Service (2014) the court held that when an employer requires an employee to use a personal cell phone for work, 2802 obliges it to pay a reasonable percentage of the phone bill, even where the employee is on an unlimited plan and incurred no extra cost, and even where somebody else pays the bill. The court deliberately declined to define "reasonable percentage," which is exactly why flat monthly stipends became the standard answer. Earlier, Gattuso v. Harte-Hanks Shoppers (2007) approved three ways to handle vehicle costs: actual expenses, a cents per mile rate, or a lump sum, and allowed reimbursement through enhanced salary or commission only if the employer separately identifies and documents which portion is reimbursement rather than pay for labor. Nothing in the statute mandates the IRS standard mileage rate; it is the near universal benchmark by convention, and an employee can still show their actual costs ran higher.

One practical consequence: in California, a defensible reimbursement position is worth more than a generous one. Paying a reasonable percentage of a phone bill and being able to show the calculation beats paying nothing and beats paying a round number you cannot justify.

Illinois wrote employers a safe harbor, and most never use it

Section 9.5(b) is unusually employer friendly for a wage statute, and it is conditional on paperwork most companies never produce. An employee is not entitled to reimbursement if the employer has an established written expense reimbursement policy and the employee failed to comply with it. The employer is not liable unless it authorized or required the expenditure, or failed to follow its own policy.

It goes further. If the written policy sets specifications or guidelines for necessary expenditures, the employer is not liable for the portion of a claim that exceeds them. In plain terms, you can cap. A policy that says economy fare, $60 a night of meals, and a specific home internet contribution is enforceable against a claim for more.

There is exactly one hard limit, written into the same sentence: the employer may not institute a policy that provides for no reimbursement or de minimis reimbursement. A cap is lawful. A token is not. And the statute handles missing paperwork sensibly, which is worth copying even outside Illinois: where supporting documentation is nonexistent, missing or lost, the employee submits a signed statement instead. Our travel and expense policy guide covers what those specifications should actually say.

The carve-outs that decide the close cases

The four indemnification states are broadly worded, so the exceptions carry the weight. North Dakota excludes expenses incurred to purchase or rent tools of a trade, or any other equipment, that the employee also uses outside the scope of employment. That single clause resolves most of the arguments people have about laptops, phones and vehicles: dual use equipment is outside the duty there in a way it is not in California.

Montana excludes losses suffered in consequence of the ordinary risks of the business the employee works in, while separately requiring indemnification in all cases for losses caused by the employer's want of ordinary care. Iowa's limit is different again and easy to miss: the duty attaches to expenses "authorized by the employer." An unauthorized purchase is not covered, which makes your approval trail the thing that determines liability, not the receipt.

Two jurisdictions outside the state statutes

Washington DC imposes a duty through the Wage-Hour Rules rather than a statute. Section 909.1 of Title 7 of the DC Municipal Regulations requires the employer to pay the cost of travel expenses incurred by the employee in performance of the business of the employer. Section 910.1 covers purchasing and maintaining any tools required of the employee, and section 908 covers required uniforms and protective clothing. DC's wage statutes themselves contain no general reimbursement mandate, so anyone searching the DC Code and finding nothing has looked in the wrong place.

Seattle reaches the same result through its Wage Theft Ordinance, SMC 14.20, by folding reimbursement into the definition of compensation the employer owes. The Office of Labor Standards describes the duty in California-style language, covering expenses reasonably necessary to perform the job or that foreseeably followed from the employer's instructions, and expressly not limited to what the employer explicitly required. Two details matter for remote teams: it applies to anyone working in Seattle regardless of where the employer sits, and compensation is payable at intervals no longer than monthly.

The states that get listed but do not have a mandate

Vendor roundups commonly say eleven states require reimbursement. They reach eleven by counting states whose rules cover uniforms only, and states where the duty exists solely because the employer promised it. Both are worth understanding, but neither is a general mandate, and treating them as one leads to budgeting for exposure you do not have while missing the exposure you do.

Pennsylvania is the clearest trap in this whole area. You will see it cited to 51 Pa. Code 17.6, "Expense reimbursement." Title 51 is Public Officers, and that chapter is a State Ethics Commission rule about disclosing transportation, lodging and hospitality on statements of financial interests. It is a disclosure obligation for public officials and it creates no private-employer duty whatsoever. Pennsylvania's real hook is the Wage Payment and Collection Law: 43 P.S. 260.2a defines fringe benefits or wage supplements to include reimbursement for expenses, so a promised reimbursement becomes enforceable as wages. Promise nothing and the statute has nothing to enforce.

New York works the same way. Labor Law 198-c treats benefits or wage supplements, expressly including reimbursement for expenses, as amounts the employer must pay where it agreed to pay them, and non-payment within 30 days of when due is a misdemeanor. It creates no free-standing duty absent a policy or agreement, and it excludes bona fide executive, administrative and professional employees earning above a weekly threshold.

Massachusetts has no general reimbursement statute. What it has is 454 CMR 27.04(4), which requires payment for travel time beyond the ordinary commute and reimbursement of the associated transportation expenses when an employee is required to report somewhere other than their fixed location or to travel place to place during the workday, and 454 CMR 27.05, which requires reimbursement of the actual cost of required uniforms. Minnesota's rule at Minn. Stat. 177.24 is narrower still and triggers at termination, when the employer must repay amounts it deducted for uniforms, equipment and supplies, and it expressly excludes tools of a trade and equipment usable outside the job. Colorado, New Jersey and Washington State appear on these lists for uniform expenses only, and Washington State has no general private-employer mandate at all, which is precisely why Seattle passed its own.

What this means for the system you buy

Read the seven statutes together and the compliance requirement is not "track expenses." It is the ability to prove four specific things after the fact, sometimes years later:

• When the expense was incurred, because Illinois runs its 30 days from that date and California accrues interest from it.
• When the employee submitted it, because Iowa and New Hampshire run their deadlines from submission or proof of payment.
• Which version of the policy applied at the time, because the Illinois safe harbor depends on an established written policy the employee failed to comply with, and policies change.
• Why anything was refused, and when you said so, because Iowa requires a written justification inside the same 30 day window.

The Illinois administrative rules add a fifth requirement that is easy to trip over: an employer that in practice pays above its own written cap becomes liable for full reimbursement regardless of what the policy says, the policies and the approvals and denials have to be retained for three years, and any unrecovered expense rolls into final compensation owed at separation. A generous exception granted once, undocumented, quietly rewrites the cap.

Most expense tools handle the first two by default. The third and fourth are where they differ, and they are worth testing in a demo rather than assuming. Ask to see a two year old report and check whether the policy version and the denial reason survived. Our expense reimbursement software comparison covers how each platform handles the audit trail and the payment rails, and the accountable plan rules govern the separate question of whether those payments are taxable.

The wider lesson is that employing people across state lines turns single decisions into fifty variants. Reimbursement deadlines are one instance of it. Employers who have already been through the same exercise for compliant posted salary ranges will recognize the shape immediately: one national policy written to the strictest state is usually cheaper than fifty policies, right up until the strictest state is California.

None of this needs a lawyer to start. It needs someone to list the states you actually employ people in, read those statutes, and check that your reimbursement run happens more often than monthly. Two of the seven deadlines are missed by batching, not by bad faith.

Questions people ask

The short version

Seven states put the duty in a statute you can read. Federal law only catches the cases where an unreimbursed expense pushes someone under the minimum wage. Three of the seven set a 30 day deadline and none of them start it at the same moment. California adds interest from the date of the expense and folds the employee's legal fees into the amount owed, which is why it drives the litigation. Illinois hands you a real defense if, and only if, you have written the policy down.

The operational fix is smaller than the legal exposure suggests: reimburse more often than monthly, timestamp submission separately from the expense date, keep the policy version that was live when the expense happened, and record the reason for every refusal on the day you refuse it. This article is general information about published statutes, not legal advice for your situation.

Statutes read on 22 August 2026 from the California Legislative Information site, the Illinois General Assembly, the Iowa Legislature, the Montana Code Annotated, the New Hampshire General Court, the North Dakota Legislative Branch, the South Dakota Legislature, and 29 CFR 531.35. Washington DC via the DC Municipal Regulations Title 7 Wage-Hour Rules, and Seattle via the Office of Labor Standards guidance on SMC 14.20. Arkansas is sometimes listed as requiring reimbursement for travelling salespeople; we could not find a statute supporting that and have left it out rather than repeat it.