# Reconciliation Statement Duplicate Line Check

Distinguish a duplicated imported statement row from two genuine same-amount transactions.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Full statement pages, bank reference IDs, dates/amounts, imported rows and register IDs.

## Workflow
1. Retain bank references and page provenance before deduplicating.
2. Group repeated bank IDs separately from same amounts with distinct IDs.
3. Check import overlap versus genuine repeated payments using supplied evidence.
4. Return possible duplicate rows for review; no deletion or merging.

## Output contract
bank_reference | imported_rows | source_page | distinct_payment_evidence | duplicate_candidate | hold

## Fictional acceptance test
Fictional reference R appears in two imports of the same page: one duplicate candidate. Two 80 payments with referencesA and B are not duplicates merely because amounts match.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://quickbooks.intuit.com/learn-support/en-us/help-article/statement-reconciliation/fix-issues-end-reconciliation-quickbooks-online/L3mZimyAb_US_en_US

Checked October 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.