Est.

Tracking Invoice Status Inside Ariba Network

Two status systems use identical words to describe completely different invoice stages.

· 9 min read · Updated
Cover illustration for “Tracking Invoice Status Inside Ariba Network”
Supplier Portal Navigation · October 12, 2026 · 9 min read · 1,976 words

A supplier logs into Ariba Network, sees the word "Sent" next to an invoice, and assumes things are moving along fine. Three weeks later, nothing has happened, because "Sent" never meant what they thought it meant. That gap between what the screen shows and what's actually true is a structural feature of how Ariba Network is built. The platform runs two separate status systems, routing status and invoice status, and both borrow the same handful of words to describe completely different events. "Sent" in one layer means the network forwarded a document. "Sent" in the other means the buyer hasn't acted yet. APA Corporation's own supplier guidance tells suppliers they can track invoices during approval and get status updates, which sounds like a complete system, but the guidance never draws a line between the two layers, so suppliers end up treating a routing confirmation as proof that progress happened, when the invoice might still be sitting untouched in the buyer's queue.

What routing status tracks and its four codes

Routing status covers one thing only: what the Ariba Network itself did with the document on its way from the supplier's system to the buyer's. It has nothing to say about what the buyer thinks of the invoice, whether anyone opened it, or whether it's anywhere near approval. Think of routing status as a tracking number for a package. It tells you the truck moved, not whether anyone signed for it.

The Ariba Network Invoice Guide documents four routing status codes, and they map onto the natural life of a submission in order. Failed means the invoice broke one of the buyer's invoicing rules, so the buyer will never receive it, and the supplier needs to fix the problem and resubmit. Queued means the network has the invoice in hand but hasn't processed it yet. Sent means the network has placed the invoice into a queue, waiting for the buyer's system to come pick it up. Acknowledged means the buyer's system confirmed it received the transmission.

Acknowledged is as far as routing status goes. It's the ceiling, not a midpoint. A supplier staring at "Acknowledged" has confirmed the document physically arrived somewhere on the buyer's side. Nothing about approval, review, or payment has started yet, and the routing layer has no further codes to tell you otherwise.

What invoice status tracks and its codes

Invoice status picks up exactly where routing status runs out of information. It tracks what the buyer does, or doesn't do, once the invoice lands, and each code corresponds to a real step inside the buyer's own approval and payment workflow.

The Ariba Network Invoice Guide and NiSource's supplier guide both lay out the same core codes. Sent means the buyer has the invoice but hasn't yet checked it against the purchase order or the receipts. Approved means the buyer matched the invoice against the PO or contract and the receipts, and cleared it for payment. Rejected means the buyer turned it down, and the supplier needs to find out why and either fix it or dispute it. Paid means the buyer ran a payment and transmitted an update back through either an Invoice Status Update message or a Remittance message, which happens only when the buyer's system is configured to trigger that update off the invoice. The SAP Community has discussed this exact mechanic: invoice status should flip to Paid after a payment run, provided the buyer actually sends one of those two messages. In practice, it's usually the Remittance message, not the Invoice Status Update, that does the work of marking something Paid.

Invoice status can say "Sent," and routing status can say "Sent," at the very same time, about the very same document. One "Sent" means the network moved the file. The other "Sent" means the buyer hasn't touched it yet. Same word, two different systems, two different meanings. The Campbell's Company's own Ariba Invoice Guide treats these as separate fields suppliers can view, and even notes that Invoice Status wasn't yet turned on for Campbell Soup at the time of the guide, with plans to add it later. That alone says something: even the buyers running Ariba don't always have both layers switched on from day one.

Workbench and Outbox in reading status

A supplier needs to know where in Ariba's interface to look for routing status and invoice status. The Ariba Network Supplier User Guide points to the Outbox as the main place to track invoice status, and it lets suppliers filter by invoice state right there. The Outbox, despite its name, is really the transmission-layer view. It's where routing status for submitted documents lives.

The Workbench works a little differently: it defaults to showing only recent invoices, and anything older drops out of view unless the date filter gets manually widened, with a ceiling even then. Past that ceiling, the only way to find an older invoice is searching by its exact invoice number.

NiSource's supplier guide walks through the practical path: start in the Workbench, find the invoice, then drill into the invoice detail. That detail record is the one place where both layers show up side by side, routing status and invoice status together. That's the full picture, and it's the only screen in Ariba where a supplier can read both halves of the story at once.

Three structural reasons why "Approved" does not mean payment is imminent

Seeing "Approved" on an invoice confirms the buyer signed off internally. It does not mean a check is in the mail, or that payment is a day away, because three separate configuration choices, each one controlled by the buyer and not the supplier, sit between approval and cash actually moving.

Payment remittance is optional on the buyer's end. Not every buyer sends remittance advice or pushes a payment status update back into Ariba Network. Whether an invoice status ever reaches "Paid" depends on whether that particular buyer configured their system to send that message. Some never do, and the invoice simply stays frozen on "Approved" forever, even after the money has actually moved.

