Ariba Network Invoice Status Tracking for Suppliers

Ariba Network offers invoice status tracking functionality for suppliers.

Why Ariba Network uses two separate tracking systems, not one

SAP Ariba Network, now officially branded SAP Business Network, is the cloud-based portal buyers use to run procure-to-pay work electronically. Every invoice a supplier submits through it kicks off two separate, parallel tracking systems at the same time: Routing Status and Invoice Status. Knowing what each one means, and reading them together instead of picking just one, is what actually keeps a payment delay from turning into a payment crisis.

Routing Status tracks the document's trip through the network's plumbing, the servers and queues that move a file from the supplier's system to the buyer's. Invoice Status tracks something completely different: what the buyer actually does with that invoice once it lands in front of them. One is about delivery. The other is about judgment.

Treat these as the same thing and the confusion writes itself. An invoice can sit at "Sent" in routing while the buyer hasn't so much as glanced at it, or it can show "Approved" on the invoice side while the actual payment is still weeks out. A supplier checking only one screen sees half the picture and assumes it's the whole thing. Every section that follows maps back to one of these two layers, or sometimes both at once, so it's worth locking the distinction in now before the status names start blurring together.

Routing Status values and when to act on them

Routing Status tracks the document's movement between supplier and buyer as it passes through Ariba's infrastructure, nothing about content or approval, just whether the file made the trip. There are five values to know.

"Accepted" means Ariba took the document in from the customer or, in testing scenarios, from a catalog tester. "Order Queued" means the document got queued up during cXML processing, an early holding stage. "Sent" means Ariba converted the file successfully and pushed it into a queue where it's waiting on the customer to pick it up. Suppliers can add up to three email addresses or distribution lists, separated by commas, in the Notifications section of account settings. They're just checkpoints along a route that, in normal cases, resolves itself within minutes.

"Acknowledged" is the status suppliers actually want to see, because it means the buyer's invoicing application has confirmed receipt and the invoice has fully cleared the network handoff.

Then there's "Failed," and this one deserves its own paragraph, separate from anything about invoice rejections later in this piece. A routing failure means Ariba could not move the document at all, and it lists the reason why. The buyer never sees the invoice, period. That matters because it changes what a supplier should do: there's no buyer decision to wait on, no reviewer to nudge, because the document simply didn't make it out of the network's front door. The only path forward is fixing whatever broke and resubmitting.

One timing rule is worth memorizing on its own. If an invoice shows as sent from the supplier's system but the routing status hasn't budged in 30 minutes, that's the signal to stop refreshing the page and call Ariba Customer Support instead. It's the one escalation trigger that lives at the routing layer, and it exists because routing problems are infrastructure problems, not judgment calls, so support is who can actually see what's stuck. "Failed" routing should be framed separately from a "Failed" invoice so readers do not conflate the two layers again.

What each Invoice Status value means for payment timing

Once an invoice clears routing, Invoice Status takes over, and this is where the buyer's own judgment enters the picture. There are five values here too, and they read almost like a funnel: from arrival, through review, and out the other side into payment or rejection.

"Sent" at this layer means the invoice has reached the buyer but nobody's checked it against the purchase order or the receipts yet, so no action has happened. "Approved" means the buyer matched it against the PO or contract and against what was actually received, and signed off on payment; once that happens, the invoice is locked and cannot be edited. "Paid" means the buyer paid it, or is in the process of doing so, though this status is visible only when the buyer's setup uses invoices to trigger payment in the first place. And "Cancelled" is the one status the supplier controls: it means the supplier cancelled the invoice on their own end.

By default, an invoice a supplier creates through Business Network skips the approval workflow entirely and gets marked "Approved" straight away, since that's simply the default setting. Buyers can turn on an approval workflow if they want one, so the actual path an invoice takes depends entirely on how that specific buyer configured their instance.

Partial invoicing trips people up too. When a supplier submits multiple partial invoices against a single PO, that PO keeps showing "Partially Invoiced" right up until every last item on it has been billed, which reflects incomplete business accurately rather than signaling an error.

What "Paid" actually guarantees is the gotcha this piece repeats twice, because it's the one that costs suppliers real money in confusion. SAP Business Network marks an invoice "Paid" the moment the buyer's ERP system transmits that status, regardless of whether the payment has actually cleared the bank. "Paid" is a signal that a process started, not proof that cash landed. Suppliers who understand "Approved" and "Paid" as distinct milestones can pace their follow-up more accurately. Rejected means the buyer rejected the invoice, or it failed Ariba Network validation.

How to find invoice status inside the Ariba Network Workbench

