Multistate HR Records Retention: Resolving Conflicting Rules

HR records retention schedule for employees in multiple states

When federal and state records retention rules conflict, keep each record for the longest period that applies to it, based on every state where the employee worked while the record was created. Federal law sets floors, not ceilings. New York, for example, requires six years for payroll records, double the federal three.

This guide is for HR, payroll and HRIS teams at employers with staff in more than one state, especially those setting up automated deletion rules.

Key takeaways

  • Federal rules are minimums. A longer state rule controls for employees who work in that state.
  • The retention period is only half the rule. The trigger event (record date, hire, termination, filing date) decides when the clock starts.
  • Track work location history, not just current location, or a relocated employee's older records can be deleted too early.
  • A litigation hold must override every automated deletion rule.
  • Some popular "rules" are really statute-of-limitations habits. Label them as policy choices, not legal requirements.

Why does the longest period always win?

Federal recordkeeping regulations tell you how long you must keep something at a minimum. They don't stop a state from requiring more. So when a New York employee's payroll record is covered by both the Fair Labor Standards Act and New York Labor Law, you meet both only by keeping it for New York's six years.

The same logic applies across states. If an employee worked in New York for two years and then moved to Florida, the payroll records created while they were in New York still carry New York's period. A policy keyed only to the employee's current state will get this wrong.

There are two kinds of "longer than federal" periods, and it helps to keep them apart:

  • Legal minimums. A statute or regulation says "keep for at least X years." These are non-negotiable.
  • Defensive periods. No rule requires them, but you keep records long enough to defend claims that can be filed later, often matched to a statute of limitations. These are policy choices you should document as such, with counsel's input.

A common mistake we see is a retention schedule that mixes the two without saying which is which. When an auditor or a court asks why something was destroyed, "our policy said so" is much stronger when the policy shows its reasoning.

What are the federal floors for common HR records?

These are the main federal minimums for private employers, with the trigger that starts the clock.

RecordFederal minimumClock startsAuthority
Payroll records (FLSA)3 yearsLast date of entry29 CFR 516.5
Time cards, wage rate tables, wage additions and deductions (FLSA)2 yearsLast entry or last effective date29 CFR 516.6
Payroll records (ADEA)3 yearsRecord date29 CFR 1627.3
Applications, hiring, promotion, discharge records (Title VII, ADA, GINA)1 yearLater of record date or personnel action; longer if a charge is filed29 CFR 1602.14
Form I-93 years after hire or 1 year after employment endsWhichever is laterUSCIS M-274
FMLA records3 yearsRecord date29 CFR 825.500
OSHA 300 Log, annual summary, 301 forms5 yearsEnd of the calendar year covered29 CFR 1904.33
Employee medical records (OSHA)Duration of employment plus 30 yearsTermination29 CFR 1910.1020
Employee exposure records (OSHA)30 yearsRecord date29 CFR 1910.1020
Benefit plan records supporting ERISA reports6 yearsFiling date of the reportERISA section 107

A few notes on these.

Form I-9 is a dual trigger. USCIS says to keep the form until "three years after the date of hire, or one year after the date employment ends, whichever is later." An employee hired January 1, 2023 and terminated December 31, 2024 hits three years from hire on January 1, 2026 and one year from termination on December 31, 2025. The later date, January 1, 2026, controls. Store I-9s apart from personnel files so a general file review doesn't expose immigration documents. For remote verification options, see our guide to Form I-9 remote document examination.

FMLA medical records go in a separate file. Under 29 CFR 825.500(g), certifications, recertifications and medical histories created for FMLA purposes must be kept as confidential medical records, separate from the usual personnel files. If you're reviewing leave data more broadly, our article on FMLA data patterns that trigger a DOL audit is a useful companion.

Background checks have no federal retention period. The Fair Credit Reporting Act's disposal section, 15 U.S.C. 1681w, deals with how to dispose of consumer report information securely, and says it doesn't itself require anyone to keep or destroy records. Many employers keep reports and adverse action notices for several years to defend claims, but that's a defensive period. Applications and hiring records connected to the check still fall under 29 CFR 1602.14.

Charges change everything. Once a discrimination charge is filed, 29 CFR 1602.14 requires keeping all relevant records, including those of other candidates for the same position, until final disposition of the charge or any lawsuit.

Where do state rules go further?

State rules vary widely, and this section covers three states that often drive multistate schedules. Use it as a pattern, not as a complete list; confirm every state you operate in with counsel or the state agency.

