Duplicate payments in NetSuite: what it checks and what gets through

What NetSuite checks for you

NetSuite has one preference that directly addresses duplicate invoice numbers: Duplicate Number Warnings under Setup > Accounting > Preferences > Accounting Preferences. It can be set to No Warnings, Warn (UI only) or Warn and Block. At No Warnings, no warning appears. At Warn (UI only), the warning is in the UI only and does not block the entry. At Warn and Block, the entry is blocked.

Warn and Block covers vendor bills and vendor credits, among other transactions, and compares a number with other records of the same type. If a vendor bill carries Reference No. INV-1043 and a second bill is entered with the same Reference No. INV-1043, the preference can block the second entry. The comparison is on the number itself, so spelling, spacing and prefixes matter.

The standard payables reports include A/P Aging Summary and Detail, A/P Register, A/P Payment History by Bill, A/P Payment History by Payment and Open Bills. Saved searches give custom lists of bills. When you export bills, the supplier invoice number is in Reference No., so keyed numbers can be compared with what the supplier printed.

What gets through

Most duplicates that get through are not exact number repeats. A clerk reads INV-1043 on the supplier invoice and keys 1043 into the bill. The number is different, so Warn and Block on the Duplicate Number Warnings preference finds no match. The same happens when a clerk adds a prefix, drops a leading zero or adds a PO reference to the invoice number. The bill is a real record in NetSuite, but it is the same supplier invoice.

A second common cause is the vendor record. The same supplier is set up twice, once under a trading name and once under a legal name, or under two remit-to addresses. The invoice is entered against the second record, and the duplicate check on the invoice number does not see the first bill because it sits under a different vendor. The payment goes out, and the supplier statement later lists two payments for one invoice.

Statements paid as invoices are another route. A supplier statement lists several open invoices and a total. If a clerk enters the statement total as a vendor bill, the underlying invoices can be paid again when they are entered or when the next payment run includes them. Re-sent payment runs cause the same damage: a run is released, the file is re-sent or the batch is rebuilt, and the same bills are paid a second time before the first payment is reconciled. Warn (UI only) adds a warning at entry, but the clerk can click past it.

Finding duplicates already paid

Start with the payment side. The standard payables reports include A/P Payment History by Bill, A/P Payment History by Payment and A/P Register. Pull the payment data into a working file and match on vendor, amount and a date window you set. Exact amount matches for the same vendor are the first filter. Then look for the same supplier invoice number in Reference No., including variants such as INV-1043 and 1043. If you export bills, the supplier invoice number is in Reference No., so the comparison is direct.

Next, match bills to payments, not just payments to payments. A bill that remains open while a payment for the same amount has already left is a candidate. The standard payables reports include Open Bills and A/P Aging Summary and Detail, and saved searches give custom lists of bills. Use those lists to sort by vendor and Reference No. A duplicate vendor record makes this harder: the same supplier can appear twice, so search by remit-to details and by the invoice number rather than by vendor name alone.

Then reconcile statements. A supplier statement is a list of invoices, not an invoice. Compare each statement line to a bill and to a payment. If a statement total was entered as a bill, you will see the same underlying invoices paid twice or a large open bill that does not match any single supplier invoice. If a vendor credit is sitting unapplied while the related bill was paid in full, treat that as recoverable money and ask the supplier to apply the credit or return it. Keep a simple log: vendor, invoice number from Reference No., payment date, amount and the action requested.

Preventing the next one

Set Duplicate Number Warnings to Warn and Block for vendor bills and vendor credits rather than Warn (UI only). A warning that can be clicked past is not a control at month-end. Warn and Block stops exact number repeats and covers vendor credits as well as bills. It will not stop a re-keyed number, so pair it with a keying standard: enter the supplier invoice number exactly as printed and put it in Reference No., with no prefixes, no PO text and no invented suffixes.

Clean the vendor master before the next payment run. Search for suppliers with the same remit-to address, the same contact or near-identical names, and consolidate the duplicate record in your ERP. When a new supplier is requested, check the existing vendor list first. A duplicate vendor record defeats invoice-level matching because the same supplier invoice can sit under two vendor names.

Separate statements from invoices in the AP process. A statement is reconciled, not entered as a bill. Before releasing a payment run, confirm the prior run has been reconciled and that no bills from it remain in the next selection. If a duplicate is found after payment, contact the supplier promptly, ask for a credit or refund, and apply the credit to the vendor account. A duplicate payment recovered as a credit is still recovered money.

Questions