When we talk about data reconciliation, we mean that the integration work isn't custom-developed. It's based on business rules that have been defined by data stewards, so that every application uses some standard set of business rules that drive complete customer detail. Data is reconciled between systems, but it is also defined in a reconciled way so that data from different systems is matched. When I modify customer information, the logic is in place to propagate those business rules to all systems.
As an aside: most CDI hubs make data changes available to all the systems that need it. CDI supports both "publish" and "subscribe," meaning that it can either propagate data changes automatically, or "hold" the data until a system requests it.
Data reconciliation ensures that the data isn't only as good as its last update, which implies data "certification" -- integrating the data according to business-approved rules. Certifying the data ensures that it's consistent across multiple, often-unrelated systems. Think about this and all the work it can save!
Dig Deeper on Customer data integration software
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.