Two-way sync
Changes in Dynamics 365 Business Central or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Xactly holds the customer relationship; Dynamics 365 Business Central runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Positions & Titles, Quotas / Targets, Payment Summary (Payable), Products & Customers in Xactly with Vendors, Items, Sales Orders, Sales Invoices in Dynamics 365 Business Central field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Invoice and payment state from Dynamics 365 Business Central shows on the account in Xactly, so reps see balances before promising the next order.
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Owners, territories, and org structure informed by Dynamics 365 Business Central stay current in Xactly.
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 | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Items Product and inventory records aligned with e-commerce and warehouse systems. | Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. | Items is specific to Dynamics 365 Business Central and Quotas / Targets to Xactly — 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. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Sales Orders is specific to Dynamics 365 Business Central and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. | |
| Sales Invoices Billing documents synced to CRMs and payment platforms. | Products & Customers Product and customer/account master used in crediting rules and reporting; loaded and updated from CRM/ERP through Connect (write) and read for lookups, so read and write. | Sales Invoices is specific to Dynamics 365 Business Central and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. | Purchase Orders is specific to Dynamics 365 Business Central and Orders to Xactly — each maps to any object or custom field on the other side. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | General Ledger Entries is specific to Dynamics 365 Business Central and Credits to Xactly — each maps to any object or custom field on the other side. | |
| Journals Staging records for financial postings created by integrations before posting. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | Journals is specific to Dynamics 365 Business Central and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. |
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.
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 applied to Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Xactly connection.
Changes in Dynamics 365 Business Central or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 Business Central or Xactly record.
Track your Dynamics 365 Business Central ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Xactly.
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.
Authenticate Dynamics 365 Business Central and Xactly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Dynamics 365 Business Central and Xactly 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 Business Central and Xactly: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Items and Sales Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Xactly: Where Dynamics 365 Business Central is the finance system of record: money status on the account; One customer master; Where Dynamics 365 Business Central manages people and org data: keep Xactly aligned. Invoice and payment state from Dynamics 365 Business Central shows on the account in Xactly, so reps see balances before promising the next order.
Dynamics 365 Business Central: 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. Xactly: Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com). Authentication: OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent. Stacksync manages authentication, retries, and rate limits on both sides.
Xactly: Xactly Connect is genuinely two-way: Orders, Credits, Participants, Positions, Quotas, and reference master are loaded into Incent through Connect load/ETL steps, while calculated Transactions and Payment Summary are extracted out, so Xactly is both a target and a source. Dynamics 365 Business Central: Writes use ETags with If-Match headers for optimistic concurrency, so stale updates are rejected instead of silently overwriting ERP data. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Xactly 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 Dynamics 365 Business Central and Xactly records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 532 integrations available for Dynamics 365 Business Central and Xactly.