Sense with Cents

One paycheck. One gross pay figure. Several different answers to “how much did you earn?”

Every pay stub has a gross pay line, and it looks like the answer. It is really the starting point for a series of questions, because the word “wages” does not mean the same thing to every law that uses it.

I have spent about 40 years turning payroll rules into code. Early on, I did payroll with a pen and the government booklets, for small businesses with no retirement plan or other benefits. For those businesses, gross pay was the only wages figure I needed. And like those of us who once withheld FICA as a single combined rate for Social Security and Medicare, I leaned into that as enough, not really separating the two items. It was a simple case, and simple was enough.

Why the definitions differ

Payroll rules are not written by one group, at one time, for one purpose. Congress, the IRS, state legislatures, tax agencies, unemployment and paid leave programs, workers’ comp rating bureaus, and local tax offices all write rules that touch the same paycheck. Nobody keeps a shared glossary. And it has been decades since anyone could count on the rules staying the same for an entire payroll year.

I have coded a federal rate that changed on July 1. I also watched a Social Security deferral arrive that was optional, started in September, and had its payback rules rewritten after the fact. We acknowledged that one but did not build it into the software, since we judged few customers would use it.

Purpose shapes each definition. Income tax measures income and uses exclusions to encourage things like retirement saving. Social Security and Medicare measure earnings that build future benefits. Unemployment insurance measures what a laid-off worker stands to lose. Workers’ comp uses payroll as a rough stand-in for risk.

Timing matters too. A law written before a benefit existed cannot mention it. When 401(k) and cafeteria plans came along (both with the Revenue Act of 1978), each older law was updated on its own schedule, or not at all. Some definitions still read like they were written for cash in an envelope, because they were.

The irony is that the most common term, “gross wages,” has no common definition. It appears on agency websites and forms, often where the law says something narrower. The word the federal laws build on is “remuneration.” Federal income tax, Social Security, and unemployment each start with all remuneration for employment, then subtract their own exceptions. Remuneration is the closest thing payroll has to a shared starting point. Everything after that is local variation.

From law text to paycheck

To be candid, many rules start as a policy goal, not a payroll design. Some newer programs, like the state-run retirement savings plans spreading from state to state, are designed and run with private firms under contract. Agency staff are then left to work out what the law text means for an actual paycheck, and guidance arrives in stages: a web page, an FAQ, a revised FAQ. Payroll developers, me included, start from the law text and adjust as the details catch up. The state workers doing that translation are usually doing their best with what they were handed.

Sometimes the guidance lags behind the law. Not long ago, one state widened which wages counted for one of its newer programs. Same rate, bigger base. For anyone with pre-tax benefits, that is a premium increase, whatever it is called, though benefits are figured on the bigger base too.

The trouble was that the agency’s own website kept the old rule, and for a while even a written opinion from the agency repeated it. Employers who followed the official source collected too little. I did not catch the change right away either. It came up in a professional group I participate in, which is one reason I stay in those groups.

It is not just wages

Overtime has the same problem, and it has it twice.

Who gets overtime. An employee can be exempt from overtime under federal rules and still be hourly under a state rule with a higher salary threshold or a stricter duties test. It works the other way too. An employer may pay overtime by union contract or company policy to someone the federal law treats as exempt from overtime. The pay stub says “OT” either way.

How much counts as overtime. Federal law looks at hours over 40 in a workweek. Some states add daily overtime and double time. Union contracts can add their own rules on top.

A recent federal change added one more meaning. For the federal overtime deduction, the W-2 reports only the premium the federal law requires, usually the “half” in time and a half. State-only overtime and contract overtime do not automatically count, and neither does overtime paid to workers the federal law does not cover, as I wrote about in FLSA OT (QOC) and Agricultural Employees.

Picture a worker in a daily-overtime state who works 10 hours on Monday and 30 hours for the week. The state says two hours of overtime. Federal law says none, since the week stayed under 40. For the W-2 figure, the answer is also none. One time card, three answers, and all three are correct.

Where it shows up

The most common place is the W-2. An employee adds up the year’s gross pay, compares it to Box 1, and writes to report an error. In my experience, most of those W-2s were right. Box 1 and Box 3 were disagreeing on purpose. (Health insurance for S-Corp shareholders is another reliable source of those emails.) That is not a complaint. We welcome the questions, including the ones that question us. More than once, a customer has pointed out something that made us think, or rethink a decision we made.

It also shows up in audits, when a deduction was treated one way for one tax and should have been treated another way for a different one. And it shows up in benefits. Unemployment, disability, and paid leave benefits can be figured on a wage base the worker never sees as a single line anywhere. One state’s paid leave program shows how much that can matter.

What the software does, and what it does not

Payroll software earns its keep here. Behind the single gross pay line, it tracks a separate base for each tax and deduction, and it keeps those bases straight every pay period. When a rule changes mid-year, the software has to change with it. Keeping up with those rules is a large part of what I do for a living, and I would not wish the hand-calculated version on anyone.

The software keeps several sets of books so you do not have to. You just need to know there are several.

What software does not do is decide which rulebook covers which employee. Whether someone is exempt from overtime, what a union contract says, which state an employee works in: those are human calls, and sometimes calls worth running past an advisor. The software applies the answer. It does not pick it.

The takeaway

When a rule, a form, or an agency website says “wages” or “overtime,” what I do is ask one question first: whose definition? Which law, which section, and as of when?

A modest understanding goes a long way. You do not need to memorize every base. Knowing they differ is enough to turn “the W-2 is wrong” into “which box am I looking at?”

Gross pay is a fine number. It just is not the answer to most of the questions payroll asks.