What does the duplicate transaction detector produce?
Identify repeated transactions, conflicting ingestion records and possible cross-feed repeats.
Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.
What do you need before you start?
- Define the authorized source population and your review rules.
- Keep the unchanged original files and record the snapshot and exclusions.
- Review missing and invalid inputs before preparing the finalized pack.
What information do you enter?
Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.
- Primary source. Exact headings transaction_id, source_system, account_id, timestamp, amount, currency, reference.
- Review reference. Customer-controlled review reference.
- Review owner. Responsible customer reviewer.
- Observation date. Real YYYY-MM-DD date. Effective date intervals include both endpoints.
- Selected source scope. Name actual populations, versions, period and known omissions.
- Population declaration. Choose the explicit working rule before preparing a result.
| Field | What to enter | Fictional example |
|---|---|---|
| Review referenceRequired | Customer-controlled review reference. | |
| Review ownerRequired | Responsible customer reviewer. | |
| Observation dateRequired | Real YYYY-MM-DD date. Effective date intervals include both endpoints. | 2026-10-09 |
| Selected source scopeRequired | Name actual populations, versions, period and known omissions. | |
| Population declarationRequired | Choose the explicit working rule before preparing a result.Choose from Selected records only, Your declared complete sources. | Selected records only |
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.
How does the duplicate transaction detector work?
- 1Select the actual sources
Primary source. Exact headings transaction_id, source_system, account_id, timestamp, amount, currency, reference.
- 2Freeze the review rules
Group exact source_system and transaction_id pairs. Remove only complete identical source rows from the working copy. Conflicting duplicate IDs stay retained. Separately compare account_id, UTC instant, exact amount, currency and reference fingerprints across distinct IDs and feeds, labeling candidates without removing them. Invalid monetary values or timestamp precision remain unresolved.
- 3Inspect complete findings
Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.
- 4Keep recoverable work
Inputs and exact source bytes save locally and survive reload. Strict restores verify tool identity, input schema, original hashes and parsed bytes before atomic replacement. Earlier generic work, prior checkpoint files and purchases remain preserved separately.
- 5Prepare the finalized pack
Prepare seven core files and the exact selected attachments, then download them free. Review the fictional sample below.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
- Common Format and MIME Type for Comma-Separated Values FilesCSV mechanics only. This source supplies no customer schema, legal requirement, matching identity, population completeness, threshold or reconciliation rule. Section 2 describes CSV records, field counts, double-quote escaping and embedded commas or line endings.RFC Editor. Reviewed 2026-10-09.
- Date and Time on the Internet TimestampsSupports supported timestamp syntax and explicit-offset conversion only. This implementation rejects leap seconds and more than three fractional digits rather than claiming full RFC coverage. No daylight saving, legal calendar or event authenticity is inferred. Sections 4.2, 4.3 and 5.6 describe stated UTC offsets, unknown offset -00:00 and date-time syntax.RFC Editor. Reviewed 2026-10-09.
Common questions
What information does the duplicate transaction detector need?
Enter primary source. Exact headings transaction_id, source_system, account_id, timestamp, amount, currency, reference; review reference. Customer-controlled review reference; review owner. Responsible customer reviewer; observation date. Real YYYY-MM-DD date. Effective date intervals include both endpoints; selected source scope. Name actual populations, versions, period and known omissions. Define the authorized source population and your review rules.
What does the duplicate transaction detector produce?
Complete on-screen source-linked findings, free result JSON and CSV, and complete annotated or transformed working datasets. Seven core files plus exact original sources. Formal PDF and DOCX, complete Excel findings and source populations, CSV findings, frozen inputs/results JSON, delivered-file hashes and instructions. Exact original source files, validated complete browser backup ZIP and preserved earlier workspace strings remain downloadable. Historical purchases stay immutable. Review unresolved findings and limitations before use.
Who makes the final decision?
A responsible person reviews the result. Mechanical working results use exact supplied source populations and your rules. Originals remain unchanged in this browser. No identity, legal obligation, source completeness, currency conversion, suppression consent, refund, cancellation, shipment or external operation is authenticated or performed.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the duplicate transaction detector for this task?
Identify repeated records and ingestion errors. Mechanical working results use exact supplied source populations and your rules. Originals remain unchanged in this browser. No identity, legal obligation, source completeness, currency conversion, suppression consent, refund, cancellation, shipment or external operation is authenticated or performed.
What still needs review?
Mechanical working results use exact supplied source populations and your rules. Originals remain unchanged in this browser. No identity, legal obligation, source completeness, currency conversion, suppression consent, refund, cancellation, shipment or external operation is authenticated or performed.
At most 5000 rows, 50 fields, 100000 cells and 5000000 parsed characters per source, 10 MB per file. Exact decimal arithmetic supports 12 whole digits and 6 fractional places.
Complete reviews are bounded to 20000 findings and 15000000 result characters. Split larger populations into explicit source batches.
Formal reports show at most 100 findings and 400 characters per displayed field. Complete sources, findings and working output values remain in Excel and JSON.