Small employers are switching from paper-and-spreadsheet pay records to digital systems because the federal Fair Labor Standards Act now expects records that can be produced "from the date the entry is made" under 29 CFR §516.6, and most state payday statutes layer on itemized paystub fields that a Word template alone can't reliably hit. The Department of Labor's Fact Sheet 21 names fourteen specific fields every employer must keep for each non-exempt employee for two-to-three years, and the IRS's Publication 583 extends that retention to four years for federal employment tax records. A spreadsheet plus a Manila folder will satisfy those requirements only if every entry reconciles, no field is missing, and the file survives the next coffee spill. Most don't.
This guide walks the four reasons the shift is happening, the eight records FLSA actually requires, the five state add-ons that catch employers by surprise (Oregon, California, New York, Illinois, Massachusetts), the cost-of-time math for a real two-employee bakery, a six-step transition plan, and a print-ready audit-readiness checklist. The strongest small-employer record set usually includes:
- Employee identification: full legal name, address, SSN, occupation, sex, and date of birth if under nineteen
- Daily and weekly hours worked for every non-exempt employee, by date
- Regular hourly rate, basis of pay, and any commissions, bonuses, or piece-rate calculations
- Total straight-time wages, total overtime wages, and additions to or deductions from wages for each pay period
- Total wages paid each pay period, with the date of payment and pay period covered
- A current Form W-4 for every W-2 employee and a current Form W-9 for every 1099 contractor
- Quarterly Form 941s, annual Form 940, and copies of every W-2 and 1099 issued
- A written retention schedule naming which records are kept how long and where they live
The strongest small-business record file tells one consistent story across every document. Hours on the time card match hours on the paystub, gross on the paystub matches the bank transfer, YTD on the December stub matches Box 1 of the W-2. If you need to model paystub math on the take-home side while you build the system, the MyStubs paycheck calculator handles gross-to-net by state, and the MyStubs paystub generator renders structured stubs that match the FLSA field list.
Paystub Generator
Build structured digital paystubs for your team
Replace the Word template with a paystub that holds employer details, gross pay, taxes, deductions, YTD totals, and pay-period dates — the exact fields FLSA §516.2 and state payday statutes require.
Create Paystubs for Your BusinessTessa's Rosewood Bakery
Threaded character for this post: Tessa Williams, owner of Rosewood Bakery in Portland, OR. Two employees plus Tessa herself: Mira (head baker, full-time, hourly at $24/hr) and Jonas (counter staff, part-time, hourly at $18/hr). Total annual payroll for 2025: $76,400 ($49,920 to Mira, $14,040 to Jonas, and $12,440 to Tessa herself as an S-corp owner-employee). Tessa runs payroll biweekly through a personal Excel file, prints each paystub on the bakery's letterhead, and files them in a Manila folder marked "Payroll." She spends roughly 6 hours every month on payroll admin — punching hours from a paper time card, recalculating overtime when Mira covers a Saturday, hand-typing each stub, printing two copies (employee + file), reconciling to her business checking, and walking the quarterly 941 to her accountant.
Three things happened in early 2026 that pushed Tessa to switch:
- Oregon's ORS 652.610 requires itemized statements with specific fields — gross wages, hours worked, pay rate, deductions, employer's name and address, pay period dates — and Tessa's Word template was missing pay rate on stubs from 2024..
- The IRS released guidance in March 2026 tightening expectations around electronic payroll records, and Tessa's accountant told her the next audit cycle would look at retention format..
- Mira applied for a used-car loan in February and needed six months of paystubs in PDF form. Tessa spent two evenings digging through the folder, rescanning bent originals, and re-typing two stubs where the print had faded.
Tessa's numbers anchor every worked example below.
Paystub Generator
Create your paystub in minutes
Build a professional paystub with built-in 2026 tax math, all 50 states, and instant PDF download.
Create Your PaystubSix-Step Manual-to-Digital Transition
Most small employers can complete the move from paper-and-spreadsheet to digital records in 30–60 days without missing a pay period. The work is sequential — choose the system before you migrate history, define the retention schedule before you delete anything — but each step is concrete.
| Step | What to do | Why it matters | Timing |
|---|---|---|---|
| 1. Inventory | List every record currently kept and where it lives (time cards, paystubs, 941s, W-2s, W-4s, I-9s, deduction authorizations) | You can't migrate what you can't find; federal recordkeeping requires you to produce records on request | Week 1 |
| 2. Choose the stack | Decide on a time-tracking tool, a paystub renderer, a cloud folder structure, and a backup destination | Each piece replaces a manual step; the combination has to balance gross to net on its own | Week 1–2 |
| 3. Define the retention schedule | Map every record type to a retention period and a storage location; document who has access | FLSA requires 2–3 years, IRS requires 4 years on employment-tax records, state statutes vary | Week 2 |
| 4. Migrate prior periods | Re-render paystubs for the prior 12 months (or longer) from real payroll data into the new format | An incomplete history is the most common reason employees can't get a loan or rental approved | Week 3–4 |
| 5. Run parallel one pay period | Run both the old spreadsheet AND the new system for one cycle; reconcile to the penny | Catches missing deductions, rounding errors, and state-field gaps before they go live | Week 5 |
| 6. Cut over and document | Issue the next pay period digitally only; archive the paper folder in a labeled bin; update the employee handbook | The cut-over is a one-day event; the documentation lives forever | Week 6 |
Tessa walked the six steps over six weeks in February–March 2026. The inventory took her two evenings and surfaced three documents she'd lost track of (Mira's 2023 W-4 was missing entirely; one bank-account-change form for Jonas had never been filed). The retention schedule took her one hour with IRS recordkeeping basics open in one tab and Oregon BOLI's small-business page in another. The migration ate her longest evening — re-rendering 26 biweekly stubs for two employees from her Excel file — and saved her every subsequent month.
The Eight FLSA-Required Fields
The federal FLSA recordkeeping rule under 29 CFR §516.2 is the floor every employer in every state must meet. The fields below come straight from the regulation, translated for a small employer who doesn't read regulations for fun. Per DOL Fact Sheet 21, each non-exempt employee's record set must include all of the following:
| FLSA-required field | What it means | Where Tessa keeps it now (paper) | Where Tessa keeps it now (digital) |
|---|---|---|---|
| Personal identification | Full legal name, address, SSN, sex, occupation, DOB if under 19 | Spiral notebook with W-4 attached | Encrypted employee file in cloud folder |
| Time and day workweek begins | The 168-hour workweek anchor (e.g., Sunday 12:01 AM) | Verbal — never written down | Documented in handbook + system setting |
| Hours worked each day | Punch in/out by date, including unpaid breaks deducted | Paper time card on clipboard | Digital time-tracking app |
| Total hours worked each workweek | Sum of daily hours by workweek | Tallied by hand in Excel | Auto-calculated by time-tracking app |
| Basis of wage payment | Hourly rate, salary, piece rate, commission percentage | Verbal — never documented | Written offer letter + payroll system record |
| Regular hourly rate | The rate used for overtime calculation | Memorized | Stored in payroll system, reflected on every stub |
| Total straight-time + overtime earnings | Pre-deduction wages for the workweek | Calculated in Excel | Auto-calculated and shown on stub |
| Total wages paid each pay period | Net pay deposited, with date of payment + pay period dates | Bank statement + paystub copy | Bank statement linked to digital stub + cloud archive |
The two fields Tessa missed most often in the manual system were "regular hourly rate" (which she'd recite to Mira verbally but never write on the stub) and "time and day workweek begins" (which she didn't know was required until her accountant flagged it during the 2024 941 review). Both fields are required by 29 CFR §516.2(a)(5) and (a)(2). The retention period for these records under 29 CFR §516.5 is three years for payroll records and two years for the underlying time records and wage-rate computations.
Five Statutes Beyond Federal Minimum
FLSA sets the federal floor; state payday and itemized-statement laws layer on requirements that vary widely. The five statutes below cover the highest-population states with the most-cited add-ons, plus Oregon (Tessa's state). The full list of state payday laws sits at the DOL state payday law page.
| State | Statute | Itemized-statement field required beyond federal | Penalty for non-compliance |
|---|---|---|---|
| Oregon | ORS 652.610 | Gross wages, hours worked (regular + overtime), pay rate, all deductions itemized, employer's business name + address, pay period dates | Civil penalty up to $1,000 per violation |
| California | CA Labor Code §226 | Nine specific fields including hourly rate, total hours, all deductions, inclusive pay-period dates, name + last 4 of SSN, applicable hourly rates and corresponding hours, sick-leave balance | $50 first violation, $100 subsequent, up to $4,000 per employee |
| New York | NY Labor Law §195 | Wage notice at hire, paystub with regular/overtime rates, allowances claimed, deductions, dates of work covered, employer name + address + phone | Up to $250 per workweek per employee |
| Illinois | IL Wage Payment and Collection Act | Hours worked, rate of pay, overtime hours and pay separately, gross + net wages, year-to-date wages, all deductions | 2% per month interest + 1–5% damages |
| Massachusetts | M.G.L. c.149 §148 | Wages "in full" each pay period, with itemized statement showing all deductions; weekly or bi-weekly pay frequency required for most workers | Treble damages + attorney's fees (mandatory) |
Tessa's Oregon-specific gap was the missing pay rate on her 2024 stubs. Under ORS 652.610, that single missing field on each of Mira's 26 biweekly stubs could in theory expose Tessa to penalties of up to $26,000. BOLI rarely pursues a small employer for a good-faith template error if corrected promptly, but the exposure exists. The digital paystub generator she switched to included the pay rate field by default, which is the kind of detail that drives the platform shift in the first place.
Tessa's Before/After Math
The bottom-line driver for most small employers isn't the regulatory risk — it's the hours. Tessa tracked her own payroll-admin hours for three months before the switch and three months after.
| Cost-of-time line item | Manual (Excel + paper) | Digital (paystub generator + cloud folder) | Monthly time saved |
|---|---|---|---|
| Punch hours from time card to Excel | 90 min/month | 0 min (time-tracking app auto-syncs) | 90 min |
| Hand-calculate overtime for partial weeks | 25 min/month | 5 min (review only) | 20 min |
| Type each paystub from Excel into Word template | 75 min/month | 10 min (generator pre-fills) | 65 min |
| Print, file, photocopy each stub | 30 min/month | 0 min (auto-archived to cloud) | 30 min |
| Reconcile to bank, fix typos | 35 min/month | 8 min (system flags mismatches) | 27 min |
| Quarterly 941 prep (¼ of total = monthly equivalent) | 30 min/month | 12 min | 18 min |
| Respond to employee paystub requests | 75 min/month | 10 min (employees self-serve) | 65 min |
| Total monthly payroll-admin time | 360 min (6.0 hrs) | 45 min (0.75 hrs) | 315 min (5.25 hrs) |
At an opportunity cost of $25/hour (what Tessa estimates her time is worth running the bakery instead of doing payroll), the manual system cost her $150/month or $1,800/year in time alone. The digital system cost her $89/month for the paystub generator + time-tracking app combination, or $1,068/year. Net annual saving: roughly $732 in pure time-cost terms, plus the reduced exposure on the ORS 652.610 itemized-statement requirement and the elimination of the two-evening scramble when Mira needed loan paystubs.
The numbers scale aggressively. A 5-employee operation typically saves 12–18 hours/month at the same per-employee admin rate. A 15-employee operation typically saves 35–50 hours/month. The fixed cost of the digital stack (paystub generator + time-tracking + cloud storage) is roughly the same whether you have 2 employees or 20, so the savings curve gets steeper with each hire. For an in-depth treatment of why digital paystubs are the operative format in 2026, see why digital paystubs matter more in 2026.
Separate Files, Separate Retention
Mixing contractor records and employee records is one of the most common mistakes small employers make on the manual side. Under the IRS classification framework (see W-9 vs W-2 for the full breakdown), each side has its own record set and retention period.
| Record type | W-2 employee | 1099 contractor | Federal retention | Where Tessa keeps it |
|---|---|---|---|---|
| Identity form | Form W-4 (filed with employer day one) | Form W-9 (collected before first payment) | 4 years after the tax year | Encrypted cloud folder per worker |
| I-9 | Required for every employee | Not required for contractors | 3 years after hire OR 1 year after termination, whichever is later | Separate I-9 folder (USCIS audit standard) |
| Pay record | Paystubs each pay period | Invoices + payment records | 3 years (FLSA) / 4 years (IRS) | Cloud paystub archive vs. AP folder |
| Year-end form | W-2 (issued by Jan 31) | 1099-NEC (issued by Jan 31) | 4 years | Annual tax archive |
| Tax remittance | 941 quarterly, 940 annual | None — contractor pays own SE tax | 4 years | Tax folder |
| Workers' comp | Covered employee, premium paid | Not covered (carrier audit verifies) | Policy duration + 4 years | Insurance folder |
| Unemployment | Employer pays SUTA + FUTA | None | Per state UI rules | Tax folder |
Tessa pays her sister-in-law's marketing freelancer (Priya, 1099 contractor) $400/month for social media work. Priya's W-9 is the upstream record; her year-end 1099-NEC is the downstream record. Under the IRS 2026 thresholds, 1099-NEC issuance is required when payments meet the applicable reporting threshold for the year. Priya's $4,800 annual total clears the threshold, so a 1099-NEC issues. None of Priya's records mix with Mira's or Jonas's — separate folder, separate retention clock, separate workers' comp treatment. Tessa's old paper system kept everything in the same Manila folder marked "Payroll." That mix would have failed an unemployment-insurance audit on day one.
Twelve-Point Self-Check
Before the next IRS, DOL, or state-agency request lands, a small employer should be able to answer "yes" to all twelve of the following. The list maps to fields the IRS Publication 15 and DOL Fact Sheet 21 actually verify.
- Every employee has a current W-4 on file (and every contractor has a current W-9)
- I-9s exist for every employee, stored separately from other records, and reviewed against the retention rule (3 years from hire or 1 year from termination, whichever is later)
- Every paystub shows all FLSA §516.2 fields plus all state add-ons
- Hours worked are documented daily for every non-exempt employee
- Overtime is calculated at 1.5x the regular rate (which includes non-discretionary bonuses) for hours over 40 in the workweek
- 941s have been filed every quarter and reconcile to W-2 totals at year-end
- 940 has been filed annually and matches state UI base reports
- Each W-2 Box 1, Box 3, and Box 5 reconcile to the December final paystub YTD totals
- Each 1099-NEC reconciles to the AP record for the contractor (no payments missing, no double-counts)
- The retention schedule names every record type, its retention period, and its storage location
- Digital records have a backup destination and an access-control policy
- A "documents under request" process exists for employees who need historical paystubs (target: same-day for current year, 48 hours for prior years)
Tessa's first run through the self-check after migration scored 10 out of 12. The two she missed: she hadn't documented her workweek anchor (Sunday 12:01 AM) and she hadn't formalized the documents-under-request process. Both fixes took under an hour. The companion piece on the IRS March 2026 rule compliance plan walks through the same audit-readiness framework with the 2026 rule overlay.
Eight Mistakes That Cost Small Employers
Most small-business recordkeeping failures aren't sophisticated. They're the same eight mistakes that show up in DOL and IRS audit notes every year.
- Mixing 1099 contractor files with W-2 employee files in the same folder system
- Missing state-specific paystub fields (Oregon pay rate, California sick-leave balance, NY allowances)
- No daily-hours log for hourly employees, only a weekly total
- Using gross-only paystubs that don't break out deductions (federal, state, FICA, voluntary)
- No written retention schedule, leading to records destroyed before the retention period or kept indefinitely
- Paper-only "just in case" — every record on paper, no backup, no access control
- Informal payment methods (Venmo, cash, check from personal account) that bypass payroll and never make it to records
- No W-4 on file before the first paycheck, leading to default withholding errors and CP2100 notices later
The fix for every item above is the same: a structured digital paystub format that mirrors FLSA §516.2 and the applicable state statute, a cloud folder with retention tags, an access-control policy that limits payroll data to the owner + accountant, and a written process for collecting W-4, W-9, and I-9 before any payment is made. For employees who need to access their own historical paystubs without going through the owner, see paystub access in 2026.
Week 1 — Inventory and choose the stack
- List every record currently kept (time cards, paystubs, 941s, W-2s, W-4s, I-9s, W-9s, 1099s, deduction authorizations)
- Identify each record's current storage location (folder, drawer, email inbox, spreadsheet)
- Decide on time-tracking, paystub generation, cloud storage, and backup destination
- Pull current-year FLSA + state statute requirements into one reference page
Week 2 — Define the retention schedule
- Write down each record type's retention period (FLSA 2–3 years, IRS 4 years, state varies)
- Name the primary storage location and the backup location for each
- Document the access-control policy (who can read, write, delete)
- Create the folder structure: by year → by quarter → by employee
Week 3 — Migrate prior 12 months
- Re-render the prior 12 months of paystubs into the new format using real payroll data
- Reconcile each re-rendered stub to the original bank transfer
- Save the originals as backup (do not destroy until the retention period expires)
- Address any gaps (missing W-4, missing pay rate field, missing daily hours) proactively
Week 4 — Parallel run and cut over
- Run the next pay period through BOTH the old system and the new system
- Reconcile the two systems to the penny; resolve every discrepancy before cut-over
- Issue the next pay period digitally only
- Archive the paper system in a labeled, dated bin
- Update the employee handbook with the new process
Tessa completed the four-week sequence between February 9 and March 8, 2026. The biggest unanticipated friction was the W-4 re-collection step: Mira's 2023 W-4 wasn't in the file, and Tessa had to ask her to fill out a new one. Awkward but trivial. Every subsequent month has been cleaner.
Copy, paste, and fill the bracketed fields. The schedule below lives in the front of every record folder (digital or physical) and is reviewed annually.
Tessa's version of this schedule lives in the first PDF of her cloud payroll folder, dated March 8, 2026, with her next review scheduled for March 2027. The discipline of the annual walk-through is what keeps the system from drifting back into the manual mess that drove the switch in the first place. For the small-business recordkeeping checklist that mirrors this template, see small business payroll recordkeeping checklist.
What is the absolute minimum a small employer must keep under federal law?
Under 29 CFR §516.2 , every employer covered by the FLSA must keep, for every non-exempt employee, the following: full name, address, SSN, sex, occupation, date of birth if under 19, time and day each workweek begins, hours worked each day, hours worked each workweek, basis of wage payment (hourly, salary, piece rate), regular hourly rate, total straight-time and overtime earnings for each workweek, total additions/deductions from wages, total wages paid each pay period, and date of payment plus pay period covered. Retention is three years for payroll records and two years for underlying time records and wage-rate computations. The IRS layer on Publication 583 extends the retention on employment-tax records to four years.
Do I need to issue paystubs at all? FLSA doesn't explicitly require it.
Correct — FLSA itself doesn't require an itemized paystub. But every state with a payday statute (which is almost every state) does require an itemized statement, and the DOL state payday law page maps the requirements state by state. In practice, if you have any non-exempt employees in any state with an itemized-statement requirement (Oregon, California, New York, Illinois, Massachusetts, Texas, and most others), you're issuing paystubs whether FLSA names them or not. The safer rule: assume every state requires an itemized paystub and let any exceptions surprise you in your favor.
Can a spreadsheet plus a Word template satisfy these requirements?
Technically yes — the regulations are medium-neutral. Practically, it's where most small employers fail. The most common failure points are missing fields (Oregon pay rate, CA sick-leave balance, NY allowances), inconsistent retention (some periods kept, some lost), no daily-hours log for hourly workers, no audit trail when corrections are made, and no backup. A structured digital paystub system avoids those failure modes by default. If you're below five employees and your records have always reconciled, the manual stack can work. The transition point for most small employers is the fifth hire or the first state-agency document request, whichever comes first.
How long do I really need to keep pay records?
Federal floors: FLSA payroll records 3 years, FLSA underlying time records 2 years, IRS employment-tax records 4 years, EEOC records 1 year for non-charged employees, 3+ years if a charge is filed. State statutes vary — California requires 4 years on most wage records under Labor Code §1174, Oregon requires the term of employment plus 3 years under ORS 652.610. The safe planning horizon for a small business is 7 years, which clears every federal and state floor and aligns with the IRS general statute of limitations on unreported income.
What changes for my recordkeeping if I switch from W-2 employees to 1099 contractors?
A lot. The two record sets shouldn't sit in the same folder. W-2 employees require W-4, I-9, daily hours log, paystubs, 941s, 940, workers' comp, SUTA, FUTA, and W-2 issuance. 1099 contractors require W-9, invoices, payment records, 1099-NEC issuance (when the year's payments meet the applicable threshold under IRS Form 1099-NEC instructions ) — but no I-9, no daily-hours log, no payroll tax remittance, and no workers' comp coverage. Misclassifying an employee as a contractor to avoid these records is the most common small-business audit trigger and exposes the employer to IRC §3509 reclassification penalties plus state-level penalties.
What state add-ons surprise small employers most often?
Five recurring ones. California Labor Code §226 requires nine specific fields on every paystub, including a sick-leave balance. New York Labor Law §195 requires a wage notice at hire (separate from the paystub) and updated if wages change. Oregon ORS 652.610 requires the pay rate on every itemized statement. Illinois requires year-to-date wages on every paystub. Massachusetts requires "wages in full" each pay period and treble damages are mandatory for non-payment violations under M.G.L. c.149 §150. Check the statute that applies in every state where you have an employee, not just the headquarters state.
How does the 2026 IRS guidance change anything?
The March 2026 IRS guidance tightened expectations around electronic payroll records and the audit trail that supports them — see the IRS March 2026 rule, part 1 for the operative changes. For most small employers, the practical impact is documentation of who entered each payroll record and when, and a clearer expectation that paper-only systems are no longer the default-safe option. If your current system already produces structured digital paystubs with timestamps, you're likely already compliant; if you're still on paper or unformatted spreadsheets, the guidance is the cue to migrate.
What's the single best first step if I'm still on paper?
Inventory. Spend two evenings listing every record you currently keep, where it lives, who can access it, and what's missing. Most small employers discover one or two records they've lost track of entirely (a 2023 W-4, an old deduction authorization, last year's I-9 for an employee who left) and one or two fields they've been missing on stubs all along. The inventory is the document that drives every other decision in the transition — system choice, retention schedule, migration scope. Without it, the rest is guessing. — David Whitaker, Paystub & Payroll Editor at MyStubs. David covers paystub anatomy, gross-to-net calculation, federal and state tax stacks, payroll recordkeeping, and the income documentation underwriters credit for mortgages, auto loans, and credit cards.
Official sources
Sources · 17 references
- U.S. Department of Labor — Fact Sheet 21 (FLSA Recordkeeping)
- 29 CFR §516.2 — Records Employers Must Keep
- 29 CFR §516.5 — Records to be Preserved 3 Years
- 29 CFR §516.6 — Records to be Preserved 2 Years
- Internal Revenue Service — Publication 583 (Starting a Business and Keeping Records)
- Internal Revenue Service — Publication 15 (Employer's Tax Guide)
- Internal Revenue Service — Recordkeeping for Small Businesses
- Oregon Revised Statutes — ORS 652.610 (Itemized Statement of Earnings)
- California Labor Code §226 (Itemized Wage Statements)
- New York Labor Law §195 (Wage Notice and Paystub Requirements)
- Illinois Wage Payment and Collection Act
- Massachusetts General Laws c.149 §148 (Payment of Wages)
- U.S. Department of Labor — State Payday Requirements
- Internal Revenue Code §6051 (W-2 Information Returns)
- Internal Revenue Service — About Form SS-4 (EIN)
- Internal Revenue Service — About Form W-9
- Internal Revenue Service — About Form 941 (Quarterly Federal Tax Return)
Discussion
No comments yet — be the first to share a state-specific note, a follow-up question, or a correction.