Monday morning exposes the weakness in many attendance processes. Payroll needs approved hours, operations is checking whether shifts were covered, and HR is trying to demonstrate that working-time limits were monitored. Each team may be working from a different spreadsheet, rota or system export, all claiming to represent the same employee's hours.
That situation isn't solved by asking everyone to clock in and out more aggressively. It's solved by defining time and attendance rules that distinguish worked time, overtime, breaks, night work, absences, travel, waiting and exceptions, then preserve the decisions made about those records. For a UK employer, the objective is twofold: evidence under the Working Time Regulations 1998, and pay-period records that can support National Minimum Wage checks.
Table of Contents
- Why Time and Attendance Rules Matter More Than a Timesheet
- The Two Layers of Evidence UK Employers Must Produce
- The Three Rule Categories Every UK Policy Needs
- Configuring Time and Attendance Rules in HRManagement365
- Counting Working Time in Hybrid, Mobile and Digital Roles
- A Worked Example of Overtime, Rounding and Approval in Practice
- Designing Rules That Survive an Audit and a Payroll Query
Why Time and Attendance Rules Matter More Than a Timesheet
A timesheet records an assertion. A well-designed attendance process records the context behind that assertion, including the shift that was scheduled, the time that was entered, the rule that was applied, the approval that followed and any adjustment made afterwards.
The distinction matters because working-time compliance and payroll accuracy ask different questions. Working-time controls need to show whether average hours, rest and night-work requirements were managed. Payroll needs to know which hours were payable, whether overtime was approved, and whether less visible activity such as travel or waiting was included where required.
The Working Time Regulations 1998 provide the statutory baseline. They establish a general maximum average working week of 48 hours, including overtime, over the applicable reference period. Workers can agree in writing to opt out of that average limit, but employers must retain current records of the agreement and continue managing other protections.
Practical rule: A clocking record is only useful when the organisation can explain how it became an approved working-time and payroll record.
From clocking data to governed evidence
A clock-in-and-pray approach captures a start and finish, then leaves HR to resolve everything else in email. It struggles with late punches, split shifts, missed breaks, site travel, changed rotas and overtime that was worked but never approved.
A rules-led model handles those situations consistently:
- Shift definitions identify expected working patterns, locations and night-work bands.
- Overtime triggers determine when extra hours require approval or a different pay treatment.
- Rounding rules apply consistently rather than allowing each manager to interpret a small variance differently.
- Rest controls flag missing breaks, insufficient daily rest or excessive consecutive work.
- Exception workflows require a reason, supporting evidence and a recorded decision.
The result is not surveillance for its own sake. It's proportionate evidence. Some roles may need detailed capture because hours vary or work occurs at night. Other populations may need scheduled-hours records with exception reporting, provided those records demonstrate compliance.
For a broader explanation of the capabilities to assess in a platform, see time and attendance systems. The key question is whether the system can connect policy, capture, approval and reporting, rather than merely display who tapped a button.
The Two Layers of Evidence UK Employers Must Produce
UK employers should separate two evidence obligations that are often combined incorrectly. The first concerns working-time compliance. The second concerns whether the organisation can prove that each worker received at least the National Minimum Wage for the relevant pay reference period.
Working-time records need to support calculations for the 48-hour average, night-work limits, daily and weekly rest, and applicable opt-out arrangements. The legislation generally requires adequate records to be retained for two years from the date they were made, but it doesn't necessarily require every worker's daily start and finish time if another reasonable method demonstrates compliance. The relevant statutory requirements are set out in the Working Time Regulations record-keeping provisions.
National Minimum Wage evidence has a different purpose. It should connect actual hours with pay, including ordinary hours, overtime, travel between appointments, waiting time, absences, shifts, premium rates and allowances. HMRC's National Minimum Wage record guidance states that records created from 1 April 2021 must generally be retained for at least six years, calculated from the end of the following pay reference period.
The evidence model
| Evidence layer | Core question | Typical records |
|---|---|---|
| Working Time Regulations | Were working-time limits and rest protections monitored? | Approved time entries, rolling calculations, breaks, night work, opt-outs and exception decisions |
| National Minimum Wage | Do hours and pay reconcile for each worker and pay period? | Hours, overtime, travel, waiting, allowances, pay components and deductions |
The retention difference creates a practical risk. An organisation may retain payroll extracts for six years while deleting the calculation trail that explains how working-time compliance was assessed after two years. That makes historical reconstruction difficult, even though the payroll record still exists.
A sensible design captures once by pay reference period, then produces both outputs. The record should separate ordinary hours, overtime, travel, waiting, absences, shifts, premium rates and allowances, and preserve an immutable history of edits and approvals. The principles of document traceability explained are useful here because evidence must show not only the final value, but also its source and decision history.
For related retention considerations, see employee records retention. Retention isn't a substitute for good classification, but it protects the audit trail once the classification has been made.
The Three Rule Categories Every UK Policy Needs
Most implementation problems come from mixing different policy decisions into one generic “attendance” setting. I normally separate the design into three categories, because each category produces different evidence and should have a different owner.
| Rule category | What it governs | Evidence produced | Common pitfall |
|---|---|---|---|
| Shift and rota rules | Patterns, breaks, night-work bands, rest and reference-period calculations | Planned shifts, approved hours, break records and rolling compliance results | Treating the rota as proof of actual working time |
| Overtime and rounding rules | Extra-hours triggers, rounding, premium treatment and time off in lieu | Overtime requests, calculations, approvals and pay allocations | Applying rounding before deciding whether time was worked |
| Exception and approval rules | Missed punches, late starts, extended breaks, travel and unusual durations | Reason codes, source evidence, manager decisions and adjustment history | Letting managers correct records without an audit trail |
Shift and rota rules
Start with the working pattern, not the interface. Define the shift, expected breaks, night-work classification, reference period and the population to which the rule applies. Adult workers generally have an uninterrupted 20-minute rest break when the working day exceeds six hours, at least 11 consecutive hours of daily rest, and weekly rest arrangements described by GOV.UK guidance on rest breaks.
The rule should calculate from approved time entries where work is variable. A rota can establish expectation, but it shouldn't replace actual hours where overtime, travel or waiting affects the result.
Overtime and rounding rules
Rounding is a payroll decision, not a convenience setting. Define whether a rounded value is used for pay, operational reporting, working-time calculations, or all three. Those outcomes may need to remain separate.
If an organisation uses time off in lieu, the conversion and approval path should be explicit. The time off in lieu guidance is relevant because TOIL can otherwise become an informal balance that payroll and HR cannot reconcile.
Exception and approval rules
Exceptions should be structured, not hidden in comments. A missed punch, an extended break, travel between sites and a late shift should each have a reason, a responsible approver and a record of the decision. This gives managers enough flexibility to correct reality without allowing silent edits to become the official record.
Configuring Time and Attendance Rules in HRManagement365
HRManagement365 is a UK and EU HR solution powered by Hubdrive and Microsoft technology. It is built on Microsoft Dynamics 365, Power Platform and Dataverse, and extends those foundations with implementation expertise, integrations, customisations, workflows and HR applications. The design question is not whether a feature exists in standard software. It's which parts can be configured safely, and which parts need a customer-specific process.
Begin with Dataverse records for workers, assignments, locations, shifts, pay periods, rule sets, exceptions and approvals. Standard Hubdrive and Microsoft functionality can provide the platform foundation, security model, forms, records and connected Microsoft 365 experience. HRManagement365 can then configure or extend the process for UK-specific policies, approval routes and operational distinctions.
A practical configuration sequence
- Create the policy structure. Store shift patterns, overtime triggers, rounding approaches, break expectations, night-work categories and effective dates as governed records.
- Capture the source event. Use an appropriate employee or manager experience for start and finish entries, grids, adjustments or imported records. A Power App may be appropriate where a field workforce needs a simpler mobile process.
- Apply rules through automation. Power Automate can route exceptions, request manager decisions, issue reminders and preserve the reason for an adjustment.
- Separate standard from extended behaviour. If a customer needs a special travel classification, project allocation, multi-stage approval or a bespoke calculation, HRManagement365 can develop the relevant Dataverse tables, Power Apps screens, workflows or custom HR application.
- Report on approved data. Power BI can present approved hours, overtime, rest concerns, night work and unresolved exceptions without treating unapproved entries as final facts.
Connecting attendance with finance
The operational process should finish where payroll and finance can use it. Approved records can be integrated with Dynamics 365 Business Central or Finance & Operations, depending on the customer's architecture and payroll arrangements. That reduces re-keying, but integration should not erase the source record, the approval, or the calculation history.
Manager self-service can sit in familiar Microsoft 365 channels such as Teams and Outlook, while HR retains governed records in Dataverse. That balance is important. A convenient submission experience doesn't justify weakening data quality or auditability.
Counting Working Time in Hybrid, Mobile and Digital Roles
“Not logged in” does not necessarily mean “not working”. The relevant question is whether the employer requires, directs or controls the activity.
UK minimum-wage guidance identifies less visible activities that may need consideration, including mandatory app log-ins, required presence at a location, employer-directed administration, waiting after accepting work and travel to an allocated starting point. The GOV.UK eligibility guidance should inform the policy classification, especially for field staff, mobile workers, on-call teams and employees moving between digital platforms.
Ask what the employer controls
A useful decision process tests the activity rather than the device:
- Was the activity mandatory? A required pre-shift safety check may be working time even if it happens before the scheduled start.
- Was the worker waiting for work after accepting it? Waiting can be materially different from ordinary personal time.
- Was travel work-directed? Ordinary commuting isn't the same as travel to an allocated starting point or between appointments.
- Did the employee perform an employer-directed task? Messages, handovers, administration and remote troubleshooting may need classification.
- Can the system record the category separately? A single total hides the information payroll and HR may need.
HRManagement365 can be extended with custom Dataverse tables and Power Automate flows to record pre-shift checks, on-call waiting, travel between sites and digital activity separately from ordinary hours. That doesn't mean recording every Teams message or monitoring every minute. It means defining the activities that matter, capturing them proportionately and documenting why the organisation classified them in a particular way.
The same approach supports hybrid work. An employee working from home may have no physical clocking event, but an approved schedule, exception record, task allocation or required check-in can still form part of a broader evidence model. The system should capture what the employer needs to evidence, not collect data merely because technology makes collection possible.
A Worked Example of Overtime, Rounding and Approval in Practice
Consider a UK multi-site services firm with office staff, field engineers and night cleaners. The groups don't need identical time and attendance rules. Office staff may follow scheduled hours with exception reporting, field engineers may need travel and site allocation, and night cleaners may require closer attention to night work and rest.
The employer configures a 15-minute rounding rule and an overtime trigger above 37.5 hours. Those are policy settings for this example, not statutory thresholds. The system keeps the source entries, applies the configured calculation, identifies time above the trigger and sends the resulting overtime record to the appropriate manager for approval.
A field engineer starts at a depot, travels to a customer site, waits for access and completes the job. If the organisation records only the customer-facing appointment, it may omit activity that needs consideration. A separate classification for travel, waiting and productive work lets HR and payroll decide how each category should be treated instead of forcing a manager to enter one unexplained total.
Exceptions need decisions, not edits
A night cleaner misses the end punch on a late shift. The record is not overwritten without review. It becomes an exception with the scheduled shift, available source information, the worker's explanation and a manager decision captured through the configured approval route, potentially in Teams.
The system also evaluates the approved record against rest and night-work policies. If a worker is approaching the 48-hour average limit, the issue should appear as a management exception before the organisation has to reconstruct the position from old spreadsheets. An opt-out, where one exists, should be linked to the worker and its effective terms, without treating it as permission to ignore fatigue or night-work controls.
For organisations reviewing the operational side of overtime, managing labour costs with AnchOps provides a useful adjacent perspective. The principle remains the same here: a cost report is only credible when the hours behind it are classified and approved.
The final reports should be practical rather than decorative. A Power BI model can show approved hours by worker and pay period, ordinary time, overtime, travel, waiting, allowances, unresolved exceptions, night work and rest concerns. A worker-level audit export should then combine approved hours, pay components and the relevant approvals so payroll or HR can retrieve one coherent record.
Designing Rules That Survive an Audit and a Payroll Query
A durable configuration connects every rule to the evidence it produces. If a rule has no identifiable output, it will be difficult to explain during an audit, a payroll query or an internal dispute.
Use this checklist when reviewing an existing process:
- Map each rule to evidence. A shift rule should produce the expected pattern and relevant rest or night-work calculation. An overtime rule should produce the trigger, value and approval. An exception rule should produce the reason, source record and decision.
- Separate source from result. Keep the original punch or submission alongside the adjusted, approved value. Don't allow the final number to replace the history.
- Preserve effective dates. Store policy versions, worker assignments and opt-out agreements with their applicable dates and withdrawal status.
- Test less visible work. Review travel, waiting, mandatory app activity, preparation, handover and remote troubleshooting.
- Confirm retention by evidence type. Working-time records generally need two years of retention, while National Minimum Wage records created from 1 April 2021 generally need at least six years, as established by the relevant legislation and HMRC guidance cited earlier.
- Reconcile before export. Approved hours, overtime, allowances and pay components should align for the worker and pay reference period.
HRManagement365, powered by Hubdrive and Microsoft, can support this design inside Dynamics 365, Dataverse and Power Platform. Its implementation work can include HR consultancy, configuration, custom approval workflows, Power Apps capture experiences, Power Automate automation, integrations, Power BI reporting and custom HR applications. Where a customer uses Business Central or Finance & Operations, the attendance process can be designed to connect approved workforce data with finance and payroll processes, subject to the organisation's architecture and local requirements.
The right outcome isn't maximum monitoring. It's a defensible evidence model that gives employees a workable process, gives managers clear decisions, gives payroll reliable hours and gives HR a historical trail.
HRManagement365 can help UK and EU organisations configure time and attendance rules, connect approved hours with Dynamics 365 Business Central or Finance & Operations, and extend standard Microsoft and Hubdrive capabilities with custom workflows, Power Apps and Dataverse applications. Visit HR Management 365 to discuss your requirements, or contact a specialist on Phone +44 1522 508096 today or send us a message.
