How to Submit an Invoice in SAP Ariba (Business Network)

To submit an invoice in SAP Ariba, open the purchase order on SAP Business Network (from the interactive PO email on a standard account, or from the Workbench on any account), click Create Invoice, choose Standard Invoice, and the PO data flips into a draft invoice. Add your invoice number, date, and tax detail, confirm the lines match what you delivered, and submit. The invoice routes into your customer's approval process, and the network shows you routing and approval status as it moves.

This guide covers the flow from the supplier's side: how Business Network accounts work (and when fees apply), receiving the PO, the PO flip, the buyer-configured invoice rules that silently shape what you are allowed to submit, the rejection reasons that catch most suppliers, and what each status means. If your customer runs Coupa instead, see the companion guide on how to submit an invoice in the Coupa Supplier Portal.

SAP Business Network, formerly Ariba Network

SAP Business Network is the transaction network that connects suppliers to buyers running SAP Ariba procurement (and related SAP applications). It was called Ariba Network for years, and you will still see both names in customer emails, training PDFs, and the product itself. For invoicing purposes they are the same thing: your customer sends purchase orders across the network, and you send order confirmations, ship notices, and invoices back across it.

An SAP Business Network invoice is not an emailed PDF. It is a structured electronic document that lands directly in your customer's invoice reconciliation process, gets matched against the PO (and often the goods receipt), and moves through their approval chain. That is why buyers standardize on it, and why an invoice emailed outside the network to an Ariba-mandated customer is typically returned unprocessed.

Standard vs enterprise accounts, and who pays fees

Suppliers connect to the network through one of two account types, and the difference matters because one of them can cost money:

• Standard account: free, forever, regardless of volume. You transact through interactive email notifications plus a lightweight portal view. For most suppliers invoicing a handful of Ariba customers, standard is enough, and no document volume triggers a fee.
• Enterprise account: full portal capabilities, with fees at high volume. Enterprise accounts add full document search and archiving, reporting, long-term visibility of transaction history, multi-user workflows, and integration options (cXML, EDI). Fees apply once your volume with a single buyer crosses both thresholds in a rolling 12-month period: 5 documents and 50,000 USD in transacted value. Past that point, SAP bills a quarterly transaction fee (a percentage of transacted volume, published at 0.155% for suppliers using SAP Business Network for supply chain collaboration and 0.35% otherwise, subject to caps) plus an annual subscription fee tiered by document count. Check SAP's current published pricing for your region before relying on exact numbers, because the schedule changes.

Two practical notes. First, you do not accidentally end up with fees: standard accounts stay free, and upgrading to enterprise is an explicit choice (though some buyers ask their strategic suppliers to upgrade). Second, if you were on an enterprise account historically, it is worth checking whether a standard account now covers your needs; suppliers can request a downgrade.

Receiving the purchase order

Everything starts with the PO, and where you find it depends on your account type:

• Standard account: the PO arrives as an interactive email (typically from [email protected]; whitelist that address). The email contains a Process Order button that takes you into the network to act on the PO. You can also see your POs in the Workbench after registering, but the email is the primary handle, so route these messages to a shared AR mailbox rather than one person's inbox.
• Enterprise account: POs appear in your Workbench and Orders views, with search and filters across your full history.

Before invoicing, check whether your customer requires intermediate documents. Many buyers require an order confirmation, and some require a ship notice or a service entry sheet (for service POs) before the network will let you invoice. If the Create Invoice button is greyed out, a missing prerequisite document is the most common reason.

The PO flip: creating the invoice from the PO

Like Coupa, Ariba's core invoicing motion is the PO flip: the network converts the purchase order into a draft invoice, carrying over line items, prices, part numbers, and bill-to details so the invoice matches the PO by construction. Step by step:

1. Open the PO (from the interactive email on standard, or the Workbench on enterprise).
2. Click Create Invoice and choose Standard Invoice. Other document types (credit memo, line-item credit memo) live in the same menu.
3. Enter the invoice header: your invoice number (unique per customer) and invoice date. Buyer rules often limit backdating, commonly to a handful of days, so invoice promptly.
4. Confirm the lines. Include only what you are billing now. For partial shipments, adjust quantities down and exclude undelivered lines; the PO status will show Partially Invoiced until the order is fully billed. Do not raise unit prices above the PO.
5. Add tax. Enter tax at header or line level as the form requires. Tax fields and validation vary with the buyer's configuration and the countries involved; entering more than one tax rate against a single line is a classic rejection trigger.
6. Add shipping, allowances, or charges only if the buyer's rules permit them; some buyers block extra charges that were not on the PO.
7. Attach documents if required (a PDF invoice image, proof of delivery). If you attach a PDF, its amounts must match the electronic invoice exactly; a mismatch between the PDF and the Ariba data is a known rejection cause.
8. Review and submit. The invoice routes to your customer, and you track it from Workbench, Invoices (or the invoice status emails on a standard account).

