Key Takeaways
- A portal does not pay you: SAP Business Network and the Coupa Supplier Portal deliver the invoice and report status; your customer’s terms and payment run set the date.
- Paid in a portal is the customer’s statement, not cash: customers mark invoices Paid as soon as their ERP sends that status, “whether or not the payment fails” (SAP, 2025).
- Remittance is optional per customer: “Not every customer sends remittance information to SAP Business Network” (SAP, 2025), and Coupa may hide payment data for some buyers (Coupa, 2026).
- The bank statement is the proof: a Coupa bank transfer in progress may take 2-3 business days to arrive (Coupa, 2026), so tie the transfer reference to the bank line before clearing the invoice.
- Transformance reads remittances in any format with over 97% extraction accuracy, and ClearMatch auto-matches 95% of payments (Transformance platform and customer data, 2026).
In This Article
- Key Takeaways
- How does getting paid work when a customer requires SAP Ariba or Coupa?
- What does the portal check, and why do invoices get rejected?
- What does each portal status mean, and what should AR do next?
- Who controls the payment date, and when does the clock start?
- How do payment status and remittance come back to you?
- What do you do when the portal says Paid and the cash is not applied?
- How do you run portal invoicing as an AR process?
- How does Transformance help once the portal remittance arrives?
How does getting paid work when a customer requires SAP Ariba or Coupa?
A portal delivers your invoice and shows its status; your customer approves and pays it. Getting paid on time takes a clean invoice and a status tracked to Paid.
Portal checklist: what is checked, where invoices stall, who fixes it, how status and remittance come back
Statuses and fields are SAP’s (Tracking Payments guide, 2025) and Coupa’s (Supplier Portal documentation, 2026); the stall and fix columns are our reading of them. Each buyer configures its own validation, tolerances and payment feed, so the customer’s supplier guide is the rule.
A supplier portal is the customer’s channel for receiving supplier invoices and returning status. SAP Business Network (still widely called Ariba Network) and the Coupa Supplier Portal both work this way, and neither pays the invoice: on Coupa, “Payment Terms determine when payments are made” (Coupa, 2026).
This page follows your invoice through the portal to the bank line. How a remittance document is read and matched is in how AI reads remittance advice and matches payments; e-invoicing mandates are in e-invoicing and cash application.
What does the portal check, and why do invoices get rejected?
The portal validates the invoice, then the customer matches it to its purchase order, contract and receipts. A difference outside the customer’s tolerance becomes an exception that a person resolves.
On SAP Business Network, a PO flip copies the purchase order into the invoice “following the buyers invoice validation rules”, and you add taxes or shipping at header or line level (SAP Learning, undated). The customer then matches it to “purchase orders, contracts, and receipts data, such as price, terms, quantity”: within its pre-configured tolerances the invoice moves to approval or payment, outside them to manual processing as an invoice exception.
SAP rejects an invoice when it fails validation on the network or the customer rejects it, and you can edit and resubmit it (SAP, 2025).
On Coupa, you create the invoice from the PO on the Orders page and pick the legal entity and remit-to from records that already exist; “Only Admins can create legal entities” (Coupa, 2026). Coupa’s cXML error pages show the kind of checks that run before a customer ever sees the invoice:
- Invoice already used: “Each invoice a supplier passes to Coupa must be unique”, so a resent number is marked as a duplicate (Coupa, 2016).
- PO line type: a quantity-based PO line needs a quantity invoice line, an amount-based one a service line (Coupa, 2022).
- Payment term missing: the payment term on your supplier record is blank, and the fix is a default term on that record (Coupa, 2019). That record lives in the customer’s system, so you ask them to fix it.
Before you send, check (our guidance): PO number, line type, price and quantity as ordered; tax and shipping where the portal does not default them; payment terms; a new invoice number; the right legal entity and remit-to; and a goods receipt at the customer.
The last item is the one you cannot see. An invoice can sit in Pending Approval because nobody at the customer posted the goods receipt, so the three-way match cannot finish.
What does each portal status mean, and what should AR do next?
Each status tells you whose turn it is. Rejected and Disputed are yours to fix, Pending Approval and Approved are the customer’s, and only a bank line proves payment.
Portal status map: what it means and what AR does next
Sources: SAP (Tracking Payments, 2025); Coupa (invoices and payments documentation, 2026).
Two rules of thumb. A status is the customer’s statement, not a bank fact. And corrections differ per platform: after SAP Approved “you can’t make any changes”, so a fix travels as a credit memo (SAP, 2025), while a disputed standard Coupa invoice can be corrected under the same invoice number (Coupa, 2026).
Who controls the payment date, and when does the clock start?
Your customer controls the payment date: its terms and payment run decide when funds leave. The portal displays that date; it does not set it.
Coupa shows a Payment Released Date, “the date that your buyer released the payment”, which it says is “not to be confused with the date your buyer created or approved the payment” (Coupa, 2026). On SAP Business Network, a scheduled payment carries the projected date, method, gross, discount applied, adjustment and net, and SAP’s advice for questions about it is “contact your customer directly” (SAP, 2025).
When the clock starts is a contract term, not a portal setting. Coupa’s own example of payment terms reads “payments are made within 45 days of invoice approval” (Coupa, 2026). That one word, approval, moves the date.
An illustrative case: you submit an invoice on March 2, and the customer posts the goods receipt late and approves on March 20. On net 45 from invoice date, payment is due April 16. On net 45 from approval, it is due May 4, 18 days later, and no portal status shows you the difference. Record which event starts the clock for every portal customer.
Where a customer runs an early-payment program, SAP shows the discount applied on the scheduled payment; whether to accept it is your finance team’s decision. How the payment travels is in ACH, wire or SEPA Instant, and what to do after the due date is in the B2B dunning cadence guide and the dunning email templates.
How do payment status and remittance come back to you?
Only if the customer sends them. SAP Business Network and Coupa show payment status and a reference when the customer’s payment data flows into the portal, and some send none.
On SAP Business Network, remittance advice arrives in one of two ways (SAP, 2025):
- Outside the network: the customer’s ERP generates the remittance advice, including status updates.
- On the network through ACH or AribaPay: the customer’s ERP sends a payment batch, and SAP Business Network creates a remittance advice for each payment in the batch.
SAP is direct: “Not every customer sends remittance information to SAP Business Network. If your invoice doesn’t move past Approved status, you’ll need to contact your customer to find out when to expect payment.” A remittance advice shows Identified Differences between the payment and the invoices, which SAP says are “often related to tax and shipping charges”.
Two SAP caveats matter for cash application. Customers mark invoices Paid “as soon as their ERP systems transmit that status to SAP Business Network, whether or not the payment fails”. And the AribaPay Funds Paid stage means the provider has sent funds to your bank; it “does not indicate whether or not your bank has credited your account” (SAP, 2025).
Coupa’s Payments page shows the method (bank transfer, check or virtual card), the status the buyer sees and, for a Paid payment, the check number or transfer reference “which you can use to track the payment with your bank”. A bank transfer in progress “may take up to 2-3 business days”; a completed one should arrive “within 1 business day”. Coupa also notes that “payment data may not be shown for some buyers due to their data privacy preferences” (Coupa, 2026).
The portal gives you a reference and a status; the bank statement is the proof, and the reference links the two.
What do you do when the portal says Paid and the cash is not applied?
Tie the portal’s payment reference to the bank line, apply the amount to the invoices it lists, and send any difference to a person with the portal record as evidence.
The order of work (our guidance):
- Find the bank line by amount, a value-date window and the portal’s payment or transfer reference.
- Apply it to the invoices on the remittance advice.
- Classify the difference: a tax or shipping line the customer did not accept, an early-payment discount taken, a short pay, or a credit memo you have not issued yet.
- No bank line after the stated settlement time? Ask the customer for the payment record. A failed or returned payment shows up only on the bank side (ACH return codes and SEPA R-transactions).
An illustrative example in USD. A distributor invoices a customer through SAP Business Network for $48,600, including a $450 shipping line. The invoice moves to Approved, then Paid. The bank line two days later is $48,150. The remittance advice shows gross $48,600, an adjustment of $450 and an amount paid of $48,150, with an identified difference on the shipping line.
AR applies $48,150 and leaves a $450 residual item. If the shipping was agreed on the PO, the residual becomes a short-pay query with the remittance advice attached. If it was not, the invoice is already Approved, so the correction is a $450 credit memo, not an edit (SAP, 2025). Either way the open item closes on evidence, not on the portal status.
The portal’s reference may not reach your statement intact, because bank reference fields are short (see the BAI2, camt.053 and MT940 guide); when nothing links, see how to match a payment with no reference. Portals are one of several remittance sources, and what stays unmatched becomes unapplied cash.
In your ERP, the invoice stays an open item until a bank line clears it, whatever the portal says (how payments post and clear open items).
How do you run portal invoicing as an AR process?
Keep one register of customers on portals, give each an owner and a weekly status review, and measure invoices stuck in Approved, Disputed or Rejected against your own terms.
Seven steps to run portal invoicing as an AR process
- List every customer that requires a portal, the platform (SAP Business Network, Coupa or another), the payment terms, the event that starts the clock and the contact who answers status questions. Owner: AR lead.
- Write a one-page invoice checklist per platform from the customer’s own supplier guide: PO and line rules, tax, payment terms, invoice number, legal entity and remit-to. Owner: billing.
- Invoice from the purchase order wherever the portal allows it, and check the fields the portal does not default, such as tax and shipping. Owner: billing.
- Review rejected, disputed and pending-approval invoices every week and answer each one the same day. Owner: AR team.
- Record for each customer whether it sends payment status and remittance into the portal, and where else remittance arrives: email, file or bank text. Owner: AR lead.
- Match every payment to a bank line by amount, date and the portal’s payment reference, and treat Paid without a bank line as an open question. Owner: cash application.
- Track four measures from your own data: first-time acceptance, days from Approved to payment released, Paid without a bank line, and remittances received per payment received. Owner: AR lead.
These measures are our definitions, not benchmarks. Keep in mind what each system knows: the portal is the customer’s view of your invoice, your ERP holds your open items, and AR owns the reconciliation between the two. What AR automation reads from and writes to the ERP sets out the ERP side.
How does Transformance help once the portal remittance arrives?
Transformance reads remittances in any format with over 97% extraction accuracy and no templates, and ClearMatch auto-matches 95% of payments, with a person approving anything that posts.
DocSense reads remittance documents with vision language models, not OCR plus regex: over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration (Transformance platform data, 2026). A remittance advice in a PDF, a spreadsheet or an email body is read as it arrives.
ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes, with 100% posting validation; nothing posts without human sign-off (Transformance customer data, 2026). ClearMatch works on the customer master data, open items, invoices and bank statements it reads from your ERP, and writes clearing postings back after approval. The ERP connection typically takes 2-3 days, and your IT team may be involved.
For the exception, such as a Paid status with a short bank line, Vero, the AI agent, investigates from Customer 360, its memory of each customer. It fetches information from internal and external sources to find more matches and proposes with the evidence attached. A person approves, and postings follow your approval thresholds.
Transformance works with customers across Europe, the United States and Australasia, including Syngenta, Eberspächer and PwC.
Who Transformance is for
- ERPs: teams whose customers pay in response to portal invoices and whose receivables clear in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).
Conclusion: follow the invoice past Approved
A portal gets your invoice to the right desk. It does not get you paid, so own the status, the reference and the bank line yourself.
Start with the customers that require a portal: terms, clock-start event and an owner for each. Review Approved-but-unpaid and Disputed invoices weekly, and treat every Paid status as a question until the bank line answers it.
Key terms
- Remittance advice: the message that tells you which invoices a payment covers.
- Purchase order: the customer’s order that a portal invoice must reference.
- Three-way match: comparing the invoice with the purchase order and the goods receipt.
- Payment terms: the agreed due date, the event that starts it and any discount.
- Credit memo: a document that reduces an invoiced amount, the fix once a portal invoice is approved.
- Cash application: matching incoming payments to the open invoices they settle.
Related guides
- Which ERP systems does Transformance integrate with?
- Where does remittance advice come from, and how is it captured?
- ACH, wire or SEPA Instant: which rail, and what remittance arrives?
- What do ACH return codes and SEPA R-transactions mean for AR?
- What dunning cadence works for B2B customers?
- How does AI read remittance advice and match payments?
- How to automate cash application with AI
Frequently Asked Questions
Does SAP Ariba or Coupa pay my invoices?
No. SAP Business Network (Ariba) and the Coupa Supplier Portal deliver your invoice and show its status, while your customer’s AP team approves it and its ERP or payment provider pays it on the customer’s terms.
Why was my invoice rejected, and how do I avoid it?
An invoice is rejected when it fails the portal’s validation or the customer’s matching to its purchase order, contract and receipts. Invoice from the PO, check tax, shipping, payment terms and the invoice number, and follow the customer’s supplier guide.
Why does my invoice show Approved but I have not been paid?
Approved means your customer has approved the invoice for payment, not that money has moved. The payment date follows the customer’s terms and payment run, and the clock may start at approval rather than at the invoice date. If the status never moves on, contact the customer.
How do I get remittance advice from Ariba or Coupa?
You see remittance details in the portal only if your customer sends them. SAP Business Network shows a remittance advice per payment, Coupa shows a transfer reference or check number on the Payments page, and some customers send neither, so agree an email or file fallback.
Which ERPs does Transformance work with?
Transformance runs in production with customers on SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations, Business Central and Odoo, and supports Oracle and Infor.
Is this for a company of our size and payment volume?
Transformance is built for mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities, and for volumes from under 1,000 to over 100,000 payments a month.
How long does it take, and what does it cost?
The ERP connection typically takes 2-3 days, and your IT team may be involved; a proof of value runs 4-5 weeks on one entity, and a full rollout takes up to 4-8 weeks. Cost depends on scope and the number of entities, so there is no figure here. Book a Call and we scope it with you.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
