Coupa Supplier Portal and SAP: Getting In to Invoice

The work is signed off. There is no dispute, no revision request, nobody unhappy. You log in to send the invoice, and the button that creates one is grey. The tooltip beside it suggests contacting your customer. So you contact your customer — the marketing manager who hired you, who has never opened this system in her life — and she says she will ask someone.

Three weeks later you are still asking.

None of that is a payment problem, which is exactly why it goes unattended for so long. Nobody is refusing to pay you. A record somewhere is missing a field. And the cost of it is quieter than a dispute: net 30 counts from a date the buyer's system stamps on a document, and a document that was never submitted has no date at all, so the clock everyone assumes is running has not started.

Two systems account for most of this. Coupa, whose supplier side is the Coupa Supplier Portal (CSP), and SAP Business Network, which absorbed what suppliers still call Ariba — the supplier login is still supplier.ariba.com. Both are free at freelance volumes. Both will let you create an account in ten minutes that cannot send an invoice. Everything below was read against Coupa's and SAP's own supplier documentation on 22 August 2026, and where a page carries its own revision date I have said so.

Nobody at the software company can pay you

The most useful thing to understand about a supplier portal is whose software it is. It is not a neutral marketplace you have joined. It is your customer's instance, configured by your customer, and almost everything that blocks you is a setting on their side.

Coupa's supplier documentation says this over and over, in the flattest possible language. On submitting invoices at all: "Your account needs to be configured to handle invoices through your customer's Coupa instance. Contact them to get set up with an invoicing method." On the missing blank-invoice button: "contact your customer and ask them to configure your supplier account so that you can submit invoices without a backing PO." On the "unauthorized or expired account" error: "Your customer has probably deactivated a setting on their end." On the generic "Please fix the below error": "Something is wrong on the customer's end... Your customer can open a ticket with Coupa support" (Invoices FAQ, last updated 17 July 2026; account and registration FAQ, last updated 24 April 2026, both read 22 August 2026).

There is a genuine supplier support channel, and it owns a short, specific list: registration where the captcha will not clear, password reset emails that never arrive, being locked out by two-factor authentication. That is supplier@coupa.com. Everything about permissions, records and money runs through the buyer.

Three things have to exist before Submit works

Joining costs nothing: "Coupa doesn't charge suppliers to use the CSP." You get in either from your customer's invitation email or by registering yourself at supplier.coupahost.com. If the invitation never arrived, check spam first, then register — but the documentation attaches a condition that causes trouble later if you skip it: "if you register, make sure to use the same email address to register that your customer used to invite you." A different address gives you a second account, and the buyer's supplier record is pointing at the first one.

Then three objects have to exist before the portal will take an invoice from you.

A legal entity. Coupa's compliant-invoicing guidance puts it plainly: "To send compliant invoices through any channel, you first need to set up a legal entity and an associated payment method in the CSP, which include registering an address. All payment methods exist inside a legal entity" (Setting Up Your Address, last updated 17 July 2026, read 22 August 2026). The name you enter here should match the payee name on the W-9 you already sent, because when the two disagree it is the portal record that accounts payable will believe.

A remit-to address, which lives inside that legal entity rather than in your profile. "If you try to raise an invoice through the CSP or a Supplier Actionable Notifications (SAN), and you have not created any remit-to addresses, you are prompted to add a remit-to address before continuing." The same page adds a line worth reading twice: "Not all your customers may be enabled to use remit-to addresses, but it is generally required on invoices." Enter it once, at onboarding, and leave it alone — the system picks up the latest version of the remit-to address when a payment method is created, and a change mid-engagement is the kind of event treasury teams freeze payment runs over.

A permission that matches how you actually bill. Coupa is explicit that "Buttons are active only for the actions that you can do", and gives the example directly: if your customer did not enable you to create invoices without a backing document, Create Blank Invoice is inactive (Create or Edit an Invoice, last updated 17 July 2026). A retainer with no purchase order behind it fails here, silently, months into a relationship that had been going fine.

