How to Submit an Invoice in the Coupa Supplier Portal

To submit an invoice in Coupa, log in to the Coupa Supplier Portal, open the purchase order your customer issued, click the create invoice icon (the gold coins) to flip the PO into a draft invoice, add your invoice number, date, tax detail, and any required attachments, then submit. Coupa routes the invoice to your customer for approval and shows you the status at every step. The portal is free for suppliers, and once your account is linked to your customer you can invoice, track approvals, and see payment information without emailing anyone.

This guide walks through the whole flow from the supplier side: registering, linking your account to a customer, the PO flip, invoicing without a PO where your customer allows it, the fields that most often cause rejections, what each invoice status means, and what to do when an invoice comes back disputed. If your customer runs SAP Ariba instead, see the companion guide on how to submit an invoice in SAP Ariba.

What the Coupa Supplier Portal is

The Coupa Supplier Portal (CSP) is the free web portal Coupa provides to suppliers whose customers run Coupa for procurement and accounts payable. When a large customer tells you they "require invoices through Coupa," this is what they mean: instead of emailing a PDF to accounts payable, you submit the invoice electronically through the portal (or one of the alternatives below), and it lands directly in their approval workflow.

From your side of the portal you can see the purchase orders your customer has issued, create and submit invoices and credit notes, check invoice and payment status, and manage your company profile, remit-to addresses, and users. One CSP account can serve multiple Coupa customers, so if three of your enterprise accounts all run Coupa you manage them from a single login.

Coupa does not charge suppliers to use the CSP. There is no per-invoice fee, no subscription tier, and no transaction percentage. If someone contacts you claiming you must pay to invoice through Coupa, treat it with suspicion and verify with your customer.

Registering and linking your account to your customer

You cannot simply sign up and start invoicing any company. Your access to a specific customer's POs and invoicing comes from a connection that the customer initiates or approves. The standard path:

1. Receive the invitation. Your customer sends an invitation email from Coupa asking you to join the CSP. Click the link and create your account (or log in if you already have one from another customer). If you never received an invitation, ask your customer's procurement or AP contact to send one; that request usually cannot be initiated from your side.
2. Complete your profile. Fill in your company details, tax registration information, and remit-to address. Some customers require you to complete an onboarding form or provide banking details before they will accept invoices.
3. Set up a legal entity. Before the CSP will let you create electronic invoices, you need to add a legal entity under Setup (Admin), including at least one remit-to address and your tax or VAT registration where applicable. This is what Coupa stamps onto your invoices to make them valid billing documents.
4. Confirm the customer link. Once connected, the customer appears in your customer selector, and their POs show up under Orders. If you already had a CSP account, an invitation from a new customer links that customer to your existing account rather than creating a second one.

Details of onboarding vary by buyer: some customers require order confirmations or advance ship notices before invoicing, and some restrict which invoice types you can send. When in doubt, check the supplier guide your customer published or ask their supplier enablement team.

The PO flip: creating an invoice from a purchase order

The PO flip is the core move in Coupa invoice submission: you take the purchase order your customer issued and "flip" it into an invoice, so the line items, prices, part numbers, and billing details carry over automatically. It is both the fastest method and the one least likely to be rejected, because the invoice starts out matching the PO by construction.

1. Log in to the CSP and select the right customer if you serve more than one Coupa buyer.
2. Open the Orders page and find the PO you are billing against. Confirm the PO number matches the order you fulfilled.
3. Click the create invoice icon on the PO row (shown as a stack of gold coins), or open the PO and choose Create Invoice. Coupa generates a draft invoice pre-populated from the PO.
4. Choose your invoicing details. Select the legal entity, remit-to address, and ship-from address you set up earlier. For your first invoice, Coupa will prompt you to create these if they do not exist yet.
5. Enter your invoice number and date. The invoice number must be unique for that customer; reusing a number is a common rejection cause.
6. Review the lines. If you are billing the full PO, leave the quantities and amounts as they carried over. For a partial invoice, reduce quantities or amounts to what you actually delivered, and delete lines you are not billing yet. Do not increase amounts above the PO; overbilling triggers a mismatch on the customer side.
7. Add tax detail. Enter the tax rate or amount at the level your customer requires (invoice level or line level). Tax handling is buyer-configured and country-dependent, so follow the fields Coupa presents.
8. Attach supporting documents if required. Some customers require a PDF copy of the invoice, timesheets, proof of delivery, or a service acceptance document. Missing required attachments is another frequent rejection cause.
9. Submit. Coupa validates the invoice, sends it into your customer's approval workflow, and the invoice appears under Invoices with a status you can track.

Once submitted, an invoice cannot be edited. If you spot an error after submission, you will need to work through the dispute or credit note process described below, so it pays to review the draft carefully.

