Your July payroll looked fine on the screen, but if you employ anyone in Alaska, Oregon, Washington D.C., or a dozen California, Illinois, and Maryland cities, the legal minimum you owe them changed overnight on July 1 — and the liability for getting it wrong started accruing with the very next hour they worked.
It is an easy miss. The federal minimum wage has not moved since 2009, so many owners set payroll once and rarely revisit it. In the meantime, states and even individual cities have taken over, and they do not coordinate calendars. Nineteen states raised wages on January 1, but a second wave hits every July 1. This year that wave covers more than 20 state and local jurisdictions, lifting pay for more than 360,000 workers by a combined $221 million annually according to the Economic Policy Institute — and leaving multi-location small employers to chase a patchwork of new rates inside a single pay period.
If you run payroll yourself or review what a bookkeeper or PEO runs for you, this is the one payroll update you cannot wait until Q4 to handle. Here is what changed, where it matters most for small businesses, and exactly how to make your system compliant before the next payroll run.
What Changed on July 1, 2026
The July increases fall into two buckets: statewide rates that moved on July 1, and city or county rates that sit on top of — and often well above — the state floor. The rule everywhere is the same: you owe the highest rate that applies to where the work is performed, not where your headquarters sits or where the employee lives.
State-Level Increases Effective July 1
- Alaska: $13.00 to $14.00 per hour. This is the second step of Ballot Measure 1 — it rises again to $15.00 on July 1, 2027, then indexes to inflation. Alaska does not allow a tip credit, so tipped employees must receive the full $14.00.
- Oregon: Statewide increase effective July 1 (rate varies by region — Portland metro highest, rural counties lowest — under Oregon's tiered system). Washington D.C. also increased on July 1, as it does annually.
- Other midyear movers: Nevada, Portland-adjacent Oregon counties, and a handful of other states adjust July 1 each year. Florida is not a July mover — its next increase to $15.00 hits September 30, 2026 — and Connecticut already moved June 1. If you operate in more than one state, you likely had at least two different effective dates in the first half of the year.
- Nebraska twist: LB 258, effective July 17, 2026, does not change the standard $15.00 rate, but it creates a new youth minimum and revises the training wage. If you hire teens or use a 90-day training rate in Nebraska, your permissible rate just changed even though the adult floor did not.
Ballotpedia counts 22 states plus D.C. raising wages at some point in 2026, pushing the nationwide average state minimum to about $11.51. The July cohort is smaller but hits hardest where local add-ons stack.
City and County Increases Effective July 1
GovDocs tracks 17 city and county increases taking effect July 1, 2026 across California, Illinois, Maryland, and Minnesota/Oregon jurisdictions. California dominates the list. While the statewide floor is $16.90, cities routinely set higher minima:
- Los Angeles, San Francisco, Berkeley, Emeryville, and Santa Monica are among the California cities that reset July 1.
- Chicago raised its citywide minimum July 1 (with separate rates for large vs. small employers and tipped workers).
- Minneapolis and St. Paul — where large employers hit $16.37 on January 1 but small and micro employers phase in through July 1 — and several Maryland and Oregon counties complete the set.
The source list matters less than the pattern: if you have employees in California, Illinois, or the D.C. metro, assume a July 1 local rate moved unless you have verified otherwise for that exact ZIP code.
Why Multi-Jurisdiction Employers Get Caught
A single storefront with a stable crew can update one rate and move on. Complexity — and penalty risk — scales the moment you have any of these:
- Remote employees in different cities. An employee working from home in Los Angeles County is owed the Los Angeles rate even if your office is in a $16.90 part of the state.
- Mobile or site-based work. Construction, cleaning, home health, and delivery crews who work across city lines in a single week may be owed different rates for hours worked in different jurisdictions. Chicago and several California cities require you to track this by hour.
- Tipped staff with a local tip credit. Chicago, D.C., and California cities handle tipped wages differently. Some eliminate the tip credit entirely; others phase it down. Applying the wrong tip credit is one of the most common audit findings.
- Youth and training wages. Nebraska's new youth wage and similar provisions elsewhere let you pay less for workers under a certain age or in the first 90 days, but the conditions are narrow — wrong age documentation or missing written notice voids the exception.
Wage theft penalties in most of these jurisdictions are not just back pay. Expect interest, waiting-time penalties, and often a per-pay-period penalty for each inaccurate pay stub.
The Payroll Update Checklist (Do This Before Your Next Run)
Treat July 1 as a midyear close — a short, disciplined sprint you can finish in a day if you approach it systematically.
1. Build Your Jurisdiction Map
List every location where work was performed in the last and next pay period — office, job site, client site, and remote home offices. For each, note the applicable city, county, and state rate. If two overlap, circle the highest number; that is the legal minimum. DOL's Consolidated Minimum Wage Table as of July 1, 2026 is a useful starting point, but verify city rates directly — state tables often exclude them.
For the 17 GovDocs-tracked cities and counties, pull the published table for July 1, 2026 and save the PDF with your payroll file. Auditors ask for contemporaneous rate sources; a screenshot with a date beats memory.
2. Update Your Payroll System on the Effective Date, Not the Pay Date
This is where most underpayments happen. If a semimonthly pay period runs June 16 to June 30 and July 1 to July 15, only the July hours are at the new rate — but if your next check covers July 1–15 and you apply the increase to the whole period, you have either overpaid or underpaid depending on timing. Conversely, if your system applies the change on the pay date instead of the work date, early-July hours get the old rate.
In most payroll platforms, the fix is to set the rate change effective July 1 per employee work location, then run a test payroll that splits the period. If your software cannot split a period by effective date, handle it as two separate runs or a manual adjustment line.
3. Audit Every Employee Against the New Floor
Run a simple report: employee, work location, current hourly rate, and new applicable minimum. Flag anyone within $0.50 of the new floor — compression raises may be contractually required even if not legally mandated, and anyone at exactly the old minimum is now below the new one.
Remember subsets:
- Tipped employees: Recompute the required cash wage and the maximum tip credit for each jurisdiction. Do not apply the federal $2.13 tipped cash wage where a city forbids it.
- Minors and trainees: Nebraska aside, most states either have no youth subminimum or limit it to the first 90 days with a written training agreement. Verify age, start date, and notice before using it.
- Salaried exempt staff: The minimum wage change does not directly change exempt salary thresholds, but a few cities tie their exempt threshold to a multiple of minimum wage — worth a quick check if you classify anyone near the line.
4. Prorate the First Pay Period That Straddles July 1
For hourly workers, math is straightforward: hours before July 1 at the old rate, hours on/after at the new. For piece-rate, flat-rate, or shift-differential pay, confirm the effective hourly rate for each hour still clears the new minimum after July 1. Daily and weekly equivalents — some cities publish a minimum per shift — can also be a trap if you pay by the day.
Keep the calculation in your payroll file. If a dispute arises six months later, a one-line note that says "7/1 hours split per attached timecard" is worth more than a reconstructed spreadsheet.
5. Issue Updated Notices and Posters
Almost every jurisdiction that raises wages requires updated workplace posters and, increasingly, written notice to each employee of the new rate. California, Chicago, and D.C. all require the poster to be displayed where employees can see it — breakroom wall for on-site staff and an electronic posting or emailed notice for remote staff. Order or print the July 1 poster now; do not wait for the state to mail one.
6. Fix Your Pay Stub
Underpayment is violation one; an inaccurate pay stub is often violation two with its own per-stub penalty. Confirm your stub shows hours, rates, gross, deductions, and net correctly for the split period, and that any youth or training rate is labeled as such. Maryland and California labor agencies routinely scan stubs during audits even when the underlying wage math was correct.
7. Budget Forward — Do Not Treat July 1 as One-and-Done
Two more 2026 milestones are already on the calendar: Florida moves to $15.00 on September 30, and Oregon and Alaska will move again July 1, 2027. If you give annual raises in January, build the midyear mandatory bump into labor costing now so you are not forced to choose between an off-cycle market increase and a mandatory one two months apart.
Common Mistakes That Trigger Back Pay and Penalties
- Assuming "state rate covers me." In Los Angeles, San Francisco, Chicago, and similar cities the city rate is $1 to $4 above the state. Paying the state rate feels compliant until the city audits you.
- Updating headquarters but missing remote workers. A Denver HQ with a remote employee in San Francisco must pay the San Francisco rate for that employee.
- Applying the increase to the whole pay period. Auditors recalculate by work date. If you lack timecards that prove when July hours were worked, they often assume the worst.
- Forgetting tipped reconciliations. You must ensure tipped employees' cash wage plus tips meets the full minimum each pay period. A good week does not excuse a bad one, and many cities now require the reconciliation weekly.
- Tossing old timecards and rate tables. Retain time records, rate-change audit logs, and the poster you displayed for at least three years — four in California. "We updated the software" is not a defense without the record.
A Note on Budgeting and Cash Flow
Midyear wage increases compress margins in real time — labor cost rises July 1 but pricing, contracts, and revenue may not adjust until next quarter. Before you absorb the increase as "just payroll," model it.
Take Alaska as an example: $1.00 more per hour times 30 hours per week times 26 weeks is $780 per employee for the second half of 2026 alone. In EPI's July cohort, that math aggregates to $221 million across the affected workforce. For a small employer with ten affected employees in a high-cost city where the bump is $0.60 to $1.35, you are looking at $4,000 to $9,000 in incremental wage plus payroll tax and workers' comp before year-end.
Track the increase as its own line — "July 1 MW increase" — in your P&L rather than burying it in general wages. That separation helps in three practical ways: you can price the next contract accurately, you can explain the variance when you review July financials, and you have the documentation if you need to support a price adjustment with a customer under a cost-escalation clause.
Keep Your Payroll Records Audit-Ready
A wage increase is also a bookkeeping test. The businesses that sail through a Department of Labor inquiry are the ones that can produce, in minutes, a clean chain: jurisdiction map, rate source, effective-date change log, split-period timecards, updated poster, and pay stubs that match. The ones that struggle are the ones that fixed the rate in the payroll system but kept no paper trail.
If you are closing July books now, reconcile payroll with extra care: confirm the payroll journal entry splits the period correctly, that employer payroll tax and workers' comp bases reflect the higher wages, and that any youth/training wages are coded separately so they do not pollute your average-hourly-rate analytics. Good books will not prevent an audit, but they make one short and boring — which is exactly what you want.
Simplify Your Financial Management
Staying on top of midyear wage changes is easier when your payroll and accounting share the same source of truth. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready — so every rate change, payroll journal, and reconciliation lives in a history you can audit and automate. Get started for free and bring the same rigor to your books that regulators expect from your payroll.