Senior Engineer

/PRNewswire/ -- SAP SE (NYSE: SAP) and Reltio Inc. today announced that SAP has agreed to acquire Reltio, a leading master data management (MDM) software...

SAP to acquire Reltio: make SAP and non-sap data ai-ready. March 27, 2026 WALLDORF & REDWOOD CITY - SAP SE (NYSE: SAP) and Reltio Inc. today announced that SAP has agreed to acquire Reltio, a leading master data management (MDM) software provider, to help customers make their SAP and non-SAP enterprise data AI-ready. Terms of the deal were not disclosed. Amplify the value of AI with your most powerful data Once closed, the acquisition will strengthen SAP Business Data Cloud (SAP BDC) - integral for SAP's AI-First and Suite-First strategy - and accelerate the evolution of SAP BDC to a fully interoperable enterprise data platform for enterprise-wide agentic AI. It will provide customers with the tools they need to unify, cleanse and harmonize data across sources for superior enterprise-wide agentic AI. "Reltio is a natural fit with SAP," said Muhammad Alam, member of the Executive Board of SAP SE, SAP Product & Engineering. "Acquiring them will further improve our position as a leading business AI provider, combining SAP and non-SAP data to deliver data context that business AI requires. AI cannot reach its full potential when data is fragmented across business units, platforms and domains without connection or context." By integrating Reltio after closing the acquisition, SAP will make customers' enterprise data fully AI-ready. Customers will be able to rely on trusted, high-quality data across SAP and non-SAP sources that Joule and Joule Agents use to deliver faster time-to-value for business AI. Reltio's platform helps organizations manage and govern structured and unstructured enterprise data from start to finish. Its AI-based entity resolution identifies and merges related records from different formats and applications into one reliable "golden record" system of context. Its cloud-native, AI-first design supports a single, consistent view of customers, products, suppliers, locations and employees across both SAP and non-SAP applications. Customers running AI tasks will benefit from increased reliability and consistency of data, bundled in a single source of truth, improving business AI. With that, customers can trust that AI results are correct, and AI-interactions are resolved fast. "Joining forces with SAP presents a tremendous opportunity for us to accelerate our mission," Reltio Founder and CEO Manish Sood said. "Enterprise AI needs trusted context that is open and interoperable across the heterogeneous IT landscapes our customers run. This combination accelerates our ability to deliver Reltio as the system of context across SAP and non-SAP environments, while maintaining continuity for our customers and our partner ecosystem." Reltio's data cleansing, unification capabilities and agent-driven workflows will work alongside SAP Business Suite applications to improve decisions, reduce integration complexity and deliver trusted, consistent data critical for successful business processes and AI use cases. Low latency delivery and support for the Model Context Protocol (MCP) enable real-time, multiagent workflows across SAP and non-SAP environments, allowing AI agents, such as a procurement agent, to assess supplier risk and trigger actions almost instantly using trusted, real-time data. Reltio offers prebuilt, industry-specific "velocity packs" that include data models, rules, matching logic and integrations, and solutions tailored to sectors like life sciences, healthcare and financial services. By integrating Reltio after closing the acquisition, SAP intends to accelerate its customers' ability to govern and expose master data as trusted and context-rich data products across multiple sources that serve both traditional analytics workloads and AI agents. Reltio will become a core capability within SAP BDC, with a flexible commercial model where customers can purchase Reltio as a separate solution or with other SAP products. The Reltio portfolio will also remain available as a standalone offering for the foreseeable future. The transaction is expected to close in Q2 or Q3 of 2026, subject to customary closing conditions, including regulatory approvals. About Reltio Reltio is a leader in data unification and management, delivering cloud-native, AI-native master data management (MDM) to help enterprises create trusted data and unlock context intelligence for analytics, automation, and agentic AI. Designed for complex, multi-vendor environments, Reltio helps organizations unify, cleanse, harmonize, govern, and activate core data from multiple sources in real time - across SAP and non-SAP systems. The Reltio Data Cloud uses advanced entity resolution, continuous data quality, and relationship intelligence within an intelligent data graph to connect data across systems and reveal the full context behind customers, products, suppliers, and other key business entities. This enables organizations to reduce data friction, improve operational execution, and accelerate time to trusted decisions. For more information, visit www.reltio.com. As a global leader in enterprise applications and business AI, SAP (NYSE:SAP) stands at the nexus of business and technology. For over 50 years, organizations have trusted SAP to bring out their best by uniting business-critical operations spanning finance, procurement, HR, supply chain, and customer experience. For more information, visit www.sap.com. Note to editors: To preview and download broadcast-standard stock footage and press photos digitally, please visit www.sap.com/photos. On this platform, you can find high resolution material for your media channels. For customers interested in learning more about SAP products: Global Customer Center: +49 180 534-34-24 United States Only: 1 (800) 872-1SAP (1-800-872-1727) This document contains forward-looking statements, which are predictions, projections, or other statements about future events. These statements are based on current expectations, forecasts, and assumptions that are subject to risks and uncertainties that could cause actual results and outcomes to materially differ. Additional information regarding these risks and uncertainties may be found in our filings with the Securities and Exchange Commission, including but not limited to the risk factors section of SAP's 2025 Annual Report on Form 20-F. (C) 2026 SAP SE. All rights reserved. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see https://www.sap.com/copyright for additional trademark information and notices. Please consider our privacy policy. If you received this press release in your e-mail and you wish to unsubscribe to our mailing list please contact [email protected] and write Unsubscribe in the subject line.

