DeepLedgerFind duplicate bills and invoices by comparing records and their source evidence, not just matching amounts. A repeated file upload, a duplicate bank download and two posted invoices are different problems. Start by identifying which one you have.
This guide is for QuickBooks Online. Keep changes to reconciled, paid or closed-period records with the person responsible for those books.
Identify the record before correcting it
| What appears twice | First check | Why it matters |
|---|---|---|
| A PDF or receipt | Whether one or two transactions were actually posted | Two copies of a file may describe one correct ledger entry |
| An item in Pending or For review | Whether the transaction is already recorded | Adding it again may create a second expense or sale |
| Two posted bills or invoices | Source document, identifiers, line items and linked payments | Deleting either copy without inspection can disturb valid links |
| A payment and a bank deposit | Whether they are linked parts of the same event | Related records are not necessarily duplicates |
Intuit's duplicate-transaction guide describes common causes, including overlapping imports and adding a bank download instead of matching it. Use its correction path for the specific record type after establishing what happened.
Build a candidate list
Confirm the company and a bounded period. Review its bill and invoice lists, and include a nearby period if the same source document could have been entered with a different date. Compare candidates across these fields:
- Vendor or customer, including the exact record identifier.
- Document number, allowing for obvious formatting differences without treating them as proof.
- Transaction date, due date and source-document date.
- Currency, subtotal, tax and total.
- Products or services, quantities and line descriptions.
- Payments, credits, attachments and reconciliation status.
A different QuickBooks identifier means a different record; it does not establish a different real-world purchase. Conversely, the same supplier and amount can occur every month without anything being wrong.
Separate candidates from confirmed duplicates
These examples are fictional:
| Candidate | Finding | Review decision |
|---|---|---|
| Two $480 bills for vendor North Paper, both citing NP-1042 | Same source bill and same items; payment links still need checking | Likely duplicate, investigate links before choosing a correction |
| Two $250 hosting bills dated a month apart | Different service months and bill numbers | Legitimate recurring charges |
| A $700 invoice and a $700 credit memo | Different transaction types with a possible correction relationship | Inspect why the credit exists; do not treat it as a second sale |
| A $900 payment and a $900 deposit | Payment is included in the deposit | Linked records may be correct |
Retain a row for each candidate with its evidence, reviewer, decision and any proposed action. That list is useful even when the conclusion is “no change.”
Ask an AI agent for evidence
With a verified DeepLedger connection, start with a read-only request:
Confirm the company, then inspect bills and invoices dated September 1 through October 10, 2026. Return possible duplicates with record identifiers, vendor or customer, document numbers, dates, currency and amounts. Explain which fields match and which differ. Identify missing source evidence and linked payments or credits that need review. Do not create, update, void, delete or send anything. If the result is incomplete, say which dates or records remain unchecked.
If the connector cannot retrieve a required field or the full record set, open the records in QuickBooks or use a suitable export. Do not turn an incomplete search into “no duplicates found.” This process creates a candidate list, not a promise of exhaustive duplicate detection.
Choose the correction in the right place
For a downloaded item still awaiting review, inspect whether it should match an existing record or whether it is an extra download. Excluding a confirmed extra download is different from removing a posted invoice. Intuit explains matching downloaded transactions to existing records.
For posted records, check payment and credit links, attachments, period restrictions and the audit history before deciding which record to retain. There is no universal “delete the newer one” rule. A correction can change customer balances, vendor balances or prior reconciliation results.
Authorize the exact correction separately. Then read back the affected records and rerun the relevant report. Preserve the explanation of why the change was made. The audit-evidence guide covers the records to retain without treating one log as a complete archive.
Prevent the next duplicate
Assign one integration or workflow to record each type of sale or purchase. Match downloaded items to existing records before adding a new transaction. Review overlapping imports and duplicate recurring templates. After a timeout, look for the intended record before retrying the write.
During month-end review, investigate unusual balances and unresolved candidates. For entries that are real but have the wrong category, use the uncategorized-transactions guide; duplication and misclassification need different corrections.
Frequently asked questions
Are two transactions with the same amount duplicates?
Not necessarily. Recurring bills, installments and separate purchases can have identical amounts. Compare the customer or vendor, document number, dates, currency, lines, source evidence and linked records.
Is excluding a bank download the same as deleting a bill?
No. A downloaded item awaiting review and a posted bill are different records. Determine where the duplicate exists before selecting a correction.
Can AI remove duplicate invoices automatically?
Use AI to prepare candidates and evidence for review. Similar records are not proof of duplication, and changes can affect payments, reconciliations and closed periods. Authorize and verify any correction separately.