Duplicate payments in QuickBooks Online: what it checks and what gets through

What QuickBooks Online checks for you

QuickBooks Online has one built-in duplicate warning at bill entry. Under Account and Settings > Advanced > Other preferences, you can turn on a preference that warns when a bill number already used for that vendor is entered again. It warns; it does not stop the bill being saved. That distinction matters: the clerk sees a signal and can still save the bill.

That warning is useful for the simplest case. A clerk enters bill 1043 for a supplier, saves it, and later enters 1043 for the same supplier. The warning appears. If the clerk saves anyway, a duplicate bill now sits in payables. The control is a speed bump, not a locked gate.

QuickBooks Online also gives you standard payables reports to review: Accounts payable aging summary and detail, Bill Payments List, Bills and applied payments, Unpaid Bills, Vendor Balance Detail, Vendor Balance Summary and Transaction List by Vendor. Not every plan includes every report. Use them to pull the population you need to check; they are not a duplicate-payment detector on their own. When you export a list, the supplier invoice number appears as Num, which is the column to normalize and match.

What gets through

Re-keyed invoice numbers are the most common gap. The supplier prints INV-1043 on one copy, and a clerk keys 1043 on a later bill. The warning keys on the bill number you enter. INV-1043 and 1043 are different strings, so the second bill can save without the warning. The same invoice is now in payables twice.

A supplier set up twice defeats the vendor scope. The warning is for that vendor. If the same supplier exists under two vendor records, a bill entered under one record does not warn against a bill entered under the other. Payments can be split across the two records, and neither record looks obviously duplicated on its own.

Statement payments are a frequent source. AP receives a statement, enters the statement total as a bill, and pays it. Later the individual invoices on that statement are also entered and paid. The statement bill may carry a statement date or a reference rather than an invoice number, so the bill-number warning has nothing useful to compare. The payment is a duplicate even though each entry looked reasonable at the time.

Re-sent payment runs get through as a payment-control failure. A run is released, the bank file needs to be sent again, or an approval is reset, and the same bills are paid a second time. The bill numbers did not change, so bill-entry warning is not the safeguard. A second release needs a check against Bills and applied payments before it goes out.

Finding duplicates already paid

Start with the payment side, not only the bill side. Pull Bill Payments List and Bills and applied payments for the period you are reviewing. Add Vendor Balance Detail and Transaction List by Vendor for the suppliers with the most activity. Accounts payable aging summary and detail help you see what is still open, but duplicates already paid will often sit in the payment history, not in the open balance. Export the lists and keep vendor, amount, payment date and Num.

Normalize the invoice number before you match. Make everything uppercase, remove spaces and punctuation, and treat INV-1043 and 1043 as the same supplier invoice. Match on vendor, amount and a short date window rather than an exact date; keying lag and payment timing make exact-date matching miss real duplicates. Review the matches by eye before you call them duplicates, because a supplier can legitimately issue two invoices for the same amount.

Check the vendor master for the same supplier set up twice. Look for supplier names that are close, and for remit-to details that point to the same place. If you find two records, review payments under both for the same invoice number, amount and period. A duplicate vendor record is easy to create and hard to see when each record has its own history.

Reconcile statements to bills and payments. A statement is a list of invoices, not a bill to pay in full without checking. If the statement total was paid as a bill and the invoices on it were also paid, you have a duplicate. Once you find one, ask the supplier for a credit back or an offset against open invoices, and keep the request and the supplier response with the payment record.

Preventing the next one

Turn the preference on, then train clerks to treat it as a stop sign. QuickBooks Online warns when a bill number already used for that vendor is entered again; it does not stop the bill being saved, so the behavior after the warning is the control. A clerk who clicks through the warning without checking the vendor, amount and prior payment has defeated the only built-in duplicate warning.

Keep one vendor record per supplier. Before adding a supplier, search for the name and remit-to details. Review the vendor list periodically for near-duplicates and close the extra record to new bills. This protects the warning's vendor scope and makes Vendor Balance Detail and Vendor Balance Summary readable.

Standardize invoice numbers at entry. Key the supplier invoice number as printed, and use one convention for punctuation. In review, normalize the Num column so INV-1043 and 1043 land together. Do not enter a statement total as a bill unless you can show that none of the invoices on the statement are already paid; reconcile the statement first.

Control the payment run. One person should release the run, and a second person should check the batch against Bills and applied payments before it is sent. A re-sent run needs the same check as a new run, not a shortcut because it was approved once. For new suppliers, require a second review before the first payment.

Questions