How does Arizona wage, overtime and meal-break law work in 2026?

Three things catch out-of-state employers:

• The rate moves every January. The Industrial Commission of Arizona announces the new rate around 30 September each year, after the August inflation figure lands. That gives you 90 days to update offer letters and salary letters tied to the minimum.
• Two city overlays. An Arizona payroll with employees physically in Flagstaff or Tucson follows the city rate, not the state. Each city publishes its own notice. Verify both in January.
• No subminimum for trainees. Arizona accepts the federal subminimum for learners, but only if you hold a US Department of Labor certificate. Assume the full state minimum otherwise.

The Proposition 206 origin

Voters approved Proposition 206, the Fair Wages and Healthy Families Act, in November 2016. It set a four-step minimum wage from 2017 to 2020 and wrote in the annual CPI indexation that has driven every 1 January raise since 2021. The same proposition introduced statewide paid sick time. The state legislature preempted cities from adding their own paid-leave rules above the Prop 206 floor. The minimum-wage layer was not preempted, which is why Flagstaff and Tucson lawfully set their own city floors.

The arithmetic is the standard federal workweek calculation. Define a fixed 168-hour workweek, total non-exempt hours, pay 1.5 times the regular rate on every hour over 40. The regular rate includes non-discretionary bonuses, shift differentials, and commissions earned in the same week. It excludes discretionary bonuses, gifts, and expense reimbursements.

Exempt vs non-exempt classification

To be exempt from overtime in Arizona, an employee needs to pass both a salary basis test and a duties test:

• Salary basis: at least $684 a week, paid as a fixed salary not reduced by quality or quantity of work.
• Duties test: primary duty must be executive, administrative, professional, computer, or outside sales. Job title alone never qualifies.

A 2024 federal rule increase that would have raised the salary basis to $1,128 a week was vacated by a Texas federal court in November 2024. The operative floor in May 2026 is still $684 a week. Misclassification is the single biggest overtime-liability source in Arizona. *Misclassification* is when a worker does the duties of a non-exempt employee but is paid as exempt. The state treats them as non-exempt anyway. Teamed’s onboarding flow runs the duties test on every salaried Arizona offer and flags borderline cases before the hire goes through.

Three operational rules for any Arizona restaurant, bar, or hospitality employer:

• The make-up runs each pay period. Track tip totals per shift and per pay period. Do not net out high-tip and low-tip weeks against each other.
• Tip pools are allowed, with limits. You can pool tips among customarily tipped staff. Managers and supervisors cannot share in the pool. That federal rule applies regardless of whether you take a tip credit.
• Service charges are not tips. A mandatory service charge added by the employer is employer revenue. If you pass it to staff, it counts as wages (taxable through payroll), not tips, and cannot count against the tip-credit ceiling.

An employer running operations in Phoenix, Flagstaff, and Tucson has three different tipped cash wages to set per location. Teamed’s payroll engine carries each location’s tip-credit configuration on the work-location field, so the right cash wage applies when the timesheet posts.

The federal default rules govern when you do choose to offer breaks:

• Short rest breaks (5 to 20 minutes): treated as paid working time. A 15-minute coffee break counts toward the 40-hour weekly overtime threshold.
• Meal periods (30+ minutes): can be unpaid, but only if the employee is fully off duty. An employee required to stay at the desk and answer the phone during a 30-minute lunch is on the clock, and the time goes back into the 40-hour weekly count.
• Nursing mothers: the PUMP Act requires reasonable break time and a private non-bathroom space to express breast milk, for one year after the child’s birth. This is federal and non-negotiable.

Most Arizona employers offer a 30-minute unpaid lunch and one or two 10-15 minute paid breaks per 8-hour shift, by policy not statute. Document the structure in the handbook and apply it consistently. Ad-hoc “take a break when you need one” phrasing creates exposure when an employee later claims they worked through unpaid time.

Minors under federal child-labor rules

Arizona adds no state-level meal-break rule for workers under 18, but federal child-labor rules cap hours, restrict hazardous occupations, and set working-time limits for 14- and 15-year-olds. Schedule a 30-minute unpaid meal break for any minor working a 5+ hour shift as a defensive practice. Document it on the timesheet.

Two operational implications for inbound payroll:

• Bi-weekly is compliant. Monthly is not. Most multi-state employers default to bi-weekly (every 14 days), which clears the 16-day max comfortably. Monthly payroll is illegal for most Arizona employee types, with narrow carve-outs for salaried executive, administrative, and professional staff.
• Involuntary terminations need out-of-cycle payroll. An Arizona employee terminated on Monday must be paid by the following Wednesday (7 working days, excluding the weekend), or on the next regular payday, whichever comes first. Configure the payroll system for ad-hoc check runs before the first Arizona termination.

What treble damages look like in dollars