Buyer invoice rules: the settings that shape what you can submit

The single most useful thing to understand about Ariba invoice submission is that your customer configures invoice rules that the network enforces before their AP team ever sees the document. These rules differ per buyer and sometimes per country, which is why the same action can succeed with one customer and fail with another. Rules commonly cover:

• Whether non-PO invoices are allowed at all (many buyers block them),
• Which invoice types you may send (standard, credit memo, service invoice),
• How far an invoice date may be backdated,
• Whether quantities and prices may deviate from the PO, and by what tolerance,
• Whether shipping and special handling charges may be added,
• Whether attachments are required or permitted,
• Whether an order confirmation, ship notice, or service entry sheet must precede the invoice.

You can usually view a customer's rules in your account (under the customer relationship settings), and buyers publish supplier guides describing them. When an invoice fails for a reason you cannot see, the buyer's rules are the first place to look.

Common rejection reasons

Across buyer configurations, the same failures come up repeatedly:

• Tax problems: multiple tax rates on one line, a tax rate the buyer's system does not recognize, or missing tax fields for the invoicing country.
• PO mismatches: prices above the PO, quantities exceeding what remains uninvoiced, currency different from the PO, or invoicing a closed or fully invoiced PO.
• Missing prerequisite documents: no order confirmation or service entry sheet where the buyer requires one.
• Mismatched attachments: a PDF invoice image whose totals, tax, or prices differ from the electronic invoice data.
• Wrong sold-to or bill-to details: the sold-to name and country on the invoice must match the PO's bill-to or sold-to information.
• Duplicate invoice number: invoice numbers must be unique per customer.
• Invoicing outside the network: emailing a PDF to a buyer who mandates Ariba gets the invoice returned or ignored, and the clock on your payment terms usually does not start.

Invoice and routing statuses explained

Ariba tracks two things: whether the document reached your customer (routing status) and what your customer did with it (invoice status).

How long an invoice sits in Sent before approval depends entirely on the buyer's reconciliation and approval process: invoices that match the PO and receipt within tolerance can approve automatically, while exceptions route to a human. If an invoice is stuck, the routing status tells you whether the problem is delivery (yours to fix) or approval (theirs to answer for).

Fixing a rejected invoice

1. Open the rejected invoice and read the rejection reason. System rejections name the failed validation; manual rejections usually carry a comment from AP.
2. Edit and resubmit. Rejected invoices can be edited and resubmitted from the invoice itself. Some buyers require the resubmission to carry a new, unique invoice number; others accept the original number. Follow your customer's guidance, and when in doubt use a new number.
3. Check the PO if the mismatch is real. If your price is right and the PO is stale, the fix is a PO change on the buyer side, not a lower invoice. Raise it with your buyer contact before resubmitting at the wrong price.
4. Watch for the pattern. Repeat rejections with one customer almost always trace to one rule (tax setup, attachment requirements, confirmation-before-invoice). Fix it once at the source and document it for whoever invoices next.

Rejections and slow reconciliation are where portal receivables quietly age. If enterprise portal invoices are dragging your collections, systematic status tracking and follow-up (see the dunning docs) matters as much as clean submission.

Integration and e-invoicing compliance notes

Two topics come up for higher-volume suppliers, and both are worth hedging because the details are buyer- and country-specific:

• Integration: enterprise accounts can integrate with your billing system or ERP via cXML or EDI, so invoices flow out of your system instead of being keyed into the portal. SAP-to-SAP integrations historically ran through SAP Cloud Integration Gateway (CIG), whose capabilities have been folding into the broader SAP Integration Suite; if your customer's enablement team mentions CIG, treat the specifics as their configuration to define. Integration projects are real IT work and mostly make sense for sustained high volume with a single buyer.
• E-invoicing compliance: in countries with regulated e-invoicing or clearance models, SAP Business Network supports country-specific compliant invoicing, but which countries are covered for your relationship, and what extra fields or processes apply, depends on the buyer's setup and current regulations. Confirm requirements with your customer for each invoicing country rather than assuming the flow you use domestically transfers.

