Portals 101: Ariba/Coupa basics for SaaS vendors

Procurement portals are where invoices go to… take a long reflective walk.

Jokes aside, portals (Ariba, Coupa, and friends) are a normal part of mid-market and enterprise buying. If you sell SaaS B2B, you will meet them. The question is whether you treat them as a one-off nuisance, or as an operating system you can run calmly.

This guide explains the basics in plain English, plus a workflow you can use the next time a customer says: “Please submit through Ariba/Coupa.”

What “portals” really are (and why they slow payment)

A portal is the buyer’s control point. It sits between “you sent an invoice” and “AP can pay it”.

Portals exist to help buyers:

• onboard suppliers,
• route approvals,
• match POs to invoices,
• enforce invoice rules,
• track status.

That is useful for them. It can be slow for you if nobody owns the workflow.

The key mindset shift:

• reminders do not fix portal blockers,
• workflow does.

Ariba vs Coupa in plain terms

SAP Ariba / SAP Business Network basics

Ariba is typically accessed via SAP’s supplier network (often referred to as Ariba Network / SAP Business Network). Suppliers usually register, then connect to the customer as a trading partner. SAP’s own support guidance describes registration confirmation and then establishing the trading relationship (including sharing your Business Network ID/ANID and accepting a relationship request). 

Once connected, invoices are often created from purchase orders or submitted using the portal invoice flow. SAP Ariba Support also provides step-by-step guidance on submitting invoices and what you can add (terms, comments, attachments) before submitting. 

What this means for SaaS vendors:

• you often need an invitation or relationship request to transact,
• the PO (if used) drives what you can invoice and how it gets approved.

Coupa Supplier Portal basics

Coupa’s supplier side is the Coupa Supplier Portal (CSP). Coupa describes CSP as a free tool for suppliers to manage interactions with customers using Coupa. 

On invoicing, Coupa’s own supplier docs describe creating invoices directly from purchase orders in CSP as a key method. 

Many buyers also use “flip PO to invoice” workflows (you invoice against what they issued).

What this means for SaaS vendors:

• Coupa often expects invoice creation against a PO (where POs exist),
• invoice rules (like uniqueness) can be strict depending on the buyer’s configuration. 

The four portal gates that delay SaaS cash

Most “portal problems” are one of these:

1. Onboarding not complete Vendor forms, bank details, tax info, contact emails, sometimes questionnaires. (Coupa onboarding flows often start with buyer-initiated requests and supplier update forms.) 
2. Not connected to the right customer account You registered an account, but you are not linked to this buyer’s tenant, or the relationship request is still pending. (Ariba calls out accepting the customer relationship request to begin transacting.) 
3. PO mismatch Invoice does not match PO terms (amount, line items, service period, entity, or the PO simply does not exist).
4. Status drift Invoice submitted, then nobody checks whether it was approved, rejected, or stuck waiting for action. In Coupa and Ariba, invoice status is visible, but someone must actually look. (Coupa and Ariba supplier docs emphasise transacting and tracking via the portal.) 

The BSB way (high level): tag the reply, run the workflow, push blockers

When a customer replies “Submit via Ariba/Coupa”, we do not treat it as “late payment”.

We treat it as a workflow tag:

• Portal/Onboarding (or Missing PO if that’s the real blocker)

Then we:

• run the portal steps,
• read every reply,
• push any internal blocker to your team with a clear ask and deadline.

That is how you stay customer-friendly while moving cash.

Step-by-step: what to do when a customer says “submit via Ariba/Coupa”

Step 1 — confirm the route (PO flip vs non-PO invoice)

Send one short question set to avoid wasted effort:

• “Do you require a PO for this invoice?”
• “Should we create the invoice from the PO in the portal, or submit a non-PO invoice?”
• “Which entity and remit-to details should we use?”

Why: in Coupa, invoicing directly from a PO is a common path. 

Step 2 — get invited and connected (don’t DIY the wrong account)

For Ariba:

• confirm whether the buyer will send a relationship request,
• confirm what identifier they need (they may ask for your network ID/ANID), and accept the request. 

