What does the cross-file reconciliation produce?
Match exact selected keys across two files and compare approved field pairs, preserving unmatched and ambiguous rows.
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.
- Separate primary and comparison exact-text CSV, one-sheet XLSX or dataset JSON sources.
- Primary key field. Exact primary field name.
- Comparison key field. Exact comparison field name.
- Field pairs to compare. JSON array of [primaryField, comparisonField] pairs. Use [] for key-only matching.
| Field | What to enter | Fictional example |
|---|---|---|
| Primary key fieldRequired | Exact primary field name. | ID |
| Comparison key fieldRequired | Exact comparison field name. | ID |
| Field pairs to compareRequired | JSON array of [primaryField, comparisonField] pairs. Use [] for key-only matching. | [["Status","Status"]] |
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 cross-file reconciliation work?
- 1Select the actual sources
Separate primary and comparison exact-text CSV, one-sheet XLSX or dataset JSON sources.
- 2Freeze the review rules
Match exact strings. Unique keys permit exact cell comparisons. Blank or duplicate keys remain unresolved. Every source row appears in the source-linked ledger.
- 3Inspect complete findings
Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.
- 4Keep recoverable work
Browser-local inputs and exact source files survive reload. Restore a validated exact-byte backup ZIP or explicitly approved private cloud revision. Earlier generic workspace keys, original files and historical purchases remain separate and preserved. Download preserved earlier strings and bytes before changing devices.
- 5Prepare the finalized pack
Prepare seven files, 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 (CSV) FilesCSV record, field and quoting conventions. This source does not specify customer schemas, matching rules, checksum arithmetic, sampling quality or import acceptance. Section 2. Definition of the CSV Format.RFC Editor. Reviewed 2026-10-08.
- Secure Hash StandardSHA-256 digest specification for exact source-byte and delivered-file checks. It does not establish authenticity or validate the named review rules. Section 6.2. SHA-256.National Institute of Standards and Technology. Reviewed 2026-10-08.
Common questions
What information does the cross-file reconciliation need?
Enter separate primary and comparison exact-text CSV, one-sheet XLSX or dataset JSON sources; primary key field. Exact primary field name; comparison key field. Exact comparison field name; field pairs to compare. JSON array of [primaryField, comparisonField] pairs. Use [] for key-only matching. Define the authorized source population and your review rules.
What does the cross-file reconciliation produce?
Complete source-linked on-screen review and free JSON/CSV results. Seven-file finalized pack. Formal PDF and DOCX, complete Excel review, CSV ledger, exact parsed sources and inputs JSON, delivered-file SHA-256 manifest and instructions. Sampled or transformed output dataset where applicable. Exact original files and browser backup ZIP remain separately downloadable. Review unresolved findings and limitations before use.
Who makes the final decision?
A responsible person reviews the result. Match exact strings. Unique keys permit exact cell comparisons. Blank or duplicate keys remain unresolved. Every source row appears in the source-linked ledger.
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 cross-file reconciliation for this task?
Match selected keys and report unmatched records. Match exact strings. Unique keys permit exact cell comparisons. Blank or duplicate keys remain unresolved. Every source row appears in the source-linked ledger.
What still needs review?
Match exact strings. Unique keys permit exact cell comparisons. Blank or duplicate keys remain unresolved. Every source row appears in the source-linked ledger.
Checks do not authenticate source records, population completeness, identifier issuance, external checks, a completed import or compliance.
Use at most 5000 data rows, 50 fields, 100000 cells and 5000000 parsed characters. Up to 10 MB per source. Typed spreadsheet cells, stored formulas and multiple worksheets require an explicit text export.
Formal reports show at most 100 rows and 300 characters per displayed field. Excel and JSON preserve complete results.