You’ve raised the invoice in Xero and emailed it. Then accounts payable replies: please submit it through our supplier portal. Until it’s in Coupa or SAP Ariba against the right purchase order, your invoice doesn’t exist as far as their payment run is concerned.

For a supplier with one or two big customers, that means another login, a PO to find and the same invoice typed in twice. Miss a field and it bounces back, often without anyone telling you until the due date has gone.

Here’s what Coupa and SAP Ariba invoice upload actually involves, what you can automate today and the parts that still need a person.

Why large customers make suppliers use Coupa and SAP Ariba

Large buyers use procurement systems to check that every invoice matches an approved purchase order before they pay it. Coupa and SAP Ariba are two of the most common.

The rule for you is simple. If the invoice isn’t in their system against the right PO, it won’t be paid. PwC UK, for example, tells its suppliers that once they’re on the Coupa Supplier Portal they must only invoice by “flipping” the purchase order in the portal, and emailed invoices are no longer accepted.

What Coupa and SAP Ariba need from you

Coupa Supplier PortalSAP Business Network (Ariba)
Cost to youFree. Coupa doesn’t charge suppliers to use its portal (Suez supplier FAQ)A standard account is free. An enterprise account becomes chargeable once you pass 5 documents and $50,000 with one buyer in a rolling 12 months (SAP)
How you invoiceOpen the PO in the portal and turn it into an invoice, then attach your own PDFCreate the invoice against the PO on the network. A standard account can send unlimited POs and invoices (SAP)
Purchase orderUsually required. “You can’t submit invoices without a backing PO” (Suez)Usually required, but each buyer sets its own rules
TrackingThe Invoices menu shows progress, comments and payments (PwC)Status shows in your account and in the buyer’s email notifications

The takeaway: the portals themselves are usually free for a small supplier. The cost is your time, and the days lost when an invoice sits outside the system.

Why Coupa and SAP Ariba invoices get rejected or stuck

Most rejections come from a handful of avoidable gaps:

  • No PO, or the wrong one. No PO usually means no invoice at all. It’s the same no PO, no pay rule as for emailed invoices.
  • Invoice number doesn’t match your books. PwC asks suppliers to use the same invoice number as their own system, so you can track payment.
  • Missing bank details. Some buyers, like Macquarie, require remittance bank details on every electronic invoice.
  • Amounts outside tolerance. If the invoice doesn’t match the PO closely enough, Coupa puts it on hold (Monk).
  • Missing codes or the wrong format. GL codes, PO number formats and VAT lines vary by buyer.

Check these five before you press submit and you’ll avoid most of the back-and-forth.

What you can automate in Coupa and SAP Ariba invoicing

Getting the PO before you invoice. This is where most portal delays start. If you ask for the PO only when the invoice is due, you’ve already lost a week. We’ve written a full guide to getting the PO number before the invoice falls due.

Status tracking. Coupa and Ariba both send email notifications when an invoice is approved, disputed or paid. Route those to one shared inbox so nobody has to log in to check.

Full submission. A few AR platforms now log in and submit for you. Tesorio says its agent matches invoices to POs, checks them and submits to Coupa and Ariba, and Tabs submits to selected portals. Both are built for larger, mostly US finance teams.

Chasing after submission. An approved invoice can still miss a payment run. A reminder to the right AP contact a few days before the due date, from your own email address, is often what moves it.

What still needs a person when you invoice through Coupa or SAP Ariba

Some of this doesn’t automate well yet, whichever tool you use:

  • Registering with each new buyer’s portal and adding your bank details the first time.
  • Splitting a PO across partial invoices, such as monthly billing against an annual PO.
  • Answering a dispute or a query left as a comment in the portal.
  • Deciding whether to accept a buyer’s request to move you to a paid account tier.

How Trove helps you get paid on Coupa and SAP Ariba invoices

Trove doesn’t upload invoices into Coupa or SAP Ariba. What it does is the work either side of the portal. Its AI spots when a customer needs a PO, drafts the email to the right person and adds the PO to the invoice in Xero as soon as it arrives. Then it sends pre-due reminders from your own email address to whichever contact holds the purse strings. When accounts payable replies with a payment date, Trove logs it against the invoice and drafts the response. Here’s how it compares with other credit control for larger customers.

We’re looking at portal uploads next. If your customers make you use Coupa, SAP Ariba or another portal, book a demo and tell us which ones.

Try Trove free for 30 days

Trove runs a free 30-day trial and takes about 15 minutes to connect to your Xero account. You can start a free trial here or book a demo if you’d like to see it first.