The slowest way to get paid is to get rejected. More buyers now take invoices only through an accounts-payable portal that checks your submission against their records the instant you send it, and a single wrong field, a PO that does not match, a duplicate number, a tax line in the wrong place, sends the whole invoice bouncing back to you. The frustrating part is that the work was fine; the template was not. Fix the template once and your invoices stop getting kicked out, which is often the difference between getting paid this cycle and waiting for the next one. Here are the seven mistakes that trigger those automatic rejections, and the fix for each.
None of these is exotic. They are the small, repeatable formatting errors that a human might overlook but an automated validation engine never does. Get them right on your template and you stop fighting the portal on every send.
Why portal-first AP rejects invoices automatically
Traditional invoicing forgave a lot, because a person read the invoice and filled in the gaps. Portal-first accounts payable does not. When you submit through a buyer’s portal, an automated engine checks your invoice against their purchase order and vendor records in the same second, and anything that does not line up is rejected back to you without a human ever seeing it. That is faster for everyone when the invoice is clean, and a brick wall when it is not. The rejections below are not the portal being difficult; they are specific fields failing a specific check, which is also why each one has a clear fix.
The seven mistakes at a glance
| Mistake | Why the portal flags it | The fix |
|---|---|---|
| Wrong or missing PO number | No PO to match against | Use the buyer’s exact PO on every invoice |
| Line items that don’t match the PO | Three-way match fails | Mirror the PO’s items, quantities, and prices |
| Totals that don’t reconcile | Math check fails | Make lines, subtotal, tax, and total agree |
| Tax entered as a lump | Tax fields not structured | List tax rate and amount as their own fields |
| Reused or blank invoice number | Duplicate detection | Give every invoice a unique number |
| Remit-to or bank details off | Not on the vendor record | Match the details the buyer has on file |
| Missing or unreadable attachment | Required document absent | Attach the right file in the required format |
1. A wrong or missing purchase order number
This is the single biggest cause of portal rejections, because the PO number is the key the whole system matches on. If your invoice has no PO, the wrong one, or one with a typo, the portal has nothing to match it against and bounces it immediately. Put the buyer’s exact purchase order number on the invoice, in the field the portal expects, for every submission. If a job has no PO, ask for one before you invoice rather than sending it blank, since many portals will not accept a non-PO invoice at all without a separate process.
2. Line items that do not match the purchase order
Even with the right PO, the portal compares your line items to it, a check often called three-way matching. If your descriptions, quantities, unit prices, or units of measure differ from the PO, or you bill more than the PO authorized, the match fails and the invoice is held. Build each invoice to mirror the PO: the same items in the same terms, at the agreed prices, within the approved amounts. If the work genuinely changed, get the PO amended first, because billing over it will stop the payment rather than stretch the order.
3. Totals that do not reconcile
Portals check the arithmetic, so an invoice whose numbers do not add up is an easy reject. If your line items do not sum to the subtotal, or the subtotal plus tax does not equal the grand total, the validation fails even when every individual number looks reasonable. Rounding errors are a common culprit. Before you submit, confirm the lines add to the subtotal, the tax is calculated on the right base, and everything rolls up to a total that matches to the cent, so the portal’s math check and yours agree.
4. Tax entered as a lump instead of structured fields
Burying tax inside a single total is a quiet rejection trigger. Validation engines expect tax as its own structured data, the rate and the amount in their proper fields, and often a valid tax identifier, rather than a figure folded into the grand total. If your template shows tax only as part of one number, the portal cannot verify it and may reject the invoice as non-compliant. Break tax out explicitly: show the taxable base, the rate, and the tax amount as separate line entries, and include the tax registration details the buyer’s system requires.
5. A reused or blank invoice number
Every invoice you send a buyer needs its own unique number, and portals enforce this to prevent paying the same bill twice. Reuse a number, leave it blank, or send a corrected copy under the old number, and the portal’s duplicate detection flags it and holds it. Use a clear, sequential numbering system with no gaps or repeats, and when you revise an invoice, issue it under a new number and reference the old one rather than resending the same identifier. That keeps each submission unique and clears the duplicate check cleanly.
6. Remit-to and bank details that do not match the record
The buyer pays the details on file, not the ones you typed today, so a mismatch stalls the payment and can trip a fraud check. If the remit-to name, address, or bank information on your invoice does not match what the buyer has in their vendor record, the portal holds it for verification, which is slow and sometimes treated as a security concern. Keep your invoice’s payment details identical to what the buyer has on file, and if your bank or address genuinely changed, update it through the buyer’s vendor-maintenance process first, before you send an invoice with the new details.
7. A missing or unreadable attachment, or the wrong format
Many portals require supporting documents, a signed timesheet, a delivery note, a receipt, or the invoice image itself, and will not process the submission without them. Others need a specific file type or a machine-readable format rather than a flat scan. Submit a blurry photo, the wrong file, or leave a required attachment off, and the invoice stalls. Check exactly what the portal asks for, attach clean, readable files, and where the buyer uses structured electronic invoicing rather than a PDF, send the format their system expects.
Portal rules vary by buyer and by the accounts-payable system they use, and validation requirements change, so treat this as general guidance and confirm the specific field, format, and document rules in your buyer’s supplier portal or onboarding guide before you submit.
How We Chose These
We focused on template-level mistakes, the ones baked into how your invoice is built, rather than one-off data entry slips, because those are what you can fix once and stop repeating. We prioritized the errors that automated portal validation catches most often, drawing on the common rejection reasons buyers and AP systems cite: purchase-order and line-item matching, arithmetic and tax structure, unique numbering, remit-to verification, and required documents. For each, we paired the reason the portal flags it with a concrete change to your template, since the goal is fewer rejections, not just a list of ways to fail.
What To Know
- Portal-first accounts payable validates every field the moment you submit, so one wrong detail rejects the whole invoice automatically.
- A wrong or missing PO number and line items that do not match the PO are the most common causes of rejection.
- Totals must reconcile to the cent, and tax has to appear as structured fields, not folded into one number.
- Every invoice needs a unique number, and the remit-to and bank details must match the buyer’s vendor record.
- Attach the exact documents and file format the portal requires, and confirm each buyer’s specific rules before submitting.
Frequently Asked Questions
Why does the portal keep rejecting my invoice?
Because one field is failing an automatic check. The most common cause is a purchase-order problem, either a wrong or missing PO number or line items that do not match the PO. Other frequent triggers are totals that do not add up, tax entered as a lump rather than structured fields, a reused invoice number, remit-to details that do not match the buyer’s record, or a missing required attachment. Fix the specific field the rejection names and resubmit.
What is three-way matching and why does it reject my invoice?
Three-way matching is when the portal compares your invoice to the purchase order and the record of goods or services received. If the items, quantities, or prices on your invoice do not match the PO, or you bill more than it authorized, the match fails and the invoice is held. Build each invoice to mirror the PO exactly, and if the scope changed, have the PO amended before you bill so the three sources line up.
Do I need a PO number on every invoice?
For PO-based buyers, yes. The PO number is the key the portal uses to match your invoice, so without it, or with the wrong one, there is nothing to reconcile against and the invoice bounces. If a particular job has no PO, ask the buyer for one before invoicing, since many portals will not accept a non-PO invoice without a separate approval route. Putting the correct PO in the expected field is the single most effective way to avoid rejection.
Why is my invoice held over bank or remit-to details?
Because the buyer pays the details in their vendor record, not the ones on a new invoice. If your remit-to name, address, or bank information does not match what they have on file, the portal holds the invoice for verification and may treat the change as a security risk. If your details genuinely changed, update them through the buyer’s vendor-maintenance process first, then send invoices that match the updated record.
How can I get invoices paid faster through a portal?
Get the template right so the automatic checks pass on the first submission. Use the exact PO number, mirror its line items and amounts, make sure the totals reconcile, break out tax into structured fields, give each invoice a unique number, match the remit-to and bank details on file, and attach the required documents in the right format. Clearing validation on the first try is what gets you into the payment run instead of back in your inbox.
What To Do Next
Audit your invoice template against these seven checks before your next send, starting with the PO number and line-item match, since those cause the most rejections. Save a portal-ready version so every invoice goes out compliant. For the specific case of a document bouncing back, see our guide to an invoice PDF rejected by a client portal, and the business section has more on getting paid on time.