ZAMBO.

Direct answer

Rejected for a missing number is not rejected work. Reissue the paper, protect the dates, and do not let the job restart itself.

The email is blunt: invoice rejected, no purchase order number, reissue and resubmit. It feels like the job has been sent back to the start, and with a big company it can quietly become exactly that: a fresh invoice date, a payment clock reset to zero, and your delivery treated as though it happened on resubmission day. None of that has to happen. A purchase order number is the client's internal key for paying you; its absence is a defect in the paperwork, not in the work, which was delivered and accepted on real dates that a reissue must carry forward, not replace. This page gives you the verification step that stops a fake or mismatched number cold, the corrected-invoice shape that replaces one document instead of creating a second charge, and the one written question about the clock that is worth more than the reissue itself.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 11, 2026. First published November 11, 2026. The records quoted below are real and public, read back from the live service on November 11, 2026.

Step 1. Get the purchase order from the client in writing, and check it against the job

Ask your client contact, not the automated rejection, for the number, and get it in a message you can keep: the purchase order number itself, the amount it covers, the department or cost center it belongs to, and the exact supplier name it was raised under. Then check those four against your job before you reissue anything. The amount should cover your invoice in full; an order raised for part of the job will pay part of the job and stall the rest. The supplier name should be your name or your business name exactly as your invoice states it, because a mismatch there is the next rejection already scheduled. And the number should come from the client, never invented, reconstructed, or borrowed from a previous job: putting an order number on an invoice that the client did not issue for this work converts a paperwork fix into a false statement, and it is the one version of this errand that can genuinely hurt you. If no order exists because nobody raised one, say so plainly and ask the contact to have one raised; many finance teams can issue a number after the fact when the delivery is documented.

Step 2. Reissue as a corrected invoice that replaces the original, never a second one

The reissued invoice is the same bill with the missing key added, and it should say so on its face. Keep the amount, the work description, and the delivery reference identical. Add the purchase order number exactly as issued, in the field or line their rejection named. Mark the document as a reissue: corrected invoice, reissued on this date, replacing invoice number so-and-so dated so-and-so, which is void and must not be paid. Send it with a covering message that repeats the replacement in one sentence and asks them to confirm the original is voided in their system. That confirmation matters more than it looks: the classic accident in this story is both versions entering the payment run, which lands you in duplicate payment territory, explaining money you never asked to receive twice. One job, one live invoice, one voided original, all of it in writing.

Step 3. Carry the delivery and acceptance dates through untouched

A reissue changes the invoice's birthday. It must not change the job's history: the work was delivered on its real date and accepted on its real date, and both belong on the corrected invoice as the record they are. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show what that history looks like when it lives on a record instead of being retyped onto each new document:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

The accepted record carries its decision with a date no reissue can move: decided_at 2026-10-16T14:31:51.146Z, decided_by client, release ok_to_release, 4 of 4 steps checked. Attach or link that record when you resubmit, and the finance team is looking at a delivery that predates their paperwork problem, which is the correct picture. The pending record shows the state to check before resubmitting at all: if your job's decision still reads pending with release on hold, the missing number may not be the real blocker; get the acceptance recorded first, because a purchase order gets an accepted job paid, it does not get an undecided job accepted.

Step 4. Ask the clock question in writing, and get the answer in writing

Here is the quiet cost of a reissue: many companies count payment terms from the date of the first valid invoice, and a rejected invoice was, in their system's view, never valid, so your 30 days can restart from the resubmission date through nobody's ill will. Do not argue the principle in the abstract; ask the concrete question in your covering message: please confirm the payment date this invoice will be paid on. A named date ends the matter. If the answer restarts the clock and the amount matters to you, your negotiation material is the record: delivery date, acceptance date, and the fact that the missing number was the client's own internal key, absent from every instruction you were given at the start. Some finance teams can and do honor the original timeline when the defect was theirs; none will if the dates are not put in front of them as facts. Whatever is agreed, keep the reply with the invoice. The next person to query this bill, on either side, should find the whole story in one forward.

Step 5. Make the number arrive before the work next time

