Pay Date vs Pay Period End Date: Tax Year

This is general information, not tax or legal advice. Payroll timing rules interact with state wage statement laws and your own employer’s practices, so confirm anything here with a CPA or your state labor agency before you set policy.

You worked the last two weeks of December. The check arrived on January 2. Come February, those hours are nowhere on your W-2, and the obvious conclusion is that somebody made a mistake.

Nobody made a mistake. Your pay stub carries three separate dates, and only one of them decides which tax year the money belongs to. It is not the one most people look at.

Wages count in the year they are paid, not the year they are earned. That is the whole rule. Everything else on this page is detail around it.

The Three Dates on Every Pay Stub

Open any stub and you will find a period and a payment, recorded separately.

Field	Example	What it means
Pay period start	December 21, 2026	First day of work covered by this check
Pay period end	January 3, 2027	Last day of work covered by this check
Pay date (check date)	January 8, 2027	The day the money is actually issued

The pay period is a window of work. The pay date is a single event: the moment funds are released to the employee. A biweekly period is 14 days long. The pay date is a point.

Those two things are not redundant, and federal law says so. Under 29 CFR 516.2, every employer must keep payroll records showing the “Date of payment and the pay period covered by payment.” The DOL’s recordkeeping fact sheet carries the same requirement in its list of records every employer has to keep.

That is the cleanest justification for why a stub shows three dates instead of one. Each answers a different question. The period answers “what work is this?” The pay date answers “when did this become income?”

You will also see the pay date labeled “check date,” “issue date,” or just “date paid.” Same thing. It is also the date every year-to-date column on the stub is measured against, which is where the tax year question starts.

Which Date Decides the Tax Year

The pay date. Always the pay date.

The IRS instruction is written in exactly those terms. The General Instructions for Forms W-2 and W-3 tell employers to file a Form W-2 for each employee “to whom you made payments (including noncash payments) for the employees’ services in your trade or business during 2026.” Payments made during the year, not work performed during it.

The same instructions make the point again in an unlikely place. In the section on deceased employees, wages paid after death but within the same calendar year still go on that year’s W-2, while “if you made the payment after the year of death, do not report it on Form W-2.” The reporting axis is the payment, not the labor.

Constructive receipt, in the regulation’s own words

Behind the W-2 rule sits 26 CFR 1.451-2, the constructive receipt regulation. Income, it says, “although not actually reduced to a taxpayer’s possession is constructively received by him in the taxable year during which it is credited to his account, set apart for him, or otherwise made available so that he may draw upon it at any time.”

Read that carefully. The trigger is availability, not deposit. If your December 31 direct deposit hit your account on December 31, that money is December income whether or not you looked at your balance until January. An uncashed paper check dated December 29 and sitting on your kitchen table is still last year’s income.

The half of the rule most articles skip

The regulation does not stop there. It adds a limit: “income is not constructively received if the taxpayer’s control of its receipt is subject to substantial limitations or restrictions.”

That cuts the other way, and almost nobody writing about pay dates mentions it. Money that was genuinely not available to you before January is not December income, even if it was calculated from December work and even if a manager told you it was “approved” in December. The regulation’s own illustration involves a dividend check mailed so late in December that the shareholder could not have gotten it until the following year. Not constructively received.

So the practical test is not “when was it earned” and not “when did I spend it.” It is: on what date could this employee first have drawn on the money? That date is the pay date, and it decides the tax year.

Deposits follow the same clock

Employers get the same rule from the other side. Under Publication 15, federal employment tax deposit obligations arise when wages are paid, not when they are earned. Wages worked in June and paid in July are a July liability. The pay date drives the deposit calendar, the withholding tables applied, and the W-2, all together. If a stub’s tax year looks ambiguous, ask which date the employer’s deposit was keyed to. It is never the period end.

Why There’s a Gap: Pay Lag and Paying in Arrears

The gap between period end and pay date has a boring cause: payroll takes time.

Hours have to be collected and closed out. A manager has to approve them. Someone has to run the calculation, fund the account, and give the bank its lead time before the money can settle. None of that can happen before the period ends, because until it ends you do not know what to pay.

That is what “paying in arrears” means: the check covers a window of work that has already closed. The alternative, current pay, issues the check on or before the last day of the period, which means estimating hours nobody has worked yet. Most employers avoid that for hourly staff, though it shows up for salaried workers whose amount does not vary.

Why the first paycheck feels wrong

Start work on a Monday, and your first check does not arrive on the next payday, because that payday belongs to a period that closed before you started. It arrives on the one after. The lag is not an error, and it corrects itself permanently.

The tax-year version of the same story: start on December 22, get your first check on January 8, and your W-2 for that first year shows nothing at all. Your December work appears on the following year’s W-2. Annoying to explain, entirely correct.

The 27-Pay-Period Year (and What It Does to Your W-2)

Every so often, a biweekly employer pays 27 times in a calendar year instead of 26. The cause is arithmetic, not generosity.

Twenty-six biweekly periods cover 364 days. A calendar year is 365 days, or 366 in a leap year. That leftover day accumulates, and roughly every 11 to 12 years it pushes an extra payday into the calendar year. Littler’s analysis lays out the mechanics.

2026, done honestly

There is a rule of thumb circulating that any biweekly employer whose first 2026 payday falls on or before roughly January 8 will have 27 paydays. It does not survive the arithmetic, and repeating it will send you looking for a 27th check that never arrives.

Pure spacing gives you a 27th payday in 2026 only if your first payday is January 1, 2026. Everything past that depends on your employer’s holiday practice, and that is where the real 2026 case comes from.

Take a Friday payer whose first 2026 payday is January 2. Count forward by fourteens: payday number 26 lands on December 18, 2026. The next one would be January 1, 2027, which is a federal holiday. Employers who pay a day early when a payday falls on a holiday will issue that check on December 31, 2026 instead.

