EU and UK Payment Deadlines: Statutory Rules vs Net Terms

A commercial team usually needs an operational due date for accounts receivable. That date may come from Net 30, Net 60, end-of-month wording, receipt of a valid invoice, delivery, acceptance, or a fixed calendar date. The calculation is a reading of the parties' documents. It should preserve the exact starting event, whether the number means calendar or business days, and any weekend adjustment. A label entered into software cannot supply terms that the agreement never states.

A statutory late-payment trigger belongs in a second field. It depends on the legal framework, the identities of the parties, the nature of the transaction, any exclusions, and the current implementing law. The trigger may follow an agreed payment date or a statutory fallback. It can determine when interest or another remedy may become available, but it does not rewrite an unclear invoice. Keeping the two fields separate prevents a collections workflow from presenting an arithmetic result as a legal conclusion.

Directive 2011/7/EU addresses payment made as remuneration for commercial transactions. Article 2 distinguishes transactions between undertakings and transactions between undertakings and public authorities. Article 3 provides the business-to-business framework. When the creditor has performed its obligations and the debtor is responsible for delay, late-payment interest follows the contractual date or payment period. If the contract fixes no date or period, Article 3 lists 30-calendar-day fallbacks tied to invoice receipt, receipt of goods or services, or an agreed acceptance procedure.

For transactions between undertakings, Article 3 says a contractual payment period should not exceed 60 calendar days unless a different period is expressly agreed and is not grossly unfair to the creditor. That is not permission to describe every 75-day term as valid. The fairness test, the actual bargain, and national law still matter. Article 7 separately addresses grossly unfair contractual terms and practices. A planning guide should therefore record the chosen term without promising that a court or authority would enforce it.

Article 4 creates a distinct structure where the debtor is a public authority. Its ordinary payment periods are anchored to 30 calendar days after the relevant invoice, goods, services, or acceptance event. The directive permits limited 60-day treatment for identified categories, including certain public undertakings carrying industrial or commercial activities and duly recognized healthcare bodies. Contractual extension for a public authority has its own objective-justification and maximum-period conditions. Those details are why a generic B2B Net 60 note cannot be copied into a public procurement file.

A directive also requires national implementation. The EUR-Lex text is the primary EU anchor for the common framework, but a live decision must use the law in the Member State that governs the transaction, including amendments, definitions, procedural rules, and any valid sector treatment. The United Kingdom materials below are a separate national framework, not an EU Member State implementation example for a new contract. Cross-border teams should identify governing law before comparing labels or counting dates.

The current revised Section 4 of the Late Payment of Commercial Debts (Interest) Act 1998 says statutory interest starts on the day after the relevant day. Subsections 2A to 2C use the agreed payment day unless another rule applies; if there is no agreed day, the relevant day is the last day of the relevant 30-day period. Subsection 2D generally substitutes that 30-day endpoint where a public authority agreed a later date. For a purchaser that is not a public authority, subsection 2E similarly uses the relevant 60-day endpoint where it is earlier than the agreed date, but subsection 2F disapplies that rule when the agreed payment date is not grossly unfair to the supplier. The advance-payment rule in subsection 2G remains a separate branch.

Subsections 2H and 2I start those 30-day and 60-day periods from the later or latest applicable event: performance of the supplier's obligation, the purchaser receiving notice of the amount claimed, and, where subsection 5A applies, the day determined under subsection 5B. Section 5B normally makes that day the day after the acceptance or verification procedure is completed, not the completion day itself. Section 5C can treat a procedure completed after the 30-day performance period as completed immediately after that period ends; section 5D disapplies that treatment for an expressly agreed longer procedure that is not grossly unfair. Section 7A lists fairness factors including good faith and fair dealing, the nature of the goods or services, and objective reasons for deviation. These provisions require a factual and legal review; a calculator cannot decide gross unfairness.

Acceptance fixture: assume performance and notice of the amount both occur by September 1, 2027, an applicable procedure is completed on September 10, 2027, and sections 5C and 5D do not alter that completion date. For 2H(c) and 2I(c), the Section 5B day is September 11, 2027, the day after the procedure is completed. A 30-day period beginning September 11 ends October 10, 2027; a 60-day period beginning that day ends November 9, 2027. Those are scoped period endpoints for the statutory branches, not automatic findings that payment is late, interest is owed, or a contractual due date changed.

GOV.UK gives a current plain-language summary: an agreed payment date must usually be within 30 days for public authorities or 60 days for business transactions; businesses may agree a longer period if it is fair to both. Where no payment date is agreed, the guidance says payment is late 30 days after invoice receipt or after delivery or service if that is later. The word usually matters. A user still has to confirm the Act's scope, later amendments, contract terms, governing law, and any substantial contractual remedy rather than treating the summary as a universal rule.

For this review, the official Section 4 XML was fetched on July 29, 2026. It identifies itself as a revised representation, reports Statute Law Database modification on February 26, 2025, and gives February 24, 2025 as the current valid-from date. Its change history exposes 2013, 2015, and 2025 amendments, including the public-authority definition change effective February 24, 2025. An as-enacted 1998 PDF does not establish the current wording by itself.