For Coupa:

• confirm whether they will invite you to CSP or connect you to their instance,
• confirm the supplier email that will receive notifications. 

Practical tip: create one shared “portal@yourcompany.com” mailbox for supplier portals so access does not vanish when someone changes roles.

Step 3 — submit the invoice correctly (and track status)

For Ariba:

• follow the portal invoice submission flow and review before submitting. 
• attach supporting docs only if the buyer requires them (SOW, timesheets, acceptance).

For Coupa:

• if a PO exists, create the invoice from the PO inside CSP (this reduces mismatch risk). 
• keep invoice numbers unique. Some buyer guidance notes Coupa may prevent reuse of invoice numbers. 

Set a rule internally:

• every portal submission gets a follow-up date and a status check.

Set a rule internally:

• every portal submission gets a follow-up date and a status check.

Step 4 — close the loop (approval, remittance, follow-up date)

Do not end at “submitted”.

Close the loop with:

• “Submitted on [date]. Current status: [e.g., pending approval]. Next check: [date].”
• ask for remittance advice if the buyer provides it,
• if rejected, respond within one business day and resubmit.

Checklist/table: your portal pack (owners, artefacts, SLAs)

Item	Why it matters	Owner	SLA	Where you store it
Portal inbox (shared)	Avoids lost access	Ops/Finance	Set once	Shared mailbox
Company legal entity details	Prevents onboarding loops	Finance	Same day	Portal pack folder
VAT/tax IDs + addresses	Prevents rejection	Finance	Same day	Portal pack folder
Bank details + remittance email	Enables payment setup	Finance	1–2 days	Secure vault
Standard invoice PDF template	Match buyer requirements	Finance/RevOps	Same day	Billing system
SOW/Order form library	Resolves “proof” requests	CS/Sales Ops	1–2 days	Contract repository
Service period wording standard	Helps PO match	RevOps	Same day	Invoice template notes
Tag + tracker (Portal/Onboarding)	Stops drift	AR owner	Same day	AR tracker / tickets
Status check cadence	Catches rejections early	AR owner	Weekly minimum	AR tracker

If you do one thing this week, build the portal pack folder and assign an owner.

Email snippet: get the portal details you need (fast, polite)

Subject: Quick details so we can submit in Ariba/Coupa today

Hi [Name],

No problem. We can submit this invoice via your portal.

Could you confirm:

1. Should we invoice against a PO (and if so, the PO number)?
2. Which portal route you prefer (Ariba/Coupa Supplier Portal link or invitation)?
3. Any invoice rules we should follow (attachments, remit-to, service period format)?

Once we have this, we’ll submit today and share the submission reference.

Thanks,

BSB AR Team (on behalf of [Your Company])

Short questions. Clear “done” outcome.

Metrics that matter

Track these weekly:

• Value of invoices tagged Portal/Onboarding
• Average days from “portal request” to “invoice submitted”
• Rejection rate (count and reasons)
• Oldest portal blocker and owner
• Over-30-day AR % excluding portal-blocked vs including portal-blocked (it shows true drag)

Common mistakes (and quick fixes)

• Mistake: treating portal work as “small admin” Fix: track it like a workflow with owners and dates.
• Mistake: registering an account but not connecting to the buyer Fix: confirm relationship/connection steps. Ariba explicitly references accepting the customer relationship request before transacting. 
• Mistake: sending reminders while the invoice is rejected in the portal Fix: check status first. Then act.
• Mistake: invoicing without a PO when the portal expects PO-based invoicing Fix: confirm whether you should invoice from the PO (common in Coupa CSP docs). 

---

If portals keep dragging invoices into next month, we can run the workflow for you.

We plug into your tools, read every reply, tag the reason, and push blockers to your team so cash keeps moving. If a buyer needs a portal step or onboarding, we see it early and handle the workflow.

Read “AR + Portals & Onboarding” (and “Managed AR Ops”) on services. If you want to talk it through, Book a call via contact.

---

Compliance & clarity: This post shares general operational guidance. It is not legal, tax, or accounting advice. Examples are illustrative and include no private client data.