Zum Hauptinhalt springen
Beancount.io LogoBeancount.io

2026 State Minimum Wage Increases: A Small Employer's Budgeting Guide

9 Minuten LesezeitMike ThriftMike Thrift
2026 State Minimum Wage Increases: A Small Employer's Budgeting Guide

If you run payroll for even a handful of hourly employees, 2026 quietly became one of the more expensive years in recent memory. Nineteen states raised their minimum wage on January 1, dozens of cities and counties layered local increases on top, and a second wave lands mid-year — Florida jumps to $15.00 an hour on September 30, and several jurisdictions add another bump on July 1. If your last labor-cost forecast still assumed 2025 rates, it's already out of date.

The bigger risk isn't the headline number. It's the ripple effect: a $1.50 bump to your lowest-paid role doesn't stay contained to that role. It compresses your entire pay ladder, and if you don't budget for that compression, you'll find out about it the hard way when a shift lead making $16.50 realizes they're now earning almost the same as a new hire.

The 2026 minimum wage landscape, state by state

2026-07-09-2026-state-minimum-wage-increases-small-employer-guide

Here's where the year-start increases landed, effective January 1, 2026, unless noted:

State2026 minimum wage
Washington$17.13
Connecticut$16.94
California$16.90
Hawaii$16.00
Rhode Island$16.00
New York (NYC, Nassau, Suffolk, Westchester)$17.00
New York (rest of state)$16.00
Arizona$15.15
Colorado$15.16
Maine$15.10
Missouri$15.00
Nebraska$15.00
Vermont$14.42
Michigan$13.73
Virginia$12.77
South Dakota$11.85
Minnesota$11.41
Ohio$11.00
Montana$10.85

New Jersey also increased its rate January 1 (specific tiers vary by employer size and industry — check the state Department of Labor schedule directly if you employ there). On top of the state list, roughly 49 cities and counties set their own, higher local floors, and 60 total jurisdictions now sit at or above $15.00 an hour, including 40 localities above $17.00.

The year isn't done moving. Four more states and 22 additional cities and counties raise their minimums again later in 2026, mostly on July 1. Florida is the one every retailer and restaurant operator should have circled: its minimum wage steps up to $15.00 an hour on September 30, 2026, the final leg of the constitutional amendment voters approved back in 2020.

The federal minimum wage, for context, hasn't moved. It's still $7.25 an hour ($2.13 for tipped employees, with a $5.12 tip credit) — a floor that's now irrelevant to the majority of employers, since state and local law always wins when it sets a higher rate.

The rule that trips people up: highest rate always wins

If an employee is covered by more than one minimum wage — federal, state, and city, say — you owe them the highest of the three, full stop. A worker in a state with a $14 minimum but a city ordinance at $16.50 gets $16.50. This gets genuinely complicated for businesses with:

  • Multiple physical locations in different cities or counties within the same state
  • Remote or hybrid employees whose "work location" for wage-law purposes is wherever they're actually sitting, not your HQ
  • Field staff or delivery workers who cross jurisdiction lines during a single shift

Before your next rate change hits, map every employee to their actual work location — not their job title's default assumption — so payroll applies the right number on day one instead of retroactively.

Watch for tipped-wage and exempt-threshold changes too

Two adjacent numbers move alongside the headline minimum wage, and both affect your labor budget even if you don't think of yourself as directly exposed:

Tipped minimum cash wage. Some jurisdictions are phasing out the tip credit entirely. Flagstaff, Arizona, for example, no longer lets employers count any portion of tips toward the wage floor starting in 2026 — tipped workers there get the full $18.35 base rate, with tips fully additional. If you run a restaurant or bar in a jurisdiction moving in this direction, your tipped-labor cost structure just changed even if your posted minimum wage didn't.

Exempt salary thresholds. In several states, the minimum annual salary required to classify an employee as exempt from overtime is pegged to a multiple of the state minimum wage. When the hourly floor rises, the exempt threshold rises with it — which means a salaried assistant manager who cleared the bar comfortably in 2025 might fall under it in 2026, forcing a raise or a reclassification to hourly (with overtime exposure) whether or not you touch their pay intentionally.

Building the ripple effect into your labor budget

The direct cost of a minimum wage increase is easy to calculate: hours × rate delta × pay periods remaining in the year. The indirect cost is where budgets blow up, because raising your floor compresses everyone stacked just above it.

