Connect invoice receipt, validation, subcontract obligations and optional early-payment finance to a UK public-contract cash forecast.
A public-sector customer can offer a credible payment obligation while a supplier still experiences a cash shortage between delivery, invoicing and receipt. The commercial task is to connect the applicable payment terms to the events that actually happen in the buyer's system and in the supplier's own subcontract chain.
The UK government's electronic invoicing and payment guidance explains the Procurement Act 2023 framework. Its current interpretation places the ordinary 30-day payment calculation at receipt of a valid, undisputed invoice, with provision for a later due date stated in the invoice. That makes invoice routing and the evidence of receipt directly relevant to working capital.
Sections 68 and 73 set implied payment terms and the relevant subcontract extension, with stated exceptions. Concessions, utilities and schools need particular attention to the applicable provisions. A supplier should identify the actual contractual route before copying a standard public-sector payment assumption into its forecast.
For an ordinary covered service contract, the key commercial point is that the relevant terms can apply even if the contract does not repeat them word for word. The guidance also distinguishes the current framework from the previous Public Contracts Regulations approach. An old template referring to the start of a validation process should not silently determine how a new Procurement Act contract is administered.
The final contract remains essential reading because it specifies what can be invoiced, when delivery milestones arise, the required information and the agreed administrative process. The payment period and the right to invoice are connected, but they are not the same question. Completing preparatory work does not necessarily mean that a priced contractual milestone has been achieved.
The official guidance states that day one is the day the contracting authority receives the invoice. Where the buyer uses an electronic invoicing system, receipt into that system is the relevant event. An internal draft, an invoice saved in the supplier's accounting package and a successfully uploaded invoice are three different records.
Consider a hypothetical support supplier whose invoice is ready on a Monday but remains in an employee's drafts until Thursday. The forecast should not treat Monday as the buyer's receipt date. Retaining the portal acknowledgement gives finance a concrete event to use when following up payment and investigating a discrepancy.
This is why the person responsible for issuing invoices needs the contract's operational instructions before performance starts. A sales team may have negotiated a sound payment schedule while leaving finance without the purchase-order reference, buyer contact or system access needed to use it. Those missing details can create a preventable delay after the work has already been paid for internally.
Section68 identifies minimum information for an alternative valid invoice route: the invoicing party, a description of the supplied goods, services or works, the requested amount and a unique identifier, together with other contractual requirements. It also recognises invoices in the required structured electronic form.
For a service supplier, the description should make the commercial connection clear. An invoice saying consulting services can be harder to reconcile than one identifying the contract, service period and applicable milestone. The underlying acceptance evidence might be a completed service report or approved timesheet, depending on the agreement. Keep that evidence attached or readily retrievable in the format the buyer specifies.
A timesheet can itself function as an invoice in the circumstances described by the guidance if it contains the required information and meets the relevant requirements. The label on the document is therefore less important than what it contains and how it is received. Avoid operating two parallel processes where the service team believes a timesheet requests payment while finance expects to submit a separate invoice later.
Section 67 defines an electronic invoice as structured information permitting automatic processing. It refers to the relevant British-adopted electronic invoicing standard and listed syntaxes. An invoice attached as a PDF to an email is not necessarily an electronic invoice in that defined sense simply because it travels electronically.
Section67 permits a particular invoicing system and, for defence authorities, one involving supplier fees. This is a specific point to cost where relevant, rather than an assumption that all public-sector invoice transmission is free.
For the supplier, implementation starts with finance operations: can the accounting system create the accepted format, who maintains the customer references, and where is successful transmission recorded? These questions concern commercial administration. They can be resolved before the first delivery without changing the product being supplied.
Section73 defines a public subcontract by its connection to performing the public contract and extends the relevant terms through that relationship. A prime should therefore examine its own payment obligations separately from the date it expects the public customer to pay.
In a hypothetical monthly service arrangement, a specialist subcontractor might complete and invoice its work before the prime invoices the customer for the whole month's service. The prime's forecast needs both receipt events. Treating the subcontract payment as automatically dependent on the customer's remittance can conceal a funding gap and may conflict with the applicable payment terms.
The guide to evidence and commitments from UK bidding partners addresses how those organisations enter the offer. At contract handover, the same partner schedule should connect to purchase orders, invoice recipients and authorised service approvers. The legal commitment and the finance workflow need to describe the same work.
Section68 excludes invalid or disputed invoices from its ordinary payment term and requires notification without undue delay. Commercial teams should therefore distinguish an overdue undisputed invoice from an invoice whose amount or validity has been challenged.
A useful dispute record identifies the invoice number, the disputed item, the reason given and the evidence needed to resolve it. For example, disagreement about an additional service day should be linked to the instruction authorising that day and the contract's pricing mechanism. Repeatedly resending the same invoice without resolving the stated issue can leave both parties looking at different versions of the problem.
Preserve the history when correcting an invoice. Finance should be able to explain what changed, why it changed and when the corrected information reached the buyer. That record is useful for collection activity and for improving the next invoice, even where the commercial team ultimately agrees a revised amount.
The guidance distinguishes full payment within the required period from a finance product that charges the supplier to receive that same payment on time. It says using such a product to satisfy the existing obligation would not comply. A supplier can, however, choose a product to receive funds earlier than the applicable payment term.
Assess that earlier-payment offer using its actual fee and the number of days gained. Compare it with the company's funding alternatives and the predictability of the underlying invoice. A familiar public customer does not by itself make every financing offer economical. Finance should also identify who bears the charge and how the transaction appears in the customer ledger. An offer that accelerates one invoice may not solve a recurring cash requirement across the rest of the contract.
The award-notice and contract-details sequence provides the earlier boundary for the cash plan: when pursuit becomes contracted delivery. After that point, an effective forecast follows achieved milestones, valid invoice receipt, disputes and actual remittances. It gives management a view of when the service consumes cash and when the contractual payment process replenishes it.
Current official electronic invoicing and payment guidance reviewed on 6 September 2026. Its stated payment interpretation is attributed; utilities and other exceptional categories are not generalised. The commercial examples are hypothetical. Current sections67/68/73 independently retrieved and read; statutory exceptions confirmed, resolving the earlier direct-access warning. The guidance interpretation of later invoice due dates remains explicitly attributed.
Suggest a correction