The Workbench is where registered suppliers go to see all of this in one place. Getting there is a short path: log into the SAP Business Network account, click the Workbench tab at the top of the page, and select the Invoices tile, which is the simplest, most direct tile for invoice management. That tile lays out the customer name, invoice number, reference document, invoice amount, and current status, all in one row per invoice. By default, it only shows the last 31 days of activity, which is fine for active invoices but useless for chasing something older.

To search further back, the Edit Filters option opens up the real search tools. Partial Match lets a supplier search by invoice number, order/PO number, or creation date, and can filter up to the last 365 days, or use a Custom Date Range for older invoices. Exact Match does what it sounds like: type in one specific invoice number and get exactly that one result back. For anyone running these searches often, the Save Filter option keeps a set of search criteria on hand so it doesn't have to get rebuilt every time.

Registered suppliers can export invoice status reports to Excel, covering up to a 365-day period and including both the Routing Status and Invoice Status columns. That single export is arguably the fastest way to reconcile a batch of invoices against what accounting is expecting. Suppliers can also build custom tiles on the Workbench to filter for specific groups, say, everything that's been rejected, or everything sitting approved but unpaid, so the dashboard shows exactly the invoices that matter day to day.

Suppliers on a Standard, free account don't get the full Workbench tile experience. They can only check invoice details through the interactive invoice email. Not every supplier sees the same screen described above.

The Invoice Status Portal: checking status without a full Ariba account

SAP Business Network rolled out the Invoice Status Portal in August 2022, built as a self-service option for customers using SAP Business Network for Procurement. A supplier doesn't need to be onboarded onto SAP Business Network at all to use it, making this a genuinely different audience than everything covered above.

Single invoice lookup requires the supplier to enter their vendor ID, email address, and invoice number, with no registration needed. The second is full registration, which unlocks a view across all of a supplier's invoices and every status they carry.

Registration isn't open to just anyone who wants to peek at a buyer's payment system, though. It generally requires an invitation email from the buyer, unless the supplier already has an existing trading relationship with that buyer on SAP Business Network. And the email address used to register has to match the one the invitation was sent to. Buyers running multiple ERP systems complicate this slightly: a supplier might have more than one supplier record on file, so registration asks them to pick the right Bill To address and system ID to land in the correct one.

Once registered, the available tiles are broken out by exactly the kind of question a supplier is actually asking: all invoices, paid, rejected, invoices pending approval, approved invoices pending payment, overdue and approved, overdue and not approved, and remittances. Whether any of that data appears at all depends on the buyer's own setup on the back end. Invoices posted to the buyer's ERP are copied over, which requires either the SAP Cloud Integration Gateway for SAP ERP or a cXML integration for non-SAP ERP systems. Some buyers also choose to push payment remittance details into the portal, though that's a configuration choice, not a guarantee. Anyone who already holds a full SAP Business Network account can log straight into the portal with the same credentials, and existing trading relationships just keep running through the Workbench as before.

How to read payment and remittance status after an invoice is approved

Getting an invoice to "Approved" feels like the finish line, but it's really just the last visible checkpoint before a separate process, payment, takes over. Remittance advice is the data that closes that loop, and it's what actually triggers the "Paid" status inside SAP Ariba Invoice Management and SAP Ariba Buying and Invoicing. That remittance data carries specifics: which invoices got bundled into a given payment, what payment method was used, bank details, any discounts applied, and other line-level payment information.

Finding it means going to the History tab on the invoice in question. The Routing Status section there shows the current state of the remittance advice, while the Status History section lays out every status change in the order it happened. Every time remittance status shifts, SAP Business Network logs it to that History tab, which makes the tab genuinely useful for tracing exactly where in the chain a payment stalled, rather than just guessing.

Delivery of that remittance advice happens one of three ways: online through the portal, via cXML, or by email, and which method applies depends entirely on how the buyer set things up.

The "Paid" caveat from earlier deserves repeating here, because this is where it actually bites. SAP Business Network marks an invoice "Paid" as soon as the buyer's ERP transmits that status, whether or not the money has cleared. Treat "Paid" as a prompt to check the bank account⟧c53⟧. The History tab is the tool for figuring out whether a stall happened before or after that "Paid" flag got set, which matters when deciding whether to call the buyer or call the bank.

Invoice rejection reasons and how to resubmit correctly