One more thing to fix while it is cheap. If the only person on your CSP account has left your company, the documented first move is internal — ask IT for temporary access to that mailbox and reset the password from the portal. Only if the old address is genuinely gone do you ask the customer to update the primary email on their side, then unlink and relink the account; transaction data carries over, but basic company information and payment locations may need re-entering. That is a fortnight you do not want to be spending during an unpaid month.

SAP: registered is not the same as connected

Registering on SAP Business Network takes a few minutes and asks for company name, address and a business contact. It also does not let you invoice anyone. SAP's own training material states the constraint twice, in almost the same words: "Any supplier can register with SAP Business Network. However, a supplier can't obtain a fully-transactional account until at least one buying organization (a 'sponsor') requests and approves a relationship with the supplier" (Exploring Supplier Registration Methods and Trading Relationships, read 22 August 2026).

That link is the trading relationship, and only the buyer creates it. What you can do is finish the profile and hand your contact your network ID — the ANID — because that is what a buyer searches on to find you and send the request. It then arrives in the Customer Relationships section of your account for you to accept.

There are two shortcuts buyers use, and they behave differently. Under quick enablement, the buyer sends a purchase order to a supplier they have no relationship with; the network creates an account holding that document and emails you a trading relationship request with a temporary ID and secure code. If you already have an account, take the Use Existing Account path rather than Create New Account — SAP's description says that migrates both the data and the trading relationship into your existing account, and the alternative leaves you administering two of them. Under light enablement you never register at all: the interactive email itself lets you accept, confirm and invoice the order.

The money question comes up constantly and the answer is usually reassuring. Standard accounts are free and support an unlimited number of documents. An account becomes chargeable only after crossing both thresholds with a single buyer — 5 documents and $50,000 of qualifying volume in a rolling 12-month lookback — and then, SAP notes, every relationship on that account becomes chargeable, not just the one that crossed. The fee has two parts: a transaction fee billed quarterly at 0.155% or 0.35% of the transacted volume, and a subscription fee billed annually against the previous year's document count (Discussing SAP Business Network Supplier Fees, read 22 August 2026). Which of the two rates applies is not a negotiation: 0.35 per cent where the relationship uses service entry sheets, 0.155 per cent everywhere else, capped at $20,000 a year per buyer relationship — a cap SAP notes takes roughly $12.9 million of volume to reach.

Two details matter more than the rates. Non-PO invoices always count towards qualifying volume, which matters if that is how you bill. And a US-based supplier who is over the threshold can still be exempt from transaction fees — when the buyer is a public sector body or a 501(c)(3), or when the supplier is certified small disadvantaged, woman-owned, minority-owned or veteran-owned.

Note what you do not control. SAP's lesson on account types says a supplier's account "will be automatically be switched to enterprise once they are sent their first non-standard trading relationship", and that an invitation to register which carries a non-standard relationship request does the same thing (Categorizing the Supplier Account Types, read 22 August 2026). Your account type is decided by the shape of the buyer's invitation, not by a choice you made. Being on an enterprise account is not itself a bill — the thresholds are — but it is worth knowing why the label changed without you touching anything.

Flipping a PO, and the invoice with no PO behind it

In Coupa the ordinary route runs through the Orders tab: find the PO, click the gold coin icon, pick your legal entity and remit-to, then fill the mandatory fields marked with a red asterisk, most of which arrive pre-filled from the order. Depending on your customer's settings you may have to accept the PO first, and accepting it fixes what you can then type: unit of measure and price come from the PO line and cannot be changed, while quantity and amount can only run from zero up to what is left on that line. You can invoice a single PO more than once — enter the amount you want to appear on this invoice — which is how milestone billing survives a portal. Credit notes work through the red coin icon or a negative quantity, and can only be created against invoices in Disputed or Approved status.

Without a PO you need one of two permissions: Create Blank Invoice, or Create Invoice from Contract if the buyer routes non-PO spend through contracts. If neither button is live, that is the email in the last section of this page rather than a support ticket.

