The Procurement (Amendment) Regulations 2026 (S.I. 2026/360) revise procurement thresholds and add two new duties: supplier registration on the Central Digital Platform and expanded contract payment transparency. New thresholds take effect from 1 January 2026, supplier identifier checks apply to below-threshold awards from 1 April 2026, and further amendments remain deferred. Contracting authorities should review live pipelines now, update valuation templates, and prepare supplier-facing communications before either date lands.
TL;DR:
- From April 2026, suppliers must register on the Central Digital Platform before contract award, but registration is not required to submit a bid.
- Threshold values for above- and below-threshold procurements vary by authority type, with the central government limit set at £135,018 including VAT.
- Contract valuation must include options, extensions, and renewals and be calculated conservatively to avoid classification challenges.
- Payment transparency duties will require timely publication of payment details on the platform, with designated ownership within contracting authorities.
- Keep track of amended commencement dates through official legislation updates, as some provisions remain deferred or subject to later change.
Table of Contents
- What changed in 2026: the statutory amendments and commencement timetable
- Thresholds from 1 January 2026: the figures and what they mean in practice
- Central Digital Platform and supplier identifier: process and impact from 1 April 2026
- Contract payment information and transparency obligations
- Compliance checklist for contracting authorities: practical next steps
- What suppliers and bidders must do now
- Where to read the rules and authoritative guidance
- Impact on existing procurement frameworks and legacy contracts
- How procurement procedures and principles have shifted under the Act
- Compliance risks and legal implications under the new Act
- Impact on supplier diversity and small business participation
- How the Act plays out in practice: illustrative scenarios
- Overview and key objectives of the Procurement Act 2026 amendments
- Transitional and deferred commencement items
- Practitioner perspective: implementing the Act as organisational change
- How Bidblock helps you stay ready for these changes
- Sources
- FAQ
What changed in 2026: the statutory amendments and commencement timetable
The Procurement (Amendment) Regulations 2026 amend the Procurement Regulations 2024 and, by extension, how contracting authorities apply the Procurement Act 2023 in practice. The instrument does not rewrite the Act's core principles. It tightens operational detail around thresholds, supplier verification, and payment reporting, inserting two new regulations that practitioners need to know by number: regulation 36A on supplier registration checks and regulation 38A on contract payment information. Both sit inside the amending regulation itself, which sets out exactly what wording changes in the 2024 Regulations.
The commencement structure is not a single switch date. It works in stages, and getting the stages wrong is the most common early mistake teams make.
- 1 January 2026 — revised threshold amounts apply to all new procurements valued from this date, replacing the previous two-year threshold set.
- 1 April 2026 — the supplier identifier and Central Digital Platform registration requirement takes effect for below-threshold contract awards.
- Ongoing — payment information publication duties under regulation 38A apply progressively as contracts reach relevant payment milestones after commencement.
- Deferred — a small number of provisions originally scheduled for October 2026 have been pushed back by a further amending instrument.
That last point matters more than it might look. The Procurement (Amendment) (No. 2026/746](https://www.legislation.gov.uk/uksi/2026/746/made). This is not a one-off. Amending instruments of this kind have become a recurring feature of Procurement Act rollout, and teams that only check the original S.I. 2026/360 risk working from a stale commencement date. Build a habit of checking legislation.gov.uk for later amendments before finalising any date-sensitive compliance plan, rather than treating the first instrument you read as final.
Thresholds from 1 January 2026: the figures and what they mean in practice
Procurement Policy Note 023 sets out the revised threshold figures that determine whether a procurement falls under above-threshold or below-threshold rules from 1 January 2026. The headline number for most public sector buyers is £135,018, the central government threshold for goods and services contracts.
| Category | Threshold from 1 January 2026 |
|---|---|
| Central government: goods and services | £135,018 |
| Sub-central authorities: goods and services | £207,720 |
| Works contracts | £5,193,000 |
| Concession contracts | £5,193,000 |
| Utilities: goods and services | a threshold figure listed in Annex A for exact amount |
These figures come from PPN 023: 2026 threshold amounts, and the Annex A table is the definitive reference for any threshold not listed above.
Pro Tip: Every threshold figure is VAT-inclusive. A contract estimated at £132,000 net of VAT crosses the £135,018 central government threshold once VAT is added, so value on a gross basis from the outset.
Thresholds move every two years because the UK's Government Procurement Agreement obligations with the World Trade Organisation are set in Special Drawing Rights, and sterling equivalents shift with exchange rates, as Cabinet Office guidance on thresholds explains. That is a currency mechanic, not a policy change, but it catches teams out every cycle because the number itself does move even when nothing else about the rules has changed.
The safest operational rule is simple: if your estimate sits close to a threshold, run the procurement as if it were above-threshold. Include every option, extension, and renewal in your value calculation rather than the base contract term alone. Treating a borderline estimate as below-threshold to avoid extra process is the single most common source of legal challenge risk in threshold classification, and it is entirely avoidable with a conservative valuation habit.
Central Digital Platform and supplier identifier: process and impact from 1 April 2026
From 1 April 2026, suppliers awarded below-threshold public sector contracts must register on the Central Digital Platform and obtain a unique supplier identifier. This is an award-stage requirement, not a bidding requirement. Suppliers do not need to hold an identifier to submit a tender, according to the techUK supplier update summarising the Cabinet Office announcement, but they must confirm registration before the contract is formally awarded.
For contracting authorities, this changes the award checklist:
- Confirm the winning supplier's Central Digital Platform registration status before issuing the award notice.
- Record the unique identifier against the contract file, not just the supplier name, so future reporting links back correctly.
- Allow for limited circumstances where confirmation happens shortly after award rather than before it, but do not treat this as a default.
- Reuse an existing identifier where a supplier already holds one from a prior award rather than requesting fresh registration.
For suppliers, the practical task is straightforward but easy to leave too late: register before you expect to win, not after. A registration delay at award stage can hold up contract signature and payment scheduling, which is an unnecessary risk for a process that takes minutes to complete once the right details are to hand.
Pro Tip: Register your organisation on the Central Digital Platform as soon as you start actively bidding, not when you receive a contract award notification. Waiting until award stage to register is the single most avoidable delay suppliers create for themselves.
Contract payment information and transparency obligations
Regulation 38A, inserted by S.I. 2026/360, expands what contracting authorities must publish about contract payments once a contract is running. This builds on the existing section 70 duty to publish payment information and sharpens what counts as reportable data at each payment milestone.
Authorities need to record and publish payment details in a consistent, timely way rather than treating this as a retrospective reporting exercise. In practice that means:
- Publishing payment information through the Central Digital Platform as the default route.
- Using a permitted alternative publication method only when the platform is genuinely unavailable, not as a matter of convenience.
- Capturing payment date, amount, and supplier identifier at the point of payment, not weeks later during a reporting cycle.
- Assigning a named owner within finance or contract management who is accountable for each publication cycle.
The operational risk here is less about the legal text and more about workflow. Payment data usually sits with finance teams, while procurement teams own the contract record, and the two rarely talk to each other on a fixed schedule. Building a simple handoff, where finance flags a payment event and procurement confirms the publication, closes that gap before it becomes a compliance finding.
Compliance checklist for contracting authorities: practical next steps
Turning the legal text into a working process takes four ordered steps.
- Identify affected procurements. Pull every live and planned procurement in your pipeline and flag those starting on or after 1 January 2026, or expecting award on or after 1 April 2026. These are the two dates that determine which rules apply.
- Update valuation templates. Rebuild your value calculation template to include VAT by default and to force inclusion of options, extensions, and renewals in the total estimate, not just the base term.
- Amend notice and award templates. Add fields for the supplier unique identifier and for the payment disclosure data points regulation 38A requires, so these are captured once rather than chased retrospectively.
- Assign internal ownership. Name who signs off legal compliance, who in finance captures payment data, and who in IT or procurement operations handles the Central Digital Platform upload. Ambiguous ownership is where most compliance gaps open up.
Pro Tip: Run a single test procurement through the full updated template before your first live award under the new rules. It surfaces missing fields and unclear ownership far more cheaply than discovering them on a live contract worth several hundred thousand pounds.
Cabinet Office guidance recommends treating this rollout as an organisational change exercise, not a document update, according to its short guide for senior leaders. Teams that assign this purely to a compliance officer, rather than building cross-functional buy-in, tend to find the gaps later and more expensively.
What suppliers and bidders must do now
Suppliers face a shorter but equally time-sensitive list of actions. The two headline items are registration and pricing discipline, but the smaller housekeeping tasks are what actually cause delays at award stage.
- Register on the Central Digital Platform and retain your unique identifier somewhere your bid team can find it quickly, since you will need it confirmed at award, not before.
- Rebuild your pricing models around VAT-inclusive figures, matching how contracting authorities now value contracts against threshold, so your quoted price and their valuation align.
- Keep your evidence library, case studies, and social value materials organised and current, so a fast turnaround request doesn't catch you scrambling for old documents.
- Maintain up-to-date accreditations with renewal dates visible, and respond quickly when a buyer asks for identifier confirmation or payment publication consent post-award.
None of these are individually difficult. The risk is timing. A supplier who leaves registration or accreditation renewal until an award notice lands is adding avoidable delay to their own contract start date.
Where to read the rules and authoritative guidance
Primary legal text should always be your first stop, not a summary of it. Start with the Procurement (Amendment) Regulations 2026 for the amending text itself, then check legislation.gov.uk periodically for further amending instruments affecting commencement dates.
- PPN 023: 2026 threshold amounts — the full Annex A table with every threshold category, not just the headline figures.
- Procurement Act 2023 guidance documents (Cabinet Office) — the full guidance collection, organised by Plan, Define, Procure, and Manage phases.
- Procure-phase documents specifically, since these cover publication, payment reporting, and Central Digital Platform mechanics in the most operational detail.
- Chambers Practice Guide on public procurement, useful for cross-referencing how legal advisers interpret the interaction between the Act, the 2024 Regulations, and amending instruments, per its 2026 practice guide.
Treat the Cabinet Office guidance collection as the working reference, not the statutory instruments alone. The instruments tell you what changed; the guidance tells you how to apply it on a live procurement.
Impact on existing procurement frameworks and legacy contracts
The 2026 amendments do not retrospectively rewrite contracts already awarded under the previous threshold regime. A contract signed under 2024 thresholds continues under the terms and value bands that applied at the point of award. Where this gets complicated is with frameworks and dynamic markets that remain open for call-offs after 1 January 2026.
A framework agreement established before the new thresholds took effect can still be used to place call-off orders after commencement, but each new call-off should be valued against the current, not historic, threshold figures when deciding whether above-threshold procedures apply. This is easy to miss because the framework itself was set up under older rules, creating a false sense that everything running through it is grandfathered.
Payment information and supplier identifier duties are similarly forward-looking rather than retrospective in most cases. A contract awarded before 1 April 2026 does not need retrospective supplier identifier registration, but any variation, extension, or new call-off processed after that date is likely to trigger the new requirement depending on how it is structured.
The practical lesson is that legacy contracts are not a safe harbour indefinitely. Any live framework, call-off arrangement, or extension mechanism needs a fresh look against the current rules rather than an assumption that the original award date settles the question permanently.
How procurement procedures and principles have shifted under the Act
The Procurement Act 2023 replaced the previous EU-derived procedure set with a smaller number of flexible procedures, and the 2026 amendments refine how those procedures interact with valuation and reporting rather than introducing new procedure types. The core principles, value for money, integrity, transparency, and non-discrimination, remain unchanged in substance.
What has shifted is the mechanics around those principles. Transparency now has a harder edge through the expanded payment publication duty under regulation 38A, moving transparency from a general principle into a specific, checkable data requirement tied to individual payment milestones. That is a meaningful change in enforceability, even without any change to the underlying principle.
Supplier verification has moved from something contracting authorities handled ad hoc, checking accreditations and financial standing case by case, into a more structured process anchored by the Central Digital Platform identifier. This does not replace due diligence on suitability, but it standardises one specific verification step across every below-threshold award from April 2026.
For procurement teams running competitive flexible procedures under the Act, the 2026 changes mainly affect the paperwork layer: valuation templates, award notices, and payment records need to reflect the new fields. The underlying procedural choices, how you structure a competitive tendering process or a direct award justification, are governed by the Act itself and remain as they were before this amendment round.
Compliance risks and legal implications under the new Act
The clearest legal risk sits in threshold misclassification. Valuing a contract without VAT, or without options and extensions, and running it as below-threshold when it should be above-threshold, is a defect that a losing bidder can challenge. The 2026 threshold changes make this risk slightly sharper because teams working from memory rather than updated templates may apply the previous year's figures without realising thresholds have moved.
Failure to check Central Digital Platform registration before award creates a different kind of risk: a delayed or defective award process rather than a challenge on the merits, but one that can still hold up contract start dates and frustrate the winning supplier. Authorities that build the identifier check into their award workflow avoid this almost entirely.
For payment information duties, the risk is less about legal challenge and more about compliance exposure over time. Missing or late payment publication doesn't typically invalidate an award, but it builds a pattern of non-compliance that becomes harder to defend if scrutinised later, whether by an oversight body or through a Freedom of Information request.
Suppliers carry a narrower but real risk too. Missing registration at award stage can delay contract signature, and inconsistent VAT treatment in bid pricing can create a mismatch between what was quoted and how the buyer values the contract for threshold purposes, occasionally triggering unnecessary process reviews on otherwise straightforward awards.
Impact on supplier diversity and small business participation
Below-threshold procedures remain the primary route through which small and medium-sized suppliers access public contracts, and the 2026 threshold increases modestly widen that route by lifting the value ceiling under which lighter-touch procedures apply. A contract that would have required above-threshold procedures under the previous threshold set may now sit comfortably below it, reducing procedural burden for both buyer and bidder.
The Central Digital Platform registration requirement is where the impact on smaller suppliers deserves closer attention. Registration itself is free and reasonably quick, but it is an additional administrative step that larger suppliers with dedicated bid teams will absorb without friction, while a small business bidding alone may not register until prompted at award stage, creating exactly the kind of delay the rules are meant to avoid.
Social value and evidence-based bidding remain the most reliable lever smaller suppliers have to compete against larger incumbents, regardless of threshold movements. Contracting authorities scoring social value contributions and demonstrable past performance, rather than headline price alone, give smaller and newer suppliers a genuine route to award. That dynamic is unchanged by the 2026 amendments, but it becomes more important as VAT-inclusive valuation and identifier checks add administrative steps that favour organisations with more bidding infrastructure.
How the Act plays out in practice: illustrative scenarios
A local authority preparing to procure a facilities management contract worth an estimated £128,000 net of VAT under the old threshold set would have treated it as below-threshold. Once VAT and the new £135,018 central government figure are applied, the same contract may sit right at the boundary, and a conservative authority would now run it above-threshold to avoid challenge risk, exactly the operational rule described earlier in the thresholds section.
A specialist IT services supplier winning a below-threshold contract in March 2026 would fall outside the Central Digital Platform requirement, since that duty starts 1 April 2026. The same supplier winning an equivalent award in May 2026 would need to confirm registration before the contract is formally awarded, an outcome that depends entirely on which side of the commencement date the award notice falls.
A housing association running a multi-year framework agreement established in 2025 continues honouring existing call-offs without disruption, but any new call-off placed after January 2026 needs revaluation against current thresholds before deciding whether above-threshold procedures apply, echoing the legacy framework point covered earlier. These scenarios share one lesson: the exact date an award notice is issued, not when the procurement started, tends to determine which rule set applies.
Overview and key objectives of the Procurement Act 2026 amendments
The 2026 amendments exist to keep the Procurement Act 2023 regime current rather than to change its underlying direction. Three objectives sit behind the changes: keep thresholds aligned with the UK's international trade obligations, close a verification gap around who is actually receiving public money below threshold, and sharpen payment transparency so subcontractors and smaller suppliers further down the supply chain have visibility into payment practice.
The threshold update is administrative housekeeping tied to currency movement under the Government Procurement Agreement, not a policy shift. The supplier identifier requirement is the more substantive change, introducing a single verifiable record of who holds public contracts even where full above-threshold competitive procedures don't apply. The payment transparency provisions extend a principle that already existed under section 70 into more specific, checkable obligations tied to actual payment events rather than general reporting.
Read together, the 2026 instruments push the Act's original ambitions, more transparency, better value for money, wider small business access, further into operational reality rather than introducing new policy territory. That is broadly good news for practitioners: it means the compliance burden is about updating process and templates, not relearning the Act's structure from scratch.
Transitional and deferred commencement items
Not every provision tied to the 2026 amendment round comes into force on schedule, and tracking deferrals is now part of standard compliance practice rather than an edge case. The clearest example is the Procurement (Amendment) (No. 2026/746](https://www.legislation.gov.uk/uksi/2026/746/made).
This pattern, an instrument setting a commencement date followed months later by a further instrument deferring it, has repeated across the Procurement Act rollout since 2023. It reflects genuine implementation complexity rather than policy indecision, but it creates a practical hazard for teams who build compliance plans around the first commencement date they encounter and never check for later amendments.
The safest practice is to treat any commencement date more than a few months out as provisional until closer to the date, and to check legislation.gov.uk for amending instruments before finalising internal deadlines tied to it. Teams building templates or training material around a specific future date should build in a review checkpoint roughly a month before that date to catch any last-minute deferral.
Practitioner perspective: implementing the Act as organisational change
The teams handling this well aren't the ones with the best legal summary. They're the ones who got legal, finance, and IT talking to each other before the deadlines hit, not after.
The most common pitfall isn't misunderstanding the law. It's pipeline misclassification, applying last year's thresholds out of habit, and under-resourcing the Central Digital Platform upload process until a deadline is already close. Cabinet Office guidance is right to frame this as an organisational change programme rather than a document update, because the failure mode is almost always operational, not legal. Senior leaders who treat this as a training and process exercise, not a one-off compliance memo, will find April 2026 far less disruptive than those who don't.
— Syed
How Bidblock helps you stay ready for these changes
For suppliers, the practical burden of the 2026 changes lands squarely on organisation: keeping evidence current, pricing consistently in VAT-inclusive terms, and having accreditation details ready the moment a buyer asks. That's the gap Bidblock is built to close, rather than adding another compliance layer on top of an already stretched bid process.
An evidence library can keep past submissions, case studies, and social value evidence organised and ready to reuse, so responding to an award-stage request doesn't mean digging through old folders. Pipeline tracking can help flag which live opportunities sit near new thresholds, so valuation decisions happen with current figures in view.
If you're managing bids against a shifting regulatory timetable, visit Bidblock to start a trial and see how the platform fits your current pipeline.
Sources
- PPN 023: 2026 threshold amounts
- The Procurement (Amendment) Regulations 2026 (regulation 3)
- Gov
- Procurement Act change from 1 April 2026: public sector supplier update - techUK
FAQ
What are the Procurement Act thresholds for 2026?
From 1 January 2026, the central government threshold for goods and services is £135,018, and the sub-central authority threshold is £207,720, with works and concession contracts set at £5,193,000, according to PPN 023. These figures are VAT-inclusive and apply to procurements valued from that date.
Has the Procurement Act 2023 been amended for 2026?
Yes. The Procurement (Amendment) Regulations 2026 (S.I. 2026/360) amend the Procurement Regulations 2024, introducing supplier registration checks and expanded payment information duties, as set out in the amending regulation. A further instrument, S.I. 2026/746, has since deferred the commencement of certain other provisions.
What is the procurement threshold for services in the UK from 2026?
For central government contracting authorities, the goods and services threshold is £135,018 from 1 January 2026, rising to £207,720 for sub-central authorities such as most local councils, per PPN 023. These thresholds are reviewed every two years to reflect currency movement under the UK's Government Procurement Agreement obligations.
Do suppliers need to register on the Central Digital Platform before bidding?
No. Registration is required at contract award for below-threshold awards from 1 April 2026, not as a condition of submitting a bid, according to the techUK supplier update. Suppliers are still advised to register early to avoid delays once an award notice is issued.
Does Bidblock support compliance with the 2026 Procurement Act changes?
Bidblock helps suppliers keep evidence, accreditation records, and past bid responses organised so they can respond quickly to award-stage requests, including identifier confirmation. Current plans and pricing are available on the Bidblock website.