Duplicate Payments in Corpay Complete

This article explains how Corpay Complete identifies and manages duplicate payments in the system.

Duplicate payments are identified when a payment file is uploaded to Corpay Complete. A payment is considered a duplicate if the following fields match between an existing payment and a newly uploaded payment. Note that all fields may not be available on every payment, but if the available fields match between the two payments, it is considered a duplicate.

• Invoice Number – This field shows the invoice number associated with the payment.
• Invoice External ID – This field shows the ID assigned by the customer's ERP for the related invoice.
• Vendor Number – This field shows the customer-provided vendor ID.
• Vendor Location Number – This field shows displays the customer-provided vendor location ID.
• Payment Reference Number – This field shows the customer’s payment reference number or their internal payment ID.
• Original Amount – This field shows the original invoice amount and is used for duplicate payment validation, as discounts can impact the net amount. If the Original Amount is not provided in the payment file, then the Net Amount will be used for matching purposes.

If a duplicate payment is detected, Corpay Complete creates an existing duplicate exception listing the duplicated items. Fields left empty are excluded from duplicate validation.

Duplicate Payment Examples

Example One

A payment file is submitted, containing the Invoice Number, Vendor Number, and Vendor Location Number.

• The Invoice Number matches an existing payment.
• The Vendor Number matches an existing payment.
• The Vendor Location Number matches an existing payment.

The uploaded payment file will trigger an existing duplicate exception.

Example Two

A payment file is submitted, containing the Invoice Number, Invoice External ID, Payment Reference Number, and Original Amount.

• The Invoice Number matches an existing payment.
• The Invoice External ID matches an existing payment.
• The Payment Reference Number matches an existing payment.
• The Original Amount matches an existing payment.

The uploaded payment file will trigger an existing duplicate exception.

Non-Duplicate Payment Examples

Example One

A payment file is submitted, containing the Invoice Number, Vendor Number, and Vendor Location Number.

• The Invoice Number matches an existing payment.
• The Vendor Number matches an existing payment.
• The Vendor Location Number does not match an existing payment.

The payment file is not a duplicate since not all fields matched.

Example Two

A payment file is submitted, containing the Invoice Number, Vendor Number, Invoice External ID, and Original Amount.

• The Invoice Number matches an existing payment.
• The Vendor Number matches an existing payment.
• The Invoice External ID matches an existing payment.
• The Original Amount does not match an existing payment.

The payment file is not a duplicate since not all fields matched.