The first statutory deadline for contract payment information under section 70 of the Procurement Act 2023 has passed. It was 29th of July 2026, rather than 31st of July, because the 30-calendar-day period began on the final day of the quarter ending on 30th of June. The first return may have been small: the duty captures only a newly commenced cohort of public contracts. That makes August a sensible point to replace a one-off exercise with a repeatable control.
The practical question is whether finance, procurement and contract-management records can show which qualifying payment belongs to which qualifying contract, and whether the authority can explain the answer later. A short, controlled review can resolve data gaps while the first reporting period is still manageable.
The first deadline was 29th of July, not 31st of July
Section 70 reporting periods are three months ending on 31st of March, 30th of June, 30th of September and 31st of December. Information must be published within 30 calendar days of the end of each period, with the period beginning on the final day of the quarter. The current contract payment information guidance confirms that the first reporting period ran from 1st of April 2026 to 30th of June 2026 and that publication was due by 29th of July 2026. For the quarter ending on 30th of September 2026, the corresponding deadline is 29th of October 2026.
The deadline is a legal publication point, not a reason to rush untested data through the platform. A post-deadline review should distinguish an error that needs correction from a genuine scope decision supported by evidence. It should also record who will own the next extraction, validation and submission cycle.
What section 70 is, and what it is not
Section 70 is a statutory transparency duty concerning payments under individual public contracts. It requires the contracting authority to publish specified information on the central digital platform for an individual payment of more than £30,000 including VAT. The test is inclusive of VAT, but the value published is net of VAT. The payment report therefore links financial data to the relevant procurement and contract record; it is not a general spend return. The required fields include authority, procurement, contract and supplier identifiers, the net payment value and the payment date, as set out in the official guidance and regulation summary.
This duty is separate from a payments compliance notice under section 69, which concerns prompt-payment obligations and has its own information and timing requirements. One report cannot evidence compliance with the other. The Government's guide to the new legislative requirements treats them as distinct transparency requirements.
Section 70 also does not displace other applicable expenditure-publication arrangements. An authority may still have central-government, local-government or other transparency duties. Keeping the purposes and populations of those datasets separate is safer than attempting to make one return satisfy every reporting obligation.
Start with contract scope, not the payment ledger
The duty applies to payments under public contracts procured under the Act in a procurement procedure commenced on or after 1st of April 2026. It does not require payment information for contracts procured under the previous regimes, or for an Act procedure commenced before that date even if award occurred later. The guidance gives detailed commencement tests, including tender notices, transparency notices and certain framework and below-threshold actions. Contract award date alone is therefore not a reliable inclusion rule.
Public-contract scope matters as much as commencement. Below-threshold and exempted contracts are not within the duty. Framework agreements and dynamic markets themselves are outside it, while qualifying call-off contracts or contracts awarded by reference to a dynamic market can be in scope. Section 70 also excludes, among others, concession contracts, utilities contracts awarded by a private utility, school contracts and particular transferred Northern Ireland arrangements. The current guidance says the section does not apply to procurement regulated by Welsh Ministers. Validate the legal and territorial position before extracting payments, particularly where an organisation operates across regimes.
The £30,000 test applies to a payment in respect of an individual contract. Separate payments of £30,000 or less do not become reportable merely because they total more than that amount in a quarter. Equally, a combined payment to one supplier only triggers reporting where more than £30,000 relates to one in-scope contract. If several invoices under that contract are combined into one payment, the combined amount can trigger the duty. That distinction should be reflected in finance rules, not recreated manually at each quarter end.
Repair the identifiers before the next quarter closes
Take every payment included, excluded or manually investigated in the first report and test the mapping behind it. The platform uses the contracting authority's PPON, the procurement's OCID, the contract identifier, the supplier identifier, the net payment amount and the payment date to connect the record. The payment information guidance also explains the limited allowance where procurement and contract identifiers are unavailable because no relevant notice was previously published.
The common problem is not a lack of data but a mismatch between finance supplier and cost-centre references, the procurement record, the contract register and the information published in the contract details notice. Identify where matching is deterministic, where it relies on a maintained cross-reference and where it is being decided afresh by a contract manager. The final category is both difficult to audit and vulnerable to inconsistency.
Give each exception a named owner and a resolution route. That may mean correcting a procurement record, confirming a supplier identifier, changing a finance coding rule or documenting a historic reference. If information may be withheld, assess the relevant section 94 grounds when the payment information is published; an earlier redaction does not automatically decide the later publication. Keep the reasoning with the reporting evidence rather than relying on an informal recollection.
Reconcile for accuracy, completeness and explainability
Reconcile in both directions. Start with the eligible-contract population and determine whether each contract generated a reportable payment. Then start with the finance extract and determine whether every payment over the threshold has been reported against the right contract or has a recorded reason why it is outside scope. Test VAT treatment, date of payment, duplicate or reversed entries and combined payment runs.
The platform permits more than one upload before the quarterly report is submitted, and allows users within the authority to collaborate. A monthly staging process can therefore reduce the quarter-end burden, provided the authority still validates the complete population and submits it on time. It also creates a clearer hand-off between finance, procurement, data and contract-management colleagues.
Give the report a clear owner and audit trail
The contracting authority that made the payment is responsible for accurate, timely publication. Name a senior accountable owner, an operational report owner and the contributors responsible for source data, scope decisions, exception resolution and submission. The workflow should say who approves the inclusion logic, who checks the completed report and where the evidence is retained.
An audit trail should make a later question answerable without recreating the whole report. Retain the extraction date, source-system logic, eligible-contract population, exclusion decisions, identifier corrections, validation evidence, submission record and published version. An optional internal payment reference can assist with duplicate checking, but it does not replace the mandatory identifiers needed to connect the payment to the contract.
Use October as a control test, not another deadline event
Treat 29th of October 2026 as the first test of a stable control, not as a second emergency. A short review now can close gaps while the first-period evidence is still accessible and can align statutory reporting with contract-register and financial-close controls without conflating their legal purposes.
Where an authority needs independent help to structure the workflow, map data ownership or review the procurement-to-contract evidence trail, Prestige's services include governance, risk, compliance and contract-management support. The Support Hub contains practical procurement reference tools. Prestige can help clarify process and evidence, while responsibility for the authority's decisions, data and publication remains with the authority.
Important scope note
This article is general information, not legal advice. Section 70 depends on the facts of the contract, procurement commencement, territory and organisation. Readers should check current law, guidance and their own organisation-specific rules before acting.