For services, the flow may include an extra step: some buyers require a service sheet (a record of hours or milestones) to be submitted and approved before you can invoice against the PO. If the Create Invoice option is unavailable on a service PO, an unapproved or missing service sheet is the usual reason.

Invoicing without a PO

Some Coupa customers allow invoices that do not reference a purchase order, often for utilities, subscriptions, legal fees, or other spend that is not managed through POs. Whether this option exists at all depends on how your customer has configured Coupa; many buyers enforce a strict no-PO-no-pay policy and will reject any unbacked invoice.

Where it is allowed, you create the invoice from the Invoices page (Create Blank Invoice or similar), select the customer, and enter lines manually instead of flipping a PO. You will usually need to supply a requester name or email on the customer side so the invoice can be routed to someone for approval. Expect slower approval than a PO-backed invoice, because a human has to claim and code it.

If you regularly deliver against a customer who has not issued a PO, the better fix is upstream: ask your contact to raise a PO before work starts. It protects you contractually and makes every subsequent invoice a clean two-way match.

Fields that commonly cause rejections

Most Coupa invoice rejections trace back to a handful of fields. Before you hit submit, check:

• PO number. The invoice must reference the correct PO, and the PO must be open with remaining balance. Invoicing a closed or fully billed PO fails.
• Quantities and amounts matching the PO. Unit prices above the PO price, quantities above what remains uninvoiced, or totals that exceed PO tolerance will be flagged or rejected. Currency must match the PO currency.
• Unique invoice number. Duplicate invoice numbers for the same customer are rejected automatically.
• Tax detail. Missing tax lines, an unexpected tax rate, or tax applied at the wrong level (line versus header) are among the most common failures, especially for VAT-country invoices.
• Required attachments. If your customer requires a PDF invoice image, delivery note, or approved service sheet, the invoice will sit or be rejected without it.
• Legal entity and remit-to information. The invoice-from and remit-to details must be set up in your legal entity, and for tax-compliant countries they must match your registration data.
• Line item descriptions and part numbers. Some buyers validate part numbers or require matching line descriptions between the PO and the invoice.

Exact validations vary because each buyer configures their own tolerances and required fields. If the same rejection keeps recurring, ask your customer's AP team which validation is firing; the reason shown in the portal comment is usually specific.

Compliant e-invoicing countries

In many countries an invoice is a regulated tax document, and Coupa operates a compliant e-invoicing framework covering more than 50 countries. When your legal entity is registered in one of these countries, Coupa validates country-specific requirements (tax fields, invoice numbering, required registration data) before issuing the invoice, and in some jurisdictions the legally binding invoice is the one generated inside Coupa rather than any PDF you attach.

Practical implications for suppliers: set up your legal entity with the correct VAT or tax registration for the country you invoice from, expect a few extra mandatory fields on the invoice form, and in clearance-model countries (where invoices must pass through a government platform) expect your customer to give you country-specific instructions. If you invoice from multiple registrations, create a legal entity for each.

Coupa invoice statuses explained

After submission, the Invoices page shows where each invoice sits. The statuses you will see most often:

Watching Coupa invoice status is how you replace the "just checking on our invoice" email: if an invoice sits in Pending Approval past the normal window, or flips to Disputed, you know exactly which document needs a follow-up and why.

What to do when an invoice is disputed or rejected

A dispute is not a dead end; it is your customer telling you what to fix. The flow:

1. Open the disputed invoice and read the dispute reason and comments. Buyers usually state the specific problem: wrong price, over-quantity, missing tax, missing attachment.
2. Choose the correction path. Depending on the reason and on country compliance rules, Coupa offers options such as voiding the invoice (if it was submitted in error or duplicated), creating a corrected invoice, or issuing a credit note that adjusts or cancels the original and then re-invoicing correctly. In compliant e-invoicing countries, the credit note path is often mandatory because issued invoices cannot simply be edited.
3. Fix the root cause. If the dispute came from a price or quantity mismatch, check whether the PO itself is outdated. Sometimes the right resolution is asking your customer to update the PO rather than lowering your invoice.
4. Resubmit and track. The corrected invoice goes through the same approval flow. Use a new invoice number if you voided the original.

Disputes cost real time: each one adds days to payment. If a meaningful share of your invoices to one customer gets disputed, the pattern (tax setup, stale PO prices, missing attachments) is usually fixable once, at the source. Persistent disputes on portal invoices are also one of the quiet drivers of high DSO on enterprise accounts; pairing clean submissions with systematic follow-up (see the dunning docs) is how AR teams keep portal receivables from aging.

SAN: invoicing from the PO email without a portal account

Coupa also supports Supplier Actionable Notifications (SAN), an email-based alternative for suppliers who do not want to maintain a portal login. If your customer has enabled SAN, the PO email you receive contains action buttons: acknowledge the order, create an invoice, or add a comment, directly from the email. Clicking Create Invoice opens a Coupa invoice form pre-filled from the PO, no CSP account required, and you still receive follow-up emails when the invoice is approved, disputed, or paid.

