ReconLoomSupport

Generic Record

Compare inventory, ERP and other structured records by the fields you choose.

Define record identity and comparison fields, then see which records match, change, appear on one side or need review. Generic Record does not apply transaction amount and date rules.

Start Free ReconciliationTry Demo

A clear record-by-record comparison

  • Choose record identity. Map the key fields that identify corresponding records.
  • See exactly what changed. Compare quantities, statuses or other selected fields.
  • Export reviewed findings. Keep source references alongside the differences.

Generic Record journey

  1. Import.Choose the supported structured files you want to compare.
  2. Understand.Inspect the datasets, headers and row shape locally before defining record meaning.
  3. Map & Configure.Define typed fields, choose identity fields and select the comparison fields that matter.
  4. Match.Identify corresponding records deterministically from the configured identity.
  5. Explain.Keep exact matches, changed records, conflicts, invalid records and one-sided records distinct.
  6. Review.Inspect the relevant result states and source provenance before export.
  7. Verify.Record a finalization reason and acknowledge unresolved exceptions when present. You do not need to make every row match. This is not independent audit certification.
  8. Export.Generate the supported local CSV or XLSX output for the comparison.

Define record identity

Choose the fields that identify a record so matching follows the structure of the dataset.

Choose what to compare

Select typed comparison fields so the result can show what changed instead of only reporting that two rows differ.

Keep result states distinct

Separate exact matches, changes, conflicts, invalid records and one-sided records for review and export.

Synthetic example

The same SKU can tell different stories.

Unchanged

SKU-A has quantity 12 and location North in both exports.

Changed field

SKU-B appears in both exports, but quantity changes from 8 to 6.

One-sided or duplicate

SKU-C appears only in the warehouse export; repeated SKU-D rows need identity review.

These invented rows show possible Generic Record categories. Your confirmed identity and comparison fields determine the actual result.

Structured-data use cases

Use explicit record identity beyond finance.

See how Generic Record supports data migration reconciliation and inventory reconciliation for structured tabular exports.

A practical business question

Beyond finance: a stock discrepancy

If SKU-102 has quantity 8 in an ERP export and 6 in a warehouse export, map SKU as the identity and quantity as a compared field. Investigate the difference. Units of measure, location granularity and bundled stock should be normalized before comparing.

Try with synthetic sample exports or review the related workflow before using business-sensitive data.