Whole-row comparison
If you do not pick keys, a row matches only when every compared column is the same after trimming. Reordered columns with the same header names still line up.
Free tool
Upload two CSVs. Leave keys blank for a whole-row comparison, or choose key columns to see changed rows. Fuzzy matching is not used here.
The default is deterministic: same values, same match. Choose key columns when a row can stay the same identity while other fields change.
No file selected yet.
The default is deterministic: same values, same match. Choose key columns when a row can stay the same identity while other fields change.
If you do not pick keys, a row matches only when every compared column is the same after trimming. Reordered columns with the same header names still line up.
A key such as id or invoice number lets the checker treat two rows as the same record and flag other fields as changed.
It does not fuzzy-match names, apply amount tolerance, or join one row to many. Those rules belong in a saved AuditExport recipe.
Continue with the full workflow, or try another free check.
Upload two or more Excel or CSV files, map columns, and separate matches from exceptions.
Compare two workbook versions and see values, formulas, and structure that changed.
Present in both, missing from either side, and possible duplicates
The same comparison engines as the Excel and CSV tools, with broader search copy
Anonymous uploads are processed in memory for this check only. They are not saved to an AuditExport workspace and are discarded when the request finishes.
CSV and .xlsx, depending on the tool. Legacy .xls, password-protected workbooks, and ZIP batches are not accepted here.
The free checker accepts up to 2 files, each file up to 1.5 mb, and 2,000 data rows per file. Larger work belongs in an AuditExport workspace.
No. Files are read in memory for this check. Nothing is written back to the file you selected.
No. These pages run a limited, exact check so you can see the problem. AuditExport adds tolerance, multi-way matching, review, reports, and saved workflows.
No. The checker reports what it can see in the files. It does not post journals, close a period, or replace professional judgment.
You can include those columns as keys. Matching stays exact. Amount tolerance is part of the full product.
Keep the mapping, review every exception, and export a report you can hand to a reviewer.