From 6 April 2026, the retention obligation becomes explicit: employers must keep records showing holiday pay and entitlement compliance, including holiday taken, carry-over, holiday pay and payments in lieu, for at least six years from the date they were made. That standard applies whether the worker is still employed or not. The duty starts in April 2026; holiday pay enforcement by the Fair Work Agency is not expected to begin before April 2027.
This post converts that duty into a week-by-week filing model you can actually run. We will cover the new duty, who is covered, what adequate records must show, how the six-year clock works, and why reconstructed spreadsheets fail at tribunal and in payroll audits. Then we will build the record from the rota, step by step: capturing time where work happens, splitting pay elements weekly, recording accrual and carry-over, and closing, dating and storing each week. We will include a worked example and the questions to ask of timesheet software before April 2026, plus where Staffly fits in this model and five actions for your next payroll cycle.
The New Duty in Plain Terms: Records From 6 April 2026
From 6 April 2026, keeping holiday records stops being a payroll habit and becomes a legal duty. The obligation sits inside the Employment Rights Act 2025, which became law on 18 December 2025. Acas confirms employers must keep records of annual leave and holiday pay, not simply calculate holiday pay when the payroll run happens.
Retention is at least six years, counted from the date each record was made rather than from the end of employment. That distinction matters: a leaver’s weekly entries stay in scope for the full six years, whether or not they remain on your books.
Records must cover four things: holiday taken, carry-over between leave years, holiday pay itself, and any payment in lieu of holiday on termination. For holiday pay, the record must show what is included, such as bonuses or commission. Azets extends the list to overtime and allowances as regular or contractual components; verify the legal basis against primary legislation before relying on it.
Format is flexible. Acas states records can be kept in any format the employer reasonably thinks fit, including a spreadsheet or an online system, provided the approach complies with UK GDPR. Lewis Silkin quotes the Employment Rights Act 2025 wording directly: records may be kept “in such a manner and format as the employer reasonably thinks fit.”
On criminal liability, Acas says failure to keep records could be an offence. Lewis Silkin reads the position more firmly, stating that from 6 April 2026 failure to keep adequate records will be a criminal offence in itself, punishable by potentially unlimited fines. Some professional commentators also read the criminal liability position more firmly than Acas’s cautious wording. Treat the range as competing interpretations rather than settled law.
The duty also reaches further across your workforce than many employers expect.
Who Is Covered: Agency, Irregular-Hours and Part-Year Workers
The duty applies to a wider group than many employers assume. Almost all workers are entitled to 5.6 weeks’ paid holiday, including agency workers, irregular-hours workers and part-year workers. GOV.UK words the entitlement for irregular-hours and part-year workers as “up to 5.6 weeks”, because entitlement is built from hours rather than fixed at a weekly figure.
That distinction drives the record design. Irregular-hours and part-year workers accrue holiday at 12.07% of hours worked in each pay period, posted on the last day of that period. GOV.UK defines irregular hours as hours that often or always change within a pay period; a part-year worker has periods in the leave year when they work nothing and are unpaid. Agency workers fall under these rules only where their pattern meets one of those definitions.
Because accrual is hours-driven, the figure changes week to week. A single annual calculation cannot credibly reconstruct it. The evidence has to originate where hours are recorded, not where pay is processed. HR typically owns entitlement while payroll handles processing, and the record must survive that handoff without being rewritten.
Two boundaries matter. Working time records, for example, evidence around the 48-hour average week, are a distinct compliance obligation under the Working Time Regulations 1998; confirm which specific duties apply to your workforce against the primary legislation. This piece is UK-scoped: Irish requirements are not covered by the sources behind it and need separate verification, even if you operate on both sides of the border.
Next, the record itself. What does “adequate” actually have to show?
What “Adequate Records” Must Actually Show
An adequate record is defined by what it can prove, not by how tidy it looks. For each worker, it must answer five questions.
Leave taken. Every instance needs a date, the hours or days taken, and the leave year it falls into. A running holiday balance with undated entries is a total, not a record.
Carry-over. Show how much holiday moved into and out of each leave year, and the basis for it, whether contractual or statutory under the Working Time Regulations 1998.
Holiday pay. Record the sum paid for holiday and the calculation behind it, not only the figure that reached the payroll run. The question asked of the record is how a number was reached, not what it was.
Payments in lieu. Where a worker leaves and receives payment for untaken holiday, that payment must be recorded against both the worker and the date.
Pay elements. Acas says the record must show what is included in holiday pay, such as bonuses or commission. Guidance from some professional advisers extends the list to overtime and allowances as regular or contractual components. If an element fed into holiday pay, the record should show it, including how a bonus or commission paid later was attributed back to the weeks it relates to. Verify the legal basis before relying on any specific enumeration.
That last requirement carries the practical test. A record shows the inputs and the working; a total shows only the outcome. A tribunal or a payroll auditor probes exactly that difference, then asks when the record was written and who approved it.
The Six-Year Clock: How Retention Works in Practice
Retention runs per record at least six years from the date it was made, as noted above.
Six years of weekly entries is a storage design problem before it is a legal one. Every entry must be findable by worker, by week and by pay element, an indexing decision made when the system is configured, not in year four.
Format is flexible. Acas permits any reasonable format, online system or spreadsheet, but findable is not the same as freely editable. A record that can be quietly rewritten carries little evidential weight.
The archive remains personal data. UK GDPR governs it: keep only what the obligation needs, secure it, restrict access by role, and schedule deletion at the end of the retention period so six years does not drift into indefinite storage. The ICO’s storage limitation principle requires you to justify the period and not hold data longer than needed.
Why Reconstructed Records Fail at Tribunal and in Payroll Audits
A spreadsheet rebuilt at the end of a leave year captures what someone concluded, not what happened week by week. It rarely shows how holiday pay was calculated at the time.
In a tribunal, it is normally the employer who must evidence compliance, and that evidence comes from the records you can produce. A missing weekly trail is the defect, not a missing annual total. A payroll audit asks the same question in a different room: show the input, the pay element and the calculation for that specific week.
Retrospective construction multiplies error. Re-entering hours, re-attributing overtime and recalculating accrual across twelve months introduces inconsistency between weeks and between workers. Manual compilation also leaves no author trail. Two versions of the same week can both look plausible, and neither can be shown to be the version that governed.
This is the practical reason tool selection matters. Choosing timesheet software on convenience rather than record design tends to become the weak link later: the system decides what evidence you still hold in year four. A tool that captures time against a named worker and a dated week, and keeps pay elements separate, produces the trail as a by-product. One that stores only approved totals does not.
The Week-By-Week Filing Model: Build the Record From the Rota
The remedy for retrospective reconstruction is to stop reconstructing. Build the record from the rota itself, so scheduling and time capture produce the evidence as a by-product of ordinary operations. Each week closes with one entry per worker: hours worked, hours of holiday taken, holiday pay calculated, and the accrual movement for that week. Nothing is written up later because nothing needs to be.
Capture the pay element at the point hours are logged. Overtime, commission and allowances sit as separate lines from the start, so they never have to be traced back from a payroll total. Post accrual weekly. The running balance becomes arithmetic, and a year-end carry-over figure is simply the sum of recorded weeks rather than a fresh calculation.
Treat each weekly entry as a dated, closed record. Once the week is approved and paid, it is final. Corrections should be additions that leave a visible trail, not silent overwrites. This is what gives the record evidential weight.
Run the model for leavers too. Their final weeks still need closing, as noted above.
Step 1: Capture Time Where the Work Happens
With the weekly entry defined, the first step is capturing the raw time that feeds it. Schedule the shift first, then record actual start, end and break against that scheduled shift, so planned and worked figures sit on the same line and any variance is visible at a glance.
Capture by exception. Where a shift ran as planned, the record simply confirms it, and the manager’s attention goes to the deviations: a late start, a missed break, an unplanned swap. Approve the week at the end of the week, while the manager still knows what happened, rather than at payroll cut-off when memory has gone cold.
Match the capture method to the workforce. Shift-based teams suit an app or clock-in point. Irregular-hours and part-year workers, whose accrual depends on hours worked, need browser or mobile entry that evidences those hours as they accrue.
Time tracking programs only help here if the capture is tied to a named worker and a dated week. Without both, you produce totals with no evidential value, and a total is not a record. The same test applies when you assess timesheet software: ask whether the system can show who worked, in which week, and against which shift.
Step 2: Split Pay Elements in the Week They Occur
Step 1 secures the hours. Step 2 ensures each hour carries its correct pay identity before the week closes.
Record basic hours, overtime, commission, bonuses and allowances as separate lines against the week, never as a single gross figure. Without that breakdown, the holiday figure can only be guessed. Leave those lines intact through approval and export; holiday pay cannot be derived later from a figure that was never split.
Confirm per contract which elements are regular and contractual for your workforce. Guidance from some professional advisers recommends that at least four weeks of statutory entitlement include all regular and contractual pay elements; verify the legal basis against regulation 13 and regulation 16 before relying on it.
Where a bonus or commission is paid quarterly or annually, attribute it to the weeks it relates to at the time of payment. That preserves the link between the element and the leave period.
Because holiday pay must reflect what a worker normally receives, this split is what lets holiday pay be evidenced rather than estimated.
The next step takes this structured week and posts the accrual it generates.
Step 3: Record Holiday Accrual and Carry-Over Weekly
Once pay elements are split, the next weekly entry is the accrual itself. Post the week’s accrual as its own line against the worker and leave year, so the running balance is a sum of recorded weeks rather than a year-end estimate. Record holiday taken in the same entry: dates, hours, the leave year it falls into, and the holiday pay figure attached to those hours. Where a carry-over decision is made, log it in the week it was made, stating whether the basis is contractual or statutory and how much is carried. For irregular-hours and part-year workers, show the hours that generated the accrual beside the figure; a bare accrual number is a conclusion without evidence. Expose the accrual and taken holiday to the worker through the same system, so a query is raised in week one rather than at year end. That weekly visibility is what turns accrual into a defensible record.
Step 4: Close, Date and Store the Week
With accrual and carry-over posted, the final step is to fix that week as evidence rather than leave it as a working draft. Close the week only once it has been approved and paid, so the entry carries an unambiguous status and everyone knows which version governs. Store it against both the worker and the date, bearing in mind that the six-year clock runs from the date the record was made and applies to leavers as well as current staff.
Make corrections additive. A later change should be a new dated entry that supersedes the old one while the original stays visible. Staffly’s design approach aims to keep the audit trail intact, treat that as a product characteristic, not a legal standard the law imposes on employers, and not as a substitute for your own accuracy check before each week closes.
Restrict edit rights by role. Approval of the week and payroll processing should be separate actions performed by separate people, which reduces the risk of silent changes and supports appropriate security under UK GDPR.
Finally, schedule deletion at the end of the retention period, applying the deletion trigger to both current staff and leavers so six years does not become indefinite storage.
Worked Example: One Week Shown End to End
Run a hypothetical week through the model. A worker on a 38-hour pattern works five shifts and also books 8 hours of holiday. Both sit on the same weekly entry, kept as separate facts rather than netted into a single figure.
Three pay lines are logged against the week: 34 basic hours at the hourly rate, 4 hours at the overtime rate, and a weekly allowance. Each is held separately, so the composition of the week is visible without reference to payroll.
Holiday pay for the 8 booked hours is calculated from the regular and contractual elements already recorded for that worker. It is not derived afterwards from the total payroll figure. For a worker with fixed hours, that calculation follows normal working hours and normal pay; for variable-hours workers, the same principle runs through the 52-week reference period, drawing on the weeks already captured.
Accrual is posted for the week and the balance carried forward shown against the leave year, so the running total is arithmetical rather than a year-end computation.
The week is then closed, dated and stored, retrievable by worker and by week. If the pay element mix changes next month, those earlier weeks still show exactly what was in force at the time.
Now reconstruct the same week six months later. The hours and the outcome can be reproduced. The trail showing which elements applied in that week, and who approved them, cannot.
What to Require of a Timesheet System Before April 2026
That contrast is the specification. Before April 2026, assess any timesheet software against six tests, not against interface polish.
Captured time. The system must record start, end and breaks against a scheduled shift. Hours should be evidence of what happened, not a total someone typed in later. Time tracking programs that accept only entered totals fail this test.
Pay element separation at source. Basic hours, overtime, commission, bonuses and allowances must sit as separate weekly lines. Choosing software for timesheet use is therefore a data-structure decision, not a visual one.
Frozen records. Once a week is closed and paid, it should not be silently editable. Corrections should create a dated superseding entry while the original remains visible.
Six-year retrievability (see above). Require a readable export, so changing supplier does not trap your evidence.
UK GDPR fit. Insist on role-based access, retention scheduling and deletion, and security proportionate to the personal data held.
Payroll-ready output. The week closed for the record should be the week paid, from the same data. When assessing timesheet tracker software, ask how the holiday pay figure is produced and exactly which pay lines feed it.
A supplier that cannot answer those questions in detail cannot evidence compliance convincingly, however good the demo looks.
Where Staffly Fits in This Model
Against those criteria, Staffly is workforce management software for Ireland and the UK, bringing scheduling, time tracking, HR, compliance, shift cover, staff communication and payroll-ready output onto one platform.
The design choice that matters most is that scheduling and time capture sit in the same place. When the rota and the hours worked against it share a system, the weekly entry described above is produced as a by-product of running the rota, not written up afterwards. That is the difference between a record and a reconstruction.
Payroll-ready output extends the same logic: the week closed for the record is the week paid, removing the reconciliation step where reconstruction usually begins.
Staffly’s design approach aims to keep the audit trail intact, treat that as a product characteristic, not a legal standard the law imposes on employers, and not as a substitute for your own accuracy check before each week closes.
Staffly operates across Ireland and the UK, but the rules set out here are the UK record-keeping requirements covered by the sources cited. Verify Irish requirements separately before applying the same model.
Conclusion: Five Actions for the Next Payroll Cycle
Staffly’s audit trail only helps if it is pointed at the right obligations. Five actions to complete before your next payroll cycle:
- Map existing records to the four required elements. Leave taken, carry-over, holiday pay and payments in lieu. Each must be evidenced, not merely calculated somewhere in payroll.
- Test pay element traceability. Can overtime, commission, bonuses and allowances be traced week by week for every worker, or only as an aggregate? Totals alone will not support a holiday pay figure under scrutiny.
- Evidence a single week end to end. Take one closed week and try to show the holiday pay calculation from the records alone. If the trail is missing, fix that week’s method before you scale anything.
- Set a weekly close routine with a named approver. The entry is dated when the week ends, and corrections become new dated entries rather than overwrites.
- Confirm retention is set to six years from each record’s creation date, for leavers as well as current staff, with deletion scheduled.
The record-keeping duty starts in April 2026; holiday pay enforcement by the Fair Work Agency is not expected before April 2027. A record you can produce on request is a compliance asset; one you can only reconstruct afterwards is a liability.