California local minimum wage rates move in eleven cities and counties on July 1, 2026, according to CalChamber’s HRWatchdog roundup. Six cities raise separate hotel, airport, or event-center rates on top, while the state floor stays at $16.90. The new rates are public. What decides whether you actually pay them is quieter: the work-location field in your payroll system. The map below shows where the rates land.

Rate sources: California DIR and CalChamber HRWatchdog. Exposure sources: Labor Code §§ 1194, 1194.2, and 1197.1.

The new California local minimum wage map

+−1×

Pinch, Ctrl + scroll, or double-click to zoom. Drag to pan once zoomed, or use the + and − buttons.

California’s state minimum wage has been $16.90 per hour since January 1, 2026, per the Department of Industrial Relations, and where a local ordinance sets a higher rate, the higher rate wins. If your hourly rates were keyed to the state table in January, the eleven cities below just moved past you:

Two things about this table do the damage. First, the rate follows where the hours are worked, not where the employee is based, and that includes remote workers. A customer-service rep working from a Pasadena apartment is owed Pasadena’s $18.57 for those hours. Second, the new rates apply to hours worked on and after July 1, which lands mid-pay-period for most employers. Waiting for the next clean period start is itself an underpayment.

Hotel and airport minimum wages split off from the city code

Six cities also raise industry-specific minimums on July 1, and none of them ride on the general citywide rate code. These follow the property type and the worker’s role:

Los Angeles adds one more layer: airport employers that do not provide the required health benefits owe additional wages on top of the $25.00. If a covered property is coded to the citywide rate, covered workers can be underpaid at once. A Los Angeles housekeeper on the general $18.42 code instead of the $25.00 hotel rate is short $6.58 every hour. A Long Beach housekeeper still at the state floor is short $9.60. In hospitality, one miscoded rate usually means the whole crew is miscoded, which is how these misses turn into class claims.

Coverage is not automatic, either. It usually turns on where the work is actually performed, and many ordinances set an hours threshold: San Francisco and Los Angeles both cover anyone who works two or more hours in a week inside city limits. Some rates vary by employer size, hotel rules can depend on room count or property type, and a Los Angeles County address only follows the county ordinance if it sits in an unincorporated area. When more than one rate could apply, the employee gets the highest. Confirm coverage city by city before you change a rate, not after.

The three location gaps that hide the underpayment

Take an hourly employee who works three shifts each week in Emeryville, California. Everything appears to be running smoothly; hours are tracked, payroll is processed, and wages are paid on time. Then July 1 arrives, and Emeryville’s local minimum wage increases to $20.34 per hour.

If the employer is unaware of the increase or has not reviewed the employee’s work location and pay rate, the employee could unknowingly be paid below the required local minimum wage. What may seem like a small oversight can quickly add up, creating wage and hour liability, back pay obligations, and potential penalties.

With several California cities and counties implementing minimum wage increases effective July 1, 2026, now is the time for employers to review their pay practices and ensure employees are being paid in accordance with the applicable local requirements.

The math behind that oversight moves fast. An Emeryville employee left at the $16.90 state floor is short $3.44 an hour, roughly $7,155 a year full time. California law can add liquidated damages equal to the unpaid minimum wages under Labor Code § 1194.2, subject to statutory defenses, and Labor Code § 1197.1 adds a civil penalty for intentional underpayment: $100 per underpaid employee per pay period at first, $250 after. The checks go out on schedule, the register looks clean, and the claim shows up a year later for money no one knew was missing.

Three data gaps account for nearly every miss we find when we pull a client’s payroll file ahead of a midyear increase. The rate table is almost never the problem.

The first is the headquarters default. Multi-site employers often have every hourly employee mapped to the worksite entered at hire. The employee floats between locations, the time clock records where they actually worked, and payroll never reconciles the two. The underpayment lives in the gap between the time and attendance export and the payroll register’s work-location column.

The second is the blank remote field. A remote or hybrid employee with no work city on file inherits a default, usually headquarters or the state rate. California treats the place where the work is performed as controlling, so a blank field is not a neutral setting. It is a decision to pay the wrong rate.

The third is the industry code that never got built. Hotel and airport rates need their own rate codes tied to the worker’s role and property, not just the address. If your HRIS has no field separating a hotel housekeeper from an office admin at the same street address, the ordinance rate has nothing to attach to.

Pull last pay period’s time data for every California hourly employee and compare the clock-in locations against the work city in payroll. If anyone logged hours in a city on either table above and payroll shows a different city, the gap is already accruing.

The 20-minute audit to run before July payroll

None of this is a policy problem. It is a payroll data problem, and the fields that decide the outcome are concrete: work location, home address for remote staff, jobsite or client site, city and county jurisdiction, the rate table, the effective date, and the audit trail showing who changed what. If your first July payroll has already been keyed, run the audit anyway. A correction this month is a line item; a correction next year is a settlement.

Work the list out of your payroll administration platform, in this order:

• Pull the work-location report: every California hourly employee, current rate, payroll work city, and remote flag.
• Match it against the July 1 lists: flag anyone working in the eleven cities or under the six industry ordinances above.
• Check remote workers against their home city: the rate follows where the work is performed, and a blank field defaults to the wrong rate.
• Confirm city versus unincorporated county: an address one block outside city limits can sit under a different ordinance, or none.
• Code industry roles separately: hotel, airport, amusement park, and event-center workers need their own rate codes, not the city default.
• Date corrections July 1: the new rates apply mid-period, to hours worked on and after July 1, not the next clean period start.
• Document the source for each rate: save the ordinance page or bulletin you relied on next to the corrected register.
• Recheck monthly through the summer: new hires, transfers, and jobsite changes reopen the location question every cycle.

Finish with the paper trail. Cities that raise rates generally expect updated workplace postings at the same time, and the flagged-worksite list you just built is the poster order list. Save the dated confirmations next to the corrected register: one folder, one audit trail.

How VertiSource HR helps before the first July close

VertiSource HR can review the export with your payroll lead before the first affected payroll closes.

Before that payroll closes, ask us to review three things: payroll-location setup, wage-rate mapping, and the July 1 exposure list. Contact VertiSource HR to schedule the review.