Duplicate payments in Sage Intacct: what it checks and what gets through

What Sage Intacct checks for you

Duplicate-number control in Sage Intacct is set in Accounts Payable configuration. For bills, checks or adjustments assigned duplicate numbers, the setting offers Show warning, Do not allow transactions to be created, or Do nothing. Treat those choices as different controls: Do not allow transactions to be created is a hard block, Show warning is an advisory that an AP clerk can override, and Do nothing leaves the check off. Bills and adjustments are checked per vendor, so the control is narrower than a full duplicate-payment review.

The setting checks duplicate numbers. It does not turn every repeated economic event into a warning. A vendor, amount and date match is a review technique you run, not something the duplicate-number setting does for you. When you export data for that review, the supplier invoice number is the Bill number, so the Bill number column is the string you normalize and compare.

Accounts Payable reports in Sage Intacct include AP Ledger, Bills analysis, Bills register, Vendor aging and Vendor list. Those reports give you a population to review and a way to inspect vendor records, but the duplicate-number setting remains a number check. If vendor reconciliation is enabled, a Vendor reconciliation report matches payments and credits to bills; it is not a reconciliation against the supplier's own statement. That distinction matters because a clean vendor reconciliation can still sit beside an unreconciled supplier statement.

What gets through

Re-keyed invoice numbers are a common miss. One clerk enters the supplier invoice as INV-1043; another enters the same invoice as 1043. A duplicate-number check compares the bill number as entered, and those are different strings. If the setting is Show warning, even an exact repeat can be overridden; if it is Do nothing, no warning appears; if it is Do not allow transactions to be created, it blocks the exact duplicate number but not the re-keyed variant.

The same supplier set up twice defeats a per-vendor check. Because bills and adjustments are checked per vendor, the same invoice number entered under two vendor records is not a duplicate number for one vendor. The payment can go out against the second record while the first bill remains paid. Vendor list review is where you look for duplicate vendor records before they split your payment history.

Statements paid as well as invoices get through because the statement usually carries a statement reference, not the invoice number. The duplicate-number check has no matching bill number to compare. Paying a statement without first matching it to open bills can therefore pay INV-1043 twice: once as the bill and once inside the statement. Supplier statement reconciliation, separate from the Vendor reconciliation report, is the control for that exposure.

Re-sent or repeated payment runs are another path. A payment run can pay the same bill again, and the duplicate-number setting is not a payment-to-bill match. If vendor reconciliation is enabled, the Vendor reconciliation report matches payments and credits to bills, which helps you see the double payment, but it is not a reconciliation against the supplier's own statement. Review the payment run against the bills it intends to pay before release.

Finding duplicates already paid

Start with the AP Ledger and Bills register, then export the detail you need. The supplier invoice number is the Bill number in the export, so normalize it before matching: treat INV-1043 and 1043 as candidates for the same invoice, not as two unrelated bills. Match on vendor, amount and a date window, then investigate exact pairs. A number-only pass will miss the re-keyed pair; a vendor-amount-date pass will surface it.

Use Vendor list to find the same supplier recorded twice, and use Vendor aging and Bills analysis to see what remains open after payment. If vendor reconciliation is enabled, run the Vendor reconciliation report to match payments and credits to bills. Remember that this report is not a reconciliation against the supplier's own statement, so it does not replace the statement work.

For each candidate, pull the bill, the payment, the remittance advice and the supplier statement. If the supplier was paid twice, ask for a credit back and track it until it is applied or refunded. If the duplicate sits as an open credit, apply it to the next bill rather than leaving it unapplied. A duplicate review is a recovery exercise and should end with a clear disposition for every candidate: valid payment, duplicate to recover, or item to escalate.

Worked situation: the same supplier invoice is entered as INV-1043 and later as 1043. Both are paid. The duplicate-number setting may not flag the second because the bill numbers differ. A review that matches vendor, amount and a date window brings the pair together; the supplier statement then confirms whether both payments cleared. The recovery step is to request a credit back for the duplicate.

Preventing the next one

Choose a duplicate-number setting you can enforce. Do not allow transactions to be created is the strongest of the three choices because it stops the exact duplicate number from becoming a bill, check or adjustment. Show warning only works if AP has a written override rule and someone reviews overrides. Do nothing is only defensible when a separate duplicate review runs on a fixed schedule.

Standardize invoice capture before the bill is saved. Enter the supplier invoice number as the Bill number and normalize prefixes and punctuation in your review file so INV-1043 and 1043 land on the same candidate list. Do not let a statement reference stand in for the invoice number; match the statement to the underlying bills first. Keep vendor names consistent enough that a vendor-amount-date match does not split the same supplier across two spellings.

Clean the vendor master with Vendor list. Look for the same supplier set up twice, because the per-vendor duplicate check cannot see across two vendor records. Before a payment run is released, compare the run to the bills it is paying and confirm that no bill was already paid in an earlier run. After payment, reconcile the supplier statement, not just the Vendor reconciliation report, and ask for credits back when a duplicate is confirmed.

If vendor reconciliation is enabled, use the Vendor reconciliation report as one input: it matches payments and credits to bills. Pair it with supplier statement reconciliation so a payment matched to a bill in Sage Intacct is also matched to the supplier's own record. The goal is not a one-time cleanup; it is a repeatable close routine that catches re-keyed numbers, duplicate vendor records and statement payments before they become recoveries.

Questions