Check Spreadsheet Data Quality Before Matching

What this tool does

Small cleanliness problems can create large matching failures. The Data Quality Checker reviews each column for blank cells, values with unwanted outer whitespace, repeated normalized values and capitalization variants that may represent inconsistent entry. It presents these as issue signals rather than automatically declaring each occurrence an error: duplicate department names are normal, while duplicate invoice numbers may be critical. The purpose is to focus a reviewer’s attention before a lookup, import or reconciliation begins.

What a good input looks like

A tool can process a file correctly and still produce a misleading business result if the input rule is vague. For Data Quality Checker, a typical situation is that a spreadsheet should be reviewed for blanks, duplicates and inconsistent values before it feeds a reconciliation. Before running anything, record the source date, the owner of each dataset and the result you expect from at least three known records. That small control makes it easier to spot a wrong key, wrong delimiter or wrong source file before the same mistake affects thousands of rows. ReconNimble deliberately keeps the free workflow visible: the browser shows the selected inputs, summary counts and result rows instead of turning the task into a black box.

Choose the input rule carefully

The central rule for this workflow is to interpret quality signals in the context of each field because repetition can be valid for categories and invalid for IDs. Stable identifiers are preferable to descriptive text whenever identity matters. A field can look unique in a ten-row preview and still repeat later, so inspect blanks and duplicates before treating it as a key. Keep an untouched copy of the source files and do not “clean” away exceptions merely to make counts agree. If two systems encode the same identifier differently, correct or normalize that known format explicitly; do not assume that similar-looking values refer to the same person, asset, invoice or transaction.

Worked review pattern

Use the supplied fictional sample first, then repeat the same steps with a small extract from your own authorised data. Write down one record that should succeed, one that should appear as an exception and one edge case such as a blank key or quoted field. Run the tool and confirm those three cases before reviewing totals. For this task the useful output is column-level issue signals and counts that guide cleanup priorities. If the known cases do not land in the expected groups, stop and inspect headers, selected keys, source scope and data types rather than accepting a plausible-looking total.

How to review the output

Treat counts as navigation, not proof. Open several result rows from each status and compare them with the original source values. Pay special attention to duplicates because a repeated key changes the meaning of one-to-one matching and joins. Where the tool creates a local download, open that new file separately and confirm its row count, headers and a few values at the beginning and end. Keep the original sources unchanged so another reviewer can reproduce the result. If the output will drive payroll, payment, asset ownership, compliance or another high-impact action, obtain the appropriate business-owner sign-off.

Common mistakes to avoid

A recurring failure mode is treating every blank or duplicate as an error, changing source data without an owner or using quality scores as compliance proof. Another is treating normalization as data correction: trimming spaces or comparing text without case sensitivity can remove harmless presentation differences, but it cannot establish that two distinct identifiers are equivalent. Also remember that browser XLSX support is intentionally tabular. It reads worksheet cell values for utility tasks; it is not a full Excel rendering or calculation engine and it does not promise preservation of macros, charts, pivot tables, conditional formatting or every workbook feature. Use the right tool for the evidence you actually need.

Privacy, scale and the next step

The public Data Quality Checker workflow processes selected source files in browser memory. Running the tool does not send those files to ReconNimble, and supported exports are created locally. Browser memory varies by device, so the configured row cap rejects oversized jobs with a clear message rather than risking a tab crash. Publishing a result is a separate, explicit action that sends only the limited displayed result data used for the share page; never publish confidential rows. When the workflow needs durable operational evidence, move into Reconcile once the data is understood and exceptions need controlled ownership and evidence. That separation keeps the high-traffic utility layer private while preserving a more controlled path for saved reconciliation work.

How to use it

1. Select the source dataset; it remains in browser memory.
2. Review issue signals by column.
3. Decide which signals are valid repetition and which require cleanup before matching.

Limitations and review points

The checker does not know your organisation’s business constraints. Repeated values and blank optional fields may be legitimate, so all findings require contextual review.

Need saved jobs or advanced matching? The free browser tool is designed for fast local checks. ReconNimble Reconcile adds authenticated saved jobs, multi-source comparison, controlled fuzzy matching, profiles, server exports and an audit trail.