Two invoices reaching a PO check: the one with a PO number is paid, the one without is returned with guidance

No-PO-No-Pay: How to Introduce It Without Disrupting Suppliers

No-PO-no-pay sounds simple: if an invoice does not quote a valid purchase order, it is not paid until one exists. In practice, it is one of the most effective tail spend controls, and one of the easiest to get wrong. Introduced badly, it delays payments to small suppliers, floods accounts payable with queries and pushes employees to raise purchase orders after the fact, which defeats the point. This guide explains why no-PO-no-pay matters for tail spend, what to fix before you switch it on, which exceptions to agree, and how to roll it out in phases so suppliers stay paid on time.

What Is No-PO-No-Pay?

Short answer

No-PO-no-pay is a policy that requires every supplier invoice to quote a valid purchase order before it is paid, apart from a short list of agreed exceptions. It makes sure purchases are approved before they happen rather than after, which brings tail spend into the agreed process and gives finance accurate commitments.

Key Takeaways

    • No-PO-no-pay moves approval to before the purchase, which is where control over tail spend starts.
    • Fix the buying side first: if raising a PO is slow, people will raise it after the invoice arrives.
    • Agree a short, written list of exceptions, such as utilities, card payments and statutory charges.
    • Phase the rollout with a warning period, and tell suppliers clearly and early.
    • Do not penalise suppliers for internal failures. Resolve returned invoices quickly and pay on time once a PO exists.

Why It Matters for Tail Spend

Tail purchases are where invoices most often arrive without a purchase order. Someone agrees a job by phone or email, the supplier delivers and invoices, and accounts payable then chases an approver to confirm it. By then the supplier, price and terms have already been chosen without procurement. Our guide to the real cost of tail spend explains the price leakage and risk this creates. No-PO-no-pay reverses the order. It also improves one of the four core measures in our guide to tail spend KPIs: PO compliance.

Fix the Buying Side First

The most common reason no-PO-no-pay fails is that raising a purchase order is too slow or too hard. Before you enforce the policy, make the compliant route easy:
    • One front door for requests. An intake-to-procure process makes it simple to request a purchase and get a PO.
    • Catalogues for common items. Pre-approved items can create POs in a few clicks.
    • Cards for small purchases. Low-value, low-risk buys can go on a card instead of a PO. See our guide to P-card policy.
    • Blanket POs for recurring services. A single PO covering a period or value allows repeat invoices without a new PO each time.
    • Fast approvals. Set approval thresholds so small purchases are approved quickly.

What Changes for Whom

Stakeholder What changes What they need
Requesters and budget holders Must raise or request a PO before committing to a supplier A fast, simple way to get a PO and clear guidance
Procurement Handles more requests up front Catalogues, preferred suppliers and intake to keep volume manageable
Accounts payable Returns or holds invoices without a valid PO A clear process, templates and authority to enforce the policy
Suppliers Must quote a valid PO number on every invoice Early notice, clear instructions and a contact for questions
Finance leadership Gains accurate commitments and better forecasts Visible support for the policy and a way to resolve escalations

Agree Your Exceptions

Some payments do not fit the PO process. List them in writing, keep the list short, and review it each year.
Exception Why it is excluded How to keep it controlled
Utilities and telecoms Recurring, usage-based bills Contract on file; budget holder reviews each bill
Rent, leases and service charges Governed by long-term agreements Payment schedule linked to the contract
Taxes, duties and statutory fees Not a purchasing decision Approved by finance
Card payments Already approved and controlled through card policy Monthly card reconciliation
Genuine emergencies Delay would cause harm or major disruption Retrospective PO within a short deadline, with a reason recorded
Recurring contracted services Repeat invoices against an existing agreement Blanket PO for the period or value
Watch the emergency route closely. If retrospective POs become routine, the policy is being bypassed rather than followed.

How to Roll It Out in Four Phases

Phase What happens Signals you are ready to move on
1. Prepare Measure invoices without POs by supplier and category, fix buying channels, agree exceptions and write the policy Most frequent non-PO suppliers have a route to a PO
2. Warn Announce the go-live date. Invoices without a PO are still paid, but flagged and followed up Non-PO invoices are falling and queries are being answered quickly
3. Enforce Invoices without a valid PO are returned or held with clear instructions Returned invoices are resolved quickly and suppliers are paid on time
4. Sustain Monitor KPIs, review exceptions and tighten or adjust rules PO compliance is stable and retrospective POs stay rare
Many organisations phase by supplier group as well: start with the suppliers that send the most non-PO invoices, then extend the policy to everyone.

