How to Chase Invoices When a Client Uses a Procurement Portal (Coupa, Ariba, SAP)

You landed a big client. Great. Then their onboarding email arrived: "Please register in our supplier portal and submit all invoices through Coupa." Suddenly you're not invoicing a person anymore — you're feeding documents into a machine, and the machine doesn't answer email.

Figuring out how to chase invoices when a client uses a procurement portal is a different game from chasing a normal late payer. Your friendly reminder emails go to a contact who genuinely can't do anything about it, because accounts payable only looks at what's in the system. Here's how to chase inside the portal, around it, and how to stop invoices getting stuck in the first place.

Why your email reminders bounce off the system

At a company big enough to run Coupa, Ariba, or SAP, the person who hired you doesn't pay you. They approved a purchase order months ago, and from that point on, your invoice lives inside a supplier procurement system that matches it against the PO, routes it for approval, and schedules payment in batch runs.

So when you email your contact "hey, invoice #204 is 20 days overdue," they check the portal, see something, and reply "it's in the system." That's not a brush-off — it's usually all they know. Your reminder didn't fail because of tone or timing. It failed because it was aimed at someone with no lever to pull.

The fix isn't to email harder. It's to find out exactly where in the machine your invoice is stuck, and then aim your chasing at the one thing that unsticks it.

Step 1: Log in and decode the status before you chase anything

Before you send a single reminder, check the invoice status in the portal. Every system uses slightly different labels, but they map to the same handful of states — and each one tells you who to chase:

• Submitted / Received. The system has it but nobody's touched it. If it's been sitting here more than a few business days, something's jammed in the matching step.
• Pending approval. A specific human needs to click a button. This is the most common stall, and it's the one state where your original contact can actually help — by nudging the approver.
• Exception / Disputed / On hold. Something didn't match: wrong PO number, price mismatch, quantity mismatch, or the goods/services were never "receipted" on their end. Nobody will fix this proactively. You have to.
• Rejected. The portal killed your invoice, often silently. As far as their AP team is concerned, you never invoiced them. The overdue clock you're counting? It doesn't exist on their side.
• Approved / Payment scheduled. You're through the maze. Now it's just waiting for the next payment run — check the scheduled pay date and stop chasing until it passes.

That last point matters more than people realize: at most portal-driven companies, your net terms start when the invoice is approved, not when you submitted it. Net 45 from approval on an invoice that sat in "pending" for three weeks is effectively net 66 from your point of view. Run your real numbers through a net terms calculator before you agree to portal terms — the cash flow gap is usually worse than the contract suggests.

The three most common reasons a vendor portal invoice is not paid

If your invoice is stuck in exception, rejected, or eternal-pending, it's almost always one of these:

1. PO problems. No PO number on the invoice, the wrong PO, or a PO that's been fully spent (you invoiced against a PO that only had budget left for part of your amount). Portals hard-fail on this.

2. The receipt was never entered. Most systems do "three-way matching": PO, invoice, and a goods receipt confirming the work was delivered. Your contact often doesn't know that clicking "receive" is their job. Your invoice matches perfectly — and still sits there forever, waiting on a step you can't see and they forgot.

3. Master data mismatches. Your registered supplier name, address, tax ID, or bank details don't match what's on the invoice. One transposed digit and you're in a hold queue nobody monitors.

None of these fix themselves. Each one needs a specific ask, sent to a specific person.

Step 2: Chase inside the portal first

Coupa and Ariba both have comment threads on individual invoices, and those comments actually route to the AP team working the queue — unlike your emails. Use them. A short comment like "Invoice INV-204 has shown 'pending approval' for 15 business days — can you tell me who the current approver is or what's blocking it?" creates a timestamped record inside the system they live in.

Also check for a supplier support channel. Larger companies have a "supplier enablement" or "vendor helpdesk" email specifically for stuck invoices — it's usually buried in the portal footer or your onboarding email. That inbox exists precisely for this, and it's staffed by people whose job is unclogging the queue.

Step 3: Chase around the portal with the right ask

Now email your actual contact — but not with a generic reminder. Give them something they can forward or act on in thirty seconds. Here's the template:

Subject: Invoice INV-204 stuck in Coupa — need a receipt entered

Hi Sam,

Quick one: invoice INV-204 ($4,800, submitted June 3 against PO 7719) is showing as "exception" in Coupa. From what I can see, the goods receipt hasn't been entered on your side, so AP can't release it.

Could you (or whoever handles receipting) confirm receipt against PO 7719? Happy to resubmit anything if needed — just let me know what's missing.

Thanks!

Notice what's doing the work here: the portal's own status, the PO number, and one specific action. You've turned "please pay me" (which they can't do) into "please click this one thing" (which they can). If you want more scripts for each escalation stage, the late payment email toolkit has copy-paste versions from friendly to firm.

If your contact shrugs, escalate to the AP or procurement team directly — ask your contact for the name, or use the supplier helpdesk to ask "who owns exceptions for supplier [your company]?" People act faster when a question has their name on it.

Prevent the next one: your portal pre-flight checklist

Chasing is damage control. For every future invoice into a supplier procurement system, spend five minutes up front:

1. Never start work without a PO number — and check the PO amount covers your full invoice, including any change orders.
2. Confirm who enters the receipt and ask them to do it when you deliver, not when you invoice.
3. Match your invoice to the PO exactly — line descriptions, amounts, currency, entity name. Boring, but exceptions feed on tiny mismatches.
4. Ask when payment runs happen. If they pay on the 15th and 30th, an invoice approved on the 16th waits two weeks no matter what you do.
5. Diarize a portal check 5 business days after submitting. Catching a rejection on day 5 instead of day 40 is the single highest-leverage habit here.

That last step is where most freelancers slip — you assume no news is good news, and the portal assumes silence is fine too. Build the check into your routine the same way you'd systemize the rest of your follow-up (the getting paid checklist is a good skeleton for that), and treat "approved, payment scheduled" as the only status that earns your silence.

Portal clients are annoying to chase, but they're also some of the most reliable payers once an invoice clears the maze — the money is budgeted, the PO exists, and nobody at a Coupa-running company is dodging your calls over $4,800. Learn to chase invoices when a client uses a procurement portal the way the portal wants — status first, specific ask second, human escalation third — and these become your slowest-but-surest invoices instead of your most stressful ones.

And for all your non-portal clients, tools like automated payment reminder software can handle the chasing for you.