AribaPay tracking stops short of the finish line too. SAP's Tracking Payments documentation (version 2511) spells out that the "Funds Sent to Supplier" stage only confirms the AribaPay provider transmitted funds toward the supplier's bank. It says nothing about whether the bank actually credited the account. A supplier staring at "Funds Paid" inside AribaPay still has to check their own bank statement to know if the money landed.

The Invoice Status Portal has its own visibility gate. SAP's ISP documentation (version 2511) confirms the portal only displays invoices received after the buyer turned the portal on, and an invoice stays invisible on it until the buyer has already approved or rejected it. That means the exact invoices a supplier most wants eyes on, the ones still sitting in the approval queue, are the ones the ISP won't show until a decision has already been made. These three constraints are configuration choices that vary from buyer to buyer. That is why the same Ariba Network experience can feel completely different depending on who's on the other end of the trading relationship.

Matching failures and account data problems in the status trail

Most invoices that stop moving haven't vanished into a black hole. They're stuck for a specific, diagnosable reason, and the status trail usually hints at what that reason is if a supplier knows how to read it.

Ariba matches every invoice against purchase orders, contracts, and receipts, using rules the buyer sets. Fail that match, and the invoice bounces back to the supplier marked Rejected. A Rejected status is genuinely actionable: review the rejection reason, fix whatever triggered it, resubmit. The rejection reason only shows up if the buyer's system transmits it.

A trickier case is an invoice parked on "Sent" (invoice status, not routing status) for days or weeks with no movement toward Approved or Rejected. That pattern often means the invoice is queued behind a PO receipt that hasn't been confirmed yet on the buyer's side, a condition the status codes themselves never spell out directly. Severn Trent's supplier guide, published January 2025, tells suppliers to contact the buyer's P2P team directly when status stalls out. That's a buyer telling its own suppliers that the platform won't always untangle the ambiguity by itself.

The structural confusion between routing and invoice status is exactly the kind of operational blocker collections teams run into while chasing payment, suppliers reporting progress that never actually happened, or teams unable to pin down the real hold-up. A tool that integrates directly with Ariba Network parses both layers automatically and only escalates when genuine buyer action is actually needed, cutting through a lot of that noise before it wastes anyone's afternoon.

How the Invoice Status Portal changes what suppliers see

The Invoice Status Portal is a real step forward in how buyers communicate status to suppliers, though it carries the same buyer-optional limits that shape the rest of Ariba's visibility.

SAP's ISP documentation (version 2511) lays out the tiles a supplier sees: all invoices, paid, rejected, pending approval, approved pending payment, overdue-approved, overdue-not-approved, and remittances. The overdue tiles earn their keep here. Overdue-approved and overdue-not-approved flag invoices that have aged past their due date, something the standard Outbox view never calls out on its own.

The ISP only exists where the buyer chose to turn it on. A buyer who hasn't configured it doesn't expose this view to suppliers at all, though those suppliers can usually still check invoice status through the SAP Business Network Workbench if there's an existing trading relationship in place. The ISP sits on the buyer's side of the fence: it's a buyer-hosted, ERP-synced interface. The data inside it is only as fresh as whatever the buyer's ERP last pushed over. A supplier checking the ISP is looking at a mirror of the buyer's own system, polished up, but still only as current as the last sync.

Status tracking limits and outbound follow-up

Ariba's status system answers most questions a supplier has, but for a meaningful slice of invoices, knowing the status still isn't the same as knowing what it will take to get paid. CUT

When the ISP isn't configured, remittance never goes out, and invoice status never updates to "Paid," the only move left is direct outreach to the buyer's AP team. Solvay's own supplier tracking page shows how this plays out on the buyer side: it routes suppliers to pick the specific Solvay entity they invoiced, then sends them down an entity-specific process from there. Status resolution, in other words, often runs through a buyer's particular procedures.

For a supplier juggling invoices across a dozen buyers, each with its own portal settings, its own remittance habits, and its own escalation path, the work of tracking status buyer-by-buyer adds up faster than any finance team can hire for. Since invoice status partly depends on whether the buyer's system is configured to transmit payment updates through an Invoice Status Update or a Remittance message, a supplier chasing payment might see a stalled status for no reason other than the buyer never set up that broadcast. Collections platforms that physically log into Ariba on a supplier's behalf can surface exactly that kind of configuration gap and chase the real blocker instead of leaving the supplier to guess at an incomplete signal. That's the specific layer a managed AR team handles: once status stalls and portal navigation itself becomes the obstacle, the team logs into systems like Ariba and Coupa directly, handles submissions, chases approvals, and escalates, without the supplier ever needing to sign in. The Enterprise tier covers supplier portal management across Coupa, Ariba, and Tipalti, plus contact discovery for invoices that have gone quiet, which is the operational half of the equation that understanding Ariba's status codes only gets a supplier halfway through.

Sources

  1. How to View Invoice Details/Status & Payment Status on the Ariba Network (AN)
  2. Track Your Invoice - Our Suppliers
  3. Ariba Invoicing Support - APA Corporation
  4. A SUPPLIERS GUIDE TO SAP ARIBA V5.1 January 2025

More in Supplier Portal Navigation