Payroll Records: What to Keep and for How Long

A complete payroll file shows who was employed, when and where work occurred, how gross pay was calculated, which taxes and deductions applied, how net pay was delivered, when liabilities were deposited, which returns were filed, and whether agencies accepted them. The IRS four-year rule is an important floor for employment tax records, not a universal destruction date. Federal wage-and-hour payroll records are generally retained for three years, related calculation records often for two years, and Form I-9 is kept while the person is employed and then until the later of three years after hire or one year after employment ends.

This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Identity and authorization records support setup

Keep employee name, address, Social Security number, occupation, work authorization, Form W-4, state forms, and direct-deposit authorization under appropriate access controls.

Time and earnings records prove gross pay

Retain workweek, hours, rates, overtime, salary basis, tips, commissions, bonuses, leave, piece rates, and corrections.

Deduction records explain net pay

Preserve elections, legal orders, benefit deductions, retirement contributions, tax levies, repayments, and employee authorizations.

Tax records must reproduce the returns

Keep wage bases, withholding methods, deposits, adjustment workpapers, Forms 941, 940, W-2 and W-3, state returns, and acceptance.

The IRS four-year period is specific

Count at least four years after filing the fourth quarter for the year, not merely four years from each paycheck.

Other laws use other clocks

Wage-and-hour records, I-9, retirement plans, workers’ compensation, unemployment, leave, and state rules need a coordinated schedule.

Electronic records must remain usable

A retained export should be readable, searchable, reproducible, protected, and available even after a vendor change.

A pending dispute suspends routine destruction

Notices, audits, litigation, claims, corrections, or known issues can require a legal or tax hold.

Step-by-step workflow

1. Inventory record categories. List employee master data, time, pay, taxes, benefits, filings, payments, accounting, notices, and approvals.
2. Map each retention authority. Record the federal tax, wage-and-hour, immigration, benefit, state, contractual, and litigation periods that apply.
3. Choose the longest applicable period. Apply the controlling period to each category and document the trigger date.
4. Export from payroll systems. Preserve detailed registers, employee histories, tax filings, confirmations, journal entries, and change logs in usable formats.
5. Restrict sensitive information. Use role-based access, encryption, multifactor authentication, secure transmission, and documented offboarding.
6. Reconcile before archiving. Tie annual registers to quarterly returns, W-2 totals, state filings, deposits, cash, and the general ledger.
7. Apply holds. Pause destruction for audits, notices, claims, corrections, litigation, or other known needs.
8. Test retrieval and destruction. Sample archived records, document authorized disposal, and retain a destruction log without preserving unnecessary personal data.

Worked example

An employee hired March 1, 2022 leaves June 30, 2026. The company calculates the I-9 retention date as the later of March 1, 2025 or June 30, 2027, so it keeps the form through June 30, 2027. That date does not control the employee’s 2026 payroll tax records, which remain subject to the separate IRS four-year period after the fourth-quarter return is filed, plus any longer state or benefit requirement.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Deleting four years after each paycheck. The federal employment-tax clock generally runs from filing the fourth quarter for the year.
• Using one retention period for every record. Tax, wage, I-9, benefits, states, and disputes differ.
• Keeping only summary PDFs. Preserve transaction detail, calculations, changes, filings, payments, and acceptance.
• Leaving records in a former vendor account. Export usable copies before access ends.
• Storing Social Security numbers broadly. Limit access and retain only what the schedule and business need require.
• Destroying records during a dispute. Apply and document a hold before routine disposal.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Practical implementation notes

Retention matrix

Track record type, authority, trigger date, minimum period, owner, location, hold, and destruction date.

Access register

Limit sensitive payroll records to named users and review access after role changes.

Annual archive

Create a year-end package outside the processing platform after W-2 and return reconciliations.

Retrieval test

Prove that an authorized reviewer can locate and read a sample record without vendor assistance.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.