Catch Duplicate Bills Before They Get Paid

BLUF: Duplicate bills are cheapest to catch between entry and payment. A QuickBooks VA can run a weekly comparison of vendor, invoice number, amount, date, and attachment, then send the owner a short exception list instead of editing the ledger on their own.

A duplicate bill rarely looks like a mistake. It looks like a normal vendor invoice that arrived twice: one copy by email, one by portal, or a recurring bill re-entered after a bank feed rule created a second transaction. The owner approves the payment because the bill looks familiar.

Why duplicates survive the normal review

Most approval routines look at one bill at a time. The reviewer checks the vendor, the amount, and whether the work was done. That is the right question for a single bill and the wrong question for the file as a whole.

Duplicates survive because the second entry arrives days after the first, often in a different format. One copy may be a PDF attachment, the other a manually entered bill without an attachment. The two records do not sit next to each other in the default list.

Payment timing hides the rest. If the first bill was already paid and the second is still open, the open balance looks like a genuine unpaid invoice.

Build the duplicate test

Use a combination of fields rather than a single match:

Flag a bill when the vendor and invoice number match, or when vendor, amount, and date are within a short window and no invoice number exists on either record.

Work the exception list in order

Start with exact matches. A same-vendor, same-number, same-amount pair is almost always a duplicate. Check the audit log to see who entered each record and when.

Then review near matches: same vendor and amount, dates one to five days apart. These are often duplicates created by a bill capture tool and a manual entry. Read the attachments before deciding.

Finally, review the ambiguous cases: same vendor, same amount, different months. A monthly software bill and a duplicate look identical in a two-row comparison. Use the invoice number, service period, and the vendor statement.

Keep the decision with the owner

The assistant prepares evidence, not a verdict on the ledger. For each candidate, record both bill numbers, the entry dates, the amounts, the attachment links, and a one-line reason for the flag.

Send the list to the owner with a recommended action: void the second bill, apply a credit, or pay both because the vendor issued two genuine invoices. The owner decides. The assistant records the decision and checks that the ledger reflects it.

If the duplicate was already paid, the next step changes. The assistant prepares a refund or credit request, links the payment, and tracks the vendor response. Do not net it against a future bill without the owner's approval.

Prevent the next one

Duplicates are a process signal. If the same vendor keeps producing them, check the intake path. A portal download plus an emailed copy will create duplicates until someone owns the deduplication step.

Set a rule with the bill capture tool if it supports duplicate detection, and review its suggestions weekly. The tool is useful but not authoritative: it will miss a re-keyed bill and flag a legitimate recurring charge.

The weekly routine

Run the review on the same day each week, before the payment run. Export the open bills, sort by vendor and amount, and compare against bills already paid in the last 45 days.

Keep the exception list small. Ten to twenty candidates is enough for a first pass; a list of a hundred means the matching rule is too loose.

Close the loop by recording what was found and what was decided. Over a quarter, the pattern shows whether the problem is a vendor, a tool, or a missing intake rule.