Tips, overtime, and the payroll data model the 2026 W-2 expects.
Tax year 2026 is the first year employers must report qualified tips and qualified overtime separately. The good news for payroll teams is that the raw material already exists in timecards and pay history. The work is classification, and there is still half a year to get it right.
Thesis
The new boxes ask payroll to classify pay, not just to total it.
Most payroll changes are arithmetic. A rate moves, a threshold shifts, a table is updated, and the pay run absorbs it. The 2026 Form W-2 changes are a different shape. Gross-to-net is untouched, every pay run this year has been correct, and yet the year end needs values that many systems have not been storing.
That is what makes this an unusually tractable problem. Nothing has to be recalculated for the employee, no one has been underpaid or overpaid, and the source data behind the new boxes is the same hours and rates that wage and hour compliance already requires. The task is to define the classification once, apply it to the elapsed part of the year, and let the rest of 2026 flow through the new codes automatically.
What changed, and why operators should care.
Three new box 12 codes
The 2026 Form W-2 adds code TP for the total cash tips reported to the employer, code TT for the total qualified overtime compensation, and code TA for employer contributions under a section 128 Trump account contribution program, effective beginning 4 July 2026.
Each code is a new reporting obligation with a distinct upstream source. TP comes from tip reporting, TT from an overtime calculation, and TA from a benefit plan that may not exist in the payroll system yet.
Box 14 gained structure
Box 14 is now split into box 14a for other information and box 14b for Treasury Tipped Occupation Codes. Box 9 was reduced in size so an additional entry can be input into box 14a.
Occupation stops being an HR attribute and becomes a tax reporting field. That is a meaningful upgrade if the employee record can carry it, and a gap if occupation lives only in a job title string.
Only the FLSA premium qualifies
The IRS defines qualified overtime compensation as overtime required under section 7 of the Fair Labor Standards Act, limited to the portion that exceeds the regular rate. Where an employee is paid time and a half, only the half applies.
This is a calculation, not a relabelling. A payroll system that stores one gross overtime earnings figure cannot produce box 12 code TT without deriving the premium portion from hours and rates.
Reporting became mandatory this year
For tax year 2025, separate reporting was optional and employers could use box 14 or a separate statement. For 2026 and later years, employers are required to report qualified overtime compensation separately, with Forms W-2, 1099-NEC and 1099-MISC updated to carry it.
Tax year 2026 is the first year the data has to exist for every affected employee. The work is capture, not year-end formatting.
Occupation lists are now final
Treasury and the IRS issued final regulations listing the occupations that customarily and regularly receive tips, effective 12 June 2026. The regulations cover more than 70 occupations and add categories such as visual artists, floral designers, and gas pump attendants.
The eligible population is knowable rather than a matter of judgment. Payroll can map its own job catalogue to the published codes and treat unmapped tipped roles as an exception queue.
Withholding is unchanged
The deductions have annual limits, up to 25,000 dollars for qualified tips and up to 12,500 dollars for qualified overtime, 25,000 dollars for joint filers, with phase-outs above 150,000 dollars of modified adjusted gross income, 300,000 dollars joint. They are deductions claimed on the return, not exemptions from withholding.
Gross-to-net does not change, so this can be missed easily. Nothing breaks in the pay run, and the gap only surfaces at year end when the box cannot be populated.
What the IRS and payroll providers are signalling.
Two points come through clearly in public guidance: the eligible occupation list is now settled, and the deductions do not change what comes out of a paycheque during the year.
“Final regulations on the ‘No Tax on Tips’ provision expand the list occupations that may claim the deduction…”
“…Why tips and overtime are still taxed during the year…”
Data Model
Give the premium portion its own identity.
The central design decision is how overtime is represented. Many payroll configurations carry a single overtime earnings code holding the full amount paid at the higher rate. Code TT needs only the part above the regular rate, and only where the overtime was required by section 7 of the Fair Labor Standards Act.
Two employees can therefore receive identical overtime pay and report different qualified amounts, because one was paid under a statutory requirement and the other under a contract or a state rule that goes further. Encoding the statutory basis on the earnings code turns that distinction into data rather than into an annual interpretation exercise.
The same logic applies to tips. Employer-reported cash tips, allocated tips, mandatory service charges, and tip pool distributions are different things, and only some of them belong in code TP.
Earnings code taxonomy
Separate FLSA-required overtime premium from every other kind of premium pay, including contractual overtime above the statutory requirement, state daily overtime, shift differentials, and policy double time.
Evidence to retain
Earnings code, statutory basis, premium multiplier, FLSA section 7 flag, regular-rate components included, effective dates, approver.
Regular rate computation
Retain the inputs to the regular rate, not just the result, since the qualified portion is defined against it and non-discretionary bonuses can move it retroactively.
Evidence to retain
Workweek, hours worked, base rate, included bonus amounts, recalculated regular rate, premium portion, calculation version, run timestamp.
Tip reporting record
Keep employer-reported cash tips distinct from charged tips, tip-outs, service charges, and pooled distributions, because only some of these reach code TP.
Evidence to retain
Employee ID, pay period, cash tips reported, allocated tips, service charges excluded, pool distribution ID, reporting statement reference.
Occupation assignment
Model occupation as a time-sliced attribute mapped to the published Treasury Tipped Occupation Codes, so an employee who changes role mid-year carries the correct code for each period.
Evidence to retain
Employee ID, occupation code, SOC mapping, effective from, effective to, source of assignment, reviewer, unmapped exception flag.
Trump account contributions
Register the section 128 contribution programme as a distinct employer-paid benefit with its own eligibility and accumulator, rather than folding it into an existing plan code.
Evidence to retain
Programme ID, employee or dependent beneficiary, contribution amount, contribution date, plan reference, effective date on or after 4 July 2026.
Year-end evidence packet
Generate the tie-out from source records so each reported box amount can be traced to the pay periods, hours, and rules that produced it.
Evidence to retain
Box code, reported total, contributing pay runs, calculation version, variance to prior method, preparer, reviewer, auditor export reference.
Put the control where the classification is decided.
A reported box amount is an assertion to a tax authority about an employee. It deserves the same traceability as a journal entry: which pay runs contributed, which rule classified them, which version of the calculation was used, and who reviewed it.
This is also where the mid-year timing helps. A classification method validated in July against a live sample can be corrected quietly. The same method discovered to be wrong in February 2027 means corrected W-2s, employee communications, and amended individual returns for people who have already filed.
The wider benefit is that this data is useful beyond the form. Once the premium portion of overtime is a first-class value, labour cost analysis, scheduling decisions, and overtime budgeting all get a cleaner input than a blended earnings total.
Implementation checklist
1. Confirm what the current year already holds
Tax year 2026 is over half elapsed. Check whether the FLSA premium portion has been separately stored since January, or whether only gross overtime earnings exist. This single answer decides the size of the work.
2. Derive the premium portion from raw inputs
Hours, rates, and workweeks are already retained for wage and hour compliance. That is enough to recompute the qualified portion for elapsed periods without asking anyone to re-enter data.
3. Split the earnings codes properly
Give FLSA-required premium its own earnings code so future pay runs classify at the source. Blended codes force a derivation every year rather than once.
4. Map the job catalogue to occupation codes
Match internal job codes to the published Treasury Tipped Occupation Codes, record the mapping with an owner, and treat every unmapped tipped role as an open item rather than a default.
5. Validate against a sample before December
Take a representative set of employees across roles and pay patterns, compute the box amounts now, and have payroll and tax review them while there is still time to change the method.
6. Publish the reconciliation early
Produce a tie-out from pay records to reported box totals as a standing report, not a January project, so any classification gap surfaces while it is still cheap to fix.
Constructive failure modes to design around.
Gross overtime is treated as qualified overtime
Report only the FLSA section 7 premium above the regular rate. Storing the multiplier and statutory basis on the earnings code makes the correct figure a query rather than a year-end reconstruction.
Occupation lives only in a job title
Promote occupation to a coded, time-sliced field mapped to the Treasury list. Free-text titles cannot be validated and cannot populate box 14b reliably.
Retroactive rate changes are missed
Non-discretionary bonuses can change the regular rate for periods already paid. Keep the regular-rate inputs so the premium can be recomputed rather than estimated.
Service charges are reported as tips
Keep mandatory service charges separate from cash tips reported by the employee. They follow different rules and only one of them belongs in code TP.
The new benefit code is added late
Set up the section 128 contribution programme as its own accumulator before contributions begin, so code TA has a clean source from the first payment.
Everything is left to the year-end vendor file
Payroll providers will supply the boxes, but the classification decisions are the employer’s. Validating the method mid-year is far cheaper than correcting W-2s after issuance.
API and event-design considerations.
A payroll classification workflow should expose events such as workweek.closed, regular_rate.computed, overtime.classified, tips.reported, occupation.assigned, retro.recomputed, and w2_box.populated.
Each event should carry employee, workweek, earnings code, statutory basis, calculation version, actor, timestamp, and idempotency key. Retroactive recomputation is the case worth designing for explicitly, because a non-discretionary bonus paid in November can change the regular rate for workweeks settled months earlier.
The output is a small sub-ledger of classification decisions sitting alongside payroll results, which is what makes the year-end tie-out a report rather than a project.
Example W-2 evidence payload
{
"w2_evidence_id": "w2_2026_emp_00418",
"employee": {
"employee_id": "emp_00418",
"occupation_periods": [
{ "ttoc": "101", "soc": "35-3031", "from": "2026-01-01", "to": "2026-05-31" },
{ "ttoc": "112", "soc": "35-1012", "from": "2026-06-01", "to": "2026-12-31" }
]
},
"box_12": {
"TP": { "amount": "8420.00", "source": "employee_reported_cash_tips" },
"TT": { "amount": "1935.50", "source": "flsa_s7_premium_portion" },
"TA": { "amount": "1000.00", "programme_id": "s128_prog_2026_01" }
},
"box_14b": { "treasury_tipped_occupation_codes": ["101", "112"] },
"overtime_derivation": {
"method": "regular_rate_recompute_v3",
"workweeks_included": 27,
"gross_overtime_paid": "5806.50",
"regular_rate_portion": "3871.00",
"qualified_premium": "1935.50",
"retro_bonus_adjustments": 2
},
"controls": {
"sampled_for_review": true,
"reviewer": "payroll_tax_manager",
"reviewed_on": "2026-07-15",
"auditor_packet_ready": true
}
}Questions CFOs and controllers should ask payroll and ERP vendors.
Practical Takeaway
A classification project with a friendly deadline.
The near-term work is well bounded: confirm what the year already holds, derive the premium portion from hours and rates, split the earnings codes, map the job catalogue to the published occupation codes, and validate a sample before the autumn close cycle. None of it requires a system replacement, and all of it is easier in July than in January.
For ERP and payroll buyers, this is a clean architecture test. A platform that treats earnings classification, occupation, and regular-rate inputs as structured data will absorb the next statutory reporting change as configuration. One that stores blended totals will need a derivation project every time a new box appears.
Sources
- IRS: General Instructions for Forms W-2 and W-3 (2026)
- IRS: Questions and answers about the new deduction for qualified overtime compensation
- IRS: Treasury and IRS issue final regulations listing occupations where workers customarily and regularly receive tips
- IRS: Occupations that customarily and regularly received tips on or before Dec. 31, 2024
- IRS: One, Big, Beautiful Bill, how to take advantage of no tax on tips and overtime
- IRS: Notice 2025-69, guidance for individual taxpayers who received qualified tips or qualified overtime
- IRS: Internal Revenue Bulletin 2026-18
- PayrollOrg: IRS releases 2026 Form W-2 with changes due to OBBBA