PROBLEM
Find what differs between two files.
A public-data inventory sample contained a workbook and CSV snapshot that needed to be compared without changing either source.
NURSERY RECONCILIATION · DEMONSTRATION
Public-data demonstration — not a customer engagement.
Friction Systems compared a 198-row workbook snapshot with a 195-row CSV snapshot and turned the differences into a reviewable exception list.
The comparison used public sample data. The source business did not hire or endorse Friction Systems, and the differences are not labeled as business errors.
CONTEXT
Two snapshots needed a deterministic comparison.
MANUAL_WORKFLOW
Inspect rows, keys, quantities, and exceptions.
A manual review would require matching the two files row by row, checking quantities, and isolating one-file-only records for follow-up.
EXECUTION + RESULT
The comparison surfaced differences without deciding what they meant.
WHAT_FS_DID
Matched shared keys and separated exceptions.
After download, Friction Systems compared the public sample and produced a machine-readable reconciliation. Neither source file was changed, and no paid resource was used.
MEASURABLE_RESULT
194 matched keys · 69 quantity differences
198 workbook rows versus 195 CSV rows; 4 workbook-only rows; 1 CSV-only row; no duplicate keys. The machine comparison took approximately 1 second after download, with $0 paid-resource spend.
OUTPUT + QUESTION
A shorter exception list for human review.
OUTPUT
A reconciliation snapshot.
The output preserved the 69 matched-key quantity differences and 5 unmatched rows as review items. Differences between snapshots remained uncertain until a person could explain them.
BUSINESS_QUESTION
Which differences actually need action?
The demonstration shows how repetitive cross-file work can become a focused operator review: connect the files, automate the comparison, then keep judgment with the person responsible.
BOUNDARY
Differences are not automatically errors.
LIMITATIONS
No customer, savings, or accuracy claim.
This public-data demonstration does not show that a source business had errors, saved time, hired Friction Systems, or endorsed the result. It is not a paid customer case study.
STATUS
DEMONSTRATION
The bounded comparison is proven on the public sample. A customer outcome would require separately verified scope, acceptance, and before/after operating evidence.