Reltio integration for Salesforce: Search Before Create, architecture, configuration, and enterprise data strategy. Modern customer-centric organizations operate in ecosystems where CRM platforms must function not just as data entry systems but as authoritative operational interfaces connected to enterprise master data. When a CRM instance accumulates duplicate or fragmented records, it undermines reporting accuracy, customer experience, and automation reliability. This is precisely the problem that Search Before Create (SBC) addresses within the integration between Reltio and Salesforce. SBC is not merely a convenience feature; it is a governance-driven architecture pattern designed to enforce record uniqueness at the point of creation by inserting an intelligent, federated search layer into the record-creation workflow. At a conceptual level, SBC introduces a validation gate between a user's intent to create a record and the actual persistence of that record. Instead of allowing a user to immediately create an Account or Contact, the system dynamically searches existing datasets to determine whether a corresponding entity already exists either locally or in upstream master data repositories. The significance of this pattern lies in its proactive nature. Traditional deduplication strategies operate after data has already been created, requiring matching algorithms, survivorship rules, and remediation workflows. SBC shifts the paradigm from reactive cleansing to preventative control. The underlying logic of SBC operates through a tiered search execution model that prioritizes speed, accuracy, and completeness. When a Salesforce user initiates a creation event, the interface presents a search form constructed from predefined input mappings. These mappings determine which fields are relevant for identity resolution. The query first executes against Salesforce's native dataset, ensuring that existing CRM records are discovered with minimal latency. If no match is returned, the request is transmitted through the integration layer to Reltio's platform, where it searches the master data tenant containing harmonized entity records. If configured, the process can extend further to external data tenants or licensed third-party datasets accessible through the same search infrastructure. This layered architecture ensures that duplicate prevention is not limited to a single system but instead spans the organization's entire data landscape. From an architectural standpoint, SBC is implemented through the managed integration package combined with orchestration logic provided by the integration hub. The managed package installs Lightning components, configuration objects, and authentication handlers within Salesforce. Meanwhile, the integration hub provides the orchestration recipes that govern request routing, API invocation, and response transformation. These recipes encapsulate reusable logic modules such as search processing, entity import, and synchronization events. By externalizing orchestration logic into integration workflows rather than embedding it directly in Salesforce code, organizations gain the ability to modify search logic or data-mapping behavior without redeploying CRM customizations. Authentication and connectivity form a critical prerequisite for SBC functionality. The Salesforce environment must be authorized to communicate with the master data platform through secure API endpoints. This typically involves configuring remote site settings, generating API credentials, and enabling endpoint collections that expose search and import services. These endpoints act as stateless services that accept structured search payloads and return normalized result sets. Because SBC is invoked synchronously from the user interface, latency optimization becomes essential. Organizations often tune query parameters, index configurations, and field selection to ensure response times remain acceptable for interactive use. A defining element of SBC configuration is the mapping definition that links Salesforce record types to master data entity types. Each mapping specifies which Salesforce object and record type correspond to which master data entity schema. It also defines which fields should be transmitted as search criteria and which should be displayed as result attributes. The selection of input fields determines search precision. Including too few identifiers may yield broad or ambiguous results, while including too many may prevent legitimate matches from appearing. Output fields, by contrast, are selected for contextual clarity, allowing users to visually confirm whether a returned result represents the same entity they intended to create. User-experience integration is achieved by overriding the standard creation action in Salesforce. Instead of launching the default record form, the system launches a custom SBC component. This component renders the search interface, executes the federated query, and presents results in an interactive grid. Users can preview candidate records, inspect attributes, and decide whether to import an existing record or proceed with creation. Importing a record pulls authoritative data from the master platform into Salesforce while preserving cross-system identifiers, thereby maintaining referential integrity across environments. If no matching record is found, the user can continue with creation, at which point synchronization logic ensures the new record is propagated upstream as a mastered entity if required by governance rules. The technical search mechanism relies on structured query execution optimized for both text-based and attribute-based matching. Depending on field type and configuration, the integration may employ full-text search semantics or structured query semantics. This dual capability allows organizations to support flexible user searches such as partial names or approximate matches while also supporting deterministic lookups based on exact identifiers like tax IDs or registration numbers. Because master data systems typically maintain enriched, standardized attributes, searches executed against them often return more accurate matches than those executed against isolated CRM datasets. From a data governance perspective, SBC plays a strategic role in enforcing golden-record discipline. Master data management initiatives aim to maintain a single authoritative representation of each real-world entity. However, if downstream operational systems are allowed to create records freely, divergence inevitably occurs. SBC ensures that operational systems respect master data authority by checking against mastered entities before allowing local creation. This transforms the CRM from an independent data silo into a controlled entry point within a governed data ecosystem. Organizations that deploy SBC frequently observe measurable improvements in data quality metrics. Duplicate record rates decline, identity resolution accuracy improves, and user confidence in CRM data increases. These improvements have downstream effects on analytics, marketing automation, and customer engagement processes that depend on reliable identity data. Furthermore, because SBC integrates seamlessly into the user workflow, it enhances governance without imposing additional manual steps or external validation tools. Operational monitoring is another important consideration. Because SBC involves multiple systems interacting synchronously, failures can arise from connectivity issues, authentication problems, or mapping misconfigurations. Logging and diagnostics within the integration layer provide visibility into request payloads, API responses, and transformation steps. Effective monitoring allows administrators to quickly identify whether a search failure originates from CRM configuration, integration logic, or master data service availability. In enterprise architecture terms, SBC exemplifies a pattern known as "preventive data stewardship." Instead of relying solely on batch reconciliation or stewardship queues, it embeds stewardship logic directly into transactional workflows. This approach aligns with modern data-mesh and domain-driven strategies, where data quality enforcement occurs at domain boundaries rather than in centralized after-the-fact processes. By validating records at creation time, SBC ensures that every new entry adheres to enterprise identity standards from the outset. In conclusion, Search Before Create within the Reltio-Salesforce integration is more than a feature toggle; it is a strategic control mechanism that aligns operational CRM activity with enterprise master data governance. Its architecture combines synchronous search orchestration, configurable mappings, federated data access, and user-centric interface design to ensure that records are created only when they truly represent new entities. For organizations pursuing a unified customer view and trustworthy analytics foundation, implementing SBC is not merely recommended but essential.