A practical way to model it:

  1. List every hourly role and its current rate, sorted lowest to highest.
  2. Apply the new minimum to whichever roles fall below it.
  3. Decide your compression policy — will you preserve the dollar gap between tiers (expensive, but keeps morale and incentive structure intact), preserve the percentage gap (cheaper), or do nothing and accept that your $0.50/hour differential between "new hire" and "six months in" just evaporated?
  4. Re-run payroll tax and benefits math — employer-side FICA, unemployment insurance, and any benefits pegged to wages all scale up with the raise, not just the gross wage line.
  5. Check your workers' comp premium basis — many states calculate it as a percentage of payroll, so a wage floor increase quietly raises this cost too.

This is exactly the kind of multi-line, multi-jurisdiction calculation that's miserable to track in a spreadsheet that gets overwritten every quarter. If your books are in a system where every payroll journal entry, tax accrual, and benefits adjustment is a plain-text, version-controlled record, you can actually diff this year's labor cost structure against last year's and see precisely where the ripple effect landed — role by role, location by location — instead of reconstructing it after the fact.

A worked example: what compression actually costs

Say you run a 12-employee coffee shop in Denver, where Colorado's state minimum climbed to $15.16 on January 1, but Denver's own city minimum wage — set independently and typically higher than the state floor — governs instead. Before the increase, your pay ladder might have looked like this: baristas at $15.00, shift leads at $16.50, and an assistant manager at $19.00.

If the new city floor lands at, say, $16.00, your baristas get an automatic $1.00/hour raise. Do nothing else, and your shift leads — who took on more responsibility specifically to earn $1.50/hour more than a barista — now earn only $0.50/hour more. That gap was the incentive to take the promotion in the first place. Preserve it in dollar terms and you're now also raising shift leads to $17.50, which pulls the assistant manager's premium into question too. One line-item rate change on a government website just became a three-tier payroll adjustment, plus the associated bump in employer FICA, unemployment insurance, and workers' comp premium — often another 10–15% on top of the raw wage increase once you add it all up.

Multiply that by 12 employees across a full year and the difference between "I updated the register's wage field" and "I modeled the ripple effect" can easily be a five-figure swing in your annual labor budget.

Common mistakes small employers make with mid-year wage changes

  • Treating the January 1 wave as the only one. Plenty of employers set a calendar reminder for New Year's and then get caught flat-footed by the July 1 and September 30 rounds. Wage floors move at least twice a year in many states now — build a recurring quarterly check into your compliance calendar, not a once-a-year one.
  • Applying the state rate when a local ordinance is higher. City and county minimum wages are common in California, Colorado, Washington, and New York, and they're almost always higher than the state floor, not lower. Defaulting to the state number without checking the specific city or county is one of the most frequent wage-and-hour violations regulators cite.
  • Forgetting tipped employees have a separate cash-wage schedule. A jurisdiction can raise its standard minimum wage without changing the tip credit rules, or it can eliminate the tip credit entirely (as Flagstaff did) — the two numbers don't move in lockstep, and assuming they do under- or over-pays your tipped staff.
  • Not re-checking exempt classifications after a raise. If a state ties the exempt salary threshold to a multiple of its minimum wage, a January 1 increase can silently push a previously exempt employee below the new threshold. Skipping this check exposes you to unpaid-overtime liability that's easy to avoid with a five-minute review.
  • Budgeting the wage increase but not the payroll tax and insurance increase that rides along with it. Employer-side FICA, state unemployment insurance, and workers' comp premiums are typically calculated as a percentage of gross wages — so every dollar you add to the wage line adds a smaller, but real, dollar amount to at least three other cost lines.

A timeline worth putting on your calendar

  • Now (before any rate change hits): map employees to work location, confirm which jurisdiction's rate governs each one, and check whether your state ties the exempt salary threshold to the minimum wage.
  • July 1, 2026: several state and local increases take effect — verify your payroll system is scheduled to update automatically, not manually, since a missed rate change is a wage-and-hour violation, not just a bookkeeping error.
  • September 30, 2026: Florida reaches $15.00/hour. If you operate there, model this cost now rather than in Q3.
  • Ongoing: post updated minimum wage notices at every physical work location — this is a compliance requirement in nearly every jurisdiction, separate from actually paying the new rate.

Keep Your Labor Costs Transparent Year-Round

Minimum wage changes are one of the few cost increases you can see coming months in advance — the hard part is tracking how they cascade through your payroll, benefits, and tax accruals without losing the thread. Beancount.io gives you plain-text, version-controlled accounting where every wage adjustment, payroll tax line, and benefits recalculation is a diffable, auditable entry — no black-box payroll report to reverse-engineer when a rate changes mid-year. Get started for free and see exactly where your labor budget stands, jurisdiction by jurisdiction.