Two alternatives are worth asking for by name. Supplier Actionable Notifications let you acknowledge, comment on and invoice a purchase order straight from the notification email "without the need to join Coupa's supplier network or create a Coupa Supplier Portal (CSP) account", and you still get follow-up notifications when the customer acts on what you sent (SAN documentation, last updated 17 July 2026). For a client you will invoice twice in your life, that is the whole solution. Separately, you can attach your own PDF to a portal invoice as an image scan — PNG, GIF, JPG, JPEG, PJPEG, TIFF or PDF, up to 100 MB, though Coupa suggests staying nearer 16 MB. Emailing the PDF to the client instead means somebody rekeys it by hand, which the documentation says "may cause a delay in payment".

SAP's flow starts from the Process Order button in the interactive email, which opens the order with Confirm Line Items, Send Ship Notice and Create Invoice. The design detail worth internalising is where the buyer's rules bite: SAP describes customer-specific invoice rules being enacted automatically as you build the invoice online, in real time, matched against the PO header and lines, and says the only way to reach the second screen of the invoice creation wizard and submit it to the customer is if all customer validation rules are met (same account-types lesson). So the two systems fail at opposite ends. SAP tends to stop you mid-wizard. Coupa tends to accept the invoice and hand it back later with a status on it.

Before you press Submit anywhere, read the remit-to line and the invoice number one more time, because that is the last moment either is editable. Coupa states it without qualification: once an invoice is submitted it cannot be changed in any way, and you can edit or delete only draft invoices.

Five status words that mean five different jobs

Portal statuses look like progress reporting. They are closer to instructions, and each one points at a different person (View and Manage Invoices, last updated 17 July 2026, read 22 August 2026).

• Draft. Created, never submitted. Nobody has seen it. This is the one that quietly eats a month, because in your own list it sits next to invoices that really did go out.
• Pending Approval, then Processing. With the customer, then with accounts payable. Nothing for you to do but note the date it moved.
• Disputed. Your customer disagrees with something, and the notification email carries the reason. Payment stops until it is resolved. From a standard e-invoice you get Void — for a duplicate or something already paid — or Correct Invoice, which may reuse the same number. For a country compliant e-invoice you cancel with a credit note and issue a corrected one, and Coupa is emphatic that the corrected invoice must have a new number.
• Voided or Abandoned. Voided means something is wrong with the invoice, and the documentation sends you to the customer to get it back on track. Abandoned means a disputed invoice has been abandoned — the customer can choose to notify you of that change and attach instructions, and there is a notification preference for this status specifically. Turn it on. If the status arrives without instructions, that absence is the thing to write about.
• Tolerance Hold or Pending Receipt. Neither is about your paperwork. Tolerance hold means the invoiced amount differs from the PO by more than the buyer allows without manual approval. Pending receipt means the customer has not yet entered the receipt that the invoice gets matched against. For services that is one person on the buyer's side clicking one button, which is why it can sit for weeks without anyone believing anything is wrong.

Two small mercies. If a customer deletes an invoice number on their side, you can reuse it. And a rejected invoice is not an appeal you have to win: create a new one to replace it.

The email that moves it, and who it goes to

The reason these stalls run for weeks is that one message goes to one person who cannot act on it. There are three different people behind a portal and they own different failures. The person who hired you holds the purchase order number and can click the receipt. Accounts payable knows where a submitted invoice sits and when the payment run is. Procurement, or a supplier enablement team, is the only group that can change what your account is allowed to do.

Write to the right one, and put the whole file in the first message so nobody has to come back for it: your legal entity name exactly as registered, the email address on the portal account, your ANID or CSP login address, the PO number if there is one, the invoice number, date, amount and currency, and the literal text on screen, quoted. Then close with a question that has a small number of answers. Which of these do you need me to change — the remit-to, the legal entity name, or the permission to invoice without a PO? An open question about why it is not working produces a reply in nine days. A closed one produces a reply the same afternoon, because answering it is faster than thinking about it.

And ask earlier than feels necessary. Two questions at kickoff, before any of it is urgent: which portal do you invoice through, and am I set up to invoice with or without a purchase order. Both take your client half a minute to find out and can take procurement a fortnight to act on. If the answers have not arrived by the time you deliver, treat that as a signal in its own right and read the first step of a collections process with the portal in mind — because an invoice that was never accepted is not a late payment yet. It is a document that does not exist.