RecordFederal floorCaliforniaNew YorkIllinois
Payroll records3 years (FLSA)3 years under Labor Code 1174(d); unemployment insurance rules require 4 years after a wage payment on which contributions are due6 years (Labor Law 195(4))3 years (820 ILCS 105/8)
Itemized wage statementsCovered by payroll rules3 years (Labor Code 226)Covered by 6-year payroll ruleCovered by payroll rule
Applications and personnel records1 year (29 CFR 1602.14)4 years (Government Code 12946)Check state rulesCheck state rules

California details come from Seyfarth's Cal-Peculiarities 2025 summary, which also suggests keeping wage statements for at least four years because of the four-year limitations period for unfair business practice claims. That's a defensive period, but a sensible one.

New York's rule is plain: employers must "establish, maintain and preserve for not less than six years" payroll records (NY Labor Law 195). For any employee who has worked in New York, that's your payroll baseline.

Workers' compensation records are governed by state programs with their own retention rules, often tied to the date of injury or claim closure. Pull those from each state's workers' compensation agency instead of assuming one national period.

If you also run payroll across states, the same location logic applies to tax setup; see how to run multi-state payroll with conflicting tax rules.

What starts the retention clock?

Most early-deletion mistakes come from the wrong trigger, not the wrong period. A six-year rule that starts at hire instead of at the record date can delete records years too soon for long-tenured employees.

  • Record date or last entry: FLSA payroll records and time cards, FMLA records, ADEA payroll records, OSHA exposure records.
  • End of calendar year: OSHA 300 Log, annual summary and 301 forms.
  • Termination: OSHA medical records (employment plus 30 years). Many employers also choose termination as the trigger for whole personnel files, which is simpler to administer but may differ from the legal trigger for individual documents.
  • Personnel action: Title VII, ADA, GINA and ADEA hiring and personnel records, with the later of the record date or the action under 1602.14.
  • Filing date: ERISA records supporting a report.
  • Later of two dates: Form I-9.
  • Open-ended: any record subject to a charge, lawsuit, investigation or litigation hold.

How should you configure HRIS retention rules?

Most enterprise HRIS and document systems let you set retention by record type and apply conditions. This approach holds up well in audits:

  1. Capture work location history. Record the state where the employee actually worked for each period, not the employer's registered address. Remote workers make this essential.
  2. Build a rule library by record type. For each type, define the period (in days or months to avoid rounding confusion), the trigger event, the jurisdictions it applies to and the legal authority or policy reason. Uniform federal records like I-9s and ERISA records can use one rule; payroll and personnel records need location-aware rules.
  3. Default to the longest applicable period. When an employee has worked in several states, compute the expiry date against every applicable rule and keep the latest.
  4. Add a litigation hold that overrides deletion. Any record tied to a charge, lawsuit, government investigation or internal investigation must be excluded from scheduled disposal until legal releases it. Destroying records under hold invites sanctions.
  5. Run deletion as a reviewed job, not a silent one. Produce a list of records due for deletion, have HR and legal approve it, then delete and log what was destroyed and when.
  6. Document the configuration. Keep a record of when rules were last reviewed, the sources behind them and who approved them.

Retention also matters when you leave a system. Before a contract ends, confirm you can export everything you still have to keep; see what happens to employee data when an HRIS contract ends.

How do you handle the edge cases?

The schedule works for typical employees. These situations are where it usually breaks:

  • Rehires. When a former employee comes back, decide whether their old file is reopened or a new one is created. Either way, records from the first period keep their original expiry dates unless a new action, such as a charge, extends them. For Form I-9, check the M-274 rules on rehires before reusing an old form.
  • Relocations. An employee who moves from Illinois to New York changes the payroll period for records created after the move, not before it. A simple way to handle this is to tag each payroll record with the work state at the time it was created.
  • Employees who work in several states at once. Traveling technicians and regional managers can generate records covered by several states in the same week. Apply the longest period to all of their records rather than splitting them.
  • Acquisitions. Records you inherit come with their original obligations. Map the acquired company's schedule to yours, keep anything subject to a hold, and don't let a system migration silently reset creation dates.
  • Vendor-held records. Timekeeping, background check, benefits and applicant tracking vendors often hold the only copy of key records. Your contracts should require them to keep data for your schedule, honor litigation holds and return data in a usable format when the relationship ends.
  • Records with health information. FMLA certifications, accommodation requests and OSHA medical records all need confidential, separate storage, and some carry very long periods. Give them their own access controls and their own disposal approval step.

