Common Pay Stub Mistakes to Check Before Downloading

The mistakes most likely to slip onto a pay stub are wrong period or pay dates, rate or hours typos, duplicated or missing deductions, net pay that does not equal gross minus deductions, and YTD totals copied from the current period. Check the data first, then the layout, then the final PDF, before you download or send it.

A stub can look finished and still be wrong, because a clean layout prints a typo as confidently as a correct figure. The sections below group the errors by where they happen, give a quick check for each, and end with the file checks people skip once the preview looks right. In the paystub builder's preview, every figure discussed here can still be fixed before a PDF exists.

Run two passes: data first, layout second

Reviewing figures and design at the same time splits your attention. The eye goes to what looks wrong, such as a wrapped name or a crowded corner, while a mistyped hourly rate looks perfectly normal. Two short passes catch more than one long one.

The data pass

Work through the stub in the same sequence every time, with the source records open beside it:

1. Identity: employer name, address and EIN; worker name and ID.
2. Dates: period start, period end, pay date and pay frequency.
3. Earnings: each line's rate times hours, or the salary per period, and any bonus or commission.
4. Deductions: every line on the source is present once, with the right amount.
5. Net pay: gross minus total deductions, compared with the deposit if there is one.
6. Year-to-date: previous YTD plus current equals the new YTD for each value.

What to have open during the review

Checking a preview against itself proves nothing, because every figure on it agrees with the entries that produced it. Open the records the figures came from instead:

• The timesheet or time clock export for hours
• The offer letter or latest pay change notice for rates and salary
• The previous stub for deductions and YTD values
• The benefits or retirement confirmation for any new election
• The bank statement line for the deposit and pay date

With those beside the preview, each check becomes a comparison between two independent sources rather than a reread of your own typing.

The layout pass

Now ignore the numbers and look at the page:

• Every field you entered is printed, and nothing you left blank prints as a stray zero or placeholder.
• No text wraps into a neighboring cell or pushes a total out of alignment.
• Labels read clearly and would make sense to someone who never saw the form.
• The template matches earlier stubs in the same series.

If the layout pass fails, the fix is often a different template rather than different data; the readability checks for layouts help you choose one.

Date mistakes that throw off every later stub

Dates cause more knock-on errors than any other field, because each period's dates set up the next one.

The table shows what a correctly shaped period looks like for each frequency.

Illustrative example (made-up figures): A biweekly employee's period is entered as March 1 to March 15, 2026.

• Days in the entered period: 15, one more than a biweekly period allows
• Correct period: March 1 to March 14 (14 days)
• Next correct period: March 15 to March 28
• Next period if the error is copied forward: March 16 to March 29, one day off, and every following period drifts with it

Other date slips to catch: a pay date earlier than the period end, which is unusual and worth confirming; a January stub still carrying last year's year; and a pay frequency setting that does not match the period length. The difference between the two dates people confuse most is laid out in pay date versus period end date. How often wages must be paid is set by state law, so check your state labor agency if a schedule looks irregular.

Earnings mistakes: rates, hours and salary per period

Most earnings errors are typing errors that still produce a believable number.

Illustrative example (made-up figures): A worker logs 37.75 hours at $21.40 an hour.

• Correct gross: 37.75 × $21.40 = $807.85
• Amount typed: $870.85
• Difference: $870.85 − $807.85 = $63.00
• $63.00 ÷ 9 = $7.00, a whole number

When two adjacent digits are swapped, the difference between the right and wrong figures is always divisible by 9. That makes it a fast way to recognize a transposition once you know a figure is off.

Salaried stubs have their own trap: dividing by the wrong number of periods. An annual salary of $52,000.00 is $52,000.00 ÷ 26 = $2,000.00 on a biweekly stub but $52,000.00 ÷ 24 = $2,166.67 on a semimonthly one. Using the wrong divisor overstates or understates every stub by $166.67.

