Skip forward into hiring notes
RosterAcorn

Sick-leave accrual bases: 2 state rules to set up

Arizona requires at least one hour of paid sick time for every 30 hours worked, and Washington for every 40 hours worked. Both states tie paid sick time to hours worked, but they use different rates, and Arizona adds a yearly limit that depends on how many people the employer has. A record built on the wrong base is off from the first pay period, and fixing it later means going back through timesheets line by line.

Key takeaways

  • Washington requires at least one hour for every 40 hours worked; Arizona requires one hour for every 30.
  • Set the accrual base from the statute for each new hire's state, never from a copied record.
  • Arizona caps yearly accrual and use at 24 hours for employers with fewer than 15 employees, and at 40 hours for those with 15 or more, unless a higher limit is selected.
  • Keep worked time and paid time away on separate earnings codes, and settle the Arizona exclusion question before applying it.

This post explains the two bases in plain terms, quotes the statute text wherever a rule matters, and lists what a hiring manager or small staffing team should put on the record on day one. It is written for the people who set up records, not for lawyers. The linked statute pages are the source for every number here, so read them before you rely on anything in this post.

How does Washington set the accrual base?

Washington sets the base as hours worked, with a floor of one hour of sick leave for every forty hours worked. The state's administrative code says that employees "accrue paid sick leave for all hours worked," and that an employee "must accrue at least one hour of paid sick leave for every forty hours worked as an employee" ( Washington WAC 296-128-620).

Those two sentences do most of the work. The first ties accrual to hours worked, so pay amounts and calendar days do not drive the balance. The second sets the minimum rate. An employer can offer more than the minimum, but the record has to be at least as large as the code requires.

For a new hire, the practical effect is that the balance starts at zero and grows with each hour worked. The count follows the hours themselves. If the first week includes training, orientation, or shadowing, check whether those hours appear as worked hours in your time records, because that is the figure the code measures.

Most small teams already have some timekeeping process, so the real question is whether it produces a worked-hours figure for each employee. A record built from scheduled hours, a flat weekly estimate, or a single pay code that bundles worked and unworked time will not match the hours the code counts. For the timekeeping side, see time clock setup.

Which paid hours count toward Washington accrual?

Only hours worked feed the balance, and the code says paid time away from work does not have to accrue. The rule reads: "Employers are not required to allow employees to accrue paid sick leave for hours paid when not working" ( WAC 296-128-620). The same section gives examples: "employers are not required to allow employees to accrue paid sick leave during vacation, paid time off, or while using paid sick leave."

Read carefully, a Washington record needs to separate two kinds of paid time. Time on the job feeds the balance. Paid time away from the job, including vacation, paid time off, and time spent using paid sick leave itself, does not have to. Those categories often share a single pay line on a payroll report, so check that your earnings codes keep them apart. If they do not, the balance will show accrual on hours the code does not require it to cover.

The code does not require accrual during those periods, which means whether you allow it is a policy decision. If you do allow accrual during paid time off, write that choice down in the policy and mirror it in the record, so a later reader can tell a deliberate policy from a payroll error.

Illustrative example: the same hours in each state

The base changes the balance in a direct way: the same hours produce different totals in each state. Take a hypothetical employee who works 40 hours in a week. At the Washington minimum of one hour for every forty hours worked, that employee accrues one hour of sick leave. At the Arizona rate of one hour for every 30 hours worked, the same 40 hours produces a little more than one hour. Both figures show the minimum rates only.

The example shows why one setup does not work for both states.

Hours that do not divide evenly by 30 or 40 leave fractions, so ask your payroll provider how they are rounded and write the answer into the record's notes.

How does Arizona set the accrual base?

Arizona sets the base as one hour of earned paid sick time for every 30 hours worked. The statute says that employees "shall accrue a minimum of one hour of earned paid sick time for every 30 hours worked" ( Arizona A.R.S. 23-372). That rate appears for both employer sizes, so the accrual rate does not change with headcount.

