PAGA matters surface in stacks. The §226 wage statement layer pays the dollars. The §226.7 meal-and-rest layer is the most-cited theory. The §2802 expense reimbursement layer is the one most employers don't know they have.
A California wage-and-hour matter is rarely about a single Labor Code section. It's about a stack: §226 wage statement defects on the documentary layer, §226.7 meal-and-rest premiums on the workflow layer, §510 overtime miscalculation on the rate layer, §201–§203 final-paycheck timing on the separation layer, and §2802 expense reimbursement on the layer most employers don't think to check until counsel asks for the records.
This post is about §2802 specifically — what it requires, where the typical employer's exposure sits, and why the layer matters more in 2026 than it did five years ago.
The statute is short. Labor Code §2802(a):
An employer shall indemnify his or her employee for all necessary expenditures or losses incurred by the employee in direct consequence of the discharge of his or her duties, or of his or her obedience to the directions of the employer.
The operative phrase is all necessary expenditures or losses. The California Supreme Court has interpreted necessary expansively. An expense is reimbursable under §2802 if (a) the employee incurred it in the course of doing the job, and (b) the expense was reasonable given the work being done.
The expansive reading means §2802 covers many categories employers don't always associate with reimbursement:
The list is not exhaustive. The standard is necessary expenditures incurred in the course of duties.
Three patterns recur in California employers who haven't audited their §2802 posture:
No structured cell-phone stipend. The employee uses a personal cell phone for work. The employer doesn't reimburse, doesn't provide a company phone, doesn't have a written policy. Every pay period the employee uses their phone for work is a per-period §2802 exposure. Across a large hourly workforce and a multi-year limitations window, the unreimbursed amounts accumulate quietly and are trivial to compute from records the employer already has.
A nominal stipend that doesn't track actual use. Some employers pay a flat monthly stipend (e.g., $25/month) intended to cover cell, internet, and incidentals. If the stipend is not tied to actual cost, and the actual cost varies meaningfully across employees, the stipend may be insufficient under §2802 for the employees whose actual use exceeds the stipend. A per-employee actual-cost analysis is the conservative path.
Equipment reimbursement that's case-by-case. The employer reimburses equipment expenses when an employee submits a receipt. The employee doesn't always submit. Employees who don't submit are still entitled under §2802; the employer's policy of we'll reimburse if you ask doesn't satisfy the obligation.
In each pattern, the §2802 exposure compounds across the four-year statute window. The PAGA layer on top — civil penalties for each §2802 violation per pay period — multiplies the exposure further.
Two structural shifts have made §2802 a larger share of total wage-and-hour exposure than it was five years ago.
The post-pandemic WFH baseline. Even in industries with mostly on-site workforces (construction and logistics included, on the administrative side), hybrid or remote arrangements for office staff are now normal. Each remote employee has internet, electricity, workspace, and equipment expenses that the §2802 analysis now reaches. Employers who haven't formalized a WFH expense policy are paying a §2802 premium per employee per pay period without knowing it.
The cell-phone-as-default communication channel. In 2015, an employer could plausibly argue that work calls were occasional and reimbursement wasn't required. In 2026, virtually every operational role requires the employee's cell phone — for Slack, Teams, scheduling apps, time-clock apps, dispatch, vendor coordination. Cochran and its progeny make this an active §2802 claim category.
Two things need separating here, because they are usually run together and only one of them is true.
The §2699 reasonable-steps provisions reach the PAGA civil penalty layered on a §2802 violation. They do not reach the reimbursement itself. The underlying obligation to indemnify is not capped, not waivable, and not defended by any document: §2804 makes any agreement by an employee to waive §2802 null and void, and Cochran holds the employer owes a reasonable percentage of the bill whether or not the employee paid anything extra. An employee signature confirming that expenses were submitted does not touch that. It never did.
What does reach it is the recurring payroll audit — the first of the four examples §2699(g)(2) enumerates, and the only instrument in the set that finds an unreimbursed expense the employee never claimed. An employer running that audit on a schedule, acting on what it finds, and recording what was done has the argument available. An employer who is not running it does not have the argument at all. Whether a court honors it, and to what extent, is discretionary — §2699(e)(2) lets a court exceed the subdivision (g) and (h) limits — so no one should be quoting you a number.
Four components:
A written reimbursement policy, distributed and acknowledged. Lists the categories the policy covers, the reimbursement methodology for each, and the submission process for actual-cost categories. Bilingual where the workforce is bilingual.
A defensible stipend methodology for fixed-cost categories. If you reimburse cell phones via a monthly stipend rather than per-call, document how the stipend was calculated and why it's reasonable for the workforce it covers. Periodic review (annual is fine) to confirm the methodology still tracks actual use.
A clean submission and approval workflow for actual-cost categories. Submission is electronic, dated, and tied to specific expenses. Approval is documented. Reimbursement is on the next pay run.
Audit and corrective action. Periodic review of the reimbursement records as part of the broader §2699(g)(2) payroll audit. This is the component that does the work. The other three describe the program; this one finds the employee who has been running dispatch off a personal phone for eleven months and never submitted anything, and the true-up entered against that finding is the record. An unreimbursed expense with nothing recorded after it is not a reasonable step. It is a documented violation with your name on it.
MicroForensics addresses §2802 through the audit module rather than the signature. The per-period attestation is a Donohue instrument and stays in its lane; expense exposure surfaces in the recurring audit, opens an item, and the item does not close until someone records the true-up or the reason there isn't one. Different instrument, different job. Assume everything we generate is produced in discovery — which is exactly why the correction field is mandatory rather than optional.
§2802 is the least-considered and most-stackable layer in California wage-and-hour exposure. It's also the one most cheaply addressed — a clear policy plus a structured reimbursement workflow plus an audit cadence. The cost to fix is small; the cost of ignoring is the multiplier on every other Labor Code section the plaintiff's firm names in the same notice.
If you'd like to walk your current reimbursement posture against the §2802 standard, the discovery call is the right starting point. Bring your policy if you have one and your most recent quarter of expense submissions.