Questions

The questions Truing is asked, with the answers it already publishes.

Is code TT just the total overtime pay?

No — and this is the error that costs the most to unwind. Box 12 code TT carries the compensation exceeding the regular rate: the half in time-and-a-half, not the whole overtime line. On a register paying $30 an hour with ten overtime hours, code TT is the $150 premium, not the $450 gross. Reporting the total overstates the figure roughly threefold.

Isn't the regular rate the base hourly rate?

Only when nothing else was paid. Non-discretionary bonuses, shift differentials and commissions fold into the regular rate under FLSA section 7, which raises the premium owed. A register that paid overtime at 1.5× base while a production bonus was running has underpaid — a wage-and-hour exposure sitting underneath the reporting one.

Didn't our payroll platform already fix this?

Going forward, yes. The major platforms added the qualified overtime and tip fields in late 2025 and early 2026, so payroll run from that point separates cleanly. None of them go back and reclassify the months already run — those periods were recorded without the split, and rebuilding them is a reconstruction off the register rather than a setting.

Who signs the workpaper?

Your preparer does. Truing produces the computation, the per-employee workbook and a method memo setting out every rule applied and the primary source behind it, so the person whose name goes on the return can review the method and stand behind it. We do not file, and we are not your preparer of record.

What if the register can't support an employee?

Then that employee is named, not estimated. Every engagement ships an exceptions report listing each employee the data cannot carry and the specific reason — a missing hours column, tips not split from mandatory service charges, an occupation with no Treasury code. If more than a fifth of the book lands there we stop and ask for a better export, rather than deliver a workbook that is mostly gaps.

These answers are derived from src/components/faq-schema.json, which is what this site already renders as its structured data, so the answer here and the answer a search engine reads cannot differ.