Let Agency Clients Fix Their Own PO and Billing

You sent the invoice on the 2nd. It's now the 18th. The work is done, the amount is right, and it still hasn't moved. Not because anyone disputes it. Because procurement wants a PO number on it, the billing entity reads Acme Corp and their AP system only pays Acme Holdings Ltd, and the one person who can tell you all this is three forwards deep in a thread you started last Tuesday.

This is the quiet tax on agency work. The invoice is correct. The metadata around it is wrong, and fixing the metadata runs through you.

Why procurement edits pile up on the agency side

Agencies bill companies with real accounts payable teams, and those teams run on rules. No PO number, no payment. Wrong legal entity, no payment. Missing AP contact, the invoice sits in someone's inbox until a reminder jogs it loose.

None of those details are things you can know when you draft the invoice. The client's procurement team assigns the PO after you've sent it. The correct billing entity lives in their vendor master, not in your project brief. You guess, you get it wrong, and the correction becomes a round trip: they email you the PO, you edit the file, you resend, they confirm, AP finally keys it in.

Each round trip is a day, sometimes three. On Net 30 terms, two or three rounds can push a 30-day invoice past 50 days old before the clock even starts counting for real. Multiply that across every client with a procurement gate and you're financing their process out of your cash flow.

Put the editable fields on the invoice, not in your inbox

The fix is to stop being the middleman for details the client owns. The PO number is theirs. The billing entity is theirs. The AP contact is theirs. There's no reason those should travel through your email at all.

JupiterInvoice does this by making the invoice a link instead of a file. You create the invoice, generate a private link, and send it. The recipient opens it with no account and no signup, and four fields are theirs to edit directly:

• The PO number
• The billing entity (the legal name AP will actually pay)
• The billing address
• The AP contact

When they change one, you get notified, and you can revert it if something looks off. They're not filing a request and waiting on you. They're typing the PO into the field where it belongs. This is the core of how invoicing built for agencies works: the people who hold the procurement details are the ones who enter them.

The invoice moves through a clear set of statuses, Draft, Sent, Viewed, Paid, so you can see it was opened and whether anything changed. PO and billing edits are tracked as amendments to the current version, not a whole new version, so you keep a clean record of who touched what without a stack of V2, V3, V4 files.

What stays yours, and why that matters to procurement

Letting the client edit does not mean handing them the whole invoice. The line items, pricing, discounts, currency, payment terms, and due date are yours alone. The recipient cannot change them. If they want a different rate or a later due date, they say so in the comment thread on the invoice, and you decide. There's no approve or decline button, no formal change-request dance. Just a question in context and your answer.

Some fields are locked for everyone once the invoice is issued: the invoice number, the issue date, your own details, and your bank details. AP teams care about this. An invoice whose number or bank details could be edited after the fact is a fraud risk they have to flag. Locked fields are one less reason for them to kick it back. If you want to understand why your invoices get bounced, the pattern usually traces to a field AP could not reconcile, and most of those are the editable ones the client should have filled in.

How this plays out on a real agency invoice

Say you're billing a retainer and a project in the same month to one client. You send the link. Their project manager opens it, sees the billing entity is the parent company and not the subsidiary that owns the budget, and corrects it. Then procurement adds the PO once it's issued. Then the PM sets the AP contact and forwards the invoice straight to accounts payable from inside the link.

You did none of that. You got three notifications and the invoice is now sitting in AP's queue with every field they need already populated. If procurement is picky about PO format, the client can check it against what AP expects before it ever becomes a problem; our PO number format checker exists for exactly that.

Comments keep the conversation on the invoice instead of scattered across email. When the finance person asks whether the retainer line can be split out separately, you see it on the invoice, you answer, and if the answer is yes, you make the edit. One source of truth, not a thread and a file that have quietly drifted apart.

If your clients routinely route invoices through procurement, this is the difference between chasing paperwork and watching it get handled. You can create an invoice and send the first link in a few minutes. It's free, with unlimited invoices; the only thing the free plan adds is a small "Powered by JupiterInvoice" footer, which Pro removes for 10 dollars a month.

Stop editing other people's PO numbers. Send a link, and let the client fill in the details they own.