The Arizona minimum is higher per hour than the Washington minimum, because one hour for every 30 is a larger share than one hour for every 40.

The rate is only part of the Arizona record. The statute also sets a yearly ceiling, and that ceiling depends on employer size. The next section covers it.

How big is the Arizona yearly limit?

The yearly limit depends on whether the employer has fewer than 15 employees or 15 or more. For an employer with fewer than 15 employees, the statute says employees "shall not be entitled to accrue or use more than 24 hours of earned paid sick time per year, unless the employer selects a higher limit." For an employer with 15 or more employees, the statute sets the limit at 40 hours per year, with the same exception for a higher limit the employer selects ( Arizona A.R.S. 23-372).

The limit covers both accrual and use. The statute's wording is "accrue or use," so the record needs to show the ceiling on both sides. Accrual stops growing once the annual limit is reached, and a worker cannot draw more than the limit either.

Do not guess at a borderline headcount. Decide the count using the full statute and your own payroll records, write down the date and reasoning, and revisit it when headcount changes. If the team places workers at client sites, confirm in the full statute whose headcount controls before applying a tier.

If your firm has selected a higher limit, the record should show that choice. The statute allows the higher limit only when the employer selects it, so a record that shows the default 24 or 40 hours while a higher limit is in force will understate the employee's entitlement.

When does an Arizona balance start?

An Arizona balance starts at the later of two dates: the commencement of employment or July 1, 2017. The statute says that earned paid sick time "shall begin to accrue at the commencement of employment or on July 1, 2017, whichever is later" ( Arizona A.R.S. 23-372). Because July 1, 2017 has long passed, the date that controls for a new hire is the start of their employment.

For the record, the accrual start date should be the day employment began. Keep the start date as a fixed field, so it can be checked later against the hire date in your HR system.

How should salaried exempt workers be handled in Arizona?

An exempt salaried employee accrues on an assumed 40-hour week unless the normal work week is shorter. The statute says that employees exempt from overtime under the Fair Labor Standards Act "will be assumed to work 40 hours in each work week for purposes of earned paid sick time accrual unless their normal work week is less than 40 hours, in which case earned paid sick time accrues based upon that normal work week" ( Arizona A.R.S. 23-372).

For an exempt salaried hire, this removes the question of logged hours. The record should show which path applies: the 40-hour assumption, or a shorter normal work week. A shorter week should be the schedule the employee is expected to keep, and it should be written into the offer or the schedule so the accrual can be reproduced later.

Hourly and non-exempt employees are different. For them the 30-hour rate applies to the hours actually worked, so the timekeeping approach from the Washington section applies here too. The two groups can sit in the same record system, but the record should label which method it uses for each person.

Does the Arizona rule exclude paid time away from work?

Do not assume the Washington exclusion carries over to Arizona. Read the full Arizona statute and confirm the answer before applying any exclusion to an Arizona record.

Until someone has read the full text, leave the question open in the record rather than deciding it by habit. A note such as "paid time away: not yet confirmed" is more useful than a silent default, because the next person who reviews the record will know a decision is pending instead of assuming one was made.

What should intake ask before the record is created?

Intake should collect the facts the accrual base depends on: the state where the work is performed, whether the job is exempt from overtime, the usual weekly schedule, and the employer's headcount tier. Without these four facts, the record cannot choose a base or a limit, so the form should not let them stay blank.

The state question comes first. Confirm which state's rule applies to the job, then read that state's statute before choosing a base. Do not fill in the record from memory of another state's rule. For a wider view of state sick-time rules, see Sick time rules for new hires in 4 states.

Exempt status matters for the Arizona exempt-week assumption, but the form should ask it for every hire. A question asked once at intake is far easier than a correction made after the first payroll run.

The usual weekly schedule matters for exempt Arizona staff, since the statute uses the normal work week when it is under 40 hours. Ask for the schedule in hours, not as a label such as "full time," because that label can mean different hours to different people.

