Real-time
Two-way sync
Changes in Dynamics 365 Business Central or Reltio instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Dynamics 365 Business Central to Reltio integration — real-time, two-way sync
Keep Dynamics 365 Business Central and Reltio 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 Dynamics 365 Business Central and Reltio
Give your engineers Dynamics 365 Business Central'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 Sales Invoices, Purchase Orders, General Ledger Entries, Journals from Dynamics 365 Business Central into Reltio and keeps both sides consistent in real time. Whatever Dynamics 365 Business Central 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 Dynamics 365 Business Central with its validations respected.
Common use cases
- 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
- 03 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
- 04 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
Common sync patterns
React to ERP changes
Updates in Dynamics 365 Business Central arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
Where Dynamics 365 Business Central 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.
Controlled write-back
Choose exactly which tables and fields may flow from Reltio back into Dynamics 365 Business Central, keeping the ERP authoritative.
What you can sync between Dynamics 365 Business Central and Reltio
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.
| Dynamics 365 Business Central objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Dimensions is specific to Dynamics 365 Business Central and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| Payments Customer and vendor payment records reconciled against invoices. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Payments is specific to Dynamics 365 Business Central and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| Customers Core master data synced with CRMs so sales and finance share one customer list. | 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. | Customers is specific to Dynamics 365 Business Central and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Vendors Supplier master data synced with procurement and AP automation tools. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Vendors is specific to Dynamics 365 Business Central and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Items Product and inventory records aligned with e-commerce and warehouse systems. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Items is specific to Dynamics 365 Business Central and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | 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 is specific to Dynamics 365 Business Central and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 Business Central and Reltio
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.
Dynamics 365 Business Central Reltio Sub-second propagation
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Dynamics 365 Business Central 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 Dynamics 365 Business Central 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.
What ships with Dynamics 365 Business Central ⇄ Reltio
Connect Dynamics 365 Business Central and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 Business Central or Reltio 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 Dynamics 365 Business Central or Reltio record.
Observability
Monitoring
Track your Dynamics 365 Business Central ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Reltio.
How the Dynamics 365 Business Central and Reltio connectors work
Dynamics 365 Business Central
- Integration surface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
- Capabilities
- read · write · webhooks
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.
How it works
How to connect Dynamics 365 Business Central to Reltio — 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.
- 01
Connect your apps
Authenticate Dynamics 365 Business Central and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dynamics 365 Business Central
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 Business Central and Reltio 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.
objects · Dynamics 365 Business Central ⇄ ReltioCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dynamics 365 Business Central ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 Business Central and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 Business Central and Reltio: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Dimensions and Payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Dynamics 365 Business Central and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. On Reltio: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Data Change Requests (DCR), Reference Data (RDM), Entities, Relations, plus custom fields where Reltio exposes them. On the Dynamics 365 Business Central side: Sales Invoices, Purchase Orders, General Ledger Entries, Journals. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Dynamics 365 Business Central and Reltio: React to ERP changes; Where Dynamics 365 Business Central is the HR system of record: people data for internal systems; Controlled write-back. Updates in Dynamics 365 Business Central arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
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 Dynamics 365 Business Central and Reltio.
Popular · 4 of 434
-
Dynamics 365 Business Central ⇄ Oracle DB -
Dynamics 365 Business Central ⇄ RavenDB -
Dynamics 365 Business Central ⇄ Redis Enterprise -
Dynamics 365 Business Central ⇄ SAP ASE (Sybase)
No integrations match .
