Full-time hour thresholds: 2 checks for monthly review

Key takeaways

• Total hours of service by calendar month, rather than by pay run.
• Document the measurement method used for each worker.
• Keep part-time workers' hours for the separate ALE calculation.
• Save monthly totals and explain corrections.

If you manage a team paid by the hour, you probably already track hours. Timesheets, shift schedules, and payroll reports show how much each person worked. What many managers do not track is whether each worker crossed a line that matters for benefits and tax reporting. For employers covered by the Affordable Care Act, that line is full-time status, and the Internal Revenue Service (IRS) gives two hour thresholds to decide it.

This post explains those thresholds, how to count them for each calendar month, and how to set up a simple routine so you are not guessing at year end. It is not tax advice. For a specific situation, talk with your payroll provider or a qualified tax professional.

Why full-time status matters

Full-time status affects how an employer meets its obligations under the Affordable Care Act. The IRS puts it plainly: "Determining which employees are full-time employees is central to the employer shared responsibility provisions." If the count is wrong, the rest of your reporting can be wrong too.

The IRS definition uses hours of service, so check that your records capture those hours rather than scheduled shifts alone.

The first habit to build is simple. Stop asking "Is this person full-time?" once a year, and start asking "Did this person reach full-time status in this month?" every month.

The two thresholds

The IRS gives two numbers. Here is the full definition from its page on identifying full-time employees:

> "For purposes of the employer shared responsibility provisions, a full-time employee is, for a calendar month, an employee employed on average at least 30 hours of service per week, or 130 hours of service per month."

Source: Identifying full-time employees | Internal Revenue Service

The weekly threshold is an average, not a minimum for every week. Confirm the applicable measurement period before calculating it.

For a monthly review, add up hours of service for the full calendar month. Keep the calculation with the underlying records so another reviewer can follow it.

Notice the phrase "hours of service." The IRS uses that term instead of "hours worked." If your timekeeping system records paid time off, training, or other non-shift time differently, confirm how those hours fit the definition. Check the IRS page for the exact rules, and write your internal definitions to match. Everyone should work from the same definition. Review your time off settings alongside those definitions.

Count by calendar month, not by pay period

Most people think in pay periods. Payroll may run every two weeks, or on the fifteenth and last day of the month. The IRS test does not use your pay schedule. It uses the calendar month.

That difference causes real errors. If a pay period runs from late in one month into the next, a worker's hours for one calendar month are split across two pay runs, and neither run shows the full monthly total. Checking only the paycheck can lead you to count the wrong month.

Here is a method that avoids the problem:

1. Export time records by calendar date, from the first day of the month to the last.
2. Add up each worker's hours of service for that month.
3. Compare the total to 130.
4. Record the result for that worker and month in a separate tracking sheet, not in the payroll report.

If your system tracks shifts rather than daily totals, convert shifts to hours before adding them. A shift that runs past midnight can fall into two calendar days, and that choice can change which month it lands in. Confirm the applicable allocation rules before documenting how to handle overnight shifts.

Use the weekly average when it helps

A weekly view can help you review changing schedules, but calculate the average using the applicable measurement period.

Consider a worker with irregular schedules. One week is heavy, and the next is light. Looking at each week separately makes that swing look dramatic. Looking at the average across the stretch shows whether the worker is, on average, close to the 30-hour mark.

Keep the weekly figures in your records, so you can show how an average was calculated if someone's status is questioned later.

Track each month, not each year

It is tempting to review hours once a year and assume the results will be clear. They usually are not. Hours change with seasons, promotions, leaves, and business needs. Under a monthly measurement method, a worker's status may change during busy months; the look-back method works differently, as explained below.

A monthly record shows the pattern as it develops, rather than leaving you to discover it in a rush at year end. Set a recurring reminder for shortly after each month closes, while the details are still fresh. Assign one person to own the review, and have a second person check a sample of records each quarter.

The look-back measurement method

The IRS allows a different approach, called the look-back measurement method. The IRS describes it like this:

> "Under the look-back measurement method, an employer may determine the status of an employee as a full-time employee during what is referred to as the stability period, based upon the hours of service of the employee in the preceding period, which is referred to as the measurement period."

In plain terms, the employer looks back at hours in one period, the measurement period, and uses that record to set status for a later period, the stability period. Status can stay fixed for a stretch of time instead of changing each month.

This method can ease administration, especially for employers with many variable-hour workers, but it has its own rules. Read the IRS page carefully before using it, and do not assume a method that works for one group of workers will work for another.

There is one important limit. The IRS says: "The look-back measurement method may not be used to determine full-time employee status for purposes of ALE status determination." Source: Identifying full-time employees | Internal Revenue Service

ALE stands for applicable large employer. Whether a business is an ALE is a separate question with its own counting method, so keep the two questions apart in your records and your process.

Full-time status is different from ALE status

Managers often mix up two ideas: whether a worker is full-time, and whether the employer is an applicable large employer. They are related but not the same.

Full-time status is decided worker by worker, using the hour thresholds above. ALE status is decided for the employer as a whole, based on its workforce size. The IRS page on determining ALE status says that if an employer "has fewer than 50 full-time employees, including full-time equivalent employees, on average during the prior year, the employer is not an ALE for the current calendar year." Source: Determining if an employer is an applicable large employer | Internal Revenue Service

