Paystub Recordkeeping for Small Businesses: Filing and Retention

Good paystub recordkeeping means every stub can be found by employee and pay period in under a minute, its file name says what it is without exposing private data, corrections sit beside the original, and nothing is deleted before federal and state retention periods end. For employment tax records, IRS guidance sets that period at four years or more.

Most small teams do not lose pay records to disasters. They lose them to a folder called "Payroll stuff", a file named "stub final (2).pdf" and a former office manager's inbox. The fixes are cheap and mostly habits. This guide covers what the rules expect, then a folder layout, a naming pattern, access and backups, consistency checks, corrections and a retention calendar. For owners still setting up what each stub should contain, the companion piece on small business paycheck stub essentials comes first.

What federal and state rules expect a business to keep

Several rules overlap, and they are not measured the same way. The Fair Labor Standards Act regulations count from the last entry in a record, the IRS counts from when a tax was due or paid, and states add their own periods. The table lists the main ones a small employer runs into, with the source for each.

Two points follow from the table. First, the periods do not replace each other: an employer in New York faces the six-year state figure as well as the federal ones. Second, federal law does not require a pay stub at all; the Department of Labor says the FLSA does not require employers to give employees pay stubs, although it does require the underlying payroll records. Many states do require a statement, which is why a copy of each stub often ends up being part of what you keep. The article on how long to keep paystub copies goes through these periods in more detail.

A folder structure built around employee and pay period

Every pay record has two natural keys: who was paid and for which period. A folder structure should let you reach a stub by either one. For most teams under about 50 people, the simplest layout that does this is year first, then employee:

• Payroll records (top folder, restricted access)
• 2026 (one folder per calendar year of pay dates)
• E014 Jordan R (employee ID followed by first name and last initial)
• 2026-05-15-E014-STUB-v1.pdf (one file per pay date)

The alternative is year first, then pay date, with every employee's stub for that date in one folder. Each layout makes one kind of question easy and the other slower.

Year then employee usually wins, because the common requests are about one person: a copy an employee asks for, a former employee's request, or a correction. The pay-date question is answered well enough by consistent file names, which is the next section.

Keep payroll files out of general shared folders entirely. A separate top folder with its own permissions is easier to protect than individual files scattered through project drives.

File names that sort, search and protect privacy

A file name should tell you what a document is before you open it, sort into the right order on its own, and reveal nothing that would harm anyone if the name alone were seen in a sync log or an email subject line. A pattern that does all three:

Pay date, employee ID, document type, version. For example, 2026-05-15-E014-STUB-v1.pdf.

Each part has a reason:

1. Pay date in year-month-day order. Files then sort chronologically in every operating system. Use the pay date, not the period end date, and keep the choice consistent; the difference between the two is explained in the article on pay date versus period end date.
2. Employee ID instead of a name or Social Security number. An internal code such as E014 is searchable and meaningless to outsiders. Never put any part of a Social Security number in a file name.
3. Document type code. STUB for a regular statement, CORR for a corrected one, YE for a year-end form such as a W-2, and so on. A short fixed list prevents "paystub", "pay-stub" and "statement" all appearing for the same thing.
4. Version. v1 for the original, v2 for a replacement. The original is never overwritten or renamed.

Illustrative example (made-up figures): A café pays 9 employees every two weeks, which is 26 pay dates a year. That produces 9 × 26 = 234 stubs in one year and 234 × 4 = 936 files over four years, before any corrections or year-end forms. With names like "stub final (2).pdf", finding one person's March stub means opening files at random. With the pattern above, searching "E014" inside the 2026 folder returns that employee's 26 files in date order.

Access, storage and backups

Pay records combine names, addresses, pay rates and often partial identification numbers, so the storage question is mainly about who can open them.

• Limit access by role. The owner and whoever runs payroll need the folder; most staff do not. Review the list whenever someone changes jobs or leaves.
• Prefer one controlled location over copies on personal laptops and phones. A shared drive with permissions, or your payroll provider's archive plus a downloaded backup, both work.
• Back up on a schedule and keep at least one copy somewhere other than the main system, so a deleted folder or a locked account does not take every record with it.
• Protect files in transit. When a stub leaves the folder by email, the checklist for emailing paystubs safely covers recipients, attachments and subject lines.

Also decide where records are kept physically, if at all. The FLSA regulations at 29 CFR 516.7 expect records to be kept safe and accessible at the place of employment or at a central recordkeeping office, and records kept centrally must be made available within 72 hours of a request from the Wage and Hour Division.

Keeping pay records consistent from one period to the next

A tidy folder of inconsistent stubs is still hard to use. Consistency means the same employer name, the same labels for the same earnings and deductions, the same layout and year-to-date totals that carry forward correctly. Choose one layout from the available paystub templates for the whole team and change it only at the start of a year.

A quick carry-forward check on each new stub catches most errors before a record is filed:

Illustrative example (made-up figures): An employee's April 30 stub shows year-to-date gross pay of $18,400. The May 15 stub shows current gross pay of $1,150, so the new year-to-date figure should be $18,400 + $1,150 = $19,550. The draft shows $19,500. The $50 gap turns out to be a small referral bonus entered on the April stub but left out of the running total. Fixing it before the stub is issued costs a minute; fixing it after means a corrected document and a note in the file.

Other checks worth building into every pay run:

