Local authorities now face a very practical Procurement Act 2023 deadline that should not be treated as a minor administrative update. A number of live obligations either begin on, or are directly tied to, 1 April 2026, and together they create real process, governance and reporting implications for councils.
For procurement, commissioning, contract management and finance teams, this is one of those moments where compliance risk does not mainly sit in legal interpretation. It sits in whether the authority has the right data, the right internal ownership, and the right operational discipline to publish accurate information on time.
Why 1 April 2026 matters
Three issues now converge around this date.
The first is the new Payments Compliance Notice timetable. The first notice must be published between 31 March 2026 and 29 April 2026, which means authorities should already be preparing their data and approvals.
The second is the start of the new requirement to publish information about payments over £30,000 made under qualifying public contracts procured under the Act, where the procurement procedure commenced on or after 1 April 2026.
The third is the introduction, from 1 April 2026, of the requirement to include a supplier’s unique identifier for notifiable below-threshold contract details notices. For councils, that matters because notifiable below-threshold contracts generally begin at £30,000 including VAT.
None of this is theoretical. These are live implementation issues, and local authorities that have not yet aligned procurement, finance and publication processes are exposed to avoidable delay and non-compliance.
The first Payments Compliance Notice is an immediate deadline
The first issue many councils need to focus on is the Payments Compliance Notice.
Under the new regime, authorities must report on payment performance for the first reporting period running from 1 October 2025 to 31 March 2026. The notice then has to be published during the period from 31 March 2026 to 29 April 2026.
This is important because the notice is not just a general narrative statement. It requires specific performance information, including average payment times, payment percentages across different time periods, and the proportion of invoices paid in line with the required payment terms. It also requires sign off by the director, or equivalent officer, with responsibility for the authority’s finances.
That immediately makes this a joint governance issue. Procurement cannot assume finance will handle it without support, and finance cannot assume procurement holds all the underlying contract context. Authorities need a clear internal owner, a clear data source, and a clear approval route.
For many councils, the real pressure point will be data quality. If invoice receipt dates are inconsistent, if systems do not distinguish cleanly between in-scope and out-of-scope transactions, or if there is no settled process for validating the figures, the notice becomes much harder to complete with confidence.
New contract payment publication duties start now
The second live issue is contract payment information.
From 1 April 2026, contracting authorities must publish information about payments over £30,000, including VAT, made under public contracts where the procurement procedure commenced on or after that date. Publication must then take place on a quarterly basis within 30 calendar days of the end of each quarter.
The key point for local authorities is that the capture point starts now. Even if the first quarterly publication is still ahead, authorities need to ensure that relevant payments can be identified correctly from the outset.
This matters because the legal duty may look simple on paper, but delivery depends on process design. Finance systems need to be able to link payments back to the correct contract. Procurement records need to show clearly whether the contract was procured under the new Act and when the procurement procedure commenced. If those links are weak, reporting becomes manual, slow and more vulnerable to error.
Authorities should not assume this can be fixed at quarter end. If the coding and contract referencing are not right from the start, the reporting burden will grow quickly.
Below-threshold awards now need closer control
The third issue is likely to affect many routine local authority procurements.
From 1 April 2026, a supplier’s unique identifier must be included in notifiable below-threshold contract details notices. For councils and other sub-central authorities, the relevant threshold is generally £30,000 including VAT.
That means a significant number of lower value awards may now require a more disciplined publication process than some authorities have previously applied. It also means buyer guidance, templates and checklists may need updating immediately.
The practical risk is straightforward. A council may be ready to publish a below-threshold contract details notice, but cannot complete the process smoothly if the supplier has not registered appropriately and the identifier has not been obtained.
There is also a timing point that authorities should not miss. Where publication of the contract details notice happens on or after 1 April 2026, the new identifier requirement may apply even if the underlying contract award activity began earlier. That creates a potential trap for procurements already moving through the pipeline.
For busy procurement teams, this is exactly the kind of procedural detail that can cause delay if it is only picked up at the end.
What councils should do this month
Authorities should treat this as a short implementation exercise rather than a passive legal update.
The first step is to confirm who owns the Payments Compliance Notice and whether the required finance approval route is already in place. If ownership is unclear, that should be escalated quickly.
The second is to test whether systems can distinguish contracts awarded under the Procurement Act 2023 from legacy contracts under the previous regime. That distinction matters for payment publication duties and future reporting accuracy.
The third is to review all below-threshold procurements that are likely to result in a contract details notice being published on or after 1 April 2026. Those cases should be checked now for supplier registration readiness and identifier availability.
The fourth is to update internal process documents. Template documents, award checklists, procurement guidance notes and publication workflows should all reflect the new requirements. Authorities using third party e-procurement systems or publication tools should also confirm that system changes have been made and tested.
Why this is more than a publication exercise
There is a temptation to treat these changes as technical notice obligations. That would be a mistake.
Payment transparency goes directly to supplier confidence, particularly for SMEs and VCSEs that are sensitive to cash flow and administrative friction. Below-threshold transparency matters because it shapes how local markets experience council procurement in practice, especially for lower value opportunities where smaller providers are most likely to engage.
In other words, this is not only a compliance issue. It is also a credibility issue.
The main takeaway for local authorities
The strongest message for councils is simple. The next phase of Procurement Act implementation is now less about learning the headline rules and more about making sure the authority can operate them properly.
1 April 2026 is a genuine operational deadline. Authorities that prepare now should be able to manage the transition sensibly. Authorities that leave it too late may discover that the real challenge is not understanding the law, but getting procurement, finance, governance and systems to work together quickly enough to meet it.