A purchase order request is the request you send a customer when an invoice can’t be paid because the PO behind it doesn’t exist, has expired, or has run out. Under a “no PO, no pay” policy, the customer’s AP team won’t approve an invoice without a valid purchase order number, however real the work was. The invoice sits, the clock doesn’t start, and your team finds out weeks later.
A controller at a data software company described the pattern last month. The customer never raised a PO, and nobody on their side knew until the invoice reached their accounting team. By then, the work was done, the invoice had been sent, and the payment was already late.
This guide covers the three PO problems behind most of these invoices, how to write a PO request that gets approved, and how to stop the next one before it starts.
What “no PO, no pay” means for a supplier
Definition
No PO, no pay
A customer policy that its AP team will not pay a supplier invoice unless it references a valid, open purchase order with enough funds to cover it. Invoices without one are rejected or held until a PO exists.
For the customer, the policy is a control on its procurement process. Every dollar of spend goes through review and approval before the invoice arrives. For the supplier, it moves part of the customer’s approval process onto your desk. If the person who ordered the work skipped the PO process, your invoice is where that gap shows up.
Some customers allow a non-PO invoice for specific categories, such as utilities, subscriptions under a set amount, or one-off services approved by email. Ask for that list. If your service is on it, the rest of this guide doesn’t apply to that customer.
Three PO problems, three different fixes
“No PO” covers three different situations. Each one comes back from the customer AP portal with a different message, and each needs a different person on the customer’s side.
| Problem | What the portal shows | Who can fix it | What to send |
|---|---|---|---|
| The PO doesn’t exist | Rejected: PO doesn’t exist, or missing PO reference | The person who ordered the work | A purchase order request with the quote or contract |
| The PO is used up | Rejected: insufficient PO funds, or PO fully invoiced | The person who ordered + procurement | A request to increase the PO amount |
| The PO has expired or closed | Rejected: PO closed | Procurement | A request to reopen or renew the PO |
| A not-to-exceed PO is close to its cap | Approved, until the next invoice goes over | The person who ordered | An increase request before the cap is hit |
A freight data company told us its main pain point was exhausted and expired POs. An elevator manufacturer asked in particular about not-to-exceed purchase order increases. Both are the same problem: a PO that was valid when the work started and isn’t by the time the invoice arrives.
How to write a purchase order request that gets approved
A purchase order request goes to a person, not a portal. The portal will keep rejecting the invoice until someone on the customer’s side issues a purchase order or changes the existing one. These five steps get you there faster.
1. Find the person who ordered the work
Your contact in AP can’t create a PO. The person who asked for the work can. Get their name from your sales or delivery team, not from the customer’s AP inbox.
2. Send the PO request before the invoice, when you can
The cheapest PO request is the one you send at order intake. If your contract or quote is signed and no PO number is included, ask for it that day.
3. Give them everything procurement will ask for
Include the amount, the products or services, the period it covers, your contract or quote reference, and the cost center, if known. A request that procurement has to send back for details loses a week.
4. Copy procurement on increases and renewals
The person who ordered the work can ask for more budget. Procurement changes the PO. Put both on the same email so neither waits for the other.
5. Set a follow-up date
Write down when you will check the portal again. A PO request without a follow-up date becomes a past-due invoice.
Here is a short PO request you can adapt:
Email Template
Hi [name], we’ve completed [work] under [contract or quote reference], and our invoice for [amount] can’t be processed in [portal] without a purchase order. Could you raise a PO for [amount] covering [period], or send me the PO number if one exists? Once I have it, I’ll submit the invoice the same day. Thanks, [your name]
Why a missing PO costs more than one late invoice
A rejected invoice doesn’t start the customer’s payment terms. On 60-day terms, three weeks spent chasing a PO pushes the payment back three weeks, and that delay repeats on every invoice tied to the same PO. Your cash flow takes the hit each time.
It adds up. Atradius’s 2026 survey of US B2B payment practices found that late payments affect an average of 22% of B2B receivables. It also names slow internal approval processes as a common reason B2B customers pay late. A missing PO is part of that approval process and is sitting on your invoice.
At ES&E, an invoice could stall in a customer’s portal over a mistyped PO or a PO with no money left on it, and the AR team found out late:
Customer Quote
“We may not even know until, like, 90 to 120 days, until it was actually due.”
Donald Henry, Controller, ES&E
That is the real cost: not the rejection itself, but the weeks before anyone sees it. If you’re deciding which invoices to chase first, our guide on which invoices can be paid now separates PO-blocked invoices from the ones a call can move.
Stop the next no-PO invoice before you send it
Most PO problems are visible before the invoice goes out. Three checks catch them.
At order intake. No PO number, no start date. If the customer won’t pay without a PO, make the PO part of the signed order, not a step for later.
Before each invoice. Check that the PO exists, is open, and has enough balance left for this invoice. A PO that’s 90% invoiced needs an increase request now, not after the rejection.
After each rejection. Log the reason by customer. If one customer’s POs keep running out, ask for larger POs or a blanket PO at the next renewal. Our guide to preventing portal invoice rejections covers other reasons for rejection.
For invoices where the PO exists but the details don’t match, such as a wrong line or a price difference, see our piece on PO mismatches and invoice rejections, and our purchase order matching guide for the full 3-way match.
Key Takeaway
A PO-blocked invoice needs a person, not a resubmission. Name the problem (missing, used up, expired, or capped), send the purchase order request to the person who ordered the work with everything procurement needs, and check every PO’s balance before the next invoice goes out.
How Monto helps you catch PO problems early
Monto is the AI co-worker your billing team hands invoice-to-cash to, across Coupa, Ariba, Tungsten, Tipalti, and more than 600 other customer AP portals. Before an invoice goes in, Monto looks for the PO in the customer’s portal. When the PO isn’t there, is out of funds, or is closed, the invoice comes back to your team as an exception with that reason. You see it the day it happens, not as a past-due call two months later.
At Miro, sourcing the PO is the part the AR team mentions first:
Customer Story
“One of my favorite things about Monto is that it will source the PO for us as well.”
Chase Dixon, Senior Accounts Receivable Analyst, Miro
Asking the customer for a new or bigger PO stays with your team. The change is that you know which invoice needs it and why, while there’s still time to fix it before the due date. For the collections side of the same problem, our guide to collecting unpaid invoices picks it up from there.
The PO is the customer’s approval, not yours
Every “no PO” rejection is the customer’s approval process asking for one more step. Send that step to the right person with everything they need before the invoice is due, and ensure the invoice is paid on the terms you agreed.
See which invoices are waiting on a PO, and why, across every customer AP portal.
Talk to our team about PO exceptions →FAQ
What is a purchase order request?
A purchase order request is a supplier’s ask to a customer to create, increase or renew a purchase order so an invoice can be approved and paid. It goes to the person who ordered the work, with the amount, the period, and the contract or quote reference.
What does “no PO, no pay” mean?
It is a customer policy that invoices are paid only when they reference a valid, open purchase order with sufficient funds. An invoice without one is rejected or held in the customer AP portal until a PO exists.
Can I invoice without a PO number?
Only if the customer accepts a non-PO invoice for that type of spend. Ask the customer’s AP team for their list of non-PO categories. Otherwise, send a PO request and submit the invoice once you have the number.
What should I do when a PO runs out of funds?
Send a request to increase the PO to the person who ordered the work and copy procurement. Include the remaining work, the amount needed, and the contract reference, and check the PO balance before each invoice so the next request goes out before it is rejected.
What is a not-to-exceed purchase order?
A not-to-exceed purchase order sets a maximum amount the customer will pay. Invoices are approved until the total reaches the cap, so suppliers should request an increase before the last invoice that would exceed it.