● Dataproof capacity
The divergence that will appear at the closing is already in your data now
Dataproof compares data between files, banks and field-to-field APIs, with traceability of each divergence. Thus, when the closing arrives, the inconsistencies have already been dealt with.
Coverage
Reconcile any font combination
Regardless of where the data is, Dataproof uses the business key as a comparison link.
File × Database
Database × Database
API × Database
Batch × Messaging
Legacy × New Core
Relational Databases
PostgreSQL, Oracle, MySQL, SQL Server, Trino (any combination).
Structured Files
CSV, Positional, XML, JSON, and XLSX formats with configurable matching key definitions.
APIs and cloud
AWS S3, REST APIs, Azure connectors. Ready for modern pipelines.
What do you come to see?
The three problems that Dataproof encounters before you need to look for
Missing record
The record exists in source A and does not appear in source B. It can be a transaction approved by the bank that did not reach the ERP. Dataproof identifies and records with the evidence needed for investigation.
Registration left over
The record appears in source B without source traceable in source A. This can indicate duplicate or posting without an identified source. The Dataproof signals with evidence for the compliance team to investigate.
Divergent value
The business key hits, but the values are different between the sources. The dataproof shows exactly which field differs, how much and in which record, so that the correction is surgical.
Process
From Configuration to Evidence in 3 Steps
Map the comparison keys
Set the business identifier and processing window. Business configures, IT validates connectivity.
Perform automatic comparison
Line by line, key to key. Missing, leftovers and divergences identified in Batch — millions of records.
Act with evidence, not guesswork
Each divergence comes with field, expected value, value found. Compliance consumes the direct report.
Practical applications
Where multi-source reconciliation generates immediate result
Banking Core Migration or ERP
Operational and financial closing
Reconciliation of Payment Methods
Reconciliation of Payment Methods
Reconciliation of Payment Methods
— Check if critical records have arrived complete and correct to the DW. Reliable management reports from the origin.
Demo
See a reconciliation being performed live
Combine capabilities
Complete your data quality chain
Databases Validation
Validate each bank individually before reconciliation: given integrity at the origin, reliable result in the comparison.
Files and Messaging
Validate the file before ingesting at the base. Combine layout validation with later reconciliation.
Frequently Asked Questions about Data Reconciliation
What is the difference between data reconciliation and validation?
Validation checks whether a given respects rules in a single source. Reconciliation compares data between two or more sources to ensure consistency. Dataproof does both, often in sequence.
Can DataProof reconcile data with composite or transformed keys?
Yes. You define the comparison key: simple, composed or derived from combined fields. The motor applies the match logic according to the business rule, not by the physical structure of the file.
How are records with discrepancies handled? Does the processing stop when a discrepancy is detected?
No. Divergent records are segregated with complete evidence and made available for treatment. The rest of the healthy lot follows normally, without delay.
Is it possible to schedule recurring reconciliations?
Yes. Via directory watcher, scheduling or API. Ideal for daily closings, flag reconciliations and continuous governance routines.
next step
Want to see what differences exist today between your sources before the next closing?
Free Diagnosis: We define the first reconciliation flow with the greatest impact, in days you have results.