Notices from three directions
HMRC sends tax code changes, student loan start and stop notices and similar updates for employees. Some reach your payroll software through its data service. Some appear in your online agent services. Some go on paper to the employer's address, and the client either forwards them, or does not.
An administrator applies the ones they see. A notice that arrived on paper at a client's office sits in a tray for a month. The employee pays the wrong tax for two periods, and HMRC's records and the payroll drift apart until the employee notices and rings.
Why notices get missed
Each route has its own place to look, and in a bureau with many clients, checking every route for every client each period is a job nobody fully owns. The software's automatic notice download helps, but only for the notices it receives and only if someone reviews and accepts them. Paper notices depend entirely on the client.
Timing matters too. A notice has an effective date, and applying it in the right period is part of getting it right. A notice found late is applied late.
What missed notices cost
Employees pay the wrong tax or loan deductions, which may be corrected later through their tax account but causes worry and calls now. Your bureau spends time explaining. Student loan deductions that start late create arrears for the employee; ones that continue after a stop notice create refunds. The client sees the bureau as the source of the problem, even when the notice never reached you.
| Notice route | Where it lands | What can go wrong |
|---|---|---|
| Payroll software data service | Inside the software | Downloaded but not reviewed |
| Agent online services | Your agent account | Not checked for every client |
| Paper to the employer | Client's office | Never forwarded |
| Employee tells the client | Email or conversation | No official notice attached |
How we build a notice queue
- We read notices from your payroll software's notice download, where it offers an API or export, and from the notices you retrieve through agent services.
- Clients get a simple way to send paper notices, a photo or scan to a bureau address, and are reminded periodically what to forward.
- Each notice is read into a structured record, employee, type, code or plan, effective date, and matched to the employee in your payroll records.
- The queue shows every notice with its status: received, matched, applied, and which run it affects.
- Before a run is signed off, the queue checks that every notice effective for that period has been applied, and flags any that have not.
- Notices that cannot be matched, for example an employee who has left, go to the administrator with a suggested action.
The queue records and checks. Applying a notice is still done in your payroll software by your administrator, following HMRC's instructions on the notice.
Every notice accounted for
Notices from every route land in one list. Paper notices get to the bureau in days rather than weeks. Nothing effective for a period is left unapplied when the run is signed off. And when an employee asks why their code changed, the administrator can find the notice in seconds.
Is your notice handling patchy?
- Paper notices reach you late or not at all.
- Nobody checks agent services for every client each period.
- Tax code notices are accepted in the software without review.
- Student loan deductions have started or stopped late.
- Employees ring about codes before you know a notice arrived.