JSON RECONCILIATION

Compare two JSON exports by key—free, local-first.

Reconcile two compatible record-based JSON exports by account_id, order_id, ticket_id, or another shared field. See records found on only one side, duplicate keys, and changed field values.

Your JSON files stay on your device. The comparison runs in your browser and does not upload selected reconciliation files to the Ops Control HQ backend.
SUPPORTED SHAPE

Use record arrays, not arbitrary nested documents.

The free tool accepts a JSON array of records, or an object with a rows array. Both datasets should contain a field that identifies corresponding records. It is designed for exported business records, not a general recursive JSON-patch diff.

WHAT YOU GET

Missing records, duplicate keys, and field mismatches.

After both files load, choose the shared key. The report separates keys found only on the left, keys found only on the right, duplicate keys, and changed values for records that exist on both sides.

Useful for recurring exports

  • CRM or account snapshots
  • Order and fulfillment exports
  • Ticket or case datasets
  • Migration before/after checks
  • Operational API exports saved as JSON

Use a stable shared key

Pick a field that represents the same record in both exports. If the key repeats, the tool flags the ambiguity rather than treating duplicate records as a clean one-to-one match.

MAKE RECONCILIATION REPEATABLE

If this comparison happens every week, make it an operating control.

Assign an owner, cadence, evidence requirement, exception threshold, and escalation path so the comparison becomes part of the operating system instead of an ad hoc cleanup task.

Structural comparison does not determine which source is authoritative and does not provide accounting, legal, compliance, underwriting, or audit conclusions.