When you should stop doing this by hand

One Ariba customer is a process. Five portal customers (Ariba here, Coupa there, a Tungsten and a couple of homegrown portals) is a part-time job: receiving POs across inboxes, matching them to invoices in your billing system, logging into each portal, flipping, submitting, then polling statuses and triaging rejections. Finance teams submitting many portal invoices a month almost universally automate it.

LedgerUp's version: Ari, LedgerUp's AI agent, monitors the AR inbox for POs and portal notifications, matches each PO to the right invoice, logs into Ariba, Coupa, and the rest with credentials you provide, submits the invoice, and tracks status changes, posting approvals and rejections to Slack the day they happen. Teams using it save about 15 hours per month on portal submissions and see a 13-day average DSO reduction on portal invoices. See procurement portal automation and the procurement portal docs for the workflow, or the contract-to-cash guide for where portal invoicing fits in the wider AR process.

At low volume, none of that is necessary: a standard account, the PO email, and the checklist above will serve you fine.

Frequently asked questions

Is SAP Ariba free for suppliers?

A standard account on SAP Business Network is free regardless of volume, and it supports receiving POs and submitting invoices. Enterprise accounts carry fees once your volume with a single buyer crosses 5 documents and 50,000 USD in a rolling 12-month period: a quarterly transaction fee plus an annual subscription tiered by document count. You do not incur fees accidentally; enterprise is an explicit upgrade.

What is the difference between an Ariba standard and enterprise account?

Standard accounts transact mainly through interactive PO emails plus a lightweight portal view, and are always free. Enterprise accounts add full document search and history, reporting, multi-user workflows, and cXML or EDI integration, and are subject to fees at high volume. Most suppliers with modest Ariba volume are fine on standard.

What is a PO flip in SAP Ariba?

A PO flip converts the purchase order into a draft invoice, carrying over line items, prices, and bill-to details so the invoice matches the PO by construction. You do it by opening the PO and clicking Create Invoice, then Standard Invoice. It is the fastest and least rejection-prone way to invoice on the network.

Why was my Ariba invoice rejected?

The usual causes: tax problems (multiple rates on one line, or a rate the buyer's system does not recognize), prices or quantities above the PO, a missing order confirmation or service entry sheet, a PDF attachment that does not match the electronic invoice amounts, wrong sold-to details, or a duplicate invoice number. The rejection reason attached to the invoice names the specific failure.

How long does Ariba invoice approval take?

It depends on the buyer's reconciliation and approval configuration. Invoices matching the PO and receipt within tolerance can approve automatically; exceptions route to humans and take days or weeks. Ariba shows you delivery (routing status) separately from approval (invoice status), so you can tell whether a stuck invoice is a delivery problem or sitting with the customer.

Can I edit an invoice after submitting it in Ariba?

Not while it is in process. If the invoice is rejected, you can edit and resubmit it; depending on your customer's rules, the resubmission may need a new, unique invoice number. If you catch an error on an invoice that has not been rejected, contact your customer's AP team and ask them to reject it, or issue a credit memo and re-invoice.

Can I submit an invoice in Ariba without a purchase order?

Only if the buyer's invoice rules allow non-PO invoices, and many buyers do not. Where allowed, you create the non-PO invoice from your account and supply routing information (such as a customer contact or email) so it reaches an approver. Expect slower approval than PO-backed invoices.

What do the Ariba invoice statuses mean?

Routing statuses (Queued, Sent, Acknowledged, Failed) tell you whether the document reached the customer's system; Failed means it never arrived and needs fixing on your side. Invoice statuses (Sent, Approved, Rejected, Paid) tell you what the customer did with it: Sent is awaiting processing, Approved is cleared for payment, Rejected carries a reason to fix, and Paid means payment was issued where the buyer shares that status.

What is an interactive PO email in Ariba?

On a standard account, each purchase order arrives as an interactive email (from [email protected]) with a Process Order button that opens the PO on the network so you can confirm it or flip it into an invoice. Because that email is your handle on the order, route it to a shared AR mailbox and whitelist the sender.

Do I need SAP software to invoice through SAP Business Network?

No. The network is a web platform: a browser and a free standard account are enough to receive POs and submit invoices. Integration options (cXML, EDI, or SAP-to-SAP via integration tooling such as CIG) exist for high-volume suppliers, but they are optional and are configured with your customer's enablement team.