When a rejection happens, the Invoice Detail tab shows a notice right at the top explaining why, and if the buyer wrote or picked a specific explanation, that message appears directly rather than in some coded shorthand. Common causes include missing required information, like a required attachment that never got attached, incorrect information such as the wrong tax percentage entered on a line, more than one tax rate applied to a single line (which the system simply won't allow), a PO that's invoiced against but has already passed its validity date, or a quantity billed that's higher than what the buyer has actually recorded as received.

The fix for that one doesn't live with the supplier at all. If the rejection is about quantity exceeding what's been received, the buyer simply hasn't posted the goods receipt yet on their end. Resubmitting a corrected invoice does nothing there. The right move is picking up the phone (or firing off an email) to the buyer's procurement team and asking them to post the receipt, not tinkering with the invoice.

Mismatched or outdated supplier account information is the recurring root cause underneath most of these categories.

Resubmission itself follows different rules depending on which layer flagged the problem, and mixing these up is an easy mistake. A Failed routing status just needs a corrected version resubmitted. A Rejected invoice status is stricter: the supplier has to use a brand-new invoice number, and the documented approach is tacking a letter or digit onto the original number rather than inventing something unrelated.

A background process called Invoice Reconciliation also runs. Once an invoice gets approved, an IR document gets created automatically on the buyer's side to track any discrepancies against the PO, contract, or receipts. If the buyer has messaging turned on for that IR document, suppliers might get communications through it, and responding to those quickly is part of actually resolving the exception rather than letting it sit.

Setting up email notifications so status changes reach you automatically

None of the above matters much if nobody's checking the Workbench regularly. That's where notifications come in. Ariba Network can fire off automatic emails whenever invoice-related events happen on a supplier's account, covering things like an invoice failing or getting rejected, or simply any status change at all on any invoice.

Setup lives in the Notifications section of account settings, and suppliers can list up to three email addresses or distribution lists, separated by commas. That's a small detail with a real practical use: instead of one person's inbox being the single point of failure for catching a rejection, a shared AR team inbox or distribution list can get looped in directly. Notifications aren't just for catching problems either; they double as a general activity log, and they're specifically useful for flagging when an invoice turns out to be undeliverable.

Suppliers using the Invoice Status Portal (the one covered earlier that doesn't require full onboarding) get their own notification setup inside that portal too, documented separately in the SAP Help Portal's November 2025 guide. Notifications flip the whole tracking process from something a supplier has to remember to go check, into something that shows up in an inbox the same day it happens. A rejection caught the morning it occurs is a five-minute fix.

How error classification assisted by automated tooling is changing the rejection resolution process

The rejection reasons themselves are getting easier to actually understand, and there's a number attached to prove it. SAP Business Network's invoice exception rate dropped from 11% in 2023 to 7% by June 2025, and the direction of that trend says as much as the numbers themselves SAP Community — Streamline Invoice Dispute with Generative AI Invoice Error Classification.

Joule, SAP's AI system embedded across SAP Business Suite, is a big part of why. It takes unstructured rejection errors, the messy raw text a system might spit out, and turns them into structured, actionable categories. For a supplier, that means rejection explanations now read more like plain language and less like a cryptic error code.

The pace of change here hasn't slowed either. By the third quarter of 2025, Joule picked up the ability to let customers interactively verify supplier invoices or run mass updates using natural language, so instead of clicking through dozens of individual records, a buyer's team can just describe what needs to change. By the first quarter of 2026, Joule was translating complex e-invoicing errors into plain language on its own, a new Dispute Resolution Agent started automating root-cause analysis on invoice disputes, and payment advice processing sped up considerably.

None of that replaces knowing the status system itself, though. AI is getting better at explaining why something got rejected, in language a person can actually use.

Account type differences that affect what invoice tracking features you get

A Standard account on SAP Business Network is free, and it covers the basics: managing purchase orders, submitting invoices for suppliers in enabled e-invoicing countries, tracking invoice status, and checking payment remittances. What it doesn't include is the full Workbench experience described earlier in this piece. Standard account holders check invoice details through the interactive invoice email instead, which works fine for occasional, low-volume invoicing but turns tedious fast for anyone submitting invoices at real volume.

An Enterprise account, the paid tier, is built for exactly that higher-volume case: one portal holding every PO and every invoice, filterable, exportable, searchable across a full year, rather than an email inbox full of individual notices https://www.eversource.com/residential/about/doing-business-with-us/procurement/procurement-systems/ariba-network. The Invoice Status Portal covered earlier sits somewhat outside this divide, since it's aimed specifically at suppliers who may not be onboarded onto SAP Business Network at all. For a smaller supplier sending a handful of invoices a month, the free tier and its email-based check-ins might be all that's ever needed. For anyone managing invoice volume that makes manual email-checking impractical, the Workbench, the filtered tiles, and the Excel export become less of a nice-to-have and more of the actual operating system for getting paid on time.