This rejection has a known birthday: the moment the job started without anyone asking how the client pays. Build the question into your start routine with any company big enough to have a finance team. Before work begins, ask for the purchase order number, or written confirmation that none is needed, and put whichever you receive in the job agreement next to the price. If the number will be raised later, agree the trigger in writing, for example the order is raised at acceptance, and name the person who raises it. Run the job on its record as usual, and at delivery the invoice goes out carrying the number on its first version, with the acceptance attached. The suppliers who never see this rejection are not luckier; they collect the client's payment keys at the same time they collect the brief.

What this page cannot settle

This page cannot raise a purchase order inside the client's company, and it cannot override a finance policy that genuinely requires one; only your client contact can get the number issued. It is general information, not legal or accounting advice; how a corrected invoice and a voided original are treated in your books and your tax filings depends on your setup and jurisdiction. A verifiable receipt proves the saved result was not changed since it was saved; it does not create an order number or compel a payment date. What the record settles is the timeline both sides argue from: when the work was delivered, when it was accepted, and by whom.

Frequently asked questions

My client's finance team rejected my invoice and wants it reissued with a purchase order number. What do I do?

Treat it as a paperwork defect and fix exactly that, in writing. Ask your client contact for the order number with its amount, department, and the supplier name it was raised under, and check all four against your job before reissuing; never invent a number or reuse one from another job. Then reissue as a corrected invoice: same amount, same work, same delivery and acceptance dates, the order number added where their rejection specified, and a line stating it replaces the original invoice, which is void and must not be paid. Ask them to confirm the void and to confirm the actual payment date, because many companies restart the payment clock at the first valid invoice. Attach the delivery record showing when the work was accepted, so the reissue reads as what it is: the same accepted job with its payment key added, not a new bill for new work.

Will reissuing restart my payment terms?

It can, and whether it does is decided by the client's payment policy, not by the calendar. Many accounts teams count terms from the first valid invoice received, and a rejected invoice never counted, so the corrected one starts the clock on its resubmission date. That is why the reissue message should always ask for the payment date itself, in writing, rather than assuming either outcome. If the restarted date is what comes back and the amount is significant, present the facts once, cleanly: the delivery date and acceptance date from the job record, and the point that the missing number was an internal key the client never provided when the work was commissioned. Teams do honor the original timeline when the defect was on their side and the dates are documented. What does not work is silence followed by outrage at day 30; the date question costs one sentence on the day you resubmit.

What if the client never issued a purchase order for this job at all?

Then the rejection has found a gap in their process, and your contact has to close it. Say plainly that no order number was provided at any point, attach the commissioning message, the delivery record, and the acceptance, and ask the contact to have an order raised against that documented job; finance teams do this routinely once the work and its acceptance are in front of them. Do not put any number on the reissue until one is genuinely issued to you for this job. While that is in motion, keep the original invoice live and dated, and get a written line from the contact confirming the job, the amount, and that the order is being raised, so the debt exists in the client's own words even before their system can pay it. If the answer becomes that no order will be raised and no payment can be made, the problem has changed shape: it is no longer a reissue question, it is a non-payment question with the full record already assembled.

Should I change the invoice date or the amount when I reissue?

The amount, never, unless the order genuinely covers a different figure, in which case that difference is a separate conversation to have before any document moves. The date handling follows your own bookkeeping rules, but the document must not pretend history moved: show the reissue date as the reissue date, mark it as a corrected invoice replacing the original by number and date, and keep the original delivery and acceptance dates printed as the record of the work. An invoice that silently takes a fresh date with no reference to its predecessor creates two risks: the original slipping into a payment run beside it, and your own books telling a story your delivery record contradicts. Corrected and replacing, stated on the face, is the whole technique.

How do I stop a finance rejection like this on the next job?

Collect the payment keys at the start, the same way you collect the brief. When the work runs through Zambo, every step lands on the job record with a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, the client accepts on that record, and the acceptance view shows status, decider, date, and release state, so the delivery half of the invoice is already documented before billing begins. New users get 20 calls and 1 wrap-up free every day per agent, and picking up work in another AI is always free. For $0.99, run your next company job on one record, ask for the purchase order number or a written no-order-needed confirmation before the first step, and put it in the agreement, so the first invoice you send already carries every key their finance team will look for: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related