UK payroll rules now change mostly through guidance, specifications and enforcement, and none of those arrives on the calendar a vendor's release plan is built around.
01
02
The rules UK payroll software has to follow are changing, but mostly not through Parliament. Since August the scope of the Construction Industry Scheme moved through a guidance edit, personal liability for company officers arrived in a penalty factsheet, the build for real-time benefits reporting was defined by a technical specification and a data guide, and employers were named for minimum-wage errors with the published diagnostic withdrawn.
Each of those changes what a payroll engine must calculate, report or keep. None of them came with a consultation or a commencement date, which is the calendar vendor release planning is built around. The obligation arrives faster than the build cycle, and without a public account of what went wrong.
What follows. Vendors that read the guidance layer directly ship compliant first and can sell change latency as a capability. Vendors planned around legislation ship late or carry the statutory error in their own marketing guidance. Enforcement rounds become marketing triggers, because there is no diagnostic to answer instead.
What would change our mind. If, over two consecutive quarters, more material UK payroll changes arrive through legislation with a consultation and a commencement date than through guidance, specification, enforcement or withdrawal combined, the claim is wrong. The Budget on 28 October is the first test.
03
UK payroll obligations now change mostly through the administrator's guidance, technical specifications, enforcement actions and withdrawn submission routes rather than through legislation with a consultation and a commencement date. Each of those channels changes what a payroll engine must calculate, report or keep, but none produces the dated, consulted instrument that vendor release planning is built around, so the obligation arrives faster than the build cycle and without a public diagnostic of what went wrong.
04
Vendors that track the guidance layer directly (specification change logs, factsheets, enforcement lists, GOV.UK change history) ship compliant first and can sell change latency as a capability; vendors planned around the legislative calendar ship late, or publish statutory parameters in their own guidance that the correction cycle never reaches. Construction and benefits payroll are exposed first, because HMRC's CIS and payrolling-of-benefits changes are running through this channel now. Buyers begin asking how a vendor learns of a guidance change, not only which regulations it supports, and enforcement rounds (the minimum-wage naming list) become marketing triggers because there is no published diagnostic to answer instead.
05
Scoped to the United Kingdom, where the channel is measured. France, Germany, Spain, South Africa and the US are not claimed; their regulators are polled but not yet classified by channel.
06
Given equal weight to the claim. Hiding the counter is how a prediction becomes an article of faith.
07
08
Specific public numbers we check on a schedule, so this claim can be tested without taking our word for it. Not checked means nobody looked. That counts as nothing, never as agreement.
| What we check | Status | Latest reading | Last checked |
|---|---|---|---|
| Material UK payroll-obligation changes recorded per quarter, classified by channel: legislation-with-consultation versus guidance, specification, enforcement or withdrawn route GOV.UK content API (public_updated_at and change history), HMRC specifications, CIPP news, legislation.gov.uk · quarterly | changing | Q3 2026 to date, per this corpus: guidance/specification 4 (CIS financing clarification 11 Aug, adviser registration 19 Aug, BIK guidance decisions 4 Sept with RTI specification 9 Sept and data item guide 16 Sept, vendor-carried PRSI rate 2 Sept), enforcement 3 (NMW naming 3 Sept, umbrella listing 10 Sept, CIS officer-liability factsheet 15 Sept), withdrawn route 1 (DfE accounts automation 20 Aug); legislation-with-consultation 2 (tipping code 19 Aug, holiday-pay enforcement consultation open to 22 Sept). | 2026-09-18 |
09
Cumulative linked signals, by direction. A line that only climbs in green is being read generously.
3 counted: 2 contradicts · 1 supports · 9 predate the claim and are not counted
| Date | Signal | Bearing | On which part of the mechanism |
|---|---|---|---|
| 2026-08-11 | signal-hmrc-cis-financing-clarification | Before the claim (not counted) | Obligations change through guidance or technical specification. |
| 2026-08-19 | signal-uk-adviser-registration-phase-two | Before the claim (not counted) | Obligations change through guidance or technical specification. |
| 2026-08-19 | signal-uk-tipping-code-consultation | Before the claim (not counted) | Obligations change through legislation with a consultation and a commencement date (the counter-channel). |
| 2026-08-20 | signal-dfe-withdraws-accounts-automation | Before the claim (not counted) | Administrative routes that software relied on are withdrawn. |
| 2026-09-02 | signal-brightpay-prsi-wrong-rate | Before the claim (not counted) | Obligations change through guidance or technical specification. |
| 2026-09-03 | signal-fwa-nmw-naming-no-diagnostic | Before the claim (not counted) | Obligations are enforced and signalled through naming, penalties and factsheets. |
| 2026-09-07 | signal-employment-hero-nmw-claim | Before the claim (not counted) | Obligations are enforced and signalled through naming, penalties and factsheets. |
| 2026-09-15 | signal-hmrc-cis-officer-liability | Before the claim (not counted) | Obligations are enforced and signalled through naming, penalties and factsheets. |
| 2026-09-16 | signal-hmrc-rti-2027-data-item-guide | Before the claim (not counted) | Obligations change through guidance or technical specification. |
| 2026-09-22 | signal-uk-bereavement-pregnancy-loss-leave | contradicts | Obligations change through legislation with a consultation and a commencement date (the counter-channel). |
| 2026-09-18 | signal-lords-finance-bill-bik-inquiry | contradicts | Obligations change through legislation with a consultation and a commencement date (the counter-channel). |
| 2026-09-21 | signal-hmrc-cwg2-relevant-accretions | supports | Obligations change through guidance or technical specification. |
10
Graduated from pattern 'compliance-through-guidance' (themes uk-payroll-params-by-guidance, uk-bik-realtime-build, enforcement-without-a-diagnostic, enforcement-as-a-marketing-trigger, vendor-guidance-carries-the-statutory-error, statutory-automation-withdrawn) on 2026-09-18 by ledger_eval.py T2: 6 digests in 28 days with no prediction carrying it.
This prediction carries no resolution date. We cannot predict when evidence will arrive, so the review cadence attaches to the instruments above rather than to the claim. It runs until the market proves it, moves it, or twelve months pass with no material signal against it.
How a signal becomes a prediction →