Getting orders out of customer portals (Coupa, Ariba) and into your ERP

The new chore: logging in to pick up orders

It usually starts with a letter from a big customer. Purchasing is moving to Coupa, or to SAP Ariba. Please register as a supplier. From now on, POs will be in the portal.

So someone on your team registers. Then a new routine begins. They log in, find the new PO, read it, and type it into your ERP. Then they log into the next customer's portal and do it again. Later they go back in to confirm the order, send a ship notice, or flip the PO into an invoice.

The odd part is that the order was already digital. Your customer's buyer typed it into a system. Now your person reads it off a screen and types it again. This guide covers what Coupa and SAP actually offer suppliers, using their own help and training pages as checked on Oct. 22, 2026, and four ways to stop the retyping.

What Coupa says about its supplier portal

Coupa's help site says the Coupa Supplier Portal is a free tool for suppliers. The same page says you can receive POs from Coupa customers three ways: through the portal, through cXML, or by email.

Coupa's purchase orders page is frank about who each method is for:

• The portal is "ideal for suppliers with low to medium volume" of POs and invoices, or who want all their Coupa customers in one place.
• cXML is for suppliers with a high volume of POs, or those who automate their PO handling.
• Email is for suppliers who lack the volume or resources to justify an automated setup.

Three details matter for a mid-size supplier.

• Each customer sets the rules. Coupa says that, depending on each customer's configuration, suppliers manage things customer by customer, including viewing POs and choosing delivery methods. Its orders FAQ adds that you only see a customer's POs if that customer has linked them to your portal account.
• You can export. The portal's PO list can be exported as a CSV or Excel file. That's a cleaner starting point than reading the screen.
• cXML goes through your customer. To get POs by cXML, Coupa says you fill out a cXML supplier questionnaire and give it to your customer, then test the connection with them.

Invoices work the same way. If a customer invoices through Coupa, Coupa says you can send invoices through the portal, cXML, actionable email notifications, or email/PDF. But its invoices page also says invoicing is optional in Coupa, so not every Coupa customer uses it, and that emailed invoices may not be allowed by every company. Check with each customer first. The portal can "flip" a PO into an invoice, and Coupa offers an invoice sync with QuickBooks Online and NetSuite. That sync covers invoices, not incoming POs.

The order was already digital. Retyping it is pure waste.

What SAP says about Ariba for suppliers

SAP now calls the Ariba Network the SAP Business Network. SAP's main supplier pricing page blocked our request, so the facts below come from SAP's own support and training pages.

• Standard accounts are free. SAP's support site says standard accounts are free, and SAP's training course says the standard level lets suppliers transact an unlimited number of documents such as POs and invoices.
• Enterprise accounts can become paid. An enterprise account costs nothing at first. SAP's support page says fees start once a supplier passes 5 documents and more than $50,000 in at least one customer relationship. The training course adds that once one relationship is chargeable, all of them are.
• The fees. SAP's course describes a yearly subscription fee plus a quarterly transaction fee of 0.155% or 0.35% of transacted volume, capped at $20,000 per trading relationship. We didn't find the subscription tiers on an SAP page we could open, so we leave them out.
• What you get for paying. The same course lists dedicated inboxes, reporting and direct integration to your ERP among the enterprise features.
• How POs reach you. SAP's supplier help says you can pick a routing method for each document type: online, email, fax, cXML or EDI. It also allows customer-specific routing.
• Invoices. Suppliers can create a PO-based invoice with a PO flip, which copies the PO data into the invoice.

The fee rules have changed over the years, and your contract with each customer may differ. Read your own account terms before you plan around any of this.

A word on cXML

Both portals keep coming back to cXML. According to cxml.org, it's a protocol for sending business documents between procurement systems, e-commerce hubs and suppliers. It covers orders, order confirmations, ship notices and invoices, much like EDI does. Ariba announced it in 1999, and Ariba is now part of SAP.

For you, cXML means the PO arrives as a structured file your systems can read with no typing at all. The catch is that someone has to build and test that connection to your ERP, and your customer has to agree to it.

Four ways to get portal orders into your ERP

Most mid-size suppliers end up with a mix. cXML or EDI for the one or two biggest portal customers. Email delivery plus automated intake for everyone else. And the same checks on every order, no matter which door it came through.

What automated intake looks like

If a customer's portal can email you the PO, the job looks a lot like any other emailed order.

1. Catch the PO. The portal's PO email lands in an order inbox. Software picks it up.
2. Read it. It pulls the PO number, ship-to, lines, quantities, prices and dates, whether the layout is Coupa's, SAP's, or a customer's own.
3. Match it. It finds the customer and ship-to in your ERP, maps the customer's part numbers to yours, and checks prices against your price list or contract.
4. Flag what doesn't fit. A new ship-to, a price that's off, or a PO number already entered gets flagged for a person, not guessed.
5. Draft for approval. Your person sees the draft next to the original PO and approves it. Then it goes into the ERP.

The portal steps that need judgment stay with a person: accepting or commenting on a PO, confirming dates, and anything the customer's rules require you to do inside the portal.

Where the other side has a point

• Low volume is fine as is. Coupa itself says the portal is ideal for low to medium volume. If you get a few portal orders a month, retyping them may cost less than any project.
• The customer decides. Coupa's cXML setup runs through the customer, and some customers won't allow email delivery or emailed invoices. You can only automate the channels they open.
• Integration can cost money. On SAP Business Network, the enterprise account that offers direct ERP integration can carry transaction fees once you pass the thresholds above.
• The portal does more than orders. Ship notices, invoice status and catalogs may still live in the portal. Automating PO intake doesn't remove the login entirely.

What to count before you decide

• How many customers send POs through a portal, and which portal each uses.
• Portal POs per month, per customer.
• Minutes per PO to log in, find it, enter it and confirm it.
• Which delivery methods each customer allows: portal only, email, export or cXML.
• How many portal orders had an error found later: wrong part, price or ship-to.

If one customer is most of the volume, start a cXML or EDI conversation with them. If the volume is spread across many customers and portals, automated email intake usually pays first.

How Peekgentic does it

We build order intake around the ERP and the customers you already have. Where a portal can email the PO, software reads it like any other emailed order, matches customers, items and prices, and drafts the order with the original beside it. Anything that doesn't match is flagged, and a person approves every order before it posts. Where volume justifies a structured feed, it runs through the same checks. See how an order-processing build works, or our guide to automating email and PDF orders.