Reconciliation Statement Duplicate Line Check

Distinguish a duplicated imported statement row from two genuine same-amount transactions. Preparation only, not an account action.

What to provide

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

How it works

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.

The output

bank_reference | imported_rows | source_page | distinct_payment_evidence | duplicate_candidate | hold

Worked fictional example

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.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More bookkeepers workflows · How-to guides

Method: reviewed source. Demand lead: Oct 10 live AIS Search Console through Oct 6: 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. Checked October 10, 2026.