Eight Employee Record Retention Mistakes That Fail Audits in More Than One Country
Delete payroll too early and you fail a tax or labor inspection. Keep CVs and sick notes too long and you breach data-protection law. Eight retention mistakes that cause both, and how to fix each one.
Using one retention period for every HR record
Most HR record-retention failures come from one of two problems. A tax inspector asks for payroll from six years ago that you've already deleted. Or a data-protection regulator asks why you still hold CVs from candidates you rejected a decade ago. Employee record retention requirements come from at least three bodies of law: tax and social security, labor inspection, and data protection. They pull in opposite directions. The first two set minimum periods. The third sets a ceiling: keep personal data only as long as you need it for a stated purpose.
The common shortcut is a blanket rule such as "we keep everything for seven years." It fails in both directions at once. Seven years is too long for unsuccessful candidates, where UK and EU data-protection authorities generally expect months, not years. It can be far too short for some occupational health records. Under UK and EU rules on hazardous substances, health surveillance and exposure records can need to be kept for decades.
What to do instead: build the schedule by record class, not by employee. For each class, write down six things: the record class, the legal basis for keeping it, the event that starts the clock, the retention period, the business owner, and the disposal method. A 50-person company typically ends up with somewhere between 15 and 30 classes. That's manageable in a spreadsheet before you touch software.
HRIS check: ask whether retention rules can be set per document type or data category, or only per employee profile. If the system can only delete a whole employee record, you'll be forced back into a blanket period.
Copying headquarters rules into every country entity
A company headquartered in London or Bangalore opens a Dubai or Singapore entity and applies its home-country schedule. This is the second most common mistake, and it surfaces when a local labor inspector or tax authority asks for documents in the local format and for the local period. Retention periods differ widely, even between neighboring countries.
The table shows indicative minimums for common record types. They're simplified, rules change, and sector-specific obligations often add to them. Use it as a starting checklist for local counsel or your payroll provider, not as the final answer.
| Country | Payroll and tax records (indicative) | Employment and personnel records (indicative) |
|---|---|---|
| United Kingdom | PAYE records: at least 3 years after the end of the tax year | Right-to-work copies: whole employment plus 2 years after it ends |
| Germany | Roughly 6 to 10 years depending on document type | No single period. Usually tied to limitation periods for claims |
| France | Payslip duplicates: around 5 years | Staff register entries: around 5 years after the employee leaves |
| Netherlands | Tax-relevant records: typically 7 years | ID copies for wage tax: kept with the payroll record for several years |
| India | Tax records often 6 to 8 years; wage registers were 3 years under older statutes | Registers are being consolidated under the new labor codes. Confirm current state rules |
| United Arab Emirates | Tax records: generally around 5 to 7 years | Employee files: a minimum period after employment ends under federal labor law. DIFC and ADGM have their own data rules |
| Singapore | Tax-related records: typically 5 years | Employment Act records: current staff, plus a short period after an employee leaves |
| Philippines | Tax records: often longer than labor minimums | Employment records: typically a few years under labor rules |
What to do instead: keep one global schedule template and add a country column for each entity. When two rules apply, the longer legal minimum wins. Data minimization starts only after that minimum has expired.
HRIS check: confirm that retention rules can be scoped by legal entity or country. Enterprise suites such as SAP SuccessFactors and Workday are built for this. Some mid-market tools only allow company-wide settings, so ask for a demonstration rather than a feature-sheet tick.
Purging payroll at the labor-law minimum and forgetting the tax clock
Labor-law minimums are often the shortest periods in the schedule. Teams that read only the employment statute delete payroll data too early. Singapore illustrates it: employment records are required for a short period after an employee leaves, but the tax authority expects supporting records for longer. Social security bodies add their own clocks: GOSI in Saudi Arabia, EPF and ESIC in India, and pension funds across Europe.
There's a second trap. Tax authorities can usually reopen assessments, and those windows can stretch if an audit is open or fraud is alleged. Deleting at exactly the minimum leaves no room for either.
Hypothetical example: say a 60-person company has entities in the UK, the Netherlands and Singapore. Its payroll vendor deletes data three years after each tax year in every country. That may satisfy UK PAYE rules. It likely falls short in the Netherlands and Singapore, and the gap only shows when a tax office asks for year five.
What to do instead: for each country, take the longest of the tax, social-security and labor periods. Add a buffer of three to twelve months to cover audit windows, then delete.
HRIS check: payroll data often sits with a separate provider such as ADP, Deel, Papaya Global or a local bureau. Get each provider's retention and export terms in the contract, including what happens to your data if you leave.
Treating right-to-work and ID copies as permanent personnel file content
Passport scans, visa pages, work permits and national ID copies are among the riskiest documents an employer holds. Companies get them wrong in both directions. Some delete them at onboarding and can't prove they made the check. Others keep them in the personnel file forever.
The UK sets a clear rule: keep evidence of the check for the whole employment and two years after it ends. The Netherlands ties ID copies to the wage-tax record. In the Gulf, the employer usually sponsors work permits and residence visas, so records follow immigration and labor procedures as well as data-protection law. The UAE's federal data-protection law, Saudi Arabia's PDPL, and DIFC and ADGM rules all limit how long you keep personal data.
What to do instead:
- Store identity and immigration documents in a restricted category, separate from performance and pay records.
- Start the retention clock at the employee's leaving date, not the upload date.
- Record that the check was done (date, document type, reviewer) as a separate entry. In some countries the log can outlive the scan itself.
HRIS check: can the system delete a document type automatically a set number of months after termination while keeping the check log? Test it with a dummy leaver before you rely on it.
Filing medical and sickness data in the general personnel file
Sick notes, fit-for-work assessments, disability accommodations and occupational health reports are special-category or sensitive data in most regimes, including the GDPR, UK GDPR, India's DPDP framework and Gulf data-protection laws. Retention periods for these records vary more than for any other type. A routine sick note might be needed for a year or two to support sick-pay calculations. Exposure records for workers handling hazardous substances can need decades.
When these records sit in the general personnel file, two things go wrong. Line managers see data they shouldn't. And the file's single retention date either deletes long-term health surveillance too early or keeps routine sick notes far too long.
What to do instead: split health data into at least three classes. First, absence and sick-pay evidence, kept as long as the sick-pay and tax periods require. Second, accommodation and disability records, kept for the employment plus the limitation period for discrimination claims. Third, statutory health surveillance, kept for the period the regulator sets. Have an occupational health provider hold clinical detail, and give HR only the fitness outcome. This article doesn't cover clinical record-keeping obligations; confirm those with your provider and employment counsel.
HRIS check: look for field-level or document-level permissions and a separate retention rule for health documents. If the only control is "HR admin sees everything," the system isn't fit for this data.
Keeping exit and candidate files indefinitely "in case of a claim"
"We might get sued" is the most common reason for keeping files past their retention date. It's legitimate only when tied to a real limitation period. In the UK and much of Europe, contract claims typically run for several years, while discrimination and unfair-dismissal claims often have much shorter filing windows. Many Asian and Gulf jurisdictions also set specific deadlines for labor complaints. Keeping an exit file for 15 years "just in case" goes beyond what most of these rules can justify, and regulators enforcing storage limitation treat it as excessive.
Candidate data is worse. Rejected applicants' CVs, interview notes and assessment results pile up in applicant tracking systems for years. Guidance from European regulators generally points to months after the hiring decision, unless the candidate agrees to join a talent pool.
What to do instead: split the exit file in two. Part one is the minimum needed to defend a claim: contract, final pay, termination letter, disciplinary or performance records relevant to the exit, and any settlement agreement. Keep it for the longest relevant limitation period plus a short buffer. Part two is everything else, such as old appraisals, training certificates and routine emails. Delete it sooner. For candidates, a common starting point is six to twelve months unless local guidance says otherwise, with explicit consent for talent pools.
HRIS check: most applicant tracking systems, including Greenhouse, Workable, Teamtailor and SmartRecruiters, offer candidate data-retention settings. Confirm they're switched on and configured; defaults vary.
Starting the clock at the wrong event and forgetting the copies
A retention period without a defined starting point can't be enforced. "Seven years" could mean from document creation, from the end of the tax year, or from the employee's leaving date. For long-serving staff those can be a decade apart. Payroll periods usually run from the end of the tax or financial year. Personnel file periods usually run from the leaving date. Health surveillance often runs from the last exposure.
The other half of this mistake is assuming the HRIS holds the only copy. Copies of the same data tend to sit in:
- payroll exports saved to shared drives,
- spreadsheets managers keep for bonus planning,
- email attachments (offer letters, sick notes, ID scans),
- backups and archives of a previous HR system after a migration.
What to do instead: give every record class one named trigger event. Then run a data map once a year: ask each department where HR data lives outside the system of record, and add those locations to the deletion procedure. For backups, document how long they're kept before being overwritten. Regulators commonly accept that backups age out on a fixed cycle rather than being edited, provided the data isn't restored for other uses.
HRIS check: confirm that retention can be triggered from a date field such as termination date or tax-year end, not just upload date. Ask how deletion works in the vendor's own backups and audit logs.
Switching on HRIS auto-deletion without holds, logs or testing
Automated purging is the right goal, but switching it on without safeguards creates a new risk: deleting records under a legal hold or an open tax audit. In most legal systems, destroying records after a dispute is reasonably foreseeable is treated more harshly than keeping them too long.
Before you rely on automation, check four things:
- Legal hold: can you freeze deletion for a named employee, entity or record class, and can only authorized people lift the hold?
- Deletion log: does the system record what was deleted, when, and under which rule, without keeping the personal data itself? Auditors will ask for this.
- Pre-purge review: does it list records due for deletion and let HR approve them first?
- Scope: does deletion reach attachments, comments, custom fields and integrated payroll or benefits modules, or only the core profile?
Cost matters here. Configurable retention, legal hold and audit logging sometimes sit in higher plan tiers or compliance add-ons. Typical 2026 market ranges for mid-market HRIS platforms run roughly $6 to $25 per employee per month, while enterprise suites are quoted individually. Prices vary by contract, country and module, so confirm with vendors. A multi-country schedule review by outside counsel adds a one-time cost that grows with the number of countries.
Decision rule: if your HRIS can't scope retention by country and record type, place legal holds and log deletions, run the purge manually each quarter from your schedule until it can. Your next step: export a list of every record class in your HRIS, map each to the six schedule fields, and take countries with no confirmed periods to local counsel first.
Questions buyers ask
How long should we keep personnel files after an employee leaves?
There's no single global answer. Most employers keep the core file for the longest relevant claim limitation period in each country, often somewhere between two and six years, plus a short buffer. Records with longer statutory periods, such as payroll and health surveillance, are kept separately for their own periods. Confirm the periods with local employment counsel.
Does data-protection law override tax or labor retention rules?
Generally, no. The GDPR, UK GDPR, India's DPDP framework and Gulf data-protection laws all allow you to keep data that another law requires you to keep. What they stop is keeping it longer than you need, so once the legal minimum and any active-claim period have passed, delete or anonymize the data.
Can we just keep everything for ten years to be safe?
That swaps tax risk for data-protection risk. Ten years is excessive for most candidate data, routine sick notes and ID copies, and regulators can penalize employers for holding stale personal data. A schedule broken down by record class is safer and usually cheaper to run.
Who should own the retention schedule: HR, finance or legal?
Usually HR owns the schedule, finance owns payroll and tax record classes, and legal or the data protection officer approves it and manages legal holds. What matters is that each record class has one named owner. Review it at least once a year and whenever you open an entity in a new country.
What should we ask an HRIS vendor about retention during evaluation?
Ask whether retention rules can be set by country, legal entity and document type. Ask what event can start the clock, whether legal holds and deletion logs are included, and whether deletion covers attachments and integrated modules. Also ask which plan tier includes these features and how the vendor handles deletion in its own backups.
Written by the Staff Fund Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.