How to automate Ariba invoice submission (and fix rejections)
Your customer moved to SAP Ariba, and now every invoice has to go through their account on SAP Business Network (the network formerly called Ariba Network). Retyping each one by hand is slow, and a single wrong field can send it back to you. You want invoices to get in, pass validation, and reach approval with as little manual work as possible.
There are two levels of automation. The lighter one is creating invoices directly from the customer's purchase order (a “PO flip”), which pre-fills the lines and needs only a free Standard account. The fuller one is sending invoices from your own billing system by cXML, EDI, or CSV upload, which requires an Enterprise account and may incur fees. Either way, every invoice is checked against your customer's invoice rules, so the real work is learning those rules and catching rejections quickly.
What are the ways to submit an invoice to Ariba?
SAP says suppliers can create invoices online in their account or submit them electronically from an external system via cXML or EDI. CSV upload is a third electronic route, but only when the customer has set it up. Here is how the options compare.
| Method | How it works | What you need |
|---|---|---|
| Interactive email order | The PO arrives by email with a Create Invoice button. You invoice from the email. | A free Standard account. Good for a handful of POs from one customer. |
| PO flip in your account | Open the PO in your SAP Business Network account and create the invoice from it. Lines and customer details carry over. | Standard or Enterprise account. The customer must allow invoicing against that PO. |
| CSV upload | Upload a file of invoices using a template the customer has arranged with SAP. SAP Business Network converts them to cXML. | An Enterprise account and a customer-specific CSV template. |
| cXML | Your billing system sends invoices directly. A 201 response means the format passed; a 500 response includes the errors. | An Enterprise account and an integration built and tested on your side. |
| EDI | Your system sends ANSI X12 or EDIFACT invoices and receives a functional acknowledgment, positive or negative. | An Enterprise account and EDI connectivity. |
SAP's Standard account FAQ describes responding to emailed orders with invoices, and its supplier enablement guide notes that Standard suppliers upgrade to an Enterprise account to use cXML, EDI, fax, or CSV. The invoice validation page explains how each method is checked. CSV is enabled from the buyer side: the customer contacts SAP to create the template, which then appears in your account.
Do you need a Standard or an Enterprise account?
For a few POs a month, PO flip from a Standard account may be enough. For many invoices across several Ariba customers, system-to-system integration is where the manual work disappears, and that needs an Enterprise account.
Cost is part of the decision. SAP lists the Standard account as free and the Enterprise account as a subscription plus a fee tied to transaction volume. According to SAP's supplier fee FAQ, an Enterprise account becomes chargeable once you pass 5 documents and $50,000 transacted in at least one customer relationship. Check the current fee schedule for your region on SAP's pricing page before you upgrade.
Start with your customer's invoice rules
Every invoice, however you send it, is validated against that buyer's rules. SAP says invoices that fail this validation are rejected, and that cXML or EDI invoices sent to a buyer who hasn't enabled invoicing for you are automatically rejected. An integration that ignores the rules simply produces rejections faster.
To view a customer's transaction rules:
- Sign in to your SAP Business Network account.
- Click your initials in the upper-right corner, then Settings > Customer Relationships.
- Switch to Classic View and click the customer's name.
- On the Customer Details page, find the transaction rules, including invoicing rules, under Additional Resources. Country-based rules are under Download invoice rules.
If there is no invoice rules section, the customer hasn't enabled you to invoice through the network yet. Ask them how they want to receive invoices. Many customers also publish instructions in their Supplier Information Portal, found in the same Customer Relationships list.
How to create an invoice from a purchase order
SAP's steps for a PO-based invoice:
- Go to Orders > Purchase Orders and find the order.
- Open it by clicking the order number.
- Click Create > Invoice.
- Enter the invoice details on the New Invoice page.
- Click Next. If anything is missing or wrong, a Message Details pop-up lists the fields to fix.
- Review the summary, then click Submit.
Online invoices are validated as you type, so many rule problems surface before you submit. That is one reason an SAP post on avoiding rejected invoices recommends PO flip: it reduces retyping errors on lines and customer details.
What do the Ariba invoice statuses mean?
Ariba shows two fields for each invoice. Routing status tells you whether the invoice reached the customer's system. Invoice status tells you where it is in their approval and payment process. Check both.
| Status | What it means | What to do next |
|---|---|---|
| Routing: Queued | SAP Business Network is sending the invoice. | Contact SAP Support if it stays Queued for more than 30 minutes. |
| Routing: Failed | The invoice didn't follow the customer's rules and wasn't delivered. | Correct the errors and resubmit. |
| Routing: Sent | Delivered, but the customer hasn't acknowledged receipt. | If it stays here, ask the customer what needs to happen. |
| Routing: Acknowledged | The invoice reached the customer's processing system. | Track the invoice status from here. |
| Routing: Obsoleted | You canceled the invoice, or edited and resubmitted it. | No action needed on the original. |
| Invoice: Sent | The customer has it but hasn't approved or rejected it. | Ask AP who is reviewing it. Don't send a duplicate. |
| Invoice: On Hold | An automatically generated service entry sheet is awaiting the customer's approval. | Ask the customer to approve the service entry sheet. |
| Invoice: Rejected | It failed network validation, or the customer rejected it. | Read the rejection notes, then edit and resubmit. |
| Invoice: Approved | Approved for payment. You can no longer change it. | Check the due date. Use a credit memo to correct a mistake. |
| Invoice: Paid | The customer paid or is issuing payment. | Match it against your remittance and bank deposit. |
Sources: SAP's status FAQ and Invoice Status Levels reference.
Why do Ariba invoices fail or get rejected?
SAP describes two kinds of rejection: automatic, based on the customer's invoicing rules, and manual, by the customer. Use the table to narrow it down, starting from the rejection notes on your own invoice.
| Problem | What to check | Who needs to act |
|---|---|---|
| Invoicing isn't allowed for this customer or PO | Is there an invoice rules section for the customer? Does the PO allow invoicing? | The buyer enables invoicing or tells you how to bill instead. |
| Amount is more than what's left on the PO | Compare the invoice with the PO's remaining amount, including earlier invoices against the same lines. | Supplier corrects the amount; buyer sends a new PO version if the PO is wrong. |
| Blanket PO maximum exceeded | Check the line's maximum amount on the blanket PO. | Buyer raises the limit if more was agreed. |
| Earlier failed invoices on the same PO | Look for failed or invalid invoices that still count against the PO. | Make sure failed documents are properly rejected, then resubmit. |
| Invoicing more than shipped or received | Does the customer only allow shipped or received quantities? Is a ship notice or receipt missing? | Supplier sends the ship notice; the customer records the receipt. |
| A date or field rule failed | Read the error message. Back-dating limits and required fields are common rules. | Supplier corrects the invoice. |
| Resubmitted invoice fails again | Is the referenced order version or ship notice still active? | Ask the customer whether the PO changed, then invoice against the current version. |
| Customer rejected it after review | Read the rejection notes for the line, price, or tax difference they found. | Supplier fixes an invoice error; buyer fixes a PO that doesn't match the agreement. |
The PO amount causes are documented in SAP's note on the accumulated PO amount error. The same rule applies here as in our Coupa rejection guide: correct the record that's wrong. If the PO still shows an old price, a corrected invoice won't fix it. The buyer needs to send a new PO version.
How to fix and resubmit a rejected Ariba invoice
You can only change a submitted invoice if its status is Failed or Rejected. SAP's edit and resubmit steps:
- Click Workbench > Rejected invoices.
- Click the invoice number. The rejection notes appear at the top of the Detail and History tabs.
- Under Detail, click Edit & Resubmit.
- Fix the issue the notes describe. Confirm the invoice still references an active order version and active documents, such as the ship notice or service entry sheet.
- Check the invoice number. If the customer doesn't allow reuse, enter a new one.
- Submit, then confirm the new invoice's routing status reaches Acknowledged.
If an invoice shows Rejected with a routing status of Failed and the reason isn't clear, SAP suggests contacting SAP Support. If the notes don't tell you what to change, ask the customer.
Can you reuse the invoice number?
Not by default. SAP Business Network doesn't allow duplicate invoice numbers unless the customer turns on the rule “Allow suppliers to reuse invoice numbers.” With that rule on, you can reuse numbers from Canceled, Failed, or Rejected invoices. Check the customer's rules before you resubmit, and keep the original and replacement linked in your own records.
If the invoice is still Sent and you've found a mistake, you can cancel it only if the customer allows cancellation. Otherwise, ask the customer to reject it so you can resubmit. Once an invoice is Approved, it can't be changed; correct it with a credit memo.
What to send your customer's AP team
Give AP enough to find the invoice and answer one specific question. Include the invoice number, PO number, amount, both statuses, and the exact rejection note. Here's a message you can adapt:
Subject: Invoice [number] rejected in Ariba, PO [number]
Hi [name], invoice [number] for [amount] shows as Rejected in SAP Business Network. The note says “[exact rejection note].” I checked it against PO [number] and found [specific difference]. I've attached [supporting document].
Could you confirm whether [specific action, such as a new PO version] is needed on your side, or whether we should resubmit a corrected invoice? Also, can we reuse invoice number [number], or should the replacement have a new one? Thanks, [name].
For other situations, our past-due invoice email templates include messages for missing POs, new AP contacts, and missed payment promises.
How to make Ariba submission less manual
- Match the method to the volume. PO flip for a few invoices, CSV for batches if the customer offers a template, and cXML or EDI when Ariba customers make up a large share of your billing.
- Record each customer's rules with the account: invoice number reuse, cancellation, non-PO invoices, back-dating limits, and shipped or received quantity requirements.
- If you build an integration, test it first. SAP offers free test accounts for exchanging test POs and invoices before you switch to production.
- Check Workbench > Rejected invoices daily. A rejection notice in an unwatched inbox is how a 30-day invoice becomes a 90-day one.
- Track both statuses. An invoice that is Sent but never Acknowledged needs a different follow-up from one that is Approved and past due.
Does Approved in Ariba mean paid?
No. Approved means the customer has accepted the invoice for payment. SAP notes that not every customer sends remittance information to the network, so an invoice may never move past Approved even after it's paid. If it's past due, check your bank deposits and ask AP for the payment date.
When portal follow-up becomes a daily job
Submitting one invoice through Ariba is easy. Keeping track of the rules, rejections, and approvals across every customer portal takes real time, and your aging report won't show that one invoice failed validation while another is waiting on a service entry sheet.
Alder helps with customer AP portals and approvals: submitting invoices into Ariba, Coupa, and custom portals, catching rejections, fixing and resubmitting them, and following up with the person who releases payment. Anything customer-facing waits for your approval. If your team spends its mornings in supplier portals, book a demo and bring a few invoices that aren't moving.