A single $3,000 unpaid final paycheque paid 14 days late, after the 7-working-day window closed, exposes the employer to $9,000 in damages plus the original $3,000. Add attorney fees if it goes to litigation. Teamed’s payroll engine flags any termination event entered into the system and schedules the final-pay run inside the statutory window automatically.

Three patterns Arizona employers see most often:

• On-premises wait time: a delivery driver between runs reading a book in the warehouse breakroom. Engaged to wait. Paid. Counts toward the 40-hour weekly overtime trigger.
• On-call at home, with restrictions: an IT engineer required to stay within 15 minutes of the office, sober, and answer calls within 5 minutes. The restriction effectively prevents personal use. Likely paid, depending on call frequency and response window.
• On-call at home, free to live normally: a service technician carrying a phone and expected to take one or two calls a week. Free to socialise, sleep, run errands. Not paid for the wait time, only for the actual call response.

Travel between job sites during the workday is paid. The ordinary commute is not. Out-of-town overnight travel during normal working hours is paid, even on weekends. Training time is paid unless it is outside normal hours, voluntary, not directly job-related, and no productive work is performed. All four have to be true.

Four things to get right before your first Arizona hire:

1. Build a state matrix with city overlays. Document each state where you employ someone, plus each Arizona city with a local minimum (Flagstaff and Tucson). Re-check on 1 January each year.
2. Tag each employee’s work location, not the company HQ. The wage-and-hour rule that applies is the rule of the location where the employee physically works. A Delaware-incorporated company with a remote employee in Flagstaff follows the Flagstaff city minimum.
3. Configure final-pay runs for the seven-working-day clock. Most multi-state payroll systems default to next-payday final pay. The Arizona rule needs a discrete flag on each Arizona record to trigger an out-of-cycle run. Configure once, on the first Arizona hire.
4. Set the tip-credit calculation per location. Phoenix, Mesa, Scottsdale, Tempe, and most of the state apply the $3.00 state tip credit (cash wage $11.70). Flagstaff applies a $2.00 city tip credit (cash wage $15.85). Tucson applies a $3.00 city tip credit (cash wage $12.00). Three configurations, not one.

For most early-stage US employers, the practical move is a single national handbook that defaults to the strictest applicable state for any benefit, plus an Arizona addendum. The addendum is short: state the current Arizona minimum with Flagstaff and Tucson overlays, state the $3.00 state tip credit, state the FLSA-only overtime rule, state the seven-working-day final-pay clock, and reference the paid-sick-time accrual under Prop 206. Teamed’s handbook template ships with the matrix pre-built and updates the state and city minimums each 1 January.

What that looks like, day to day:

• Onboarding. Every offer letter runs an exempt-versus-non-exempt screen against the federal $684 salary basis and the duties test. Borderline cases get flagged to your country specialist for a 15-minute call before the offer goes out.
• Time and pay. The platform records workweek, daily hours, on-call entries with an engaged/waiting flag, meal breaks (auto-deducted only when 30 minutes or more), and short paid breaks (auto-included as hours worked). Overtime calculates at 1.5 times the regular rate for every hour over 40 in the workweek.
• Tipped roles. The platform applies the correct tip credit for the employee’s work location: $11.70 cash wage for the state floor, $15.85 for Flagstaff, $12.00 for Tucson. The pay-period make-up runs automatically. Any shortfall against the applicable minimum is added to the next pay run.
• Pay frequency. Bi-weekly payroll is the default for Arizona employees, satisfying the 16-day-max gap. Semi-monthly is supported on request for clients with a US-wide semi-monthly cycle.
• Final-pay runs. A termination event entered into the platform triggers an out-of-cycle final-pay run scheduled inside the statutory window. The payroll specialist confirms the wire date with the client the same day.
• Multi-state employees. The work-location field on each record drives the rules applied. An employee tagged Phoenix follows Arizona rules. The same employee on a four-week assignment in San Francisco follows California rules for those four weeks.

Behind the platform sits a named country specialist for the US, an in-house payroll lead who knows the Arizona Wage Act final-pay mechanics by heart, and a named legal specialist for wage disputes. When something looks off on a timesheet, you message the same person. No support tickets. No chatbot triage.

Contractor onboarding, EOR payroll, and entity graduation all live on one platform. An Arizona contractor who converts to W-2 keeps their record. That same employee can graduate from EOR to your own US entity without changing systems. One timeline. One platform.

Pricing is one number per employee per month, in any currency you pay us in. No FX mark-up. Statutory employer cost (FICA, FUTA, Arizona UI, workers’ comp) passes through itemised on every invoice. No setup fees. No exit fees.

When EOR is the right call (and when it isn’t)

EOR works while you’re testing the Arizona market, ramping a small remote team, or running one or two hires alongside a larger US payroll elsewhere.

Once you have six or more Arizona employees and predictable hiring ahead, the maths of running your own US entity starts to win. Teamed’s Crossover Calculator tells you the month the EOR model stops being right. The conversation is built into the relationship.