K-12 Has Three Overtime Definitions. The W-2 Wants Only One.

Starting with the 2026 tax year, every public school district must report the federal overtime premium for each non-exempt employee in W-2 Box 12 under code TT. Code TT is the new W-2 designation for qualified overtime compensation, which the IRS defines as the 0.5 portion of FLSA time-and-a-half pay. The reasonable-estimate grace period that applied to 2025 under IRS Notice 2025-62 is over. The exact number is now required.

For most private-sector employers, this is manageable math. For K-12 districts, it almost never is.

Which Overtime Hours Count for W-2 Box 12 Code TT?

K-12 districts don't operate under a single overtime framework. They operate under three at the same time. Each one has its own trigger, and only one of them counts for federal reporting:

Federal FLSA overtime triggers at 40 hours of actual time worked in a 7-day work week. This is the only category that belongs in Box 12.

State overtime adds a second layer that varies by state. California, for example, counts overtime after 8 hours worked in a day, which means an employee can trigger state overtime without approaching the 40-hour federal threshold. State overtime does not belong in Box 12.

District and union policy overtime adds a third layer of holiday premiums, event pay, and agreed-upon differentials. These function like overtime but aren't tied to the federal definition. District-policy overtime does not belong in Box 12.

As Natalie Rhodes, District Success Partner at Informed K12, described it: "It's harder than it looks because of the unique environment that district employees work in. There are many different overlapping definitions of overtime that rarely align, and now you and your payroll teams are going to have to isolate what number actually makes for that kind of federal deduction."

The challenge isn't just separating FLSA from "blended overtime." It's separating federal from state from district-policy, when all three can show up in the same week for the same employee. "Your ERP very often only blends overtime into a single bucket," Rhodes explained. "It's not telling you, was that state overtime, was that district policy overtime? And it's not able to get me the actual number of what is the federal overtime that should be reported to taxes."

That three-way separation is what has to be untangled before the first W-2s go out.

What Else Affects the Federal Overtime Calculation?

Two factors complicate the federal number further.

The first is multiple roles at different pay rates. An employee who works as a paraeducator at one rate and a coach at another has a "regular rate" for FLSA purposes that's a weighted average of all earnings that week, not the hourly rate of the specific job where overtime hours were logged. Most ERPs don't compute that weighted rate automatically across job codes.

The second is absence reconciliation. The 40-hour threshold reflects actual time worked, so paid leave that lives in a separate HR system has to be reconciled against timesheet data each week to confirm whether the FLSA threshold was actually crossed.

Your Pay Period Probably Doesn't Match the FLSA Work Week

FLSA overtime is calculated on a 7-day cycle. Most district pay periods are bi-weekly or semi-monthly, which means the federal calculation has to run week by week, not pay period by pay period. If your payroll team is reviewing overtime on the same cadence as your pay run, they aren't seeing the federal premium accurately.

Districts in states like Washington, where state overtime mirrors the federal 40-hour-per-week standard, have a structural advantage. Their timesheet cycles already align with the FLSA work week. Every other district has to build the weekly view themselves before December.

Where Districts Are Starting

When polled on how they currently track actual hours for non-exempt employees, attendees at a recent Informed K12 session reported a wide range: digital timesheets, paper and spreadsheet-based timesheets, and mixed approaches that vary by employee group or department. That variation matters because, as Rhodes noted, "where you are in this stage impacts what you can do next."

Districts that are restructuring their processes are taking two primary approaches.

The first is pay code specificity. That means creating separate codes for each of the three overtime definitions, so federal, state, and district-policy overtime each have their own line. With that separation in place, payroll staff can pull the qualifying federal premium with a filter rather than reconstructing every overtime record at year-end.

The second is data export quality. Districts that can't restructure their timesheet systems before the 2026 filing deadline are building toward weekly exports in clean, usable formats like Excel, CSV, or via API. That way payroll teams can run the analysis periodically rather than all at once in December. Some are adding an absence column directly to the timesheet form so the 40-hour calculation reflects time-off data without requiring a separate lookup.

Preeti Nalavade, VP of Solutions and Strategy at Informed K12, noted that most payroll teams prefer to keep human review in the loop regardless of how automated the data flow becomes: "Having that extra human set of eyes on the data before it gets uploaded is something that we hear a lot of payroll teams prefer. Payroll is very critical, important information that needs to be accurate before folks get paid."

What to Do Before December

Three actions districts can take before filing season arrives:

Set up pay codes that distinguish all three overtime definitions. A single FLSA-vs-other split isn't enough when state-triggered and district-policy overtime can both appear in the same week. Federal, state, and district-policy each need their own code.

Add absence reconciliation to your weekly overtime review. Whether that means a column on existing timesheets or a cross-reference against your leave system, the 40-hour calculation is only accurate if it reflects actual time worked.

Set a reporting cadence now. Monthly or quarterly review of Box 12 totals is more manageable than an end-of-year audit. Building that into your payroll calendar before summer ends is easier than retrofitting it in October.

None of this requires replacing your ERP or overhauling your payroll system. It requires knowing where your data lives, what format it's in, and what calculation your payroll team needs to run each week.

Not sure where your district stands? Take the Overtime Readiness Assessment for quick check on your current processes and what gaps you might have.


Please note: This information is for educational purposes and should not be construed as legal, financial, or tax advice. Consult your county office of education and legal counsel for compliance guidance or consult a qualified professional for advice specific to your situation.