Figures › Redundancy

Maximum statutory redundancy pay

The maximum statutory redundancy payment — 20 × 1.5 × the capped week's pay, the canonical form of the statutory derivation.

£22,530.00
Derivation verified Derived Great Britain in force since 2026-04-06

Checked against its sources: statute verified 2026-09-21·guidance verified 2026-09-21

Scope: A CEILING, reached only by an employee with twenty or more reckonable years ALL served at or after forty-one and a week's pay at or above the statutory limit; every other case is less, because s.162(2) allows one week's pay for a year served between twenty-two and forty and half a week's pay for a year below that (Redundancy pay: weeks per year of service, age 22 to 40 and …under_22). Great Britain only — the Northern Ireland maximum (Northern Ireland: maximum redundancy payment and basic award) rests on a different Order with a different cap and is never coupled to this one. The limbs are Redundancy pay: maximum years of service counted, Redundancy pay: weeks per year of service, age 41 and over and Maximum week's pay (redundancy and unfair dismissal); this record is only their product (D14), and the build refuses a build in which they disagree.

How it is worked out: Redundancy pay: maximum years of service counted × Redundancy pay: weeks per year of service, age 41 and over × Maximum week's pay (redundancy and unfair dismissal) — recomputed from its corroborated inputs on every build.

Current sources

History

ValueFromToStatusSources
£22,530.002026-04-06—Derivation verified

Receipt

Everything above is reproducible and independently checkable — no trust in this site required (how verification works).

Figure ID
employment.redundancy.max_payment
Name in the API
Maximum statutory redundancy payment (30 weeks x capped week's pay)
Record fields (source type · unit · jurisdiction · status)
derived·GBP·GB·derivation_verified
Derivation
employment.redundancy.service_cap_years@numeric * employment.redundancy.age_multiplier.41_and_over@numeric * employment.redundancy.weekly_pay_cap
Record hash (canonical JSON, SHA-256)
sha256:5e339cacdd2e514d5175addbe83f6add5c6b9f85852ddaf47c1d1e53ff05c86b
Source snapshots (SHA-256)
Legislation: sha256:02a10a969b94cf04366e8f0425d3b8d4c697bbd76dfd5e7964814b00cf8ca162
Legislation: sha256:e38d02439befd69a9eae7bee9249fb1e7eaeda026295edb37fadf4d42abfd510
Official guidance: sha256:6ccddcb3b0098580207823ba25cd4300ade2ee1c8cb94c7105ef3bd602415490
Listed in the signed manifest
release 3.0.0 manifest · record_hashes["employment.redundancy.max_payment"]
Machine-readable record
/v1/figures/employment.redundancy.max_payment · current only: /v1/figures/employment.redundancy.max_payment/current
Compiler's notes

Not a figure any document states, which is why it is a derivation and not a carry — s.162 gives a calculation and prints no sum. NO LITERAL REMAINS IN THE FORMULA, and that is the change this row records. The old spelling was 20 * 1.5 * Maximum week's pay (redundancy and unfair dismissal), written at Gate 0 when neither digit had a record to point at; both now do, so the 20 reads Redundancy pay: maximum years of service counted (s.162(3), “twenty years”) and the 1.5 reads Redundancy pay: weeks per year of service, age 41 and over (s.162(2)(a), “one and a half weeks' pay”), each through @numeric, the selector the DSL reads a scalar count or ratio with. The value is unchanged at £22,530.00 and Gate 2 recomputes it from the same three numbers. This is the opposite case to Statutory pay recovery: small employers (total), whose 100 must stay a literal because regulation 4(b)(i) states its proportion in words and no record can hold it: here the statute states both multipliers outright, so a literal would have been a second copy of a figure the corpus already carries. The record's NAME still says “30 weeks”, which is 20 × 1.5 and is how the guidance and the profession say it; the name is a label, not the formula. The declared invariant on Maximum week's pay (redundancy and unfair dismissal) (“max_payment == 20 * 1.5 * this”) still spells its multipliers as digits — it is a Gate 0 leftover on a record this script does not own, and FM-7 already recomputes the same identity every build, so it is a duplicate to retire rather than a second place to edit.