Paystub Doesn't Match Your Salary? Here's Why

Last updated: November 11, 2026 · WageYard Editorial · Estimates, not tax or legal advice

You accepted a $60,000 salary, divided by twelve got $5,000 a month — and the actual deposit says something like $2,308 or $1,529, and it changes month to month. Almost every salaried worker has done this double-take, and in the overwhelming majority of cases the payroll system is right and the mental model is wrong: salary is an annual contract number; a paystub is a snapshot after deductions, on a calendar that isn't 12 months long. Five things explain nearly every mismatch — pre-tax deductions, partial pay periods, unpaid-leave proration, the 26-vs-24 pay calendar, and (rarely, but worth ruling out) outright misclassification. Here's the five-minute audit, in the order errors usually appear.

First, three numbers that are not the same number

Half of the confusion is vocabulary. Three figures ride on every stub:

Your offer letter quotes the first family of numbers; your bank account only ever sees the last. The salary pages on this site publish the gross per-check figure for 19 common salaries — for example $50,000 is $1,923.08 gross per biweekly check before any deduction — and the pay calculator runs your own. If the gross on your stub already disagrees with salary ÷ pay periods, keep reading; that's where the real errors live. If gross matches and net looks small, you're in deduction territory, which is reason one.

Reason 1: pre-tax deductions shrink the stub before taxes ever see it

401(k) contributions, health/dental/vision premiums, HSA and FSA payroll contributions, and commuter benefits all come out before taxable wages are computed. They don't reduce your salary — raises and bonuses still compute off the full figure — but they absolutely reduce the taxable line and the deposit. Worked example, $60,000 salary on 26 pay periods:

Notice the sneaky bonus: because FICA applies to taxable wages, pre-tax deductions lower your payroll tax too — that's the same mechanism the IRS deduction and credit rules are built around. The check "should" be bigger, and it is — $365.38 of it went somewhere real (retirement, insurance, HSA), it just didn't land in checking. Rebuild this table for your actual elections with the after-tax calculator.

Reason 2: partial pay periods — first and last checks

Most payroll runs in arrears with a lag: you work one period, get paid a cycle or two later. Start a job on a Wednesday in the middle of a pay period and your first check covers only the days between your start date and the period end — sometimes four days' worth — while the stub for your full first period arrives later still. The same bookend happens on the way out: a final check prorates your last days plus any accrued PTO payout, and it frequently looks strange because taxes on final pay are often withheld at flat supplemental rates. Rule of thumb: one small stub at each end of employment is normal payroll plumbing; two consecutive small full-period checks is a ticket for payroll.

Reason 3: unpaid leave gets prorated against the period

Salary assumes you worked the whole period. Unpaid FMLA leave, personal days beyond your PTO balance, or a disciplinary suspension without pay get deducted as a daily rate — typically the period's salary ÷ working days in that period. That proration is per-period, so a single unpaid week inside a biweekly check wipes out roughly half the check, which reads like a payroll error and usually isn't. Paid leave, by contrast, should show as hours at full rate. If the deduction days don't match the days you were actually out, that's the question for payroll — bring the calendar.

Reason 4: your pay calendar isn't twelve months long

"Per month" is an abstraction payroll never uses. If you're paid 26 times a year, gross per check is salary ÷ 26 — $2,307.69 at $60,000 — and two checks sum to $4,615.38, not the $5,000 a ÷12 brain expects. If you're semimonthly (24), it's exactly $2,500. Same salary, two stubs that disagree with each other. The mismatch compounds in months with three paydays. This one has a full guide: how to budget 26 paychecks walks the calendar month by month, with a 2026 payday table.

Reason 5: "salaried" but actually hourly — the misclassification check

Here's the reason with teeth. "Exempt" is not a synonym for salaried: under the FLSA, exempt status requires genuinely executive, administrative, or professional duties and the salary threshold, and plenty of roles that wear the title fail the duties test. If you should be non-exempt, the law treats you as an hourly employee — which retroactively converts your stubs into hourly math and can mean owed overtime on every hour past 40. The mismatch signs: your "salary" visibly dips when you work short weeks, your employer logs your hours and disciplines lateness, or your take-home tracks a timesheet. The rules live at the DOL Wage and Hour Division; what you'd be owed as an hourly worker is on the rate pages — e.g. the same $60,000 at 2,080 hours is a $30/hour job with time-and-a-half at $45, which our overtime guide shows how to compute. If that's your situation, keep a private hours log before any conversation with payroll or a lawyer.

Why your W-2 doesn't match your salary (and your paystub)

Same confusion, annual scale — and it's the search that lands a lot of people here: your last paystub doesn't match your W-2. They were never measuring the same thing. Your salary is an annual promise; the paystub is one period's gross after period-specific events; the W-2 is a tax-year tally with its own arithmetic. Box 1 (wages, tips, other compensation) is what's left after pre-tax deductions — 401(k) contributions, health premiums, HSA, transit — come off every check first, so a $60,000 salary commonly reports as $55,000-ish in Box 1 even when every stub was correct. Box 16 (state wages) usually doesn't match Box 1 either, because some states don't honor certain federal pre-tax breaks. Then stack the period-level events from above: a partial first or last check (reason 2) shifts one stub without shifting the year, a January-dated December check may belong to the other W-2 (constructive receipt — the check you actually received before Dec 31 counts in that year, which is why "only 25 checks on this year's stubs, 26 on the W-2" happens), and mid-year benefit changes reprice gross without touching salary. The reconciliation that actually works: add up period-1 gross through period-26 gross from your final stubs for the calendar year (payroll portals export it), then compare that to Box 1 after subtracting the year's total pre-tax deferrals — not your last stub or your last month to a W-2 box. If gross-sum matches salary but Box 1 doesn't, the difference is pre-tax deductions doing their job; if the gross-sum itself is off, that's a payroll ticket, and the 26-paycheck guide shows how check counts can hide in the math.

The five-minute audit

1. Find the pay frequency on the stub or portal: 24 or 26 periods? Confirm with salary ÷ periods and compare to gross, not net.
2. Sum YTD, don't eyeball one stub. Annualizing one weird check is how 80% of false alarms start; YTD gross ÷ checks paid should equal salary ÷ periods.
3. List every pre-tax deduction — 401(k) %, premium costs, HSA — and check they match your open-enrollment elections.
4. Flag period-length events: start date, end date, unpaid leave, jury duty, unpaid FMLA — each prorates the period it lands in.
5. Only then consider errors: a stale W-4, a mid-year benefit change, or a retroactive premium catch-up are the classic payroll-confirmed mistakes. Misclassification (reason 5) is the last box, not the first.

FAQ

Rebuild your per-check numbers in the calculator

Sources & notes

• U.S. Department of Labor — Wage and Hour Division: FLSA exempt/non-exempt criteria and overtime rules behind the misclassification check in reason five.
• IRS — Credits and Deductions: the treatment of pre-tax retirement and health contributions and the deduction framework the worked stub example follows.

Last verified November 11, 2026.