Receipt Is a Fact, Not a Function: Auditing Buyer Portals and the Payment Clock in 2026

A supplier uploads an invoice at 09:14 on a Tuesday. The portal issues a reference, displays a green tick and closes the window. Three weeks later the buyer's ledger shows no trace of the invoice. The supplier's file says 'submitted'; the buyer's file says 'not received'. Between those two statements sits a contractual question that can decide whether the payment clock ever started.

When Submission and Receipt Part Company

The statutory framework is familiar. Under the Late Payment of Commercial Debts (Interest) Act 1998, the default payment period for business-to-business debts is 30 days, extendable by agreement to no more than 60 days unless the term is grossly unfair. The clock generally begins on the relevant day — often the later of delivery of the goods or services and the presentation of a valid invoice. The difficulty is that 'valid' is not defined by the statute in the granular way that a buyer's portal defines it.

Portals introduce a validation layer. An invoice may be uploaded but not accepted; accepted but not matched to a purchase order; matched but held in a workflow queue. Each stage is a potential reset point. Buyer terms frequently provide that an invoice is 'received' only when it has passed validation and appears on the buyer's accounts payable system. That is a contractual definition of receipt, and it can displace the ordinary meaning of the word if it is properly incorporated, clearly drafted and not grossly unfair.

The Contract Behind the Login

Portal terms of use are a contract. Suppliers accept them at onboarding, often by ticking a box that few read and fewer retain. The first audit step is therefore documentary: capture the version of the portal terms in force at the date of each submission. Look for defined terms such as 'invoice', 'valid invoice', 'receipt', 'dispute' and 'rejection'. Check whether the buyer reserves a unilateral right to vary the terms and, if so, how notice is given.

A term that says 'invoices are deemed received on the next working day after successful validation' is not necessarily unlawful. But it must be transparent, and it must not operate as a trap. Where the validation process is controlled entirely by the buyer, and where rejection reasons are opaque, the supplier has a legitimate interest in challenging a term that converts an administrative failure on the buyer's side into an indefinite extension of credit.

Four Records Every Submission Should Generate

Evidence is the practical answer to a definitional problem. For each invoice, a supplier should hold four records. First, a submission receipt showing the timestamp, the portal reference, the invoice number, the amount and, where possible, a file hash or PDF copy of what was uploaded. Second, a validation status — accepted, rejected or pending — captured as a screenshot or system-generated PDF. Third, any rejection code and the free-text explanation that accompanied it. Fourth, an independent acknowledgement from the buyer's finance team or accounts payable mailbox.

The fourth record matters most when the first three are ambiguous. A short covering email to a named AP contact, sent at the same time as the portal upload, creates a parallel evidence trail that does not depend on the buyer's system. It need not be adversarial. A sentence such as 'Please find the invoice attached for reference; it has also been submitted via the portal under reference X' is sufficient to establish that the document left the supplier's control on a known date.

Reading Rejection Codes as Payment Events

Rejection codes are often generic: invalid purchase order, supplier not set up, tax mismatch, duplicate submission, missing cost centre. Some reflect genuine defects. Others reflect buyer-side administration — a supplier record that has not been created, a cost centre that has changed, a workflow that has no owner. The distinction matters because a rejection for a buyer-side reason should not be treated as a fresh start to the payment period.

Suppliers should log the date of rejection, the stated reason and the date of resubmission. If the reason is outside the supplier's control, the resubmission should be accompanied by a short note recording that fact. Where a buyer's terms purport to restart the clock on every rejection, the supplier should test whether that term was fairly drawn to its attention and whether it operates as a penalty for the buyer's own delay.

Pricing the Admin Burden

Portal compliance is not free. It consumes training time, multiple logins, manual re-keying, rejection handling and escalation. A useful discipline is to calculate the cost per invoice: hours spent multiplied by an internal hourly rate, plus any subscription or connection fees. That figure can be compared with the statutory compensation available for late payment — £40, £70 or £100 depending on the size of the debt — and with statutory interest at 8 per cent above the Bank of England base rate.

In many cases the compensation will not cover the administrative cost of chasing a portal rejection. That is an argument for pricing the burden at the quotation stage, either as an explicit administration charge for buyers who insist on a particular platform or as a factor in the overall margin. It is also an argument for negotiating a service-level commitment from the buyer: a maximum validation period, a named escalation contact and a commitment that rejection reasons will be specific rather than generic.

Escalation: From Service Desk to Statutory Demand

Escalation should be staged and documented. Begin with the portal support desk and obtain a ticket reference. Move to the named buyer contact in procurement or finance, setting out the submission date, the portal reference and the absence of a valid rejection reason. If the invoice remains unpaid, issue a formal letter before action that cites the contractual term relied on and the statutory late payment regime. For debts below £10,000, the County Court Money Claims Online process is a proportionate route; larger claims may require legal advice.

The key point is that a supplier who can prove receipt is in a stronger position than one who can only prove submission. The evidence pack described above is what converts an argument about a portal into a claim about a debt.

A Short Audit Checklist

• Retain the portal terms in force at each submission, not merely the current version.
• Identify the contractual definition of 'receipt' and any deemed-receipt clause.
• Capture a timestamped submission receipt and a validation status for every invoice.
• Send a parallel email to a named AP contact with the invoice attached.
• Log every rejection code, its stated reason and the resubmission date.
• Calculate the internal cost per portal invoice and review it at least annually.
• Negotiate a maximum validation period and a named escalation contact.
• Keep a chronology that can support a letter before action or a court claim.

Portals are not neutral pipes. They are contractual infrastructure, and they allocate risk. In 2026, with e-invoicing adoption spreading across public sector procurement and large private buyers, the supplier who treats receipt as a fact to be proved — rather than a function to be performed — is the supplier best placed to keep the payment clock running on time.