Adding a PO Number After the Invoice Was Sent

You send an invoice on Net 30. Three days later the reply lands: "AP won't process this without a PO number." The invoice is already out, the amount is correct, nothing about the work has changed. You just need a reference number added so the client's accounts payable team can match it to their system. Reissuing the whole thing feels like overkill, and it is.

Here is exactly how that gets handled when the invoice is a shared link rather than a static PDF, step by step, and who does what at each point.

Step 1: The client opens the link and finds the field

The invoice you sent is a private link. The client opens it, no account, no login, no signup. They see the same branded invoice you see, including the payment details and terms. Near the billing details there is a field for a purchase order number. It is one of the fields the recipient can edit directly, alongside their billing entity, billing address, and accounts payable contact.

If the client is not sure what format their PO should follow, or whether they even have one issued yet, they can check it against a PO number format checker before they type it in. Most delays here come from a PO that was never raised on the client's side, not from anything on the invoice.

Step 2: The client types the PO number and saves

The client enters the number, for example PO-48213, and saves. That is the whole action on their end. They do not request a change, they do not wait for you to approve it, and they do not need to email you a screenshot. The purchase order sits on the invoice immediately.

This matters because a PO number is not a change to what you are billing. If you want the background on why AP treats this reference as a gate, the guide to how purchase orders work covers where the number comes from and why a match to their system is required before payment.

Step 3: You get notified, and you can revert if something looks off

The moment the client saves the PO, you are notified. You see the number that was added and by whom. If it is wrong, mistyped, or attached to the wrong invoice, you can revert it in one click. Most of the time you glance at it and move on.

The important part: adding the PO does not create a new version of the invoice. This is a tracked amendment, recorded against the current version, not a jump from V1 to V2. Content edits (line items, pricing, currency, terms) create a new version. PO numbers and billing details are amendments to the version you already issued. If you want the practical line between the two, see the difference between invoice versions and amendments.

That distinction keeps your records clean. The invoice number stays fixed. The issue date stays fixed. Your bank details stay fixed. Those are locked once the invoice is sent. Only the client-editable reference fields moved, and every move is logged.

Why this beats the PDF version of the same task

With a flat PDF, adding a PO number means the client emails you, you open the file, add the number, re-export, rename it, and email it back. Now two PDFs exist. AP might process the old one. You might lose track of which is current. The back-and-forth that a static PDF creates is exactly where invoices go quiet for a week.

A shared invoice has one canonical copy. The PO appears on it, the client can still edit their own billing fields if the entity or address also needs fixing, and there is no second file drifting around a mailbox. If AP wants a PDF for their filing, the client can download the current one, PO number included, straight from the link.

What to do if the client asks for this and you are unsure

If a client tells you a PO is needed after you have already issued, the short answer is: send them the link and point them at the PO field. The longer answer, with the exact wording to reply with, is in the walkthrough for when a client wants to add a PO number after sending. It covers the case where the PO must appear before you send too, so AP never bounces it in the first place.

A few things worth confirming while you are there:

• The PO reference matches the number the client's procurement team actually raised, not a placeholder.
• The billing entity on the invoice matches the entity the PO was issued to. A mismatch here is a common reason AP keeps rejecting an invoice.
• The accounts payable contact is set, so the invoice can be forwarded to the right inbox for approval.

After the PO is on: the path to paid

Once the PO number is attached and the billing details check out, the client forwards the invoice to their AP contact and, when the numbers are agreed, approves it. Approval locks that version permanently. You have a fixed invoice number, a matching PO, a clean amendment history, and a paper trail that shows exactly when the reference was added and by whom.

If you are setting up a new invoice and already know a client runs everything through procurement, you can add the PO field expectations up front when you create the invoice. That saves the round trip entirely. Either way, the number goes on the same invoice, tracked, and nobody reissues anything.