Step-by-Step Checklist

    1. Measure the baseline. Find the share of tail invoices that arrive without a PO, and the suppliers and categories behind them.
    1. Fix the routes to a PO. Intake, catalogues, cards, blanket POs and faster approvals.
    1. Write the policy and exceptions. Keep it short and get finance leadership to sign it off.
    1. Brief internal teams. Explain what changes for requesters, budget holders and AP, and why.
    1. Notify suppliers. Send clear notice with the go-live date and how to quote a PO.
    1. Run the warning period. Pay non-PO invoices but flag and follow up every one.
    1. Go live. Return or hold non-PO invoices with clear instructions on what to do next.
    1. Resolve fast. Get POs raised quickly for genuine purchases so suppliers are not left waiting.
    1. Monitor and adjust. Track the measures below and refine the rules.

What to Tell Suppliers

Clear communication prevents most supplier problems. Adapt this notice to your organisation:

Sample supplier notice

Subject: Purchase order numbers required on all invoices from [date]

From [date], every invoice sent to [organisation] must quote a valid purchase order (PO) number. This helps us approve purchases in advance and pay you on time.

What you need to do: before supplying any goods or services, ask your contact at [organisation] for a PO number. Quote it in the [reference field / top right] of your invoice and send invoices to [AP email address].

Invoices without a PO: from [date], invoices that do not quote a valid PO will be returned to you with guidance on how to obtain one. Until then, we will continue to pay them but will contact you to confirm the PO.

Questions: contact [name, email, phone]. Thank you for your support.

Protecting Suppliers

    • Do not punish suppliers for internal failures. If an employee ordered without a PO, help the supplier get one quickly.
    • Pay promptly once a PO exists. Returned invoices should not lose their place in the payment run once corrected.
    • Give small suppliers extra help. They are most affected by delays and least likely to have read your notice.
    • Check payment obligations. Late-payment rules in many countries give suppliers rights to interest on overdue invoices. Confirm with your finance or legal team how returned invoices are treated.

How to Measure Success

Measure What it shows
PO compliance on tail invoices Whether invoices now arrive with a valid PO
Invoices returned or held for missing POs Whether the policy is being enforced, and where gaps remain
Time to resolve returned invoices Whether suppliers are being kept waiting
Retrospective POs as a share of all POs Whether the policy is followed or just worked around
Supplier queries about POs Whether communication is clear
Invoices paid late Whether the policy is harming suppliers

Common Mistakes

    • Switching it on before fixing the buying side. The result is a wave of retrospective POs.
    • No warning period. Suppliers and employees learn about the policy from returned invoices.
    • Too many exceptions. A long exception list becomes the new normal route.
    • AP left alone to enforce it. Without visible support from finance leadership, AP faces pressure to make exceptions.
    • Measuring compliance only. High compliance with many retrospective POs means control has not really moved upstream.

Next step

See where your organisation stands. The Tail Spend Management Assessor asks four quick questions and points you to the management approach that fits your profile, so you can see which changes to make before switching on no-PO-no-pay.

Frequently Asked Questions

What does no-PO-no-pay mean?

No-PO-no-pay means that supplier invoices are only paid if they quote a valid purchase order, except for a short list of agreed exceptions. Invoices without a PO are returned or held until a PO is raised for a genuine, approved purchase.

What should be excluded from no-PO-no-pay?

Common exceptions include utilities and telecoms, rent and leases, taxes and statutory fees, card payments and genuine emergencies. Recurring contracted services are usually handled with a blanket PO rather than excluded.

What is a retrospective purchase order?

A retrospective PO is raised after the goods or services have been ordered or delivered, often after the invoice arrives. Occasional retrospective POs for genuine emergencies are normal, but frequent ones show the policy is being worked around.

How do you introduce no-PO-no-pay without upsetting suppliers?

Fix the internal routes to a PO first, give suppliers clear notice with a go-live date, run a warning period where invoices are still paid but flagged, resolve returned invoices quickly, and pay on time once a valid PO exists.