Real-time
Two-way sync
Changes in Acumatica or Reltio instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Acumatica to Reltio integration — real-time, two-way sync
Keep Acumatica 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 Acumatica and Reltio
Give your engineers Acumatica'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 Journal Transactions, Projects, Opportunities and Cases, Customers from Acumatica into Reltio and keeps both sides consistent in real time. Whatever Acumatica 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 Acumatica 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 Mirror stock items and quantities to external channels so availability stays accurate across systems.
- 04 Replicate journal transactions and financial data into a SQL database for reporting and consolidation.
Common sync patterns
React to ERP changes
Updates in Acumatica arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
Where Acumatica 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 Acumatica, keeping the ERP authoritative.
What you can sync between Acumatica 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.
| Acumatica objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Opportunities and Cases is specific to Acumatica and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Customers is specific to Acumatica and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Vendors Supplier records aligned with procurement and AP automation. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Vendors is specific to Acumatica and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | 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. | Sales Orders is specific to Acumatica and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | 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. | Invoices is specific to Acumatica and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | 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. | Purchase Orders is specific to Acumatica and Crosswalks to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Acumatica 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.
Acumatica Reltio Sub-second propagation
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Acumatica 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 Acumatica 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 Acumatica ⇄ Reltio
Connect Acumatica and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Acumatica 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 Acumatica or Reltio record.
Observability
Monitoring
Track your Acumatica ⇄ Reltio sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Acumatica and Reltio.
How the Acumatica and Reltio connectors work
Acumatica
- Integration surface
- Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries
- Authentication
- OAuth 2.0 or cookie-based session login with Acumatica credentials
- Change detection
- Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
- 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 Acumatica 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 Acumatica 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.
Acumatica
connected
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Acumatica 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 · Acumatica ⇄ 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.
Acumatica ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Acumatica and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Acumatica and Reltio: authenticate both systems, choose the objects to sync (such as Acumatica's Opportunities and Cases and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Reltio: Every Reltio entity carries one or more crosswalks — references to the source systems and their record IDs — which is how survivorship merges multiple source records into one golden record and how writes are attributed back to a source. Acumatica: Custom fields defined in the instance can be added to the API entity contract, so tenant customizations participate in syncs alongside standard fields. Stacksync's field mapping accounts for these differences between Acumatica and Reltio without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Acumatica and Reltio records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Acumatica and Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Acumatica–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Acumatica and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. 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.
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 441 integrations available for Acumatica and Reltio.
Popular · 5 of 441
-
Acumatica ⇄ MongoDB -
Acumatica ⇄ CockroachDB -
Acumatica ⇄ Google AlloyDB -
Acumatica ⇄ Dynamo DB -
Reltio ⇄ Linnworks
No integrations match .
