Reconcile CSV and Excel Files Without Manual Row-by-Row Comparison

Reconcile 2–50 named sources in one run. Start a new reconciliation or use a saved workflow, and upload one file per source. Reconixe accepts:

• CSV — comma-separated exports from almost any system;
• XLSX — Excel workbooks.

Files should contain a header row followed by one record per row. Reconixe checks each file before it is used and lists its columns, so you can confirm the right data was uploaded. Other formats, such as older .xls workbooks or PDFs, are not accepted as inputs.

A little preparation makes a CSV or Excel reconciliation far more reliable. Before uploading, it helps to check that:

• every source file includes a column that identifies each record in the same way, such as an order number or transaction reference;
• the first row contains column headers rather than a title or blank line;
• the key values are written consistently across sources — for example, the same prefixes and no stray spaces;
• each file contains only the period or scope you intend to compare.

If a key column is missing from one of the files, Reconixe stops before running rather than producing a misleading result, and no rows are counted toward your usage.

Map matching keys for a new reconciliation, or save a workflow for comparisons you repeat whenever new files arrive.

• Map a key column from every source — for example, Transaction ID in each file.
• Records are matched by exact key values.
• Advanced matching options are available only on plans that include them.
• Each run preserves its source configuration; saved-workflow runs also record the published version used.

After a multi-source run completes, every record lands in a clear category:

• Matched — the key appears exactly once in every source;
• Partial — the key is present in some sources but absent from others;
• Missing key — a row has an empty value in a key column;
• Ambiguous — a key is duplicated in any source, so rows cannot be paired with confidence.

Partial, ambiguous and missing-key results become exceptions. Your team can review each one, add a note, and mark it resolved, so nothing is quietly overlooked.

A spreadsheet comparison often loses its context once the file is saved over. In Reconixe, each completed reconciliation keeps its counts, exception records, the source rows behind each exception, and the review history in one place.

The uploaded input files themselves are not kept indefinitely — the reconciliation results and evidence are what remain available in your history, subject to your plan's retention period.

Completed runs can be exported in the format that suits the next step:

• CSV — for further processing or importing elsewhere;
• XLSX — a workbook with summary and outcome sheets (multi-source: matched, partial, ambiguous, missing key; classic two-file runs retain their A/B sheets);
• PDF — a readable summary for sharing or record-keeping.

Can I compare more than two files at once? Yes. Name 2–50 sources for a new reconciliation and upload one file per source. Classic Dataset A/B workflows remain available for two-file comparisons.

Do header rows count toward my usage? No. Only data rows processed across all source files count toward your monthly row allowance.

What happens with duplicate keys? Reconixe does not guess. Duplicated keys are reported as ambiguous so a person can decide which record is correct.

Can I import directly from another system? Not at present. Export the data from your system as CSV or XLSX, then upload it.

When the same exports need to be compared on a regular schedule, a repeatable workflow removes much of the manual setup and makes the result consistent from one run to the next. Your team can spend its attention on the exceptions that genuinely need judgement instead of on lining up rows.

Reconixe is part of a broader approach to data reconciliation software for operations teams. Plan capacity — users, active workflows, and rows per month — is listed on the pricing page.