Invoice admin
Invoice rejected by a customer portal: resolve the specific error
When a customer portal rejects an invoice, save the exact reason, establish whether the problem is the file, a field, a customer reference or the underlying charge, and resolve that specific issue. Check the existing submission before trying again. A rejected upload does not by itself establish that the invoice was cancelled or that a new due date was agreed.
By PayerPing · Published
Capture the message before changing anything
Record the invoice number, submission identifier, time and exact rejection text. Check whether the whole submission failed or an existing invoice record now has a query. Keep the original invoice and submission evidence so you can explain what changed.
Do not remove parts of an invoice number, select an unrelated PO or alter an amount simply to get past a screen. If the error is unclear, ask the customer's accounts contact what needs correcting and where. The examples below are plain-language fictional messages; they are not real portal error codes or universal instructions.
Match the rejection to the right next action
| Message | Check first | Next action |
|---|---|---|
| “File cannot be opened” | Can you open the file? What format is accepted? | Provide the same invoice in the confirmed accepted format |
| “Order not found” | Exact PO, customer entity and order owner | Get the confirmed reference and submission instruction |
| “Amount does not match order” | Invoice lines, agreed scope and order coverage | Ask which figure differs; review with project contact |
| “Duplicate invoice” | Existing portal record and earlier submissions | Ask whether the existing record should continue |
| “Work confirmation missing” | Which line and which confirmation? | Supply the relevant record through the confirmed route |
A file problem can often be resolved without changing the charge. An amount mismatch needs investigation before any amendment. Use your established accounting process for changes to issued documents, following the invoice correction workflow for the accompanying communication.
Ask how to resolve the existing submission
Subject: Invoice [number] — portal rejection [record identifier] Hi [known accounts contact], The submission for invoice [number], [amount], showed this message on [date]: “[exact rejection text]” I have checked [specific source / field]. Could you confirm [the missing reference / exact mismatch / required document] and whether I should update the existing portal record or resubmit it? Please also confirm how the earlier record will be identified so this does not create a second invoice entry. Thanks, [name / business]
Ask for the reference itself when that is the blocker. The missing PO guide helps identify who can provide it. Keep any disagreement about the work or price separate from a technical rejection.
Fictional history: one invoice, a confirmed correction
On 5 November 2026, INV-733 for £960 is rejected under record R-90 with “Order not found”. The owner checks the customer confirmation and finds that the portal field contains PO-281 instead of the confirmed PO-218. The issued invoice already shows PO-218 correctly.
Accounts instructs the owner to correct that field on R-90 and submit it again. The owner records: “6 November: portal PO field corrected to PO-218 following accounts instruction; invoice document, £960 amount and agreed due date unchanged.” The portal then shows “received for review”. That closes the rejection step, not the payment step.
Before resuming reminders, check for a reply or payment and use the current invoice details. If the customer still questions the work or amount, continue the invoice query conversation instead of treating successful submission as resolution.
Keep reading
- Correcting an invoice before sending another follow-up
- Invoice query response template: clarify the issue before chasing
- Customer purchase order missing? Check the invoice process