Is Your Payment Application Valid? Lessons from Netomnia v MJ Quinn
A construction payment application can identify the amount claimed and explain how it has been calculated, yet still fail to trigger the payment machinery. Missing project references, supporting records or other information required by the contract may be enough to invalidate it.
That is the practical warning from Netomnia Ltd v MJ Quinn Integrated Services Ltd [2026] EWHC 1824 (TCC). MJ Quinn submitted 168 applications for payment on the same day, together worth more than £4.7 million. The application considered by the Court was for only £3,770.84, but it was held not to be a valid payment notice because it omitted contractually required identifiers and a Purchase Order reference.
For contractors and subcontractors, the lesson is not simply to provide more paperwork. It is to understand exactly what the contract makes part of a valid application, and to build those requirements into the payment process before the first valuation is submitted.
Why the validity of the application matters
Payment disputes often focus on whether the paying party issued a valid payment notice or pay less notice on time. However, the contractor’s application may itself need to operate as the relevant notice if the paying party fails to issue one. Under section 110B(4) of the Housing Grants, Construction and Regeneration Act 1996, an application can become the payee’s payment notice, but only where it is a notification made in accordance with the contract.
If the application is not contractually compliant, the amount claimed may not become the notified sum merely because the paying party failed to respond. That can remove the basis for a ‘smash and grab’ adjudication and leave the contractor having to pursue the underlying valuation or wait for a later payment cycle. Administrative detail can therefore have an immediate cash-flow consequence.
What happened in Netomnia v MJ Quinn?
Netomnia engaged MJ Quinn under a Master Services Agreement for the design and installation of fibre-optic infrastructure across the United Kingdom. The work was administered through numerous Work Orders across a large and complex network.
The contract required each application for payment to:
- state the sum considered due;
- explain the basis on which that sum was calculated;
- provide a breakdown of the activities performed;
- include documentation and information reasonably required to verify its accuracy; and
- reference the corresponding Purchase Order.
The application examined by the Court identified the relevant Work Order, but did not include the corresponding Purchase Order number, Polygon ID or Feature ID. Those identifiers allowed Netomnia to locate the works within its systems and check what was being claimed.
An adjudicator had concluded that the application was valid. Netomnia then brought Part 8 proceedings, and the Court reached the opposite conclusion and decided that the application did not comply with the contractual requirements and could not operate as a payment notice under section 110B(4).
Why the Work Order reference was not enough
The Court assessed what information was ‘reasonably required’ objectively and in the commercial context of the contract. Netomnia’s network involved hundreds of Work Orders, thousands of geographic areas described as polygons and millions of individual network features. Multiple applications also had to be checked within the short period available for issuing payment notices.
Against that background, the Work Order reference alone did not allow Netomnia to verify the claim efficiently. The Polygon ID and Feature ID were not treated as optional administrative details. They connected the application to the particular location and work items within Netomnia’s systems and were reasonably required to verify its accuracy.
This does not mean that every omission from every application will be fatal. The conclusion depended on the words of this contract and the way the parties’ payment process operated. It does, however, show that information may be essential even if it does not affect the arithmetic of the valuation.
Internal administration did not excuse the missing Purchase Order
MJ Quinn argued that it had not been properly provided with the Purchase Order and that the order did not correspond with the indexation and permit costs claimed. The Court rejected both arguments. The Purchase Order had been sent to MJ Quinn’s accounts department more than two years earlier. A failure to circulate or retain it internally did not mean that it had not been provided to the company.
The Purchase Order also remained the corresponding order even though the application included indexation and permit costs. Those sums still related to the same underlying works. The contractual requirement to identify the order therefore continued to apply.
This is a useful operational lesson. Commercial, project and accounts teams may each hold different parts of the information needed for a compliant application. If those systems do not connect, the resulting payment risk remains with the party making the application.
Could the Scheme or previous practice save the application?
MJ Quinn argued that, if it could not comply with the Purchase Order requirement, the contractual payment mechanism was inadequate and the Scheme for Construction Contracts should apply. The Court disagreed. The mechanism itself was workable; the difficulty arose because information available to MJ Quinn had not been included. The Scheme does not replace an adequate contractual mechanism merely because a party has failed to operate it correctly.
The argument based on the parties’ previous practice also failed. There was no sufficiently established shared assumption that Netomnia would accept an application lacking all of the information omitted here. Occasional acceptance of imperfect applications did not prevent Netomnia from relying on the contract in this case.
Contractors should therefore be cautious about relying on statements such as ‘they accepted it last month’ or ‘we have always done it this way’. A course of dealing may be relevant in some circumstances, but it is not a reliable substitute for compliance with clear payment provisions.
What should contractors check before submitting an application?
The precise requirements will depend on the contract, but a practical pre-submission check should usually address:
- Timing. Is the application being submitted for the correct valuation date and within any contractual window?
- Purpose. Does the document make clear that it is the application for the relevant payment cycle?
- Sum claimed. Is the amount applied for clear, consistent and free from conflicting figures?
- Basis of calculation. Can the paying party understand how the amount has been derived without reconstructing it from previous correspondence?
- Contractual information. Are all required project, package, Work Order, Purchase Order or location references included?
- Supporting records. Does the application contain the substantiation expressly required by the contract or reasonably necessary for verification?
- Form and submission. Has the correct template, platform, recipient, address and method of service been used?
- Internal sign-off. Have the commercial, project and accounts teams checked that the application is complete before it is issued?
CCC’s guidance on interim payment applications and final accounts explains why clear presentation and supporting detail can improve both payment outcomes and the strength of any later claim.
What should paying parties take from the decision?
For employers and contractors assessing downstream applications, the judgment confirms that properly drafted verification requirements can have real effect. However, it is not a licence to reject an application for any minor omission. Whether information is required, and whether the omission prevents contractual compliance, must be assessed against the wording and commercial operation of the particular contract.
If an application appears defective, the safer course will often be to identify the problem promptly while still protecting the payment position by issuing any required payment notice and pay less notice.
The key takeaway
A valid construction payment application may need to do considerably more than state the sum claimed and provide a valuation. If the contract requires project identifiers, Purchase Order references or supporting information, omitting them may prevent the application from operating as the payee’s payment notice.
The best protection is to identify the contractual requirements and incorporate them into the application template and check every submission before it is issued. By the time validity is being argued in adjudication, a preventable administrative omission may already have become an expensive payment dispute.
How CCC can help
Contract & Construction Consultants (CCC) advises employers, contractors and subcontractors on payment applications, payment notices, pay less notices and related disputes. We can:
- review contractual payment provisions and prepare project-specific payment checklists;
- review or prepare interim applications and final accounts;
- assess whether an application, payment notice or pay less notice is contractually valid;
- advise on notified-sum and true-value payment strategies; and
- prepare or respond to payment claims in construction adjudication.
