The Missing PO Number That Quietly Kills Your Invoice

You sent the invoice on day one. Net 30. On day 35 you email a polite nudge and get back: "Hi, AP can't process this without a PO number. Can you reissue?" You reissue. The clock restarts somewhere inside their system. You get paid on day 58.

That six-digit string was the only thing standing between you and the money. It is the single most common reason a clean B2B invoice sits unpaid, and it is almost entirely a workflow problem, not an accounting one.

Why AP refuses to pay an invoice with no PO

In any company past a certain size, accounts payable does not pay invoices. They pay matched invoices. The PO number is the key that joins three records: the purchase order the buyer raised internally, the goods-received or services-accepted note, and your invoice. No key, no match. No match, no payment run.

This is called three-way matching, and AP teams are measured on how clean their match rate is. When your invoice arrives without a PO number, or with a PO that does not exist in their ERP, it gets routed to an exceptions queue. Exceptions queues are worked in batches, often weekly, sometimes less often. Your invoice is not late because anyone dislikes you. It is late because it failed an automated check and is now waiting for a human to manually research it.

The same thing happens with a PO that is formatted wrong. A leading zero stripped by a spreadsheet, a hyphen where their system expects none, a PO from the wrong cost center. If you want to sanity-check a number before you send, the PO number format checker will catch the obvious shapes.

What the delay actually costs

Take a 4,800 dollar invoice on Net 30. If a missing PO pushes payment to day 55, you have financed your client for 25 extra days at zero interest. On one invoice that is annoying. Across a year of work with the same client, at typical small-business cost of capital, it is real money you are giving up. It also distorts every cash-flow forecast you make, because you cannot predict which invoices will trip the exceptions queue.

And there is the soft cost. Reissuing a PDF, updating your records, chasing the new approval, re-sending to the AP inbox. Twenty minutes per invoice. Multiply by how often this happens. This is the boring tax that the research on late Net 30 invoices keeps surfacing.

The usual fixes, and why they only half work

The standard advice is: ask for the PO before you start work. Good in theory. In practice the person who hires you often does not know the PO number yet, has not raised the PO, or works at a company where POs are only cut after the first invoice arrives. You can also ask AP directly, but you usually do not have a contact there until something is already wrong.

The other common workaround is to leave a blank "PO Number:" field on the invoice and hope the client writes it in by hand before forwarding to AP. They will not. They will forward the PDF as-is, AP will bounce it, and the email will land in your inbox three weeks later.

You can put the PO field on your invoice template (the free invoice generator includes one), but a static PDF still has to come back to you for any edit. That is the loop you want to break.

Let the recipient add the PO themselves

The cleanest fix is to stop treating the invoice as a finished document and start treating it as a shared record. When you send a JupiterInvoice link, the recipient can add the PO number directly to the invoice without asking you for anything. They open the link, type the PO into the PO field, and the invoice updates. You get a notification. If they typed something wrong, you can revert it in one click.

The PO number, billing entity, billing address, and AP contact are all recipient-editable fields. The recipient changes them; you are notified; you can revert if needed. That covers about 80 percent of the "can you reissue?" emails you currently get. Crucially, none of this creates a new invoice version. Your invoice number stays the same. Your issue date stays the same. The bank details and totals stay locked. The amendment is tracked against the existing version, which keeps your records clean and your accountant happy.

The same link also lets the recipient set or update the AP contact and forward the invoice to AP directly, so the document arrives in the right inbox the first time. The PO Roulette reel is a half-joke version of the workflow this replaces.

What to do on your next invoice

Three concrete changes. First, include a PO field on every B2B invoice even if you do not have a number yet. An empty field is a prompt; no field at all gets ignored. Second, send the invoice as a link the client can act on, not a PDF they have to email back to you. Third, ask once, in the email that delivers the link: "If you need a PO on this, you can add it directly from the link, no reissue needed." That sentence alone has saved more invoices than any chasing template.

If you want to try the workflow on a real invoice, create one in about two minutes and send the link. Agencies and consultancies tend to feel the biggest difference, which is why there is a tailored setup for agency invoicing. The PO problem does not need a process. It needs a field the client can fill in.