← Back to all resources

Coupa troubleshooting

Coupa duplicate invoice number: check the original before resubmitting

Troubleshoot a duplicate invoice number in Coupa without creating a duplicate receivable. Find the original invoice and agree the correction path with AP.

LedgerUp team · Updated

When Coupa reports a duplicate invoice number, find the original invoice for that customer before trying a different number. The charge may already be submitted or approved. If the original is wrong, agree its correction, void, or credit treatment with the buyer before sending a replacement; renumbering the same charge can create two payable invoices.

Buyer settings, document status, and country-specific invoice rules vary. Follow the rejection message and your customer’s supplier instructions. This guide explains checks and escalation, not permission to bypass buyer approvals.

Why this happens

A duplicate warning can result from two team members submitting the same billing record, a retry after a slow response, or a number reused from an earlier invoice. The invoice number is a control, not a cosmetic field. Treat the warning as a reconciliation task between your billing system, the portal, and the buyer’s records.

How to investigate and resolve it

  1. Search the original number. In the correct customer view, look for the invoice number and compare dates, amounts, currency, and PO references. Check your AR system and any submission confirmation.
  2. Read the original status. Determine whether the original is a draft, submitted, approved, disputed, or otherwise closed. An invoice that is awaiting approval is not a reason to send the same charge again.
  3. Confirm whether it is the same charge. Compare the service period or delivery evidence, not just the total. Two legitimate invoices may have accidentally shared a number; one invoice may also have been submitted twice.
  4. Agree the correction with AP. If the original is incorrect, follow the options available for that document and country. Ask whether a credit note, void, or replacement is required. Do not assume every submitted invoice is editable.
  5. Reconcile the replacement. Use the invoice number and references approved for the correction. Link the records in your AR system and check that the buyer is not processing both originals and replacements for payment.

What the supplier can fix—and what the buyer must confirm

Supplier: Find the source billing record, coordinate team ownership, and ensure each legitimate charge has the appropriate unique invoice identity.

Buyer: Confirm how the original is recorded and which correction process is accepted. AP should resolve ambiguous payable status before a replacement is issued.

Example: choosing the right next action

An operator submits invoice INV-1042, then a colleague tries again because the page was slow. The second attempt reports a duplicate. If the first invoice is already pending approval, the next step is status tracking, not creating INV-1042-A.

A message you can send to AP or procurement

Coupa reports invoice [number] as a duplicate. We found [original status] against PO [number] for [amount and currency]. Please confirm whether the original is in your payable records and, if a correction is needed, the required cancellation or credit and replacement process.

How to confirm the issue is resolved

Before retrying, confirm that the source of the rejection has changed—not only that you can press Submit. Keep the original and correction references linked in your AR records. After submission, inspect the document’s status and any buyer response. An accepted submission is not the same as approval or payment; if the invoice is rejected again, preserve the new reason and ask the responsible owner to address it.

Frequently asked questions

Can I add a suffix to bypass the duplicate check?

Not as a shortcut. First establish whether the charge already exists; a suffix can make a duplicate look like a new invoice.

Does a duplicate warning mean we have been paid?

No. Check the original invoice and payment records separately. Submission, approval, and payment are different events.

Prevent the same exception next time

Keep a customer-specific invoice checklist with required fields, documents, approvers, and correction rules. Before each submission, compare the source invoice, PO, and supporting evidence. Give one person or process clear submission ownership and track status changes so a rejected invoice does not disappear from follow-up.

For the full submission flow, use the supplier guide below. For recurring portal work, LedgerUp’s procurement portal automation is a separate option to explore; the buyer still controls order changes and approvals.