No PO, no pay: how to make a purchase order policy work without stopping the business

On the 25th of the month, the AP team at a plastic packaging manufacturer in Cikarang starts preparing the payment run. Among the invoices is one for Rp 18,600,000 from a workshop that rewound a burnt-out motor on an extrusion line. The work was done two weeks earlier, after the maintenance supervisor called the workshop at night to keep the line running. The invoice has no PO number, because there was no PO.

The company has had a “no PO, no pay” rule since January. So AP does what it always does: it asks the supervisor to raise a PO, the supervisor raises one dated that day for exactly the invoice amount, the department head approves it in a minute and the invoice is paid. On paper, the rule held. In reality, nobody approved the repair before it was ordered, nobody compared the price and the approval recorded something that had already happened.

No PO, no pay is one of the most common rules in procurement, and one of the most quietly worked around. This guide covers what the rule is for, what should and shouldn’t need a purchase order, a worked example of one month’s invoices, why the rule fails and how to set it up so it holds.

What is a no PO, no pay policy?

A no PO, no pay policy says a vendor invoice is paid only if it quotes a purchase order that was approved before the goods or services were ordered. The purchase order (PO) is the company’s commitment to the vendor: what is being bought, at what price and on what terms. It’s the step in procure-to-pay where an approved request becomes an order.

The rule isn’t about paperwork. A PO raised before the order gives you four things an invoice can’t:

• Approval before the commitment. Someone with the authority agreed to the spend while there was still a choice.
• A budget check. The order counts against the budget as a commitment before the invoice arrives.
• An agreed price. The quantity, price and terms are agreed in writing before the vendor delivers.
• Something to match against. The invoice and the goods receipt are checked against the PO, line by line, through 3-way matching.

A PO raised after the invoice gives you none of them. It records a decision someone already made alone.

What needs a PO, and what doesn’t

The rule only holds if it covers spend where a PO is possible and useful. A typical split, as an example to adapt:

Spend	PO needed	Controlled by
Goods, stock and spare parts	Yes	A PO before the order
One-off services and projects	Yes	A PO before the order
Regular supplies from one vendor	Yes, one per period	A blanket PO
Emergency repairs	Yes, within a working day	An emergency route
Utilities, rent and taxes	No	The contract or schedule
Small purchases under a limit	No	Expense claims or petty cash

A blanket PO covers repeated purchases from one vendor over a period, such as pallets for a quarter, up to an agreed amount. Each invoice is drawn against it, so a weekly order needs one approval instead of thirteen. An emergency route lets someone order first when a line is down, provided they record the reason and raise the PO within a working day, approved by a named person.

How the rule works, step by step

1. Request. The requester raises a purchase request, checked against budget and policy.
2. Approve. The request goes through your approval matrix before anything is ordered.
3. Order. The approved request becomes a PO, sent to the vendor with its number.
4. Receive. The goods or services are recorded against the PO lines when they arrive.
5. Invoice. The vendor quotes the PO number on the invoice.
6. Match and pay. The invoice is matched to the PO and the receipt, and paid on its terms.
7. Handle the rest. An invoice without a PO is checked against the list of exempt spend. If it isn’t exempt, it goes to a stricter approval chain with the requester’s explanation, and it’s counted as an exception.

A worked example: one month’s invoices

Here is the Cikarang manufacturer’s October, sorted by when the PO was raised:

October invoices	Invoices	Rp ’000
PO raised before the order	212	1,846,300
Exempt: utilities, rent, subscriptions	26	412,750
PO raised after the invoice	38	297,400
No PO at all	14	63,200
Total	290	2,619,650

On paper, 250 of the 290 invoices had a PO, about 86%, and the monthly report said the policy was working. Only 212 had one before the order. The 38 POs raised after the invoice, worth Rp 297.4 million, came from three places:

• 21 repairs and breakdowns, Rp 168,900,000. The motor rewind among them. Genuine emergencies with no emergency route, so every one became a PO raised after the fact.
• 11 invoices from three regular vendors, Rp 94,300,000. Pallets, packaging tape and forklift gas, ordered by WhatsApp every week because a PO for each order felt absurd. One blanket PO per vendor would have covered them.
• 6 purchases that waited for approval, Rp 34,200,000. The request was raised, but its approval took longer than the vendor’s delivery, so the goods arrived first.

The 14 invoices with no PO at all, about Rp 4.5 million each on average, were small one-off purchases that belonged in expense claims or petty cash.

None of the 38 was fraud. But each was spend nobody approved before it was ordered, and each group needs a different fix: an emergency route, a blanket PO and faster approvals. Refusing to pay the workshop would have fixed none of them.

