The Empty Field: Why a Missing Purchase Order Reference Is a Payment Delay in Disguise

A purchase order number is often treated as an administrative detail: useful for the customer's records, helpful for reconciliation, but secondary to the commercial reality that goods or services have been supplied and payment is due. In practice, that assumption can be costly. For larger customers, the PO reference is frequently the key that allows an invoice to enter the payment run at all. Without it, the invoice may not be disputed on its merits. It may simply fail to match.

The distinction matters. A genuine dispute about quality, quantity or contractual performance is one route to late payment. A missing PO reference is another, quieter route. It can produce the same cash-flow effect while attracting far less attention, because the supplier is not told that payment is being withheld. The supplier is told that the invoice cannot be processed.

When the matching engine says no

Many accounts payable functions now rely on automated matching between the invoice, the purchase order and, where relevant, a goods receipt or service confirmation. The invoice is not read as a narrative request for payment. It is read as a data record. If the PO number is absent, invalid, closed, overcommitted or attached to a different legal entity, the system may place the invoice on hold before any human being considers whether the work was done.

The supplier's experience is familiar. An invoice is submitted promptly. A portal shows it as received but not validated. A query is raised asking for the correct PO. The invoice is re-submitted. The validation clock effectively restarts. What looked like a 30-day payment term becomes a 45- or 60-day cycle, not because the customer has decided to pay late in the ordinary sense, but because the invoice has failed an internal control.

This is the central risk in so-called no PO, no pay policies. They are presented as procurement discipline, and in many organisations they serve that purpose. But from a supplier's perspective, they can operate as a payment-delay mechanism that sits outside the contractual payment term.

A policy rarely applied with perfect consistency

One of the practical difficulties is that no PO, no pay is seldom enforced with uniform rigour. A large customer may have group-wide rules, but individual business units, buying teams or accounts payable centres may apply them differently. Low-value purchases may be exempt. Emergency orders may be ratified after the event. A long-standing supplier may have been paid without a PO for months, creating a reasonable expectation that the practice is tolerated.

That inconsistency can encourage a risky conclusion: if the customer has paid without a PO before, it will probably do so again. It may, but the supplier has no control over which invoice is selected for scrutiny. A change ofAP clerk, a new system, an audit review or a routine clean-up of unmatched invoices can bring the practice to an abrupt end.

The safer position is to treat a PO reference as part of the order, not part of the invoice. By the time an invoice is issued, the opportunity to capture the reference cleanly may already have passed.

Capture the reference before dispatch

A practical control is to make the PO number a mandatory field at sales order stage. The following checks are proportionate for most suppliers dealing with larger customers:

• Record the customer's full legal entity name, not merely the trading name or site name.
• Obtain the PO number in writing before fulfilling the order, even where the buyer says it will follow.
• Check that the PO covers the value and scope actually being supplied, including delivery charges, variations and VAT treatment where relevant.
• Note the buyer's name, date of authorisation and the route by which the PO was received.
• Retain a copy of the PO or a screenshot from the customer's procurement portal.
• Identify any portal or invoice-submission requirement before the first invoice is raised.
• Flag missing PO data internally before dispatch, not after the invoice has been rejected.

Where a customer insists that no PO is required, obtain that confirmation in writing and identify who gave it. A verbal assurance from a site manager may not survive an accounts payable query several weeks later.

Build the reference into every route to invoice

Invoice templates should force the PO number onto the document and into any accompanying submission. A free-text field is not enough if it can be left blank. The stronger approach is a validation rule that prevents an invoice from being finalised without the reference, together with a check that the number matches the format used by that customer.

For portal submissions, the same discipline applies. The PO field should be completed from source data rather than retyped from memory. Email submissions should carry the PO number in the subject line and in the body, not only in an attachment. Where credit notes or revised invoices are issued, the original PO reference should remain visible so that the customer's system can link the documents.

None of this guarantees prompt payment, but it reduces the likelihood of a preventable rejection. It also creates a cleaner evidence trail if a rejection is later disputed.

Escalate on day one, not day thirty

When an invoice is rejected for a missing or incorrect PO, the supplier should treat the rejection as a live payment issue rather than a minor correction. Log the date of rejection, the stated reason and the date of resubmission. Contact both the accounts payable team and the buyer, and ask for written confirmation that the corrected invoice has been matched and returned to the payment queue.

If the customer has rejected an invoice for a reason that appears inconsistent with the order documentation, say so promptly and in writing. Keep the tone factual. Identify the PO evidence, the delivery or service confirmation and the date the invoice was first submitted. The longer the matter is left, the easier it becomes for the original submission date to disappear from the customer's records.

Suppliers should also distinguish between a data correction and a disguised dispute. A missing PO number is usually a validation failure. A claim that the work was not authorised may be a contractual dispute. The two require different responses, and legal advice may be appropriate where the sums are significant or the pattern is repeated.

The reference is part of the payment term

No PO, no pay policies are unlikely to disappear. For suppliers, the lesson is not that every customer will use them unfairly, but that the PO reference is a payment control in its own right. It should be captured at order stage, embedded in the invoice process and monitored when a rejection occurs. Treated that way, it becomes what it should be: a routine commercial record, not an empty field that quietly adds weeks to the time it takes to be paid.