• The pay period starts the day after the previous period ended, with no gap or overlap.
• Deduction labels match last period's labels exactly, unless something genuinely changed.
• Hours on the stub match the approved timesheet for hourly staff.
• Net pay matches the amount sent by direct deposit or written on the check.

Supporting documents that belong next to the stubs

A stub is a summary. The evidence behind each figure lives in other documents, and a stub without them is hard to defend if a number is questioned. For each employee, keep a supporting subfolder beside the stubs, using the same naming pattern with its own type codes:

• TIME: approved timesheets or time-clock exports. The FLSA regulation at 29 CFR 516.6 treats time cards as supplementary records to keep for at least 2 years.
• RATE: offer letters, raise approvals and pay-rate change notices, so every rate on a stub has a start date.
• W4: federal and state withholding certificates. The IRS lists copies of withholding certificates among the employment tax records it expects employers to keep.
• BEN: benefit and retirement elections that explain each pre-tax or post-tax deduction.
• ORDER: garnishment or support orders, with the date each started and ended.
• DD: direct deposit authorizations, stored in the same restricted folder because they contain account numbers.

As a working rule, keep a supporting document for as long as the longest-retained stub that relies on it. A 2023 raise approval still explains every rate on 2026 stubs.

Corrections: the original, the replacement and the note between them

When a stub is wrong, the worst outcome is a folder where only the corrected version exists and nobody can say what changed. Keep three things together: the original file (v1), the corrected file (a CORR type with v2), and a short note stating what was wrong, what changed, who approved it and when the corrected copy was given to the employee.

That note can be a plain text file with the same base name, or a line in a corrections log for the year. The article on correcting a paystub record sets out what that note should contain and what to check before reissuing.

Closing out a payroll year

The weeks after the last pay date of the year are the best time to make the folder complete, because every missing file is still easy to trace. For 2026, the IRS General Instructions for Forms W-2 and W-3 set February 1, 2027 as the date to furnish employee copies and file with the Social Security Administration, so the close-out fits between the final December payroll and that deadline.

1. Count the stubs for each employee and compare with the number of pay dates they were employed for.
2. Compare each employee's final year-to-date totals with the figures going onto their Form W-2.
3. Save W-2 copies and the W-3 into the year folder once issued.
4. Move corrected stubs and their notes into place, and confirm no draft or duplicate files remain.
5. Change the year folder to read-only for everyone except the payroll owner.
6. Write the retention review date for that year into the calendar described below.

Illustrative example (made-up figures): A salon's 2026 folder shows 26 stubs for every full-year employee except E007, who has 25. Sorting E007's files by name shows that the July 3 stub was saved as 2026-07-02-E007-STUB-v1.pdf, a day early, while a second file, for June 19, is missing. The June 19 PDF turns up in a downloads folder. Renaming one file and filing the other takes five minutes in January; finding them in 2029 would take far longer.

A retention calendar and a disposal log

Retention rules tell you the minimum, not when to delete. A simple calendar turns them into a date. For each year of records, note the longest period that applies to your business and the event it counts from, then set a review date.

Illustrative example (made-up figures): A business in a state with no longer rule decides to apply the IRS four-year period to all 2026 pay records. Assume the last employment tax related to 2026 wages was due or paid on January 31, 2027; the business treats January 31, 2031 as the earliest date to review those records for disposal. If a New York location is involved, the six-year state period pushes that review date later for the New York records. These dates are assumptions for illustration, not a determination of what applies to any business.

When a review date arrives, check for anything that should pause disposal, such as an open wage claim, an audit or a pending correction. If files are deleted, record what was deleted, the date range it covered and who approved it. That log is small, and it answers the question "where are the 2026 records?" long after they are gone.

Answering requests for copies of past stubs

Sooner or later someone asks for an old stub: a current employee who lost one, a former employee sorting out a tax question, an accountant, or a state agency. A short, repeatable process protects both the employee and the business.

• Confirm the requester's identity through contact details already on file, not only the details in the request.
• For requests from anyone other than the employee, many employers ask for the employee's written authorization first.
• Send copies through the same protected method used for regular delivery, never as an open attachment to an unverified address.
• Log the date of the request, what was sent and the date it went out.

Some states set deadlines. California Labor Code section 226(b) gives current and former employees the right to inspect or receive copies of their employment records on reasonable request, and employers have 21 calendar days to comply. A log makes it easy to show that a request was met on time.

Dividing recordkeeping tasks on a small team

In a business of five or ten people, one person often does everything, which is exactly when errors go unseen. Even a light split helps:

1. One person prepares the stubs from timesheets and pay rates.
2. A second person, often the owner, reviews them against the checks above.
3. The preparer files the approved PDFs using the naming pattern and records any correction in the log.
4. Once a quarter, someone other than the preparer spot-checks five random files for correct names, folders and access.

If you produce stubs with PayStubGo, PayStubGo's generator lets you preview each PDF before download; saving that downloaded file into your own folder structure is what makes it part of your records. PayStubGo formats the figures you enter, and it does not run payroll or keep your official records for you.

Retention periods and wage-statement requirements vary by state, and some cities add their own rules, so the federal figures above are a floor rather than a full answer. The Department of Labor's Wage and Hour Division, the IRS and your state labor department publish the requirements that apply to you. This guide describes recordkeeping practice, not legal advice; for a question about your own obligations, ask an employment attorney or your state agency.