Duplicate invoice detection software for QuickBooks helps you check possible repeat submissions. Compare the source documents before approving another QuickBooks Online Bill.
A new filename doesn’t make a new purchase.
A supplier sends a reminder. A teammate uploads it again.
You shouldn’t need to remember every invoice to spot a repeat.
Web uploads compare file fingerprints against files for the same client in your organization, including repeats in the current batch. When configured, email intake compares existing files across the organization before client assignment.
Check email intake setupAt approval, invoice fields are compared with up to 100 eligible other ScannerPilot documents for the same client. This can include documents under review, approved, syncing, already synced or marked duplicate; deleted documents are excluded.
Previously synced ScannerPilot documents can be comparison candidates. Entries created directly in QuickBooks or by other tools are not searched by these checks. Inspect existing accounting records separately before approving another Bill.
One supplier invoice, submitted twice for the same client. Compare the two sources, see the actual review-warning text and try the supported Mark duplicate action.
exact_match: Same vendor, invoice number, total, and invoice date.
The new scan has a different fingerprint. Its supplier, invoice number, date and total match the earlier same-client document, so approval returns “Exact duplicate detected.” without an override reason.
Fictional documents in an illustrative layout. Warning text and action names reflect the product; the example uses no live QuickBooks connection and creates no accounting records.
ScannerPilot checks file fingerprints during upload and compares supplier, reference, date and amount at approval before QuickBooks Online sync.
Review normalizes supplier-name case, punctuation and spacing before comparing. Confirm the supplier against both originals.
An exact match needs the same normalized reference. A likely match can use equal or overlapping references, or a missing reference, alongside the other required fields.
Exact matches use the same invoice date. Likely matches allow dates up to seven days apart when the supplier, total and reference rules also match.
Review compares totals rounded to two decimal places. A matching amount alone does not trigger a match.
Upload checks compare the file’s checksum. Renaming an unchanged file preserves its fingerprint; a fresh scan can change it. This is separate from invoice-field matching.
Same supplier. Same amount. Another month.
A recurring invoice may be perfectly legitimate.
Matching amounts alone do not trigger a field match. Check the reference, dates and original documents.
Same total. Different invoice. Worth checking.
Bring matching details into view before another record reaches your books.
Possible duplicateCompare the source and the extracted details. Check anything that needs a closer look.
Evidence, side by sideUse Mark duplicate for a confirmed repeat. An exact field match needs a Duplicate override reason to proceed with approval; sending to QuickBooks is a separate step.
Your approval comes firstDuplicate detection, without
the complicated explanation.
It is a check for documents that may represent a transaction you have already uploaded. ScannerPilot surfaces possible repeats before QuickBooks Online sync, so you can compare the evidence and decide what to do.
There are two checks. Upload checks compare file checksums. At approval, an exact field match requires the same normalized supplier, invoice number, invoice date and total. A likely match requires the same supplier and total, dates within seven days, and invoice references that match, contain one another or are missing on either document.
The filename is not the whole check. An unchanged file can have the same fingerprint after it is renamed. A new scan can have a different fingerprint, while its supplier, invoice number, date and total still point to the same transaction.
The monthly example on this page does not meet the field-matching rules: its invoice numbers differ and its dates are more than seven days apart. A matching supplier and total alone are not enough. Compare billing periods and originals before approving any separate transaction.
No. Treat a warning as a reason to investigate, not as an automatic verdict. This is a pre-sync document review workflow, not a payment-blocking service or a guarantee that every duplicate will be detected.
No. Web uploads check files for the same client, including repeats in the current batch. Configured email intake checks existing files across the organization before client assignment. At approval, field checks compare up to 100 eligible other ScannerPilot documents for the same client, including previously synced documents. They do not query the historical QuickBooks ledger.
Approval returns “Exact duplicate detected.” unless a non-empty Duplicate override reason is supplied. Compare the originals, then use Mark duplicate for a confirmed repeat. Only override after establishing why another accounting record is appropriate. Approval and sending to QuickBooks remain separate actions.
Yes. Missing or differently extracted details, changed files and documents outside the eligible comparison set can leave a repeat undetected. Review the source and existing accounting entries. These checks do not provide historical duplicate cleanup, duplicate-payment recovery or guaranteed prevention of every duplicate.
Everyday paperwork. A clearer path.Bring possible duplicates into focus.
Keep your next QuickBooks entry considered.