SAN works well for low-volume relationships: a handful of POs a year, one person handling billing. Its limits show at scale. You depend on the PO email surviving your inbox, you have no consolidated view of invoice statuses across orders, and multi-user AR teams cannot share access cleanly. Most suppliers with recurring enterprise volume end up on the full CSP, or automate the flow entirely.

When you should stop doing this by hand

Everything above is manageable for a few invoices a month. It stops being manageable when portal invoicing becomes a job: an AR person logging into Coupa, Ariba, and three other portals, matching POs to invoices line by line, re-keying data the billing system already has, then checking statuses daily and chasing disputes. Finance teams that submit dozens of portal invoices monthly almost always automate this, either with scripts they maintain themselves or with an agent built for it.

LedgerUp's approach: Ari, LedgerUp's AI agent, monitors your AR inbox for POs and portal notifications, matches each PO to the right invoice in your billing system, logs into the portals with credentials you provide, submits the invoice (PO flip included), and tracks status changes, surfacing approvals and disputes in Slack instead of making someone poll the portal. Teams using it save about 15 hours per month on portal submissions and see a 13-day average DSO reduction on portal invoices, mostly because invoices go in correct the first time and disputes get caught the day they happen. See procurement portal automation for the product overview and the procurement portal docs for how the workflow runs, or the broader contract-to-cash guide for where portal invoicing sits in the full AR cycle.

If your volume is a few invoices a month, skip the automation and just use the checklist in this guide. The point of the CSP is that it is free and reliable; the point of automating it is only reached when the hours add up.

Frequently asked questions

Is the Coupa Supplier Portal free?

Yes. Coupa does not charge suppliers to register for or use the Coupa Supplier Portal. There are no subscription tiers, per-invoice fees, or transaction percentages for suppliers. Be wary of any third party claiming you must pay to invoice a Coupa customer.

What is a PO flip in Coupa?

A PO flip is creating an invoice directly from the purchase order, so the PO's line items, prices, and billing details carry over into the invoice automatically. In the CSP you do this by clicking the create invoice icon (gold coins) on the PO row. Because the invoice starts out matching the PO, flipped invoices are far less likely to be rejected than manually keyed ones.

Why was my Coupa invoice rejected or disputed?

The most common causes are a duplicate invoice number, prices or quantities that exceed the PO, missing or incorrect tax detail, missing required attachments (PDF image, delivery note, or approved service sheet), invoicing a closed PO, or legal entity data that does not match your tax registration. The dispute reason shown on the invoice usually names the specific problem.

How long does Coupa invoice approval take?

It depends on the buyer, not on Coupa. Once submitted, the invoice enters your customer's internal approval workflow, and that can run from same-day (clean PO-backed invoices with auto-matching) to weeks (invoices requiring manual review or exception handling). A PO-flipped invoice that matches the PO exactly approves fastest. If an invoice sits in Pending Approval unusually long, contact your customer's AP team.

Can I edit an invoice after submitting it in Coupa?

No. Once submitted, an invoice cannot be edited. If it contains an error, wait for your customer to dispute it (or contact them to dispute it), then resolve via a corrected invoice or credit note, or void it where allowed and submit a new invoice with a new number. Only draft invoices can be edited freely.

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

Only if your customer has enabled non-PO invoicing. Many buyers enforce no-PO-no-pay and reject any invoice without a PO reference. Where it is allowed, you create a blank invoice in the CSP, enter lines manually, and usually name a requester on the customer side for routing. If you deliver regularly without POs, ask your customer to start issuing them; it speeds up every approval.

What do the Coupa invoice statuses mean?

Draft means not yet submitted, Processing means Coupa is validating it, Pending Approval means it is in your customer's approval workflow, Approved means it is cleared for payment, Disputed means your customer flagged a problem and sent it back, Voided means it was cancelled, and Abandoned means a disputed invoice your customer does not want resubmitted.

What is SAN (Supplier Actionable Notifications) in Coupa?

SAN lets you act on a Coupa PO directly from the PO email, including creating and submitting an invoice, without registering for a CSP account. You still receive email updates when the invoice is approved, disputed, or paid. It suits low-volume suppliers; higher-volume teams get more from the full portal or from automating submissions.

Can one CSP account serve multiple customers?

Yes. A single Coupa Supplier Portal account can be linked to every customer of yours that runs Coupa. Each new customer sends an invitation that links to your existing account, and you switch between customers inside the portal. Your legal entities and remit-to addresses are set up once and reused.

Does Coupa handle country-specific e-invoicing compliance?

Yes, Coupa supports compliant e-invoicing in more than 50 countries, validating country-specific tax and invoice requirements before issuing the invoice. You need to set up your legal entity with the correct tax or VAT registration for each country you invoice from, and in clearance-model countries your customer may give you additional country-specific instructions.