Data Reconciliation

Prove your data agrees — and know who owns it when it doesn't.

Pinnova BDS reconciles the same business figures across your source and reference systems, proves they match within tolerance, and routes every break straight to the person accountable for it.

Runs entirely inside your firewall — on Windows or as a Linux container. Reconciles across SAP HANA, Microsoft SQL Server, MySQL, PostgreSQL, Oracle, Snowflake, Databricks, and DB2.

Reconciliation Run · Revenue by Region
APAC
SAP HANA ↔ Snowflake
Reconciled
Source 4,182,904Reference 4,182,904
EMEA
SAP HANA ↔ Snowflake
Reconciled
Source 6,507,318Reference 6,507,318
AMER
SAP HANA ↔ Snowflake
Break → routed to owner
Source 2,940,110Reference 2,938,740Δ 1,370
Any ↔ Any
Reconcile the same value across different databases
Row-level
Drill from a mismatch down to the exact offending records
Named ownership
Every data product carries a responsible and accountable owner
100% On-Prem
Runs inside your firewall — your data never leaves it
The Problem

The same number, three different answers

  • The figure that drives your close or inventory position lives in an ERP, a warehouse, and a lakehouse.
  • Migrations and everyday drift pull those copies apart — quietly.
  • Generic data-quality tools test one table in place — they can't tell you whether two systems agree.
  • By the time a mismatch surfaces, it's a restated number, an audit finding, or a stock-out — owned by no one.
The Pinnova Way

Reconciled, proven, and owned

  • Checksum source against reference within a defined tolerance — real mismatches, not rounding noise.
  • Drill straight down to the offending rows, exported as CSV.
  • Every break is routed to the data product's named, accountable owner.
  • Quality, volume, and performance trends show the numbers holding over time.
How it works

Three steps to a number you can defend

01

Connect

Point Pinnova BDS at your source and reference systems with read-only connections. Adding a new database type is a config file, not a project.

02

Reconcile & drill down

Checksum both sides within your tolerance, then descend automatically to the exact rows that disagree — even across billions of records.

03

Route to the owner

Each data product has a named owner. Failures notify the right person, and trends show quality moving over time.

What you get

One platform, from proof to ownership

Reconciliation is one discipline in the Pinnova lifecycle — and it comes wired to profiling, ownership, monitoring, and reporting out of the box.

Cross-database validation

Checksum reconciliation between systems on different platforms, with configurable tolerance and automatic row-level drill-down.

Data profiling

Row counts and full column schema captured automatically, with downloadable samples — so teams see the shape of a dataset before they build on it.

Ownership & accountability

Named technical and business owners — responsible and accountable — on every data product, so every break has a name attached.

Trends & reporting

Quality, volume, and validation-runtime trends with scorecards and filters, so leaders see the health of their data products over time.

Alerts on failure

Validation failures surface to the accountable team so issues get worked — not discovered at quarter-end.

Self-service reporting

Business users get a reporting-only view of the data products they own — in one dashboard, with Power BI-ready exports.

Why Pinnova BDS is different

Others flag an anomaly and stop. Pinnova BDS proves two systems agree — and hands the break to its owner.

Correctness and accountability in one place — the difference between a dashboard and a number you can defend.

Runs where your data lives

Enterprise-ready, on your terms

Self-hosted

Installs and runs entirely inside your firewall. Schemas, samples, and connection details never leave your network.

Read-only access

Connects to your sources read-only, and credentials stay as environment-scoped secrets — never stored in the app database.

Access control

Role-based sign-in with CSRF protection on every change, plus optional Microsoft Entra ID single sign-on.

Extensible

Support a new database type with a single properties file — no code change and no vendor project.

See it reconcile your own data

Download the free tier and reconcile two systems that ought to agree — up to 3 data products, and no data ever leaves your network.