Audit missing and duplicate reference keys before a join
An order code missing from a product list cannot be matched, while a repeated reference code is ambiguous. Audit both spreadsheets before joining to identify which records need correction.

How to use this tool
- Add the source spreadsheet followed by the reference spreadsheet.
- Select their respective key columns.
- Run the audit and inspect reported rows in both original source and reference spreadsheets.
- Download the relationship report.
Choose the right settings
Add the records to be connected first and the reference list second, preserving that input order. Select each spreadsheet's key column and compare how their identifier values are written.
- Supported input
- CSV,TSV,XLSX
- Available settings
- Key column
- Reference key
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
orders + reference catalog → key relationship reportExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Read issues for the source and reference spreadsheets separately to locate the responsible records. Follow row numbers for empty keys, missing references and duplicates back to the original identifier values.
If the result is different from what you expected
Many missing references warrant checking file order and the chosen key columns before changing data. The report identifies relationship issues; correct source identifiers or reference records and repeat the inspection.
Limits to keep in mind
- Add source then reference. Report empty, missing and duplicate reference keys.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.