The workforce size test depends on monthly counts. To find it, the IRS says an employer "adds its total number of full-time employees for each month of the prior calendar year to the total number of full-time equivalent employees for each calendar month of the prior calendar year and divides that total number by 12." Source: Determining if an employer is an applicable large employer | Internal Revenue Service

This is why monthly tracking pays off twice. The same records that show who is full-time in a given month also feed the workforce size calculation. If monthly totals are missing at year end, reconstruct them from existing time records before calculating workforce size.

What full-time equivalent means

The ALE test uses full-time equivalent employees, a separate measure from the full-time count. The IRS example describes an employer with 15 part-time employees, each logging 60 hours of service per month during 2018. Those workers do not reach the 130-hour full-time threshold, yet they still count toward the full-time equivalent figure, which the example puts at 7.5 for each month.

For a manager, the lesson is that part-time workers are not invisible in the ALE count. Record their hours every month, not just the hours of workers who cross the full-time line.

The full-time equivalent calculation is the one most likely to confuse people. Write down how your company does it and keep the worksheet with your records. If you are unsure, ask your tax advisor to review the method once a year.

A worked example from the IRS

The IRS example shows how the monthly figures add up. It totals the full-time employees for each month of 2018 to reach 480 for the year, which is 40 employees multiplied by 12 months. It then totals the full-time equivalent employees for each month, which comes to 90 for the year, or 7.5 multiplied by 12.

Each month produces one number. The yearly totals are sums of twelve monthly figures, and the workforce size is the combined total divided by 12. A business that tracks every month has every input it needs at year end.

Illustrative example: a monthly hours check

An illustrative worker has 60 hours of service in one part of a calendar month and 90 in the rest. Add both amounts before comparing the monthly total with the threshold. Keep the dated records together even if the hours appear in separate pay runs.

Set up a monthly tracker

You do not need expensive software to track full-time status. A spreadsheet with a few columns works for many teams. Include these columns:

• Employee ID. Use a consistent identifier so you can match records across months.
• Month. Use the calendar month, with the first and last dates written clearly.
• Hours of service for the month. Total the hours for the full calendar month, using your written definition.
• Full-time monthly test. Mark yes or no, based on whether the total meets 130 hours.
• Weekly average, if needed. Add this for the applicable measurement period.
• Notes. Record leaves, schedule changes, corrections, or anything that explains an unusual number.

Add a summary tab that counts full-time and part-time workers for each month. This gives you the monthly figures that feed the ALE calculation and helps you spot trends quickly.

Limit editing rights to the people who need them, and keep a copy of each month's version when you close it. If a record changes after the month is closed, note the reason and the date of the change. These are the details people ask about later. Use timesheet approval and edit rules to review your correction process.

Common mistakes to avoid

Several errors come up often when managers track full-time status.

Counting scheduled hours instead of hours of service. Use records that capture hours of service and reconcile any gaps.

Using pay periods instead of calendar months. Pay periods often cut across months. Pull the monthly total from dates, not from pay runs.

Forgetting part-time workers in the ALE count. Full-time equivalent employees are part of the workforce size calculation. Leaving them out understates the total.

Mixing methods without a plan. If you use the look-back measurement method for some workers, document which workers use it, which periods apply, and when status changes. Do not switch between methods informally.

Waiting until year end. Review records monthly so you can fix errors while the details are still clear.

Ignoring corrections. Someone forgets to clock out, a supervisor adjusts a shift, or a leave is recorded late. When you correct a record, update the monthly total and note what changed. A silent change is hard to defend later.

A quick checklist for each month

Use this checklist after each calendar month closes:

1. Confirm that time records for the full calendar month are complete.
2. Export hours of service by calendar date, not by pay period.
3. Total each worker's hours for the month.
4. Mark each worker as full-time or not, using the 130-hour monthly threshold.
5. If using a weekly average, confirm the measurement period and keep the calculation.
6. Update the summary count of full-time and part-time workers.
7. Record any corrections, leaves, or schedule changes in the notes column.
8. Save a copy of the closed month, and have a second person spot-check a sample.

Keep records you can explain

Questions about a worker's status can come up long after the month has closed. Your records should answer them without a scramble. Keep the time data, the monthly totals, the method you used, and the reasons for any unusual results.

Write down your definitions. What counts as hours of service in your company? How do you treat overnight shifts, paid leave, and training? How do you assign hours to a calendar month? A short written policy makes it easier to train new managers and to show that your process is consistent.

Review your method once a year with your tax professional. Rules and interpretations can change, and a short annual review helps you catch problems before they grow.

Start your monthly review today

Export the last closed calendar month's dated time records, total hours of service for each worker, and save the totals with any corrections explained.

Common questions

Can I use pay-period totals?

Use calendar-month totals for the monthly test. If a pay period crosses a month boundary, separate the hours by calendar date before adding them.

Do part-time workers matter for ALE status?

Yes, their hours contribute to the full-time equivalent calculation. Keep their records alongside those of full-time workers.

Does the look-back method determine ALE status?

No, the look-back method cannot determine full-time employee status for ALE status determination. Keep that calculation separate from employee status during a stability period.