Screen a receivables export for possible duplicate invoices before ranking overdue balances or assigning collection weeks. A duplicated sales record can overstate both accounts receivable and expected cash, while two similar-looking records may be legitimate installments, corrections, or separate deliverables. The control is to flag candidates, trace each to source evidence, and let the accounting owner resolve the books.
Intuit's duplicate-transaction guidance recommends comparing dates, amounts, parties, and linked records before removing anything. It also distinguishes a payment and its related deposit from a true duplicate. Intuit's duplicate-number guidance shows how customer transactions can be sorted and reviewed by transaction number. A repeated number is a review signal, not proof that the balance is duplicated.
Build a candidate screen
Start with the dated invoice-level export used for the forecast. Flag rows that share several of these fields:
- customer or customer-job;
- invoice number;
- original amount and open amount;
- invoice date and due date;
- memo, project, purchase order, or service period;
- source-system creation or modification reference, when available.
Use exact matches first, then review near matches such as the same customer and amount within a narrow date range. Keep the detection logic documented so the next snapshot can reproduce it.
Separate five common outcomes
- **True duplicate invoice:** one business event was recorded twice.
- **Duplicate number only:** two distinct transactions share an identifier but represent different work or periods.
- **Replacement or correction:** a newer invoice supersedes an older voided or credited record.
- **Installment or milestone pair:** similar amounts are intentionally billed as separate obligations.
- **Linked payment and deposit:** two records describe different stages of the same cash event and should not be treated as duplicate invoices.
Do not delete, void, or net any row inside the forecasting file. Preserve the candidate and send it to the authorized accounting owner with the evidence needed to classify it.
Block suspect rows from expected cash
Until a material duplicate candidate is resolved, keep the affected amount visible as a data-quality exception and exclude it from the supported expected-cash total. If both rows remain in the source and the finance owner confirms they are distinct, document the differentiator and restore each supported assumption.
When the books are corrected, generate a new export. Do not overwrite the old file or silently remove a forecast row. The before-and-after record should show which invoice remained, which changed, who approved the resolution, and the new open balance.
Add a review table
For each candidate pair, record the two invoice identifiers, customer, dates, amounts, matching fields, differentiating evidence, status, owner, decision date, retained transaction, and replacement reference if any. This turns an apparent duplicate into a reviewable control rather than an unsupported judgment.
The QuickBooks export-columns checklist defines useful source fields. The voided-or-deleted invoice guide covers replacement and removal traceability, while the AR reconciliation guide confirms the corrected detail against the control balance.
Decision rule
A duplicate screen should identify candidates, not make accounting changes. Forecast each supported open obligation once. Block unresolved candidates, preserve both snapshots, and restore expected cash only after the current source population is reconciled.
AR Pulse analyzes an authorized QuickBooks receivables export; it does not access credentials or change accounting records. Finance owners with a clean invoice population can view the example report.