How Workplace Nursery Payroll Deductions Work

TL;DR: A workplace nursery benefit under Section 318 ITEPA 2003 works as a pre-tax salary deduction. The employee gives up an agreed amount of gross salary; the employer uses that amount to pay the nursery directly. Because the deduction comes out before income tax and employee National Insurance are calculated, taxable pay falls and the employee keeps more of their pay. Payroll runs it as a salary-sacrifice deduction each pay period, with an automatic National Minimum Wage floor check so a deduction can never take pay below the NMW.

If you run payroll, the workplace nursery benefit is not exotic — it is a salary-sacrifice arrangement, processed the same way as a pension or cycle-to-work deduction, but pointed at registered childcare. The mechanism is well established under Section 318 ITEPA 2003. What trips teams up is the detail: which figure the deduction comes out of, what the payslip should show, how the saving actually arises, and where the common errors hide. This guide walks through the payroll side end to end.

The headline for your reader: the employer runs the programme and pays the nursery; the platform is the software that keeps it compliant and clean each month. Parents pay nursery fees from pre-tax salary, so their taxable pay falls and the saving shows on the payslip.

What changes on the payslip

The clearest way to understand a salary-sacrifice deduction is to look at a payslip before and after the arrangement starts. The numbers below are illustrative only — they are not a quote, and real figures depend on tax code, earnings, and nursery cost.

The point of the table is the bottom two rows. Before, the employee pays the £800 nursery bill out of net pay, leaving them £1,630. After, the £800 comes out before tax and NI, so although net pay on the payslip looks lower, the nursery is already paid and the employee is left with more in hand. The difference is the income tax and employee NI no longer charged on that £800.

Step 1 — Set up the salary-sacrifice agreement

A salary-sacrifice deduction is a contractual change, not a voluntary post-tax payment. The employee agrees, in writing and before the relevant pay period, to give up a defined amount of gross salary in return for the workplace nursery benefit. This is what makes the deduction pre-tax. The agreement names the amount, the start date, and the conditions under which it can change (for example a life event or annual review).

Get this wrong and the deduction is just a net deduction with no tax effect — see the difference explained below. The agreement is the legal basis for reducing taxable pay, so it has to exist and be dated before the first deduction runs.

Step 2 — Apply the deduction before tax and NI

In your payroll software, the workplace nursery amount is configured as a pre-tax (salary-sacrifice) deduction, not a post-tax one. That ordering is the whole mechanism: the deduction reduces gross pay first, and income tax and employee National Insurance are then calculated on the lower figure. Employer National Insurance is also calculated on the reduced figure, which is part of why the arrangement can be designed cost-neutral for the employer.

• Income tax saving — the sacrificed amount is no longer taxed at the employee’s marginal rate.
• Employee NI saving — the sacrificed amount is no longer subject to employee National Insurance.
• Employer NI saving — the employer’s NI bill falls on the reduced gross, which can fund the cost of running the programme.

Step 3 — Run the National Minimum Wage floor check

A salary-sacrifice deduction cannot take an employee’s pay below the National Minimum Wage (or National Living Wage) for the hours they work. This is a hard legal limit, not a guideline. If a requested deduction would breach the floor, it must be reduced or declined for that employee.

This is the check payroll teams most often miss when doing it by hand, because it depends on hours worked, age band, and the current NMW rate — all of which move. A platform should run this automatically for every employee, every pay period, and flag or cap any deduction that would breach the floor before it reaches your payroll file. Halo performs this check automatically as part of generating the deduction file.

Step 4 — Pay the nursery directly

The employer — not the employee — pays the nursery. Once the deduction is taken, the corresponding amount is remitted to the nursery for that child’s fees. The benefit works with any Ofsted or Care Inspectorate registered nursery, so you are not tied to a single provider. From the employee’s perspective the fee is handled; from payroll’s perspective it is one outbound payment (or a consolidated remittance) per cycle, reconciled against the deductions taken.

Salary-sacrifice deduction vs net deduction

These are not interchangeable, and confusing them is the single most expensive payroll error here:

• Salary-sacrifice (pre-tax) deduction — comes out of gross pay before tax and NI are calculated. Requires a written agreement that varies the contract. Reduces taxable pay, so it generates the tax and NI saving. This is the workplace nursery mechanism.
• Net deduction — comes out of pay after tax and NI have already been charged. Needs no contractual variation but produces no saving; the employee has already been taxed on that money. If you process the workplace nursery amount as a net deduction by mistake, the employee gets the inconvenience with none of the benefit.

Common payroll errors and how to avoid them

• Processing it as a net deduction — the deduction is taken after tax instead of before, so no saving arises. Avoid by configuring the line as a pre-tax salary-sacrifice deduction and reconciling taxable pay before and after.
• No dated written agreement — the sacrifice runs before the agreement is signed, undermining the pre-tax basis. Avoid by gating the first deduction on a signed, dated agreement.
• Skipping the NMW floor check — a deduction takes pay below the minimum wage. Avoid by running an automatic per-employee floor check every cycle, not a manual spot-check.
• Stale figures after a leaver, change, or absence — a deduction continues after a child leaves nursery, or runs during unpaid leave when there is no pay to deduct from. Avoid by syncing starters, leavers, and changes into the deduction file each period.
• Manual re-keying between systems — copying amounts from a spreadsheet into payroll introduces transposition errors. Avoid by importing a generated deduction file in your payroll software’s native format.
• Treating the saving as the employer’s cost — forgetting the employer NI saving that helps fund the programme. Avoid by modelling the arrangement as cost-neutral up front.

How a platform integrates cleanly with payroll software

Workplace nursery benefit platforms simplify tax-efficient childcare support by removing the manual steps between enrolment and the payroll run. A clean integration does four things each month: confirms who is enrolled and for how much, runs the NMW floor check on every employee, produces a deduction file in a format your payroll software imports directly, and reconciles the payments out to nurseries. The aim is that payroll imports one file, applies one set of pre-tax deductions, and is done.

Platforms integrate cleanly with payroll software when they output standard deduction files that map to your provider’s import format, rather than asking you to re-key figures by hand. The heavy compliance work — Section 318 eligibility, the registered-nursery check, the NMW floor, the audit trail — sits in the platform, so payroll only ever sees a clean, checked set of pre-tax deductions.

See Halo for employers for how the programme is run, try the savings calculator to model an illustrative saving, and follow the payroll setup guide to wire the deduction file into your payroll software. If you are starting from scratch, read how to set up a workplace nursery.

This is not tax advice. Actual savings depend on your circumstances, employer participation, and nursery costs.