Holiday Pay Records: Configuring Retention So Six Years Is Actually Achievable

Six years of holiday pay records sounds like a storage problem. In practice, it is a configuration problem. Most employers already capture the leave and the pay; the gap is that the evidence sits scattered across payroll runs, spreadsheets and folders, and cannot answer a question about a two-year-old payment in minutes.

From 6 April 2026, employers must keep adequate records of annual leave and holiday pay for at least six years from the date they were made. That shift makes retention a setting in your leave management system rather than a habit kept in a filing cabinet. The sensible default is to retain and version each record, not delete it once the payslip is issued. Records can be kept in any reasonable format, so the question is not whether a system can hold them, but whether it holds everything the law requires.

This post sets out what each holiday record must hold, by leave year, then works through three steps: setting retention to keep and version, tying every leave record to the pay actually calculated and the policy version in force, and testing that the retained set is complete. It closes with configuration tips, common pitfalls, and where to start before April 2026.

The Six-Year Rule Is a System Setting, Not a Filing Cabinet

From 6 April 2026, employers must keep records of annual leave and holiday pay for at least six years from the date they were made, as Acas guidance on keeping holiday records sets out. Most organisations still treat this as a payroll folder, emptied once the payslip is issued.

That habit breaks when a query arrives about a leave year two or three years back. The export is gone, and Azets reads the six-year window as aligning with limitation periods, so holiday pay questions can surface long after the pay run.

The record must also evidence the entitlement itself. Most workers get 5.6 weeks’ paid holiday a year: 28 days for a five-day week and 16.8 days for someone working three days a week, per GOV.UK. Every record has to prove that baseline against the pattern actually worked.

Enforcement sits with the Fair Work Agency, which can require records to be produced and issue penalty notices. Acas is more conditional: failure to prove records “could be” a criminal offence, with “likely” unlimited fines. Hold both registers rather than one confident claim.

So this is a configuration task, not a record-keeping chore, and it gets harder where a workforce spans several countries, as managing leave across borders shows. The four decisions ahead: what a record holds, how long it stays, how it ties to pay and policy, and how completeness is tested.

What Each Holiday Record Must Hold, by Leave Year

With the retention rule framed as a system setting, the first configuration decision is content.

Acas lists four required items: holiday taken, holiday carried over from previous leave years, holiday pay, and payments in lieu of holiday when someone leaves. Each is a distinct field, not a line on a payslip. A single total evidences none of them individually.

For holiday pay, the record must show what the payment included, such as bonuses or commission. Azets adds salary, overtime, commission, bonuses and allowances as the regular or contractual components in play. When those components change, whether through the 2026 Budget or an internal pay review, the record still has to show what applied at the time.

One Record Per Worker, Per Leave Year

The structure to configure is one record per worker per leave year, with entitlement, taken, carried over and paid tracked as separate values. This is a design recommendation rather than a statutory format, but it is what allows a later query to be answered without reconstructing the calculation.

Acas states that records can be kept in any reasonable format, including an online system, and that an existing payroll system counts if it holds everything the law requires.

In practice, that means configuring the fields once so the leave and pay processes populate them, rather than typing them in afterwards. In Activ People HR, this configuration sits within leave and absence management. A complete retained set is also the foundation of HR data that tells a story.

For international employers, one further rule applies. Where several leave types run side by side, such as ROL in Italy or RTT in France, each balance needs its own record lines so holiday pay for one type is never mixed with another.

Step 1: Set Retention to Keep and Version, Not Delete

The previous section defined what a record holds; this step decides how long it survives. The default to change is deletion. Many configurations clear a leave record once the payslip is issued, which is precisely the habit the six-year obligation rules out: records must be kept for at least six years, and ‘at least’ makes six years a floor, not a tidy-up trigger.

The start of the clock deserves pinning down. Acas says retention runs ‘from the date they were made’; Azets says ‘from the date they are created’. Apply the conservative reading, so the earliest plausible interpretation governs and an audit cannot argue the window opened later than you assumed.

Expressed as configuration, retention in a leave management system needs three settings:

• A retention window defined per record type, not globally.
• A rule that blocks deletion while a record is still inside its window.
• Export capability, so a record can be produced on request without being rebuilt.

Versioning sits alongside those settings. Where a holiday pay calculation is corrected, the superseded version stays readable instead of being overwritten, so the calculation originally applied remains demonstrable. This is a design recommendation, not a legal requirement; no source prescribes versioning. It is simply how a leave system management setup makes six years achievable, much as a training record’s expiry date is what makes it an early-warning system rather than a stored file.

Backfill is the awkward part. Records created before 6 April 2026 still need to be reachable, and Azets recommends electronic systems covering records created before and after that date. Earlier leave years therefore have to be loaded, not left in a previous system. With the window set, the next step is deciding what each retained record points to.

Step 2: Tie Every Leave Record to the Pay Calculated and the Policy in Force

