If you run payroll for employees in more than one state, "the minimum wage went up" is never a single fact — it's up to fifty different facts, several of which changed again halfway through the year. On January 1, 2026, nineteen states raised their minimum wage floors in the same week, and more than a dozen additional state and local rates shifted again on July 1. Miss one of them and you're not just underpaying a worker — you're exposed to back wages, liquidated damages, and in some states, penalties that stack per pay period.
For a business with employees in two, five, or twenty states, keeping the wage floor straight for every jurisdiction is quietly one of the hardest parts of running payroll. Here's what actually changed in 2026, and a checklist for building a system that doesn't rely on someone remembering to check fifty different labor department websites.
The states that raised their minimum wage on January 1, 2026
Nineteen states increased their minimum wage at the start of the year, most through automatic inflation indexing written into state law years ago rather than fresh legislation:
| State | 2026 rate |
|---|---|
| Washington | $17.13 |
| Connecticut | $16.94 |
| California | $16.90 |
| New Jersey | $15.92 |
| New York (NYC, Long Island, Westchester) | $17.00 |
| New York (rest of state) | $16.00 |
| Hawaii | $16.00 |
| Rhode Island | $16.00 |
| Arizona | $15.15 |
| Colorado | $15.16 |
| Maine | $15.10 |
| Missouri | $15.00 |
| Nebraska | $15.00 |
| Vermont | $14.42 |
| Virginia | $12.77 |
| South Dakota | $11.85 |
| Michigan | $13.73 |
| Minnesota | $11.41 |
| Ohio | $11.00 |
| Montana | $10.85 |
Six of those states — Arizona, Colorado, Hawaii, Maine, Missouri, and Nebraska — crossed $15 an hour for the first time. Washington now holds the title of highest statewide minimum wage in the country.
Florida followed later in the year, rising to $15.00 on September 30, 2026, the final step of a ballot-initiative phase-in voters approved back in 2020. Alaska and Oregon also stepped up their rates on their own annual schedules — Oregon's is one of the more complicated ones, with three different regional tiers ($14.05 to $16.30) depending on whether the work is performed inside the Portland metro urban growth boundary, in a standard county, or in a designated nonurban county.
States that didn't move — and the ones still at $7.25
A second group of states already sits above the federal floor but simply didn't have a scheduled increase in 2026: Arkansas ($11.00), Delaware ($15.00), Illinois ($15.00), Maryland ($15.00), Massachusetts ($15.00), Nevada ($12.00), New Mexico ($12.00), and West Virginia ($8.75). If you have workers in these states, the number on your last pay stub is still correct — but don't assume that means nothing changed. Several of these states, along with plenty that did raise wages, also rolled out unrelated payroll obligations in 2026 (more on that below).
Then there's a third group — twenty states in total — that still defaults to the federal minimum wage of $7.25 an hour, unchanged since 2009: Alabama, Georgia, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Mississippi, New Hampshire, North Carolina, North Dakota, Oklahoma, Pennsylvania, South Carolina, Tennessee, Texas, Utah, Wisconsin, and Wyoming. For employers whose only footprint is in one of these states, the compliance question is simpler. For anyone with a multi-state workforce, it means your pay floor can legitimately range from $7.25 to $17.13 depending purely on which state an employee clocks in from.
Local wages can override the state rate — and cities keep adding new ones
State-level charts only tell half the story. Roughly 68 cities and counties raised their own local minimum wages in January 2026 on top of (or instead of) their state's rate, and when local and state law disagree, the employer must pay whichever rate is higher for the employee. California alone has dozens of cities with wages above the $16.90 state floor — some, like Hayward and Novato, tie their local rate to employer size, meaning two businesses across the street from each other can owe different minimums depending on headcount.
Tipped wages add another layer. Flagstaff, Arizona eliminated its subminimum tipped wage entirely for 2026, meaning tipped employees there must now receive the full local minimum — $18.35 an hour — before tips, not a reduced "tip credit" rate. If your payroll system still assumes a flat tip credit calculation nationwide, a jurisdiction like this will silently generate underpayments every single pay period until someone catches it.
The practical takeaway: a payroll process built around "look up the state rate" is already outdated. You need location-level granularity down to the city or county for any employee working in a state that permits local wage ordinances — mainly California, New York, Washington, Illinois, Minnesota, and a handful of others.
It's not just the wage floor — three other 2026 changes hit payroll at the same time
Multi-state employers who only track minimum wage numbers can still get blindsided, because several unrelated compliance changes landed in the same window:
- New paid family and medical leave (PFML) programs. Maryland, Minnesota, and Delaware all activated mandatory PFML programs on January 1, 2026, each with its own payroll tax withholding, contribution rate, and remittance schedule. If you have even one employee in these states, you likely have a new payroll deduction line and a new quarterly filing you didn't have last year.
- Pay transparency mandates. A growing majority of states and cities now require job postings to disclose a minimum and maximum salary range — and several extend that obligation to internal promotion postings, not just external job ads. This isn't a minimum-wage issue directly, but HR and payroll teams that manage compensation bands together are updating both processes at once.
- Automatic payroll tax filing changes from major providers. Some payroll platforms shifted core tax-filing behavior in 2026, moving from an opt-in model to fully automatic withdrawal and filing. If your business relies on one of these platforms, confirm exactly when the switch takes effect for your account and what happens to any manual overrides you had in place.
None of these show up if you're only scanning a "minimum wage by state" table, which is exactly why treating wage compliance as an isolated task is risky.
A multi-state payroll compliance checklist for 2026
- Map every work location, not just every state. Build a list of every city and county where you have an employee physically working — including remote employees — not just the states. Local ordinances are where most surprises live.
- Confirm effective dates, not just rates. Several 2026 changes (Florida, Oregon, various city ordinances) took effect mid-year rather than January 1. A rate that's correct in June can be wrong in October.
- Check tipped and subminimum wage rules separately. Tip credit percentages, training wages, and subminimum wage eligibility follow their own rules per jurisdiction and don't always move in lockstep with the standard minimum wage.
- Verify your payroll software's update cadence. Ask your provider (or your in-house payroll team) exactly when rate tables are refreshed and whether local ordinances are covered automatically or require manual entry.
- Reconcile exempt employee salary thresholds too. Some states tie exempt-employee minimum salary requirements to their minimum wage; a wage increase can quietly push a previously exempt employee below the new threshold.
- Audit new deductions and filings. If you added employees in Maryland, Minnesota, or Delaware this year, confirm PFML withholding and remittance are actually configured — this is easy to miss because it isn't a "raise the number" change like minimum wage.
- Document your compliance date trail. Keep a dated record of when each jurisdiction's rate was confirmed and applied. If a wage claim surfaces later, being able to show exactly when you implemented a rate change is a meaningfully stronger position than reconstructing it after the fact.
Keep Your Payroll Records Auditable, Not Just Accurate
A wage claim or Department of Labor audit doesn't just ask what you paid — it asks when you knew a rate changed and when your payroll actually reflected it. Beancount.io's plain-text accounting gives every payroll adjustment a permanent, version-controlled history you can point to, so proving compliance across dozens of jurisdictions doesn't mean digging through spreadsheets or platform support tickets. Get started for free and keep your financial records as auditable as your payroll needs to be.