Payment Status Visibility Inside Coupa Pay for Suppliers
Suppliers must match payment status to their payment method to know whether to wait or take action.

Payment status visibility inside Coupa Pay tells suppliers what happens next only when the status is read with the payment method. A bank transfer can require nothing more than waiting, while a virtual card or digital check requires action to collect the money. The same label is not the same instruction, and knowing the difference keeps a released payment from becoming uncollected cash.
How payment status in Coupa Pay is structured, and why it doesn't mean the same thing for every payment
The Coupa Supplier Portal, or CSP, separates payments into two categories, namely Invoice Payments and PO Payments. Invoice Payments can be made by bank transfer, digital check, or virtual card, while PO Payments are always made by virtual card. That split matters because the method determines how a payment moves from the buyer to the supplier. A shared status label describes a stage, but it does not tell the whole story.
The Payment Released Date provides another anchor. It marks the buyer’s last step in releasing the payment. Reading a status without knowing the method behind it can therefore lead a supplier to wait when action is required, or act when nothing needs doing.
Where to find payment status in the CSP and what the navigation actually shows
Start with the Invoices tab in the main menu, select the customer, and find the invoice row. The Status column is where the invoice’s status appears. Despite its promising name, the Payments tab is not the starting point for that field. The Payments page serves a different job, including managing payment methods and accessing card or check details.
Coupa’s CSP documentation directs suppliers to hover over a Paid status or select the invoice to reveal its Check Number or Transfer Reference. Those references connect the portal record to the payment at the bank. Before the invoice reaches that point, the status identifies its place in the workflow.
Invoice payments also have two remittance views, namely Remittance by Payment # and Remittance by Invoice #. The default, Remittance by Payment #, groups information around the remittance number, while the other view groups it around the invoice number. This changes how multi-invoice payments are presented while leaving the underlying data unchanged. Clicking a Payment Number shows all the payment details, including information for that payment method, virtual card details, and links to download a digital check.
What each invoice status label means before payment is released
Before payment begins, invoice statuses describe the buyer’s internal workflow. Organon and DaVita’s supplier-facing guides explain the labels used during these stages. Draft means the supplier has created the invoice but has not submitted it. Processing means it is transferring to the buyer’s system. Pending Approval / Pending Action means it is waiting for review or approval steps in the buyer’s workflow.
Pending Receipt means confirmation that the goods or services were received is still needed before approval. AP Hold means accounts payable must review the invoice, and the supplier does not need to act until the hold is released. On Hold means review is needed outside AP.
Approved means the buyer has accepted the invoice for payment. Payment Terms determine when payment is due, typically counted from the invoice date or receipt date.
Disputed means the buyer needs changes, and the supplier must settle the dispute before payment can go ahead. Rejected / Voided / Withdrawn means the invoice will not be paid in its current form. The reasons appear in the comments.
What "Payment in Progress" means for a bank transfer, and what the supplier does not need to do
For a bank-to-bank transfer, Payment in Progress is informational. The funds are already moving and will arrive in the supplier’s account within two to three business days. Once the buyer releases the payment, the process passes to the financial institutions involved. The supplier does not need to collect a payment instrument, charge anything, or take another step in the CSP to receive the transfer.
The Payment Released Date marks the end of the buyer’s side, but it is not the value date at the supplier’s bank. For ACH and cross-border transfers, it is normal for those dates to be different. The status alone is therefore not a reason to ask the buyer’s AP team to do something more.
Coupa Pay buyers send remittance notification emails with bank transfer payments, and those emails have the payment details. If the amount or timing is unclear, suppliers should cross-reference the email with the CSP record. Once the status becomes Paid, the Transfer Reference provides the identifier for tracing the payment with the bank if it does not appear as expected. That reference is more useful for a bank query than the status label on its own.
What "Payment in Progress" means for a virtual card, and the action the supplier must take to collect the funds
For a virtual card, Payment in Progress means the buyer has issued a card. The supplier must charge that card through its payment terminal or processor to receive the money. This is the sharp contrast with bank transfer, where release puts the funds in motion without supplier action. Here, waiting does not collect the payment.
The supplier must handle a virtual card for every PO Payment and for Invoice Payments where the buyer has set up payment by card. The CSP is where the supplier can discover the card and access its details, but charging it happens outside the portal.
Coupa’s CSP documentation gives suppliers two ways to obtain card details. They can check the email associated with the CSP account for the details sent by the buyer, or use View Virtual Card on the Payments page. That action button appears in the row only when a supplier card is active. Clicking the Payment Number in the PO Payments strategic view shows all the virtual card details for that PO.
Suppliers who subscribe to Advanced can find Open Virtual Card Balances in the Receivables section of the Transaction Dashboard. This view shows cards whose payments have yet to be fully processed, including those with open balances and those that will expire soon. Its drill-down shows the POs or invoices tied to the card, the total charges, the amount left, and the expiration date. Suppliers need to check this view or the card email because they can collect payment only until the card expires.
What "Payment in Progress" means for a digital check, and how to deposit it
Digital check is a US-only payment method in Coupa Pay. For this method, Payment in Progress means the buyer has issued a check that the supplier must download and deposit using a mobile banking app. Like virtual card, it requires a collection step. Unlike bank transfer, the funds do not arrive automatically just because the buyer has finished.
The Invoice Payments table provides a download button in the row for invoices paid by digital check. The supplier uses it to view and save the digital copy, then deposits the check through mobile banking. Coupa’s CSP Payments documentation treats digital check as its own invoice payment method, with dedicated guidance. The download makes the check available, but depositing it is the action that completes the supplier’s part.
Once the status moves to Paid, hovering over the status or opening the invoice reveals the Check Number. The supplier can use this number to verify the deposit with the bank. It serves the same reconciliation purpose that the Transfer Reference serves for bank transfers.
What the "Paid" status reveals and how to use it for reconciliation
Paid is the shared endpoint of the invoice payment lifecycle, but the supporting detail still depends on the method. For digital checks, the CSP shows the Check Number, and for bank transfers, it shows a Transfer Reference. These identifiers let suppliers match payments in their books or query the bank. The label says the lifecycle has reached its endpoint, while the reference identifies the payment involved.
The remittance breakdown becomes especially useful when one payment covers several invoices. In Remittance by Payment #, clicking the Invoice Numbers opens the Remittance by Invoice # breakdown. This shows each invoice covered by that payment rather than leaving the supplier with only a combined amount. Advanced subscribers can open that breakdown from the All Customers strategic view.
Macquarie makes the payment reference number visible in the CSP with invoice approval, payment status, and payment amount. With these details, suppliers can match payments to their records without having to contact AP. AECOM also identifies real-time tracking of POs, invoice status, and payments from the account dashboard as a CSP benefit for suppliers.
How the free tier and the Advanced subscription determine how much payment visibility a supplier actually has
The free CSP tier limits payment visibility to one buyer at a time. A supplier working with multiple Coupa Pay buyers must therefore query each separately.
Coupa Advanced adds the strategic view, which aggregates payment data across Coupa Pay buyers in near-real time. Subscribers access it by selecting All (Offered by Advanced) in the Select Customer menu. Cross-buyer visibility, one of the most useful features for suppliers managing many customers, sits behind the subscription.
Advanced also has Invoice Payments and PO Payments views that let suppliers see payments across buyers, with advanced filtering and search. Search fields include Payment Number, Invoice Number, Payer, PO Number, and Payment Status, while PO Payments also supports Card Status filtering across buyers. Custom Views let suppliers save configurable table layouts to favorites, and both payment tables support CSV exports of filtered data. The payment history goes back to six months before the Advanced subscription starts.
The Transaction Dashboard adds Receivables tools, including Open Virtual Card Balances and Aging Analysis of Overdue Receivables. Aging Analysis lets suppliers drill down to overdue invoices across buyers, including those who pay outside Coupa Pay. However, buyers with FedRAMP, HIPAA, or legacy Coupa Core privacy configurations may be absent from the strategic view altogether. A buyer that is a federal agency may therefore have no data shown there even with Advanced. Paying for aggregation does not override the buyer’s privacy configuration.
Where status visibility ends and what suppliers should do when the CSP does not have the answer
Organon’s supplier guide warns that payment information may be unpopulated when the invoice payment date is not yet due. An approved invoice can therefore have no payment details to show.
Suppliers on the free tier must still look up each buyer separately, and privacy restrictions can keep a buyer’s data out of the strategic view even with a subscription. With virtual cards, having the details still leaves the supplier at risk of missing payment if it fails to charge the card before it expires. Monitoring Open Virtual Card Balances where available, or the card email, addresses that collection risk.
When the CSP cannot provide a clear answer, the practical escalation route is the buyer’s AP team or supplier helpdesk. DaVita and Organon publish dedicated supplier contact points for that purpose. The useful distinction is whether the supplier is waiting for a transfer, holding an uncollected card or check, or facing a gap the portal cannot explain.


