A project goes live late on a Friday. By Monday, several employees have worked evenings and part of the weekend, managers are approving requests in email, and HR is trying to work out which hours belong in payroll and which should become paid time off. Everyone agrees that the extra work happened. Nobody agrees on how the balance should be recorded.
Time off in lieu, or TOIL, can solve that problem, but only when HR treats it as a controlled pay and absence process. A spreadsheet with a running total isn't enough. The policy must define the employee's entitlement, the accrual rate, approvals, expiry, carry-over, termination treatment and the relationship between the date worked and the date taken.
UK and EU organisations also need to separate three questions. Is the employee entitled to TOIL? When must the extra hours be paid or compensated? Does the arrangement preserve rest, minimum wage and payroll records? Those questions often produce different answers.
Table of Contents
- What time off in lieu actually means for employers
- UK legal framework and EU context for TOIL
- The hidden payroll risk in a simple hour swap
- Common TOIL policy models and how to choose
- Calculating, approving and tracking TOIL correctly
- Automating TOIL inside a Microsoft-based HR platform
- Pros, cons and common misconceptions about TOIL
- Putting a compliant TOIL policy into practice
What time off in lieu actually means for employers
Time off in lieu means paid time off given in exchange for extra hours already worked, usually instead of an overtime payment. An employee works beyond their normal schedule, the organisation records and approves those hours, and the employee later takes paid time away from work under the terms of the TOIL policy.
TOIL isn't annual leave. It shouldn't reduce the employee's ordinary holiday entitlement, and it isn't unpaid leave. It also isn't automatically the same as overtime pay. Whether the employee can choose between cash and time, or whether the employer can offer TOIL instead of cash, depends on the employment contract, collective arrangements and applicable law.
In the UK, TOIL isn't a statutory right. The arrangement exists because the employer has included it in a contract, staff handbook or workplace policy. UK guidance on time off in lieu explains that employers may give paid time off instead of paying overtime, while the terms still need to fit within wider working-time requirements.
Practical rule: Never rely on the phrase “time back” in an email. Define TOIL as a formal policy entitlement with a recorded transaction.
What a workable policy must decide
A sound policy answers these points before anyone works additional hours:
- Eligibility: Identify which employee groups can accrue TOIL and whether any roles must receive overtime pay.
- Accrual rate: State whether one extra hour creates one hour of TOIL or a different contractual entitlement.
- Approval: Require pre-authorisation where possible, with a documented exception route for urgent work.
- Booking: Set out how employees request time off and how managers assess operational cover.
- Balance rules: Define caps, expiry and carry-over rather than allowing an unlimited bank.
- Leaving employment: State how unused balances are handled, subject to the contract and applicable law.
That makes TOIL a workforce planning tool, not an informal favour. It can give employees recovery time after intense delivery periods and help managers handle fluctuating demand, but only if every party understands the exchange.
Keep TOIL distinct from ordinary paid time off in your policy architecture. The difference is explained further in this guide to PTO and paid time off, which helps HR teams avoid placing different absence rights into one generic leave category.
UK legal framework and EU context for TOIL
The UK legal framework sets boundaries around TOIL, but it doesn't create a general TOIL entitlement. The Working Time Regulations 1998 include an average 48-hour weekly limit, measured over a 17-week reference period, unless the worker has opted out. UK guidance on time off and paid leave places time off in lieu within that wider working-time context.
The important operational distinction is timing. The extra hours are working time when the employee performs them. The later TOIL booking is time away from work. Treating the two events as a simple balance transfer can hide whether the original work breached rest or pay requirements.
Rest is a separate control
TOIL can't be used to erase the need for recovery. Acas identifies statutory rest rights including a 20-minute break where a worker is expected to work more than 6 hours, 11 hours' rest between working days, and 24 hours every 7 days or 48 hours every 14 days between working weeks. These rights are summarised in Acas guidance on asking for and taking holiday.
Where a worker is required to work during a period that would otherwise be a rest period or rest break, the employer must, wherever possible, provide an equivalent period of compensatory rest. Northern Ireland overtime guidance explains that appropriate health and safety protection is required in exceptional cases where equivalent rest isn't objectively possible.
The EU context follows the same basic principle, but local implementation matters. The EU Working Time Directive framework addresses daily and weekly rest, working-time limits and night-work protections. It doesn't provide one universal TOIL rule for every member state. National legislation, collective agreements and employment contracts can determine whether compensation is paid, taken as leave, uplifted or subject to particular deadlines.
Policy is the missing layer
For a UK and EU workforce, the employer should treat legislation as a set of guardrails. The policy then fills in the practical detail for each jurisdiction and employee population.
A single group policy can work, but only with country-specific rules for eligibility, accrual, rest, payroll and termination. Get local employment and payroll advice before applying one UK rule across EU entities. The most important design principle is to keep hours worked, hours taken and pay treatment as separate fields, even when the employee sees one simple balance.
The hidden payroll risk in a simple hour swap
The common assumption is that TOIL is harmless if the employee agrees to an hour-for-hour swap. That assumption is wrong. Employee agreement doesn't remove National Minimum Wage risk.
HMRC's treatment is precise. The extra hours count as working time in the pay reference period when they were worked. The later TOIL is non-working time. HMRC's National Minimum Wage manual explains why an employer can face a problem if the pay associated with the worked hours is deferred, withheld or otherwise fails to keep average hourly pay above the legal minimum in that original period.
The issue appears when payroll records only the later absence. A worker may take paid TOIL in a subsequent period, creating a superficially sensible overall result, while the original period still contains extra working time without sufficient pay. Near the minimum wage, frequent overtime or an inconsistent pay process makes the exposure more serious.
Payroll should reconcile the accrual date and the take date separately. They aren't interchangeable events.
A second edge case concerns contractual overtime premiums. If night, weekend or unsociable-hours treatment applies, a basic 1:1 TOIL record may fail to preserve the value that the contract or collective arrangement requires. Don't assume that a future booking at base rate replaces every payment obligation created when the work was performed.
TOIL swap scenarios and payroll risk
| Swap pattern | Pay treatment in worked period | Pay treatment in taken period | Risk flag |
|---|---|---|---|
| Approved hours converted to TOIL immediately | Payroll records the extra work and applies the required pay treatment for that period | Paid absence deducts from the approved TOIL balance | Lower risk when records remain linked |
| Hours worked, approval delayed | The original work may be missing or misclassified in the relevant pay reference period | Later booking appears as ordinary paid time off | High risk, because approval timing can break reconciliation |
| Cash withheld until TOIL is taken | Extra hours may not receive the required treatment when earned | Later paid absence is expected to compensate for earlier work | High NMW risk, particularly for lower-paid workers |
| Premium hours exchanged at base-rate TOIL | Payroll records hours without the required premium element | Future absence is paid at ordinary rules | Contract and payroll review required |
| Unapproved hours added retrospectively | Payroll has no reliable authorisation or reason code | Employee requests a balance that may not be valid | Audit and dispute risk |
Before approving a policy, ask payroll to confirm how the accrual date, take date, pay reference period and pay run will reconcile. The same principle should govern the wider payroll and HR process, not just TOIL.
Common TOIL policy models and how to choose
There isn't one correct TOIL model. The right choice depends on the workforce, contractual overtime rules, operational rhythm and payroll capability. HR teams get into trouble when they copy a 1:1 rule from a salaried office population and apply it to shift workers with premiums and tightly controlled working hours.
Four models worth considering
Straight time gives one hour of TOIL for each approved extra hour worked. It suits salaried knowledge workers who occasionally support a launch, client deadline or emergency task. It becomes harder to defend where the contract would otherwise provide enhanced overtime treatment.
Uplifted time gives a higher TOIL value for specified work, such as weekends, nights or public holidays. The uplift must be contractual or clearly authorised. It shouldn't be inserted as an informal reward that payroll can't reproduce consistently.
Capped balances limit how much TOIL an employee can hold. A cap helps managers plan absence and helps finance understand potential liabilities, but it must include an exception process. A cap that prevents an employee from receiving the agreed compensation creates a different problem.
Carry-over and expiry rules determine whether unused TOIL moves into a later policy period or expires. Use-it-or-lose-it wording needs careful drafting and fair communication. If operational pressure repeatedly prevents employees from taking approved TOIL, automatic expiry can create employee relations risk.
Choosing a TOIL policy model by workforce profile
| Policy model | How it works | Best fit | Watch-outs |
|---|---|---|---|
| Straight time | Approved extra hours convert at the standard ratio | Salaried professional teams with occasional peaks | Check that it doesn’t undercut contractual overtime |
| Uplifted time | Certain hours receive an enhanced accrual value | Shift-based, operational or unsociable-hours teams | Premium rules need payroll and contract alignment |
| Capped balance | Accrual stops or escalates after a defined ceiling | Organisations managing absence capacity and liabilities | Exceptions must be visible and approved |
| Carry-over | Unused balance moves forward under stated rules | Teams with seasonal work or delayed project recovery | Monitor ageing balances and expiry communications |
| Manager discretion | Managers approve exceptional time back case by case | Senior or highly autonomous populations | Inconsistent decisions can create fairness concerns |
The policy model should be selected before configuration. Standard Dynamics 365 Human Resources leave parameters may support leave types, eligibility and approval settings, but a TOIL process often needs additional fields and logic for worked hours, accrual rate, caps, reference periods and payroll treatment.
HRManagement365 should configure those extensions only after HR, payroll and finance agree the policy. The platform can then reflect a decision that the business has made. It shouldn’t be used to conceal an unresolved one.
Calculating, approving and tracking TOIL correctly
A TOIL transaction starts when the extra work happens, not when the employee remembers it weeks later. The employee or manager should record the date, hours and reason, while the line manager confirms that the work was authorised or falls within the documented emergency route.
The system then calculates the entitlement using the approved policy rule. If the rule is straight time, the approved hours become the balance under that rule. If an uplift applies, the system should store both the hours worked and the resulting TOIL credit, rather than overwriting the underlying work record.
A reliable approval sequence
- Employee submission: The employee submits extra hours with the date worked, project or reason code and supporting timesheet.
- Manager review: The manager checks the work, operational need, budget and applicable cap.
- HR exception review: HR reviews unusual ratios, retrospective submissions, cap overrides and disputed entries.
- Accrual posting: The approved credit is posted against the correct pay reference period and linked to its originating work record.
- Leave booking: The employee requests TOIL, the manager approves the absence, and the system deducts the approved amount.
An auditable record should retain the date worked, hours, project or reason code, approving manager, accrual period, taken date and remaining balance. Add timestamps and the relevant payroll status where the system supports it.
The two failures that cause most disputes
The first failure is approving TOIL in a later month than the work was performed. The second is losing the relationship between the worked hours and the time taken. Both make payroll reconciliation harder and weaken the evidence available for an HMRC review.
A proper leave and absence process should therefore preserve the transaction history rather than merely display a balance. The approach described in leave and absence management is useful because TOIL belongs in the same governed absence environment as other leave, while retaining its separate accrual and payroll logic.
Automating TOIL inside a Microsoft-based HR platform
A UK manufacturing organisation with 400 employees can have a very different TOIL profile from a professional services firm. Production peaks, engineering call-outs and weekend maintenance create a need to capture hours accurately, approve them quickly and show managers whether balances are becoming operationally difficult.
In an HRManagement365 design, the solution is based on Microsoft Dynamics 365, Dataverse and Power Platform. Standard Dynamics 365 Human Resources leave types can provide the employee-facing absence structure, while a custom TOIL entity in Dataverse can hold the additional information that a normal leave booking doesn’t capture.
That custom entity should include worked hours, accrual rate, cap, reference period, approval status and the originating timesheet entry. This is an extension configured or developed for the organisation’s process. It shouldn’t be presented as an automatic feature of standard Microsoft functionality.
Where automation earns its keep
Power Automate can be configured to:
- post approved accruals after the manager confirms the work;
- check the available balance and cap before a TOIL booking proceeds;
- route carry-over or ageing warnings to HR at the relevant review point;
- notify employees and managers when balances change;
- send a cash payment element to the payroll process where the policy permits payment instead of leave.
Managers need a self-service view showing pending approvals, current balances and upcoming bookings. HR and finance need a different view, usually through Power BI, showing accruals, takings and potential liabilities by department. The audit trail should connect the TOIL record to the timesheet, approval and booking rather than leaving those records in separate inboxes.
Organisations exploring wider workflow design may also benefit from guidance on how to automate leave and contracts, particularly where TOIL approvals sit alongside employee lifecycle processes.
Standard platform versus specialist extension
Microsoft Dataverse provides the structured data layer. Power Automate provides workflow orchestration. Power BI provides reporting, subject to the data model and reporting configuration. Dynamics 365 and Microsoft 365 provide the surrounding business environment, including identity, security and familiar employee access routes.
HRManagement365 can configure the policy, build custom workflows, create Power Apps or custom HR applications, and integrate the resulting records with Business Central, Finance & Operations or a payroll system. Customers can self-serve routine policy administration where that access is designed into the solution. Specialist input remains appropriate for cross-border rules, payroll interfaces, complex accrual logic, security roles and changes that affect historical balances.
The valuable outcome isn’t a prettier TOIL form. It’s a traceable chain from hours worked to approval, accrual, booking and payroll treatment.
Pros, cons and common misconceptions about TOIL
TOIL has a legitimate place in workforce management. It can control overtime cash outlay, give project teams flexibility during uneven workloads and provide paid recovery time after demanding delivery periods. Employees may also value the choice between immediate cash and time away from work, provided the choice is genuine and the policy is applied consistently.
The risks are less visible. A 1:1 arrangement can create NMW exposure if the pay treatment for the original work is wrong. Uncapped balances can grow into an operational and financial liability. Managers can undermine the benefit by approving accruals but repeatedly refusing reasonable requests to take the time.
Misconceptions that need removing
TOIL is a statutory UK right. It isn’t. The employer must create the entitlement through a contract or policy, subject to other legal obligations.
TOIL counts towards statutory holiday. It doesn’t replace statutory annual leave. Keep the balances and reporting categories separate.
Employee agreement makes any exchange lawful. It doesn’t. Agreement can’t remove minimum wage, rest or contractual payment requirements.
TOIL always replaces overtime pay. It may do so only where the contract and applicable rules allow it. If overtime pay is already owed, the employer can’t relabel it as future leave.
Unused TOIL can always be rolled into a termination payment or PILON. Treat this carefully. The contract, payroll treatment and local law determine what happens, and EU member states can impose different payment requirements.
Questions to resolve before launch
- Accrual: What creates an entitlement, and who can approve it?
- Rate: Is the exchange straight time, uplifted or linked to the overtime rule?
- Carry-over: How much can move forward, and what happens if the employee couldn’t take it?
- Expiry: When does unused time expire, and how are reminders evidenced?
- Discretion: What limits apply when managers approve or refuse bookings?
- Termination: How are unused balances treated on leaving?
- Record: Which system is the authoritative source for hours, balances and payroll?
If those answers aren’t written down, automation won’t fix the policy. It will only make inconsistent decisions happen faster.
Putting a compliant TOIL policy into practice
Start with the documents. Revise the TOIL clause in employment contracts, reference the detailed policy in the staff handbook and create country-specific schedules where UK and EU requirements differ. State the accrual rate, any uplift, the approval route, caps, carry-over, expiry, booking notice and treatment on termination.
Then configure the controls in the system:
- Capture the work: Record the date earned, hours earned, reason code and approving manager.
- Protect the pay record: Store the underlying pay reference period and keep the worked event separate from the later leave booking.
- Control the balance: Apply the approved cap and carry-over rules automatically, with an exception route for HR.
- Make booking visible: Let employees request TOIL through a governed workflow and let managers see the operational impact.
- Preserve evidence: Keep timestamps, approvals, amendments and links to the originating timesheet.
- Review ageing balances: Use reporting to identify unused time before it becomes a capacity or payroll issue.
A single source of truth inside the HR system is the practical standard. Avoid parallel spreadsheets, email approvals and manually edited payroll totals. Automated expiry reminders, balance alerts and a Power BI dashboard can help HR identify exceptions, but the dashboard is only as reliable as the accrual and take records beneath it.
The implementation should finish with manager training and a controlled review of real transactions. Test ordinary accruals, late submissions, cap overrides, carry-over, disputed hours, payroll reconciliation and termination treatment before releasing the process to the wider workforce.
Speak to an HRManagement365 specialist about a scoped discovery call. HRManagement365, powered by Hubdrive and Microsoft, can help configure TOIL workflows, connect time and absence records with Dynamics 365 and payroll processes, and extend the platform with Dataverse, Power Automate and Power BI where standard configuration isn’t enough. Visit HR Management 365 to discuss a UK or EU implementation, call +44 1522 508096 today, or send us a message.
