A car scheme, a bike scheme and a pension exchange
One client has just launched an electric car scheme through a provider. Another runs cycle to work each spring. Several use pension salary exchange. Each arrangement means a deduction from gross pay that starts on a date, may change when a car is swapped or an agreement is varied, and ends when the agreement ends or the employee leaves.
The details arrive however they arrive. A provider emails a monthly schedule. A client's HR person forwards an employee's agreement. An employee emails the bureau directly to say their car was delivered late. Somebody has to turn all of that into the right pay element, for the right amount, from the right period.
Why sacrifice arrangements trip bureaus up
Sacrifice deductions do not come from the client's normal payroll changes, so they bypass the intake routine. Start dates depend on events outside the payroll, such as a car delivery or a bike collection. End dates are often months or years away and nobody sets a reminder. Leavers with an active agreement need special handling that is easy to forget in a busy run.
The rules around what a sacrifice can reduce pay to, and how benefits are then reported, are set by HMRC and each client's own scheme terms. Those decisions belong to the client and their advisers. The operational problem for the bureau is making sure the agreed deductions are applied, changed and stopped at the right time.
What mistakes cost
A deduction that starts late or runs past its end date is a correction that affects pay, pension and possibly benefit reporting. Employees notice and are unhappy, particularly when a deduction continues after they returned a car. Providers chase clients for missing payments, and clients chase the bureau. At year end, arrangements recorded wrongly during the year create extra work on benefit reporting.
| Event | Where the information comes from | Common slip |
|---|---|---|
| New arrangement starts | Provider schedule or client instruction | Starts a period late |
| Amount changes | Provider variation notice | Old amount carried on |
| Arrangement ends | Agreement end date | Deduction keeps running |
| Employee leaves mid-agreement | Leaver notice | Settlement not handled as the scheme requires |
| Employee's pay drops | Hours or rate change | Nobody checks it against the sacrifice |
How we build a salary sacrifice register
- Every arrangement across every client is recorded in one register: employee, client, scheme type, provider, amount, start date, end date and the pay element it maps to in your payroll software.
- Provider schedules and notices sent to a dedicated address are read automatically, with a model extracting employee, amount and dates, and a person confirming anything unclear.
- Before each pay run, the register produces the sacrifice changes for that period for the administrator to approve and import, rather than having to spot them in emails.
- Arrangements approaching their end date are flagged in advance, so the deduction stops in the right period.
- When a leaver is processed, any active arrangement is flagged with the client's instructions for that scheme, so the settlement is handled as the client and provider require.
- A check compares each employee's pay after sacrifice with the limits you configure and flags anything below them for the client to review.
The register reports what has been agreed and applied. Whether an arrangement is set up correctly for tax and pay purposes is for the client and their adviser to decide.
Sacrifices that start and stop on time
Administrators see every arrangement affecting a run before they process it. Providers' schedules are handled the day they arrive, not found in an inbox at month end. End dates are caught in advance. Leavers with agreements are handled properly. And at year end, the bureau has a clean record of every arrangement across every client to hand to whoever does the benefit reporting.
Is salary sacrifice getting messy?
- Several clients run car, bike or pension sacrifice schemes.
- Provider schedules arrive by email and are applied by hand.
- A deduction has kept running after an agreement ended.
- Leavers with active agreements have caused corrections.
- Nobody has one list of every arrangement across the bureau.