What the Procurement Act 2023 Means for Your Contract Management System

The Procurement Act 2023 has been live since February 2025, and most of the attention so far has landed on the sourcing side: new notice types, new procedures, the central digital platform. Understandably so — those changes were immediate and visible.

But the part that’s proving harder to absorb is quieter and more persistent. It lives inside your contract management processes, your finance systems, and your reporting infrastructure. And unlike a one-off compliance exercise, it doesn’t stop once a contract is awarded.

This post covers what changed, what you’re now required to do, what that means for your systems, and how to approach it practically.

What changed

Under the old Public Contracts Regulations 2015 framework, transparency obligations were concentrated at the front end of procurement — advertising opportunities, publishing award notices. Contract management sat largely in the shadows. Once a contract was signed, the public record largely went dark.

The Procurement Act 2023 changes that fundamentally. Transparency is now a requirement across the entire contract lifecycle — from pipeline to termination. That means ongoing obligations to publish, record, and report at multiple points during the life of every in-scope contract.

The new notice framework reflects this. Where the old regime had a handful of notice types, PA2023 introduces a structured sequence: pipeline notices (UK1), market engagement (UK2), tender notices (UK4), award notices (UK6), contract details (UK7), performance notices (UK9), change notices (UK10), termination notices (UK11), and payments compliance notices (UK17). Each one has its own trigger, timeline, and content requirement.

This isn’t bureaucracy for its own sake. The policy intent is genuine: to make public spending more scrutinisable, to give suppliers a clearer picture of how authorities operate, and to create a data infrastructure that supports better commercial decisions over time. But the operational reality is that your contract management system now needs to support a level of ongoing publication it was probably never designed for.

What public bodies now need to do

Three obligations in particular are reshaping day-to-day contract management.

Track and report supplier performance (UK9)

For any public contract with an estimated value above £5 million, you are now required to set and publish measurable KPIs at the outset and report against them at least annually using the UK9 Contract Performance Notice. The notice must record actual performance scores, not just whether targets were broadly met. It also has a second function: recording formal breaches or material failures to perform.

The implication is that KPIs can no longer be treated as contract formalities. They need to be defined with precision before award, monitored consistently during delivery, and documented in a form that supports publication. If your current process involves a spreadsheet updated quarterly by a contract manager who then archives it in a shared drive, that process needs to change.

Publish payment compliance data every six months (UK17)

From 1 January 2026, every contracting authority must publish a UK17 Payments Compliance Notice within 30 days of the end of each six-month reporting period. The notice records your average time to pay invoices, the percentage paid within 30 days, between 31 and 60 days, and beyond 60 days, and the proportion of sums that became payable but were not paid within the reporting period.

Critically, the notice must be approved by a director or equivalent senior officer before publication. That means this is not a back-office reporting task — it carries accountability at leadership level.

The first reporting period ran from 1 October 2025 to 30 March 2026. If your organisation published on time, you already know whether your systems were ready for this. If you haven’t yet worked through the data collection process, the next deadline is coming.

Publish contract changes and terminations (UK10, UK11)

Changes to in-scope contracts — extensions, scope modifications, value adjustments — must now be published through a UK10 Contract Change Notice. This is a significant shift from a world in which contract variations were internal documents. Similarly, contract terminations require a UK11 notice, with reasons recorded.

This creates a real-time audit trail of contract events that sits on the public record. The quality of that record depends entirely on the discipline of your internal processes — and on whether your system makes those processes easy to follow.

What that means for your systems

The honest answer is that many contract management systems in the public sector were built for a different era. They were designed to store documents, track renewal dates, and generate reports on demand. Some are well-maintained; others are a mixture of spreadsheets, email threads, and institutional memory.

PA2023 doesn’t mandate a specific technology approach. But it does create a set of demands that are difficult to meet without the right infrastructure.

Data capture at the point of activity. Payment dates, KPI scores, contract events — these need to be recorded when they happen, not reconstructed later. A system that requires manual data entry after the fact, or that relies on finance and procurement operating in separate silos, will create gaps.

Integration between procurement and finance. The UK17 notice draws on invoice payment data that typically lives in a finance system, not a procurement system. If those systems don’t talk to each other, someone has to manually extract, reconcile, and calculate the reporting metrics every six months. That’s a significant risk of error, and a significant drain on resource.

A notice publishing workflow. Publishing to Find a Tender isn’t just a data exercise — it requires internal sign-off, accurate classification, and a reliable connection to the central digital platform. Organisations that are managing this manually, notice by notice, are finding it time-consuming and error-prone.

An audit trail that supports scrutiny. The point of PA2023’s transparency regime is that any interested party — a supplier, a journalist, a councillor — can follow the lifecycle of a contract on the public record. That means the data you publish needs to be accurate, consistent, and complete. If your internal records don’t support that, you’ll know when someone looks closely.

How to approach it

The organisations handling this well aren’t necessarily the ones with the most sophisticated systems. They’re the ones who started by mapping what they actually needed to track, and worked backwards from the publishing obligations to the data collection processes that needed to support them.

A few practical starting points:

Audit your current contracts against the new obligations. Which of your live contracts are above the £5 million threshold? Do they have published KPIs? Are the KPIs measurable enough to report against? This is the UK9 gap analysis, and most organisations find gaps.

Map your invoice payment data flow. Where does payment date data live? Who owns it? How long does it take to extract and calculate the metrics required for a UK17 notice? If the answer involves multiple handoffs and manual reconciliation, that process needs tightening before the next reporting deadline.

Treat the notice publishing workflow as a process, not a task. Each notice type has a trigger, a content requirement, a timeline, and a sign-off requirement. Treating these as ad hoc tasks creates risk. Documenting them as formal processes — with owners, timelines, and checklists — creates consistency.

Don’t retrofit indefinitely. Procurement teams have been creative about making old systems work under new rules. But there’s a limit to how far a spreadsheet-based approach can take you when the obligation is to publish structured data to a national platform, approved at director level, every six months, indefinitely. At some point the cost of the workaround exceeds the cost of the solution.

The Procurement Act 2023 represents a genuine shift in what contract management means in the public sector. The transparency obligations aren’t optional extras — they’re statutory requirements, and the data underpinning them needs to be collected, managed, and published to a standard that will hold up to scrutiny.

The good news is that the requirements are clear enough that you can build the right processes around them. The question is whether your current systems make that straightforward, or whether they’re making it harder than it needs to be.