When in doubt on any edge case, extend rather than delete, write down why, and ask counsel to confirm at the next review.

What goes wrong when records are destroyed too early?

These scenarios are illustrative, not real cases, but each reflects how missing records hurt employers.

The discrimination charge

A former employee in California says their termination was retaliation for a complaint. The employer's reason was poor performance, documented in reviews. Those reviews were deleted 14 months after termination, which cleared the federal one-year floor but not California's four-year rule for personnel records. Without the reviews, the employer can't show the performance problems predated the complaint, and its position weakens badly.

The wage audit

A state labor department reviews a New York location and asks for payroll records going back six years. The employer kept three, matching the FLSA. It now can't show what it paid for half the period it's being asked about, and it has violated New York's recordkeeping rule on top of whatever the audit finds.

The overtime lawsuit

Hourly employees sue under the FLSA for unpaid overtime. The FLSA allows two years to file, or three for willful violations (29 U.S.C. 255), and FLSA time cards only have to be kept for two years. If time records for part of the claim period are gone, the Supreme Court's rule in Anderson v. Mt. Clemens Pottery applies: once employees show uncompensated work by "just and reasonable inference," the burden shifts to the employer to produce evidence of the precise hours. Without records, approximate damages can be awarded. Keeping time records at least as long as payroll records closes that gap.

What should a written retention policy include?

  • Scope: every entity, location and worker group covered, and every format, including paper, HRIS, email, shared drives and third-party platforms.
  • Retention schedule: record type, period, trigger, legal authority or policy reason, and jurisdictions.
  • Conflict rule: "When more than one requirement applies, the longest period governs."
  • Litigation hold procedure: what triggers a hold, who issues and releases it, how systems and custodians are notified.
  • Disposal procedure: secure destruction for records with personal, health or financial information, with a destruction log.
  • Ownership and review: HR as owner, counsel as reviewer, an annual review, and a review whenever you start employing people in a new state.
  • Training: for everyone who manages records, with acknowledgment.

Retention decisions also feed other compliance work. For example, adverse impact analysis of hiring needs applicant data; see how to self-audit your ATS for disparate impact.

Records retention checklist

  • List every record type you create, including those in payroll, benefits, ATS, timekeeping and safety systems.
  • For each, write down the federal floor and trigger.
  • Add each state where you employ people and note any longer requirement.
  • Mark defensive periods separately from legal minimums.
  • Confirm the HRIS stores work location history.
  • Test the deletion rules on a sample of multistate employees before turning them on.
  • Confirm the litigation hold override works in every system that deletes records.

FAQ

Can we just keep everything forever to be safe?

It's tempting, but it creates its own risks. Every record you keep is discoverable in litigation, has to be protected in a breach, and may conflict with privacy rules that limit how long you hold personal data. A schedule that keeps records for the longest required or justified period, then deletes them on a logged process, is easier to defend than unlimited hoarding.

Which state's rule applies to a remote employee?

Generally, the state where the employee performs the work, not where your headquarters is. If they've worked in several states, records created during each period carry that state's rules, and the simplest safe approach is to apply the longest period among them. Confirm unusual cases, such as employees who split time across states each week, with counsel.

Do these periods apply to electronic records too?

Yes. Retention rules apply to the information, not the format. Payroll data in an HRIS, scanned I-9s, emails about a personnel decision and records in a vendor's platform all count. Electronic storage must keep records accurate, accessible and producible when an agency or court asks for them.

What to do next

  • Pull your current schedule and add a trigger column and an authority column for each record type.
  • Identify every employee with work history in New York or California and check how long their payroll and personnel records are kept.
  • Test your litigation hold in each system that runs automated deletion.
  • Book an annual review with employment counsel and add "new state" as a review trigger.

Sources

This article is general information, not legal advice. Retention rules change; confirm your schedule with employment counsel.

Last reviewed: October 2026.

Comments

Popular Posts

Why Workday Onboarding Breaks Down for Frontline Employees

Are Biometrics Better Than Passwords? What NIST Says

How to Improve the Customer Experience (CX)

How to Market Your Handyman Services to Small Business Owners

Interview Tips for Beginners: A Step-by-Step Prep Plan

Are Mobile Apps Tracking Your Every Move? How to Check

Predictive Scheduling Laws: Where They Apply and How to Comply

How Do I Log In and Sign In to Workday HCM

Multi-State Remote Employees: Payroll Tax Registration Steps

End-of-Day Routines That Boost Productivity at Work