WARN Act and Your Expense Reimbursements — What Happens to Unpaid Expenses After a Layoff
WARN Act and Your Expense Reimbursements — What Happens to Unpaid Expenses After a Layoff When a WARN notice lands, most people think about severance, health insurance, and the final paycheck. The smaller line on the ledger gets forgotten: the mileage, the phone bill, the hotel receipt in a drawer. It should not be. That money is yours, and the 60-day notice period is the best time to collect it…
When a WARN Act notice arrives, most employees think about severance, health insurance, and their final paycheck. However, an often-overlooked aspect is unpaid expenses incurred while working. These costs are yours to reclaim, and the 60-day notice period is the optimal window to recoup them before access to company resources is revoked.
Reimbursable expenses encompass costs like mileage for work trips, a share of a personal cell phone bill, home internet, office supplies, travel and lodging, required tools and uniforms, and client meals. To qualify, the expense must have been necessary, reasonable, and for the employer's benefit, not yours. For instance, a laptop purchased by the company is company property, whereas miles driven in a personal vehicle to a client site are yours to reclaim.
The WARN Act itself does not address expense reimbursement. Rather, the right to be repaid stems from state law, your employer's written policy, or the terms of your employment. The strength of this right varies by state. California and Illinois have the most robust rules. California's Labor Code Section 2802 mandates reimbursement for "all necessary expenditures or losses" incurred during employment, which includes items like a personal cell phone bill, mileage, and home-office costs.
The right is non-waivable, and successful claims can result in interest and attorney's fees. Claims must be filed within three years.
In Illinois, the Wage Payment and Collection Act requires employers to reimburse any necessary expenses incurred within the scope of employment. A crucial deadline exists: expenses must be submitted with supporting documentation within 30 calendar days of incurring them, unless the employer's written policy allows for a longer period.
If a receipt is lost, a signed statement detailing the expense can suffice. However, if the employer maintains a compliant written policy and you failed to adhere to it, you may forfeit your right to reimbursement. In most states, reimbursement rests solely on company policy, a promise that should be upheld in writing.
Upon receiving a WARN notice, submit every outstanding expense as soon as possible, not during your final week. Expense systems and email access are often disabled on or before the last day, making it challenging to submit a claim with a paper trail later. Save copies of all receipts, mileage logs, approvals, and policies outside the company's systems in case of access loss. If the company portal is the only place records reside, export or screenshot them immediately.
If the money remains unpaid, begin by sending a written request to HR or payroll, outlining each expense with its date and amount, along with attached receipts. Retain a copy for your records. Should this approach fail, the next steps depend on your state. In California, file a claim with the Labor Commissioner; in Illinois, the Department of Labor handles Wage Payment Act claims.
Even in states without reimbursement statutes, unpaid expenses may still be recoverable as unpaid wages or under the employer's policy, with small claims court as an option for modest amounts.
Severance agreements may include a general release of claims, which could affect the recovery of unpaid expenses. Before signing any agreement, review it for such provisions. Lastly, remember that reimbursements paid under the IRS's accountable-plan rules are generally not taxable income, while amounts paid outside these rules may be treated as wages. This information is for general guidance only and should not be considered tax or legal advice.
Rewritten by urgent.news; may contain errors — check the original.
Source: dev.to