For headcount, ask the team to state the count it used and the date it was taken, so the tier in the record can be traced back to a specific figure.

How should a team explain the balance to a new hire?

Give the new hire a short written statement that shows the balance, the accrual base in plain words, and the yearly limit that applies. A statement like that lets the employee check the number without asking, which saves time for a small team and reduces disputes about what was earned.

Write the base in words the employee can follow. "One hour for every 30 hours worked" is clearer than a code. If the balance is zero on the first day, say so, and say when accrual began, so the employee does not expect leave they have not yet earned.

What goes wrong when a record is copied from another hire?

A wrong base often enters a new file through copying, because the copied fields look right until someone checks them against the statute. A team that builds one record and duplicates it for each new hire carries forward the state, the headcount tier, the limit, and the start date of the original employee. Any one of those can be wrong for the next person.

A common copy error is applying an Arizona setup to a Washington hire, or the reverse. The two bases look alike on a form: both say hours worked and both say one hour. Only the divisor differs, 30 for Arizona and 40 for Washington, so a quick glance can miss it.

The headcount tier is the second risk. A record built while the employer had fewer than 15 employees still carries the lower limit after the team grows past that line, unless someone updates it. The start date is the third. Copying a start date from an earlier hire puts the wrong accrual start on the record. Each new hire needs a start date tied to their own employment.

The fix is simple: treat the copied record as a blank form, and require a person to re-enter the state, tier, limit, and start date for every new hire. Make that check a required step on the intake form rather than a suggestion in the training notes.

How do you test a record before the first payroll?

A team should test each record type with a known set of hours before the first real payroll run. Enter a hypothetical week or month of hours, and confirm that the balance matches a hand calculation from the statute's rate. This takes a few minutes and catches the divisor and rounding errors described above.

For a Washington test, use 40 hours: the record should show one hour at the 40-hour minimum. For an Arizona test, use 30 hours: the record should show one hour at the 30-hour rate. If the record shows a different number, stop and check the base field before anything else.

Test the limit as well. Enter enough hours in a test year to reach the cap for the tier, and confirm that accrual stops at 24 hours for an employer with fewer than 15 employees or at 40 hours for one with 15 or more, unless a higher limit is set. A test that stops at the wrong number points to a tier error rather than a math error.

Test an exempt Arizona record separately. Confirm that it follows the 40-hour assumption, or the shorter documented week, and not the hours on a timesheet. Keep a copy of the test in the record's notes so the method can be reproduced later.

How often should a team check the balance?

A team should check the balance against recorded hours each pay period, because that is the cadence that catches a wrong code before it builds up. The check does not need to be elaborate. Compare the accrued total with the hours in the timekeeping system, confirm the earnings codes separate worked time from paid time away, and confirm the limit in use still matches the employer's headcount tier.

When something changes, such as headcount crossing 15, a new higher limit, or a change in how exempt staff are scheduled, write the change into the record with the date it took effect. Changes made without a date are the hardest to explain later.

Where should a team verify the rules before using them?

A team should verify each rule against the statute page before applying it to a record. The two sources this post relies on are the Washington administrative code section and the Arizona statute, and each one is linked where its rule appears above. Read the current text rather than a copy, because a summary can lag behind the source.

Those pages are the starting point for your own review. If a record will be used to make a pay or leave decision, have the people responsible for compliance read the full text and agree on the method. This post does not replace that review.

Next step you can take today

Today, pull one open record for an Arizona or Washington employee and check its state, headcount tier, and accrual base against the statute pages linked above.

Frequently asked questions

Do Arizona and Washington use the same accrual base?

No. Washington requires at least one hour for every 40 hours worked, and Arizona requires at least one hour for every 30 hours worked.

What is the Arizona yearly limit?

For an employer with fewer than 15 employees, the limit is 24 hours per year. For 15 or more, it is 40 hours per year, unless the employer selects a higher limit.

When does an Arizona balance start?

It starts at the later of the start of employment or July 1, 2017, so for a new hire it begins on the first day of employment.

Sources