Invoice rejected for a missing purchase order? Fix the blocker first.

A rejected submission is not the same as an unpaid approved invoice

A purchase order, or PO, is a buyer’s purchasing record. When a client requires one, its accounts-payable process may match your invoice against that record before approval. A missing number can stop the invoice before it enters the normal payment queue. A number that exists but is closed, belongs to a different entity or does not cover the billed work can create a different blocker.

Start with the rejection notice, not another generic payment reminder. Capture its exact wording, invoice reference, submission date, portal or email channel, and any case number. Ask which stage failed: document intake, matching, service approval or payment approval. Your contact saying “finance has it” is useful context, but it is not evidence that the invoice passed those steps.

UCLA’s rejected-invoice guidance provides a concrete example. It distinguishes initial submission rejections from later approval rejections. An invoice rejected at initial submission may not appear in its procurement system at all. UCLA also requires the PO number in the invoice file; putting it only in an email subject is insufficient for that process. Other buyers have their own requirements, so check your client’s instructions.

Match the rejection reason to a person who can fix it

Treat this as a diagnostic checklist, not a claim that every buyer uses all these controls. For example, UCLA directs suppliers with missing POs to the UCLA customer who placed the order, rather than asking AP to create the PO. In your account, identify the equivalent purchasing owner instead of sending the same request repeatedly to an inbox that cannot authorize it.

Do not invent a PO number, reuse one for unrelated work or split an invoice simply to get under a purchasing limit. If the buyer disputes whether the work was authorized, route that commercial issue to the account lead. Correcting invoice formatting cannot resolve a scope disagreement.

Ask the client sponsor for a specific purchasing action

Give the sponsor enough context to locate the order: the service period or milestone, their legal entity, the invoice reference, amount and exact rejection. Ask for a named owner and response date. If you already have a PO, ask about its status or required amendment instead of asking for another number without explanation.

Subject: PO needed to resolve invoice [number] submission

Hi [name],

[AP / the portal] rejected invoice [number] for [service period or milestone], [currency and amount], with this reason: “[exact rejection wording].”

Could you confirm the valid purchase-order reference for this work, or introduce us to the person who can arrange it? Please also confirm whether the PO needs a particular line or service reference on the invoice.

We will update the invoice through our billing process and resubmit using your required route once the details are confirmed. Could you let us know the owner and expected next step by [date]?

The original invoice was issued on [date] with a stated due date of [date]. We will keep that history visible while the submission issue is resolved.

Thank you,
[name]
[role and business]

Keep the request factual. If work started before a required PO was issued, say so internally and review the approval history. Ask the sponsor how the buyer handles that situation; do not suggest backdating an authorization or represent a pending purchase approval as completed.

Correct the document without creating a second debt

1. Check the current record first. Confirm that the invoice was not already accepted or paid through another submission. Search by invoice number and amount, and reconcile any payment or credit.
2. Use your approved correction process. Depending on your accounting system and applicable invoicing rules, a correction may use a revised document or require a credit and replacement. Preserve the audit trail and link any replacement to the original. Do not create a second open receivable for the same work.
3. Validate the purchasing details. Check the PO, relevant line, buyer and supplier entities, currency, service period, amount and required evidence. Put each detail where the client requires it, including on the invoice file where applicable.
4. Submit through the designated channel. Avoid sending independent copies to multiple processing inboxes or portals. If AP asks for a reference copy by email, label it clearly and follow their instruction about duplicate processing.
5. Save the result. Record the corrected version, submission timestamp, receipt or case reference and next acceptance check. A file upload succeeding only proves that upload step succeeded.

Confirm acceptance, then ask when payment can move

Separate four checkpoints in your notes: submitted, accepted into processing, approved for payment and paid. A buyer may use different status names; ask what theirs means. An acceptance message can still leave a project approval outstanding, and a scheduled payment can still be awaiting bank receipt.

Subject: Acceptance check — invoice [number], PO [reference]

Hi [name / AP team],

We resubmitted the corrected invoice [number] for [currency and amount] on [date] through [channel], using PO [reference]. The submission reference is [reference].

Could you confirm that it has been accepted into your processing queue and whether any approval or supporting document is still required? Please identify the owner of any remaining action.

The original stated due date is [date]. Please confirm the payment date your team has recorded and the expected payment run, so we can resolve any difference in timing.

Thank you,
[name]
[role and business]

A corrected submission may affect payment timing if the agreement makes a valid invoice or another acceptance condition the starting point. Alternatively, the original due date may still apply. Read the agreed terms and resolve any difference with an authorized person. Do not silently change the invoice date, due date or aging report just because a new copy was uploaded.

Record the expected cash receipt separately for your 13-week cash flow forecast. For example, AP may schedule a transfer for 6 October even though the contractual due date remains 1 October. Those dates answer different questions. Keep the payment promise and allow for the agreed transfer method when choosing the receipt check.

If the buyer cannot supply a PO, escalate the decision

Once the requested date passes, check whether the blocker is an absent purchasing owner, a pending approval, insufficient budget or disagreement over the work. Give the account lead the agreement, rejection notice, invoice, supporting approval and actions already tried. Ask for a decision on the route to resolution, with a named client contact and next review date.

• If the sponsor is absent, find an authorized delegate rather than assuming AP can bypass procurement.
• If purchasing approval is pending, ask what evidence or decision is missing and who owns it.
• If the buyer says a non-PO route is available, obtain its requirements from an authorized contact before resubmitting.
• If the work or amount is disputed, separate that issue from the technical rejection and assign a commercial owner.
• If no workable route is offered, have the finance or account lead review the contract and appropriate next step. Do not treat a portal error as permission to add fees or suspend work automatically.

Use the broader overdue-invoice workflow when the issue moves beyond invoice correction. Once the invoice is accepted and no blocker remains, choose a payment reminder that reflects its actual due date, balance and latest reply.

Move the PO check into onboarding and scope changes

For the next invoice, collect purchasing requirements before the billing deadline. For recurring agency work, include the PO owner and renewal point in the retainer payment terms brief. A yearly PO can still run out of value when the monthly scope grows.

Client billing entity:
Supplier entity and vendor ID:
PO required: yes / no / awaiting confirmation
Purchasing owner and backup:
PO number, status and relevant line:
Covered service period and scope:
Authorized amount and remaining value:
Approved change requiring an amendment:
Required invoice fields and supporting evidence:
Submission portal or inbox:
AP contact and approval owner:
How acceptance will be confirmed:
Agreed terms and payment-run requirements:
PO renewal or review date:
Internal billing owner:

Review this record when scope changes, a new entity signs, a PO nears expiry or a retainer renews. Track repeated rejection reasons in your accounts receivable process, then fix the most frequent preventable cause. The useful improvement is an invoice that can enter the correct queue with its evidence intact.