Skip to content
ERP ⇄ CRM

SAP Business ByDesign to Xactly integration — real-time, two-way sync

Keep SAP Business ByDesign 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.

  • 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 SAP Business ByDesign and Xactly

Close the gap between front office and back office: Xactly and SAP Business ByDesign share customers and status in real time, in both directions.

Xactly holds the customer relationship; SAP Business ByDesign 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 Payment Summary (Payable), Products & Customers, Orders, Credits in Xactly with Employees, Business Partners (Accounts), Contacts, Sales Orders in SAP Business ByDesign 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.

Common use cases

  • 01 Mirror commission Transactions and Credits into a data warehouse to power rep-facing dashboards and comp-plan analytics without manual exports.
  • 02 Sync Participants, Positions, Titles, and Quotas from an HRIS/HCM and planning tools into Xactly so the org hierarchy and targets stay aligned with headcount changes.
  • 03 Replicate customer invoices into a reporting database or collections tool without manual exports.
  • 04 Align the ByDesign material master with external product catalogs and inventory systems.

Common sync patterns

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

Where SAP Business ByDesign manages people and org data: keep Xactly aligned

Owners, territories, and org structure informed by SAP Business ByDesign stay current in Xactly.

Where SAP Business ByDesign handles order-to-cash: closed-won flows through

A deal won in Xactly creates or updates the customer in SAP Business ByDesign with clean data, so fulfillment and invoicing start without re-entry.

What you can sync between SAP Business ByDesign and 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.

SAP Business ByDesign objects Xactly objects How this pairing syncs
Sales Orders Order documents created from external channels and read for status. 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. Sales Orders is specific to SAP Business ByDesign and Credits to Xactly — each maps to any object or custom field on the other side.
Customer Invoices Billing documents synced outward for collections and CRM visibility. 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. Customer Invoices is specific to SAP Business ByDesign and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side.
Materials / Products Item master data aligned with e-commerce and inventory systems. Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. Materials / Products is specific to SAP Business ByDesign and Participants (Payees) to Xactly — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier systems. Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. Purchase Orders is specific to SAP Business ByDesign and Positions & Titles to Xactly — each maps to any object or custom field on the other side.
Opportunities Built-in CRM records synced with external sales tools when both are in use. 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. Opportunities is specific to SAP Business ByDesign and Quotas / Targets to Xactly — each maps to any object or custom field on the other side.
Projects Project structures and tasks read for time and billing integrations. Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. Projects is specific to SAP Business ByDesign and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side.

How changes propagate between SAP Business ByDesign and Xactly

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.

SAP Business ByDesign Xactly Interval-based propagation

DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed timestamps.

DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.

Xactly SAP Business ByDesign Interval-based propagation

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 SAP Business ByDesign through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Xactly: Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
What ships with SAP Business ByDesign ⇄ Xactly

Connect SAP Business ByDesign and Xactly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Business ByDesign–Xactly connection.

Real-time

Two-way sync

Changes in SAP Business ByDesign or Xactly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP Business ByDesign or Xactly 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 SAP Business ByDesign or Xactly record.

Observability

Monitoring

Track your SAP Business ByDesign ⇄ Xactly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP Business ByDesign and Xactly.

How the SAP Business ByDesign and Xactly connectors work

SAP Business ByDesign

Integration surface
SOAP web services plus OData services for analytical and custom data access
Authentication
Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios
Change detection
Polling on last-changed timestamps; the platform does not offer a general webhook surface
Capabilities
read · write

Xactly

Integration surface
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.
Change detection
No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based.
Capabilities
read · write
Rate limits
Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
Xactly setup guide
How it works

How to connect SAP Business ByDesign to Xactly — 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 SAP Business ByDesign 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    SAP Business ByDesign connected
    Xactly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP Business ByDesign 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · SAP Business ByDesign ⇄ Xactly
    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
    SAP Business ByDesign Xactly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

SAP Business ByDesign and Xactly 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 539 integrations available for SAP Business ByDesign and Xactly.

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

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