Net 30 is incomplete unless the record identifies what happened on day zero. An invoice may say 30 days from invoice date, while a master agreement says 30 days after receipt of a correct invoice and an approved purchase order. A buyer portal may reject the invoice until acceptance. Those documents can create different operational dates even though each screen displays Net 30. The accounts team should save the controlling clause and the evidence timestamp instead of silently selecting the earliest convenient event.

The same discipline applies to day counting. Thirty calendar days is not thirty business days. End-of-month plus 30 uses a month-end anchor. A clause that moves a due date falling on a non-working day needs the specified calendar and direction of movement. The statutory sources discussed here use calendar-day periods in key provisions, but that does not convert every negotiated Net term into calendar days. Contract arithmetic and statutory arithmetic remain separately labeled calculations.

Assume a UK business supplier issues an invoice on August 2, 2027, delivers the goods on August 4, 2027, and has a signed clause fixing payment on November 15, 2027. No acceptance procedure is assumed. The operational contract due date remains November 15 because that is the date the parties wrote. For the statutory branch, the later event is delivery on August 4. A 60-day period beginning that day ends on October 2, 2027, so the agreed date falls beyond the subsection 2E endpoint.

For a qualifying debt owed by a non-public purchaser, October 2 is the candidate relevant day under subsection 2E unless subsection 2F disapplies that cap because the November 15 agreement is not grossly unfair to the supplier. If 2E controls, the following-day marker is October 3, 2027; if 2F applies, the agreed-day branch instead points to November 16, 2027. The fairness result depends on the contract and section 7A factors, so finance should record both branches and obtain legal review. The calculator may reproduce November 15 as the contractual due date but cannot choose between the statutory outcomes.

Assume a supplier completes services for an EU public authority on October 8, 2027. The authority receives a correct invoice on October 12, 2027, no contractual payment date is recorded, and no acceptance procedure or special authority category is assumed. A 30-calendar-day planning count from the later invoice event reaches November 11, 2027. The file should label that date as a directive-based review point, not as a negotiated Net 30 term.

Before collection action, the supplier must identify the Member State law that implements Article 4, verify the authority classification, confirm invoice receipt, and check whether an acceptance process or permitted exception changes the period. If the contract actually contains a valid fixed date, the analysis must start again with that term. This example deliberately separates October 12 as the evidence event, November 11 as the planning endpoint, and any later remedy date determined under the applicable national law.

Create a small evidence packet for material invoices. Include the executed payment clause, governing-law clause, invoice issue and receipt timestamps, delivery or service completion, acceptance status, disputes, amendments, and the exact counting convention used by the ledger. Add a source note identifying the provision reviewed and the review date. This packet lets finance explain why its reminder date exists without claiming that the reminder itself establishes a statutory right.

Use separate status labels such as contract due, statutory review required, disputed, and adviser confirmed. Do not label an amount legally late merely because the software clock passed a calculated date. When a counterparty is a public authority, a healthcare body, or located in another jurisdiction, route the file to the owner responsible for legal and procurement scope. Recheck official text near enforcement because legislation and guidance can change after publication.

For an EU transaction, save the Member State, title and version of the implementing law, official URL, language reviewed, and verification date alongside the directive reference. Record whether the debtor is an undertaking or public authority, whether a recognized healthcare or public-undertaking category is asserted, and whether acceptance evidence changes the starting event. Reading the directive's 30-day and 60-day figures does not by itself resolve the national procedure or remedy.

For a UK transaction, keep the GOV.UK summary and the current revised legislation.gov.uk provision as separate evidence. The guide's source record identifies the exact Section 4 XML representation, revised status, modification date, valid-from date, and verification date. A table of contents or as-enacted PDF can help locate the Act, but neither alone proves the wording in force for a current-law review.

A cross-border ledger should not collapse this work into one legal due date. Use columns for the contractual due date, statutory candidate or candidates, verified jurisdiction, unresolved scope facts, next action, and responsible reviewer. That record makes a repeated number such as 30 traceable to its actual role instead of implying that every Net 30 label, fallback period, and public-authority rule has the same legal effect.

This guide does not determine governing law, characterize a party, interpret a complete contract, test gross unfairness, calculate interest, assess responsibility for delay, or identify every exclusion and remedy. It does not cover consumer debts, taxes, employment payments, insolvency claims, construction-specific procedures, public procurement rules beyond the cited payment framework, or local civil procedure. Currency, tax, acceptance, set-off, and dispute provisions may also affect a real account.

The EUR-Lex directive is an EU framework that Member States implement through national law. The UK Act and GOV.UK guidance have their own territorial and transaction scope. Neither source makes a DeadlineDays result binding. Use the invoice calculator only to reproduce a clearly stated arithmetic convention, preserve the inputs, and discuss the result with the contract owner or qualified adviser before relying on a remedy date.