And there it is: a 27th check, dated inside 2026, covering wages that would otherwise have been paid, and taxed, in 2027. Nobody worked extra. A calendar shifted, and a pay period’s wages moved into the 2026 W-2.

What employers do about it

Two broad options, and the choice has to be made before the year starts.

• Recalculate the biweekly amount so annual salary divides across 27 checks instead of 26. Each check is smaller. This usually requires advance written notice under state pay-notice laws, so it is not a decision to make in December.
• Absorb the extra payroll, paying the normal biweekly amount 27 times and accepting roughly one additional period of payroll cost that year. Simple, and it happens once a decade or so.

Benefit deductions need their own answer: spreading a fixed annual premium over 27 deductions instead of 26 changes the per-check amount, and some employers skip the deduction on the extra check entirely.

What employees see

A bigger W-2 for that year, without a raise. If you are salaried and your employer absorbed the extra payroll, your reported wages for that calendar year genuinely are higher, because you were paid 27 times in it. The following year returns to normal.

Check your own schedule rather than assuming. A pay frequency converter makes the distinction concrete: semimonthly employers always have exactly 24 paydays and never face this at all.

Dating a Pay Stub So YTD and the W-2 Reconcile

If you are the one creating the document, this is the section that matters. Four rules cover almost every case.

1. The stub belongs to the pay date’s calendar year. Not the period’s. A stub for December 21 to January 3, paid January 8, is a document of the new year. File it, number it, and total it there.

2. YTD resets January 1, on the pay date. The year-to-date columns run from January 1 through the current pay date, regardless of hire date or when the work happened. That December period paid in January opens the new year’s YTD at its own gross amount. If YTD columns are new to you, what YTD means on a pay stub walks through every line.

3. Never date a stub by the period end because it “feels” like that month’s work. This is the most common dating error, and it silently pushes a stub into the wrong tax year. The document follows the money.

4. Keep both dates on the stub, always. Federal recordkeeping requires the payment date and the period covered, and many state wage statement laws require the period on the statement itself. A stub showing only one date is incomplete no matter which one it shows.

Getting this right is mostly a matter of having three separate fields rather than one date box. Payslip44 stores pay period start, pay period end, and pay date as distinct values, so a December period paid in January is straightforward to build correctly. Every stub is created on your device with decimal-precise math, then exported as PDF, PNG, CSV, or text.

At year end, reconciling is a summing exercise: total the gross from every stub whose pay date falls in the year, then compare against the W-2. A YTD earnings calculator does the arithmetic. Expect W-2 Box 1 to come in lower than YTD gross if there are pre-tax deductions in the mix; that difference is normal.

Get Payslip44 for iOS or Android if you would rather have the three date fields built in than manage them in a spreadsheet.

Common Dating Mistakes on Pay Stubs

A short list of the errors that cause real problems, mostly at the worst possible moment.

• A pay date earlier than the period end. This says the employee was paid for work not yet performed. Lenders and underwriters reviewing stubs for income verification treat it as a red flag, and it usually means someone typed the period end wrong.
• YTD carried over from the wrong year. A January stub showing December’s YTD totals will never reconcile to a W-2. YTD restarts at zero on the first pay date of the new calendar year.
• Backdating a stub to shift income between years. It does not work, because constructive receipt looks at when the money was available, not what the paper says. It also creates a document that contradicts the employer’s deposit records.
• Overlapping or gapped periods. Two consecutive stubs should meet exactly: one period ends, the next begins the following day. Overlaps double-count days and gaps drop them.
• Reusing last period’s dates. Easy to do when duplicating a previous stub, and easy to miss, since every other number can look right.

If you spot any of these on a stub you already issued, how to correct a pay stub covers the fix, and common pay stub errors has the wider list of things worth checking before you send one out.

The Short Version

Three dates, one decision. The period start and period end describe the work. The pay date decides the tax year, drives the W-2, resets and advances the YTD columns, and sets the employer’s deposit deadline.

When a December period is paid in January, those wages are next year’s. When a calendar quirk drops a 27th check into December, those wages are this year’s. In both cases the answer comes from the same question: what date could the employee first have drawn on the money?

Frequently Asked Questions

Which date determines the tax year for a paycheck?

The pay date. Wages belong to the calendar year they are paid, not the year the work was done.

My pay period ended December 31 but I was paid January 2. Which W-2 are those wages on?

Next year's. The check date controls, so those wages open the new year's W-2 and the new year's YTD column.

What is constructive receipt?

Income counts when it is credited to your account, set apart for you, or otherwise made available so you can draw on it, even if you have not cashed it. The exception is when your control over the money is subject to substantial limits or restrictions (26 CFR 1.451-2).

What is the difference between the pay period end date and the check date?

The period end closes the stretch of work being paid for. The check date is when the money is actually issued. They are almost never the same day.

Why is my first paycheck later than I expected?

Pay lag. Most employers pay in arrears, so your first check covers a period that has already closed and arrives some days after it ends.

What happens in a year with 27 biweekly pay periods?

You may receive an extra paycheck inside that calendar year, which raises that year's W-2 wages. Employers either recalculate the biweekly amount or absorb the cost of one additional payroll.

Will 2026 have 27 pay periods?

Only for some biweekly employers. The arithmetic gap plus a payday shifted off the January 1, 2027 federal holiday can push a 27th check onto December 31, 2026.

Can an employer change the pay date to move wages into a different tax year?

No. Backdating or holding a check to shift income between years does not work once the money was already available to the employee.

Does a pay stub have to show both the pay period and the pay date?

Federal recordkeeping rules require the employer to keep both the date of payment and the pay period covered. Many state wage statement laws also require the pay period to appear on the stub itself.