Why Client Portals Reject Your Invoice PDF (and Fixes)

Most portal invoice rejections come from one of two things: the file the system could not read, or the data it read and did not like. Here is how to tell them apart and fix each.

You uploaded the invoice, the client’s portal spun for a second, and then it threw the invoice back at you with a vague error. It is one of the more maddening parts of getting paid by a bigger company, because the work is done and the money is just sitting behind a validation rule. The upside: portals like Coupa and SAP Ariba reject invoices for a short, predictable list of reasons, and almost all of them are fixable in a few minutes once you know which one you hit.

Bottom Line First

An invoice PDF gets rejected for one of two reasons. Either the portal could not read the file, which points to a password, a huge file, or a scanned image with no text layer, or it read the file fine and rejected the content, which points to a missing or wrong purchase-order number, a duplicate invoice number, or totals that do not match the PO. Figure out which bucket you are in first, because the fixes are completely different.

First, read the rejection like a clue

The error message usually tells you which bucket you are in, even when it is worded badly. Anything about “unreadable file,” “cannot process,” “invalid format,” or “file too large” is a file problem. Anything naming a field, a PO, an amount, a tax line, or a duplicate is a data problem. Screenshot the exact message before you do anything, because portals often let you resubmit only a limited number of times before they lock the invoice for manual review.

Data and PO problems: the portal read it and said no

Large buyers route invoices through automated matching, so your PDF is checked against the purchase order line by line. If anything is off, it bounces. The usual offenders:

• Missing or wrong PO number. The PO has to appear on the invoice and match exactly, including any prefix. Most portals will not accept a non-PO invoice at all.
• Totals that do not match the PO. A price, quantity, tax line, or currency that differs from the PO triggers a mismatch, which is the core of how invoice reconciliation works.
• Duplicate invoice number. Reusing a number from a prior or rejected invoice fails. Add a suffix like -A or -2 to make it unique.
• An expired or fully billed PO. If the PO is closed or past its validity date, ask your client’s accounts-payable contact to reopen or reissue it.

The fix here is never technical. You correct the number, the total, or the PO reference on the invoice itself, then resubmit. If the PO is the problem, the ball is in your client’s court, so email their AP contact rather than resubmitting the same thing five times.

File and format problems: the portal could not read it

These are the sneaky ones, because your invoice looks perfect when you open it. The portal’s ingestion engine, though, needs machine-readable text and a clean file. Common blockers:

• Password protection or encryption. Even a light “open” password stops automated processing. Remove it and re-export.
• A scanned image with no text layer. If you printed and scanned the invoice, it is a picture. Run it through OCR or, better, export a fresh PDF straight from your invoicing tool so the text is selectable.
• File too large. Many portals cap uploads around 10 MB. Flatten the PDF and compress images to shrink it.
• Odd fonts or multiple invoices in one file. Non-embedded fonts break text extraction, and portals expect one invoice per file, not a batch.

My rule of thumb: never scan a printed invoice for a portal. Export the PDF directly from the software that made it, so the text is real and the file is small.

The 6-step fix before you resubmit

Run this sequence and you will clear the vast majority of rejections on the next try.

1. Read the error and decide: file problem or data problem.
2. Confirm the PO number is on the invoice and matches exactly.
3. Check that totals, tax, and currency match the PO down to the cent.
4. Make the invoice number unique if you have submitted before.
5. Re-export a fresh PDF, no password, text selectable, one invoice, under the size cap.
6. Name the file clearly, often the invoice number, and upload again.

How to stop it happening next time

Getting rejected once is normal. Getting rejected on every invoice to the same client means you have not matched their spec yet. Ask their accounts-payable team for the portal’s requirements up front, since each platform enforces its own, and modern accounts-payable systems are strict by design. Save a portal-ready template with the right fields, keep the PO number on file with the project, and export the same clean way every time. For choosing tools that play well with these portals, our guide to what billing software must do is a useful starting point.

What To Know

• Portal rejections split into file problems and data problems, and the fixes are different.
• A missing or mismatched PO number is the single most common data rejection.
• Passwords, oversized files, and scanned image PDFs are the most common file rejections.
• Export a fresh PDF from your invoicing tool instead of scanning a printed copy.

Frequently Asked Questions

Why does the portal say my invoice PDF is invalid when it opens fine?

Opening fine and being machine-readable are different things. The portal’s ingestion engine may be blocked by a password, a scanned image with no text layer, an oversized file, or non-embedded fonts. Re-export a clean, text-based PDF from your invoicing software.

Do I have to include a PO number on every invoice?

For most large-buyer portals, yes. PO-based portals like Coupa and SAP Ariba match each invoice to a purchase order, and a missing or mismatched PO is a top rejection reason. If you were not given a PO, request one from your client before invoicing.

How do I fix a duplicate invoice number error?

Make the number unique. If you already submitted invoice 1043 and it was rejected, resubmit as 1043-A or 1043-2. Portals block exact reuse of a number that already exists in their system.

What file size and format do AP portals want?

A text-based PDF, one invoice per file, usually under about 10 MB, with no password. Some portals also accept or prefer structured formats like cXML, but a clean PDF is the safe default when you are unsure.

The portal locked my invoice after several tries. What now?

Stop resubmitting and contact the client’s accounts-payable team directly. After a set number of failures, portals route the invoice to manual review, and a person on their end can release or correct it faster than another upload.

What To Do Next

Open the rejection message, sort it into a file problem or a data problem, and work the six-step fix in order. If the block is a PO that is closed or missing, that is a client-side fix, so email their AP contact instead of resubmitting. For more practical operations and billing guidance, browse Visboo’s Business section.