Check a PO Number Against the Format AP Expects

You sent the invoice with the PO number the client gave you. Two weeks later AP kicks it back: the number does not match anything in their system. Now the invoice sits at 0 dollars paid while you chase down which digit was wrong.

Most PO rejections are not about the work. They are about a number that is one character off, missing a prefix, or padded with the wrong count of zeros. That is a format problem, and you can catch it before you hit send.

What a PO number actually is, and why AP is strict about it

A purchase order is the buyer's internal authorization to spend. The PO number is the key that links your invoice to that authorization inside their accounts payable system. No match, no payment. AP does not have the authority to pay against a number that does not exist in their records.

That is why the format matters so much. If their system expects PO-4500012345 and you typed 4500012345, the match fails. If it expects ten digits and you sent nine, same result. AP will not guess. They bounce it.

The five things to check before you send

Run the PO number the client gave you against these five points. Most rejections come from one of them.

• Prefix. Many systems require a leading tag like PO, 4500, or a department code. If the client's past POs all start the same way and yours does not, add it or confirm.
• Length. Count the digits. SAP-based systems often use exactly 10. Others use 6 or 8. A number that is short or long by one is the most common miss.
• Separators. Some formats use a hyphen (PO-100234), some run it together (PO100234). Match the exact punctuation.
• Leading zeros. If the system stores 0000100234 and you drop the zeros, the match can fail. Keep them.
• Letters vs numbers. An O read as a zero, or an I read as a one, kills the match. Retype it, do not copy a blurry screenshot.

If you want to check the pattern quickly against common formats, the PO number format checker flags length and structure problems in a few seconds. It will not confirm the number exists in the client's system (only their AP can do that), but it catches the shape errors that cause most bounces.

How to confirm the format when you are not sure

If this is a new client, you do not have a past invoice to copy from. Ask directly. One line in an email to your contact: "Before I invoice, can you confirm the exact PO number and format, including any prefix and the full digit count?" That question takes them ten seconds and saves you a rejection cycle.

If you have billed them before, pull an old invoice that got paid. Copy that PO format exactly. The pattern almost never changes for the same buyer.

When the client tells you to bill through a vendor portal instead, the portal usually enforces the format for you. That is a different situation with its own headaches, and it is worth knowing what to do when a client wants their portal before you get stuck creating yet another login.

Put the PO number where AP can find it

A correct PO number in the wrong spot still gets flagged. AP teams scan for it near the top of the invoice, usually in the header alongside the invoice number and date. Do not bury it in a line item description or the notes field.

If you are unsure what else AP looks for before they approve payment, the accounts payable approval checklist lays out the fields they check, field by field. Getting the PO right is one line on that list, but it is the one that stops payment cold when it is wrong.

What to do when the PO number changes after you send

Sometimes the client gives you a placeholder, then a real PO comes through a week later. Or they issue the PO number after you have already invoiced. On a static PDF, that means reissuing the whole document and hoping AP catches the new version.

With recipient editing on a shared invoice link, the client can add or correct the PO number themselves, directly on the invoice you already sent. You get notified, and you can revert it if something looks off. The PO number is one of the fields the recipient can edit without an account and without you rebuilding anything. Handling a PO number added after sending becomes a tracked amendment on the current version rather than a new document.

The fastest path to a first-time-clean invoice

Ask for the exact format up front. Check the number against the five points above. Put it in the header. Send a link the client can correct if the PO shifts later.

When you are ready to build one, you can create an invoice with the PO number in place and share it as a link the recipient works with directly. No PDF loop, no waiting to find out which digit was wrong.