Step 1 keeps the record alive. Step 2 makes it answerable.

A leave record that shows days taken but not the pay those days produced cannot answer whether bonuses, commission or overtime were included. Each leave record should point to the pay calculation it generated and to the policy version that governed it, so both are retrievable together rather than reconstructed from a payroll export.

The pay elements must stay visible as separate values: salary, overtime, commission, bonuses and allowances. Acas requires holiday pay records to show what is included, such as bonuses or commission, and sets out how bonus treatment depends on the basis of the bonus. The calculation basis, not just the amount, therefore belongs in the record.

When a holiday pay policy or a leave allocation rule is updated, the version in force at the time of the leave stays attached to that leave record. The same discipline applies to wider absence policy changes, such as those covered in our guide to Day-One Statutory Sick Pay: Rebuilding Your Absence Rules.

Where employees use one system as a frontend and data is mastered in an enterprise platform, decide explicitly which side is the retained record of authority. Two partial copies satisfy nobody. Activ People HR is commonly used this way by corporate customers.

Linking records to payslips and policy versions is a recommended design pattern, not a legal requirement. No source prescribes it; it is what makes the six-year obligation answerable. Treat answering a two-year-old query quickly as the design goal, not a measured service level.

Step 3: Test That the Retained Set Is Complete

With pay and policy linked, the remaining question is whether the retained set is complete. Guidance recommends auditing records and checking the four-week pay elements, but stops short of a test method. Treat the four checks below as a proposed routine.

Population test. For a chosen leave year, compare headcount with the number of workers holding at least one leave record and one pay record. Investigate every worker with neither. Gaps usually signal a missed starter, leaver or transfer.

Field-completeness test. Confirm each record holds holiday taken, holiday carried over, holiday pay and any payment in lieu. Check that pay elements are evidenced individually, not collapsed into one figure.

Query test. Pick a leave year two years back and reconstruct one worker’s holiday pay from the retained record alone. Any step requiring guesswork is a configuration gap, not a search problem.

Retention test. Confirm the deletion rule removes no record still inside its six-year window, and that backfilled years behave the same way as new ones.

An hr leave management software setup that passes these four checks turns retention from an annual panic into a routine audit. Keep the test output as evidence the set is complete, applying the same discipline as an audit-ready employee file.

Configuration Tips and Common Pitfalls

A complete set is only as good as the configuration beneath it. Six pitfalls account for most failures.

Ambiguous retention start. Acas frames the six-year clock as running “from the date they were made”; Azets says “from the date they are created”. Apply the earliest plausible start so either reading is satisfied.

The payslip treated as the record. A payslip shows what was paid. It does not show holiday taken, holiday carried over, or which pay elements were included. Keep it as evidence of payment, not as the record itself.

Records split across systems. Where one worker’s data sits in more than one place, document which copy is authoritative. The business impact of managing leave in a global company grows with headcount and jurisdictions when that rule is missing.

Part-time and irregular-hours workers. Minimum entitlement scales with the working pattern: a three-day week gives at least 16.8 days. The record must show the scaling calculation, not only the resulting balance.

Multiple leave types in one organisation. Where balances such as ROL in Italy or RTT in France coexist, keep separate records per leave type. A query on one balance should not require unpicking the others.

No re-test after change. A policy update or a system migration can break the link between a leave record and the pay it produced. Add both events to your audit trigger list.

Each pitfall is a configuration decision, not a training issue.

Where to Start Before April 2026

With the pitfalls addressed, the remaining work is verification. Retention is a setting in the leave system, not an instruction to payroll, and six years is only achievable if the record is designed to be kept.

Four actions make that real.

Define the record. Before 6 April 2026, configure the four required fields (holiday taken, holiday carried over, holiday pay, and payments in lieu) plus the pay elements: salary, overtime, commission, bonuses and allowances. Check them against Acas and Azets rather than internal habit.

Set retention to keep and version. Apply the conservative reading of when the six-year clock starts, so the earliest interpretation governs, and backfill earlier leave years so they remain reachable. Give it a review cadence, in the same way you would Plan Annual Leave Effectively each year.

Link leave to pay and policy. Every leave record should point to the pay calculation it produced and the policy version in force. Then run the four completeness tests and keep the results as audit evidence.

Audit now. Review current records while gaps can still be corrected without pressure. Where a configurable leave management system is already in place, treat the retention rule as configuration to verify rather than a project to start.

Conclusion

The six-year rule lives in configuration, not in a filing cabinet. To make it achievable, define the required holiday and pay fields, set retention to keep and version from the earliest possible clock start, link every leave record to the pay calculation and policy version in force, and prove completeness through the four tests. Those choices turn retention from an instruction into a reliable record. The next step is a practical audit before April 2026: review current holiday pay records, correct gaps while there is still time, and verify that your leave management system is configured to preserve versioned evidence. Do this now and audit readiness stops being a scramble. It becomes a repeatable process that protects both payroll accuracy and compliance confidence.