Skip to content
allanninal.dev/build
Collaborate

Part 3 of 7 · Pension enrolment assessor series ~5 min read

Postponement is a decision with a date on it

High-turnover employers postpone new starters as a matter of routine, and for a reasonable reason. What turns a reasonable policy into a compliance failure is treating it as something the payroll does, rather than a decision somebody makes about a person, on a date, with a letter.

Key takeaways

  • Every duty hangs off a date: a first pay run, a crossing, or a birthday.
  • The joining window is six weeks from the automatic enrolment date.
  • Postponement lasts up to three months and needs a written notice to the worker.
  • On the deferral date the worker is assessed again, and a new window can open.
  • Postponement cannot be used at re-enrolment.

Three ways a duty starts

Three routes to an automatic enrolment date and the joining window that followsThree boxes on the left feed one box on the right. A new starter, over the trigger in their first pay run, labelled day one. Pay crosses the trigger, meaning earnings paid in one pay period, labelled any pay run. A birthday, turning 22 while already paid over the trigger, labelled on the date. All three converge on Automatic enrolment date, the date every deadline hangs off, which feeds a box labelled Six-week joining window: enrol and write, or postpone. A note says three routes lead to one date, and a date that is wrong by a week moves every deadline after it by a week, invisibly until one is missed.A new starterover the trigger intheir first pay runday onePay crosses the triggerearnings paid inone pay periodany pay runA birthdayturning 22, alreadypaid over the triggeron the dateAutomatic enrolment datethe date everydeadline hangs offSix-week joining windowenrol and write,or postponeThree routes, one date. A date that is wrong by a week moves every deadline after it by a week, and nothing about that is visible until one is missed.
Fig 1. Three ways a worker becomes an eligible jobholder, converging on the one date the rest of the system is built around.
  • Management
  • Analytics
  • People

Why the date is stored, not derived

It is tempting to work the automatic enrolment date out whenever it is needed, from the assessments. It is also a reliable way to get a different answer after a payroll correction. If a December pay run is re-issued because somebody’s hours were keyed wrongly, the week a worker crossed the trigger can change, and a recomputed date would quietly move a deadline behind a letter that has already been sent.

So the date is written once, when the assessment that created the duty is made, beside the id of that assessment. A later correction produces a new assessment and, if the date genuinely moves, a new duty record that supersedes the old one and says why. The letter that went out is still explained by the record that existed when it went out.

The six weeks

From the automatic enrolment date the employer has six weeks, the joining window, to arrange active membership effective from that date and to write to the worker with the enrolment information. Contributions are calculated on earnings paid from the automatic enrolment date, which is why an enrolment made late in the window is a payroll adjustment and one made after it is a conversation.

In a weekly payroll six weeks is six pay runs, and the practical risk is not forgetting but assuming: that the module did it, that the site manager sent the letter, that the upload to the provider succeeded. The system does not enrol anybody itself. It holds the duty open until evidence of each part arrives — the provider’s confirmation, the letter’s send record — and escalates when the fifth week begins with either missing.

Postponing, properly

Postponement from the duty arising to the assessment on the deferral dateA horizontal row of five boxes joined by arrows. Duty arises, from a first pay run or a crossing. Notice sent, in writing within six weeks. Deferral date, up to three months later. Assess again, on the pay for that period. And Enrol or not, with a new window if the worker is eligible then. A note says the second box is what makes it postponement, and without the notice the first box is simply an enrolment that did not happen.POSTPONEMENT, FROM DECISION TO REASSESSMENTDuty arisesa first pay runor a crossingNotice sentin writing, withinsix weeksDeferral dateup to threemonths laterAssess againon the pay forthat periodEnrol or nota new window ifeligible thenThe second box is what makes it postponement. Without the notice, the first box is simply an enrolment that did not happen.
Fig 2. Five steps, one of them a letter. A worker can also opt in at any point while postponed, which ends the postponement for them.
  • App integration
  • Machine learning
  • Analytics

A decision, made by somebody, about somebody

In the worked example the group postpones new starters because 71 of last year’s 188 starters left within three months. That is a sound reason and the system does not second-guess it. What it will not do is hold postponement as a flag in the payroll that applies to everybody who joins, because a flag has no date, no notice and nobody who decided it.

Instead each postponement is a record: the worker, the duty it postpones, the deferral date, who decided, and the send record of the notice. The notice tells the worker they have been postponed and that they can opt in during the postponement. A worker who does opt in ends it for themselves, and the system opens the enrolment duty from the day their notice arrived.

What happens on the deferral date

On the deferral date the worker is assessed again, on what they are paid in the pay period that includes it. If they are an eligible jobholder then, the deferral date becomes their automatic enrolment date and a fresh six weeks begins. If they are not — a porter paid £141.35 that week — they are not enrolled, and the duty comes back the ordinary way the next time a pay run crosses the trigger.

That second outcome is where a flag does its real damage. The payroll believes the worker has been dealt with, because a postponement ran its course. The per-period assessment keeps running regardless, and that is the only reason the later crossing gets caught at all.

What a postponement record holds

  • Worker and duty. The duty it postpones, and the date that duty arose.
  • Deferral date. No more than three months after postponement started.
  • Decided by. A named person and a reason, even when the reason is policy.
  • Notice. The send record and its date, checked against the six weeks.
  • Opt-in. Set if the worker opted in while postponed, which ends it.
  • Outcome. The assessment made on the deferral date, by id.

Where postponement cannot help

Postponement is a tool for first enrolment. The Regulator’s guidance is plain that it cannot be used at cyclical re-enrolment, and the system enforces that by refusing to create a postponement record against a re-enrolment duty, rather than by trusting somebody to remember the rule three years after they last read it.

The next post is the part of the system that deals with staff, or more exactly reads what staff write: the messages about the pension, and what a sentence like I don’t want it is and is not allowed to turn into.

All posts