ShipDataFast Reconciliation Engine

Compare corresponding records across datasets using explicit matching, mapping, and tolerance rules, executed inside your controlled environment.

Accelerating delivery without vendor data exposure.

The Reconciliation Engine is the local-first tooling we build and adapt to each client's matching rules, for migration assurance and ongoing cross-system checks. We can also run the reconciliation ourselves from files and rules you supply.

Rather than pushing sensitive financial transactions, customer PII, or ledger records into third-party cloud SaaS platforms, the engine runs directly inside your designated infrastructure, delivering deterministic comparison with complete data perimeter control.

CONCEPTUAL DATA FIXTURE

Exact matching example

Illustration under exact matching, single currency, zero tolerance policy.

Record	Source Amount	Target Amount	Expected Result
TX-100	100.00	100.00	Match
TX-101	49.95	50.95	Difference: target minus source = 1.00
TX-102	25.00	Absent	Source only (missing in target)
TX-103	Absent	12.00	Target only (unmatched in source)

Three source records, three target records, four distinct keys, one matched record and three exception records. Note: absent records are treated distinctly from null values.

TX-101 (Value difference: +1.00): Source recorded 49.95; target ledger posted 50.95. Root cause: Target pipeline incorrectly added a legacy fixed handling fee rather than reading source post-discount net balance.

TX-102 (Missing in target / Source only): Present in core transaction DB but unposted in target. Root cause: Transaction arrived within the last 5 seconds of the daily cut-off window and was delayed by the ingestion broker queue into the following date batch.

TX-103 (Unmatched in source / Target only): Present in target analytical warehouse without source row match. Root cause: An upstream refund adjustment event produced a separate target line item using a synthetic key instead of referencing original parent TX-100.

CONSULTING DELIVERY

Need implementation or custom reconciliation?

The software accelerates delivery, but complex reconciliations succeed because of senior engineering: designing mapping tables, resolving composite keys, managing cut-off rules, and creating defensible audit trails.

Explore our Data Reconciliation Consulting service →

Discuss the Reconciliation Engine

Tell us which systems you need to reconcile and your reconciliation timeline.

Discuss Data Reconciliation