Skip to content
Database ⇄ ERP

Reltio to SAP S/4HANA integration — real-time, two-way sync

Keep Reltio and SAP S/4HANA in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Reltio and SAP S/4HANA

Give your engineers SAP S/4HANA's data in Reltio: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Billing Documents (Invoices), Deliveries, Journal Entries, Customer / Supplier Roles from SAP S/4HANA into Reltio and keeps both sides consistent in real time. Whatever SAP S/4HANA is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Reltio sync back into SAP S/4HANA with its validations respected.

Common use cases

  • 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 03 Keep supplier records aligned between S/4HANA procurement and third-party spend platforms.
  • 04 Push closed-won CRM opportunities into S/4HANA as sales orders without manual re-keying.

Common sync patterns

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the SAP S/4HANA interface, limits, and retries.

React to ERP changes

Updates in SAP S/4HANA arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.

Where SAP S/4HANA is the HR system of record: people data for internal systems

Worker and org records stay current in Reltio for provisioning, access, and reporting systems that read from the database.

What you can sync between Reltio and SAP S/4HANA

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Reltio objects SAP S/4HANA objects How this pairing syncs
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Matches (Potential Matches) is specific to Reltio and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Production Orders Manufacturing order status surfaced in planning and operations tools. Activity Log is specific to Reltio and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Data Change Requests (DCR) is specific to Reltio and Business Partners to SAP S/4HANA — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Reference Data (RDM) is specific to Reltio and Sales Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Entities is specific to Reltio and Purchase Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Relations is specific to Reltio and Products / Materials to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Reltio and SAP S/4HANA

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Reltio SAP S/4HANA Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA Reltio Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Reltio ⇄ SAP S/4HANA

Connect Reltio and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in Reltio or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or SAP S/4HANA data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Reltio or SAP S/4HANA record.

Observability

Monitoring

Track your Reltio ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and SAP S/4HANA.

How the Reltio and SAP S/4HANA connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect Reltio to SAP S/4HANA — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Reltio and SAP S/4HANA with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Reltio connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio and SAP S/4HANA objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Reltio ⇄ SAP S/4HANA
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Reltio SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Reltio and SAP S/4HANA integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 434 integrations available for Reltio and SAP S/4HANA.

Popular · 7 of 434
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.