Why no PO, no pay fails

• It covers spend that can’t have a PO. Electricity, rent and tax payments go through the exception process every month, so exceptions become normal and the rule loses its credibility.
• There’s no route for emergencies. When a line is down, people order first, and the PO raised afterwards is counted as compliance.
• Regular orders need a PO each time. A weekly order of packaging tape needs a weekly PO, so people stop raising them.
• Approvals are slower than deliveries. If a PO takes four days to approve and the vendor delivers in two, the order goes out before the approval.
• It’s enforced at the invoice. By then the vendor has delivered, and refusing to pay punishes the vendor rather than the person who ordered.
• Vendors were never told. They deliver on a phone call and invoice whoever called them.
• The report counts PO numbers, not PO dates. Any invoice with a PO counts as compliant, however late the PO was raised.

No PO, no pay in Indonesia

• PO susulan. POs raised after the fact are common enough to have a name (PO susulan). Report them as exceptions, by department and requester, not as compliance.
• Orders by WhatsApp and phone. Plants, project sites and branches often order from regular vendors by message. Make the PO as quick to raise and approve from a phone, or give those vendors a blanket PO.
• Tell vendors in writing. Send each vendor a letter with the date the rule starts, and print it on every PO: invoices must quote the PO number and be addressed to the PT and NPWP named on the PO.
• Set the tax treatment on the PO. Whether a purchase is a service with PPh 23 withheld, and whether VAT applies, is easier to settle when the PO is raised than when the invoice is paid. Record it on the PO so the invoice and the faktur pajak are checked against it, and confirm the treatment for each category with your tax adviser.
• Approvals the anggaran dasar requires. Some large purchases or contracts may need approval from the Board of Commissioners (Dewan Komisaris) under the articles of association (anggaran dasar). The PO stage, before the commitment, is where that approval has to be in place.

Signs your PO policy needs work

You probably need to look at your PO policy if any of these sound familiar:

• Invoices arrive for orders finance didn’t know about.
• POs are raised on the day the invoice arrives, for exactly the invoice amount.
• The PO date is later than the delivery date.
• Utility bills and rent go through the same exception process every month.
• Regular supplies need a new PO every week.
• Vendors are told to “wait for the PO” after they’ve delivered.
• Your compliance report counts any invoice with a PO number as compliant.

A PO raised after the invoice is a receipt, not an approval.

How to set up no PO, no pay

1. Measure where you are. Sort three months of invoices into four groups: PO before the order, PO after, exempt and no PO. Compare each PO’s date with the delivery and invoice dates.
2. Write the exemptions down. List the categories that never need a PO, and how each one is controlled instead.
3. Make the PO faster than the workaround. Keep approved vendors and agreed prices ready to pick, let approvers act from a phone and give approvals a deadline in your approval matrix.
4. Give regular vendors a blanket PO. One PO per vendor per period, with an amount, drawn down by each invoice.
5. Create an emergency route. Order first, record the reason and raise the PO within one working day, approved by a named person.
6. Tell vendors, and start soft. Send the letter, then for the first month or two route invoices without a PO to the requester and their manager rather than back to the vendor. Once the routes above work, return invoices without a PO to the vendor.
7. Report exceptions monthly. By department and requester, with POs raised after the fact counted as exceptions. Go through the largest few with each department head.

---

How Procapy helps

In Proca to Pay, the purchase request is raised in Procapy rather than in a chat message, starting from your approved vendors, catalogue items and contract prices. Before it can be submitted, ProcAI checks it against policy, budget and the vendor list. ProcApprove routes it through your delegation-of-authority matrix, approvers act from their phone with the budget and policy context on the same screen, and reminders and escalation run themselves. Once approved, the request becomes a purchase order with no re-entry, and open commitments are visible to finance before the invoice arrives.

When the invoice comes, ProcAI reads it in any format, from PDF and photo to e-invoice and scanned paper, links it to its PO and three-way matching runs within the tolerances you set. You decide which categories or amounts must have a PO. Invoices without one still go through capture, approval, fraud checks and payment, matched against the approved request and budget instead, and an invoice with no PO, or one that exceeds its PO, goes to a different, stricter approval chain. For the request that truly can’t wait, a break-glass path with a mandatory justification keeps the exception on the record.

Most teams are live in under two weeks. The fraud and risk page covers the invoice checks in more detail. Book a 30-minute walkthrough, bring a month of vendor invoices, and we’ll run them through the duplicate, mismatch and policy checks live.