Also check that overtime uses the rate your records show, that a bonus sits on its own line rather than inside regular pay, and that reimbursements are handled the way the source record handles them.

Pay changes partway through a period

A raise that starts mid-period often produces a stub that is right for half the period and wrong for the rest. Employers prorate in different ways, so follow the method your payroll records use; the example shows one common approach.

Illustrative example (made-up figures): A semimonthly salary rises from $2,500.00 to $2,750.00 per period, effective on the ninth day of a 15-day period, prorated by calendar days.

• Days at the old salary: 8, so $2,500.00 × 8 ÷ 15 = $1,333.33
• Days at the new salary: 7, so $2,750.00 × 7 ÷ 15 = $1,283.33
• Gross pay for the period: $1,333.33 + $1,283.33 = $2,616.66

Entering either full salary instead would miss by more than $100: the old figure is $2,616.66 − $2,500.00 = $116.66 too low, and the new one is $2,750.00 − $2,616.66 = $133.34 too high.

Deduction mistakes: duplicates, gaps and stale amounts

Deduction errors are hard to see because a stub with one line too many or one too few still looks complete.

• Duplicates. A premium entered as a preset line and again as a custom line doubles the deduction. Scan for two lines with similar labels and matching amounts.
• Gaps. A local tax, union dues or a retirement contribution that appears on the source record but not on the stub inflates net pay.
• Stale amounts. Benefit elections, retirement percentages and withholding change during a year. Copying last quarter's amounts forward misses those changes, which is why the explainer on deductions that change between periods is worth a look before you reuse old figures.
• Vague labels. "Deduction 1" or "Misc" tells a reader nothing. Use the label from the source record.

Net pay mistakes the layout will not flag

A summary block prints whatever net figure it receives. If you type or override net pay, nothing on the page tells you the arithmetic no longer works.

Illustrative example (made-up figures): Gross pay is $1,245.00, with these deductions (amounts assumed): federal withholding $96.00, state tax $41.20, Social Security $77.19, Medicare $18.05 and dental $35.93.

• Total deductions: $96.00 + $41.20 + $77.19 + $18.05 + $35.93 = $268.37
• Net pay: $1,245.00 − $268.37 = $976.63
• Net pay typed on the stub: $986.63, which is $10.00 too high

A bank deposit of $976.63 would expose that error at once, which is why the deposit is the best single cross-check for net pay. If the deposit differs for a legitimate reason, such as pay split between two accounts, note that reason in your own records.

Rounding is the one difference not worth chasing. Medicare at 1.45% of $1,245.00 is $18.0525, which prints as $18.05. Over a year, the sum of rounded per-period amounts can drift a cent or two from the percentage applied to the YTD total. A one-cent gap usually means rounding; a gap of a dollar or more means a line is wrong.

YTD mistakes: copied, skipped and reset figures

Year-to-date values fail in predictable ways:

• Copied current figures. A YTD value equal to the current value is only right on the first pay date of the year or the first stub of a new job.
• Skipped periods. Adding this period's pay to a YTD figure two stubs old leaves out one period entirely.
• Values that shrink. Within a year, a YTD figure should be at least as large as on the previous stub unless a documented correction reduced it.
• Wrong reset. YTD usually restarts with the first pay date in January, not the first period that begins in January.

The rule is simple: previous YTD plus current equals new YTD. For example, a previous YTD net of $14,210.40 plus a current net of $976.63 gives a new YTD net of $15,187.03. When totals still look odd against a calendar year, the explainer on calendar-year YTD mismatches covers the usual causes.

Identity and privacy mistakes

These errors are small on the page and awkward later.

• Names misspelled, or first and last names swapped.
• An old address for either party.
• An EIN in the wrong format; it has nine digits, usually written as 12-3456789.
• An employee ID that does not match the one used elsewhere.
• More personal data than needed. At most the last four digits of a Social Security number belong on a stub, and bank account numbers do not belong there at all.

Mistakes that only appear across a set of stubs

When several consecutive stubs are prepared together, each one can look fine alone while the set is inconsistent. Lay the stubs side by side and check:

• Gaps and overlaps. Each period should start the day after the previous one ends. A set running March 1 to 14 and then March 16 to 29 skips a day, while March 1 to 14 followed by March 14 to 27 counts one twice.
• YTD steps. Each stub's YTD gross should exceed the previous stub's by exactly that stub's current gross.
• Changes applied at the wrong point. A new deduction or raise belongs on stubs from the first affected pay date, not on every stub in the set or only the last one.
• Check or stub numbers. If you use them, they should rise in order with no repeats.
• Pay dates on non-business days. A pay date on a weekend or holiday is worth confirming against the actual deposit.

January and year-end mistakes

The turn of the year packs several errors into a few stubs:

• The wrong year. A first January stub still showing last year in the pay date is easy to miss, because the day and month look right.
• YTD not restarted. The first pay date of the new year starts fresh year-to-date totals, even when the period itself began in December.
• A December period paid in January. For federal wage reporting, the year pay is received generally decides where it counts, so a period ending December 27 but paid January 2 usually opens the new year's YTD.
• An extra biweekly pay date. Some years contain 27 biweekly pay dates instead of 26, and a salary divided by 26 in such a year may not match how the employer handled it.

Mistakes on contractor and self-employed records

Payment records for independent contractors and the self-employed borrow the paystub format without every payroll convention. Typical slips:

• Withholding lines that never happened. If nothing was withheld from a contractor payment, the record should not show federal or state tax deductions.
• Wage labels on service payments. "Regular pay" can misdescribe a payment against an invoice; a label naming the project or service is clearer.
• Service dates confused with payment dates. Record the period the work covered and, separately, the date the payment arrived.
• Fees netted out of sight. If a platform kept a fee, show the gross payment and the fee as separate lines so the amount received can be traced.

A symptom-to-cause table for the preview

When something looks off but the cause is not obvious, start from the symptom.

When a symptom has more than one possible cause, fix the earliest one first: dates before earnings, earnings before deductions, and deductions before net pay and YTD. Each later figure is built on the earlier ones, so a corrected date or rate can make a downstream problem disappear.

Checks on the final PDF itself

The preview and the delivered file should match, but confirm it. Open the actual PDF, not the preview, and run these checks.

If you added a deposit slip, confirm its page is there; it is an extra on one or two stubs and included from three stubs upward. Keep Social Security numbers and pay amounts out of file names, and before forwarding the file anywhere, run through the basics of sending a stub by email safely.

Extra checks when you started from a template file

If the stub began as a downloaded template file rather than a guided form, a few more mistakes are possible:

• Missing fields. Some template files have no place for a pay date, pay frequency or YTD values, so the stub omits them without any warning.
• Formulas that skip rows. A total built for five deduction rows ignores a sixth one added below it.
• Locked or flattened fields. A PDF form may allow typing in some boxes but not others, leaving old sample text in place.
• Font substitution. A file opened on a different computer may swap fonts, shifting columns so figures sit under the wrong headings.
• Leftover sample data. Placeholder names, dates or amounts survive in corners that were never edited.

Read such a file cell by cell after exporting it, since nothing in the process checked it for you.

When you spot a mistake after downloading

Resist editing the figures in a PDF editor. A figure changed in the file no longer matches the entries behind it, totals may not recalculate, and an edited document is harder to explain later. Re-create the stub from corrected inputs instead, replace any copy you already sent, and keep a short note of what changed and why, as described in documenting a correction.

Catching these errors improves the record, but PayStubGo remains a formatting tool that builds a PDF from the figures you enter, not a payroll or verification service. Where a deduction, tax amount or wage rule is in doubt, the employer's payroll provider or a tax professional is the right source.