Skip to content
ERP ⇄ CRM

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

Keep SAP S/4HANA 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 S/4HANA and Xactly

Close the gap between front office and back office: Xactly and SAP S/4HANA share customers and status in real time, in both directions.

Xactly holds the customer relationship; SAP S/4HANA 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 Products & Customers, Orders, Credits, Transactions (Commission & Bonus) in Xactly with Sales Orders, Purchase Orders, Products / Materials, Billing Documents (Invoices) in SAP S/4HANA 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 Feed S/4HANA financial and logistics documents into a data warehouse for reporting without custom ABAP extracts.
  • 04 Keep supplier records aligned between S/4HANA procurement and third-party spend platforms.

Common sync patterns

Where SAP S/4HANA manages people and org data: keep Xactly aligned

Owners, territories, and org structure informed by SAP S/4HANA stay current in Xactly.

Where SAP S/4HANA handles order-to-cash: closed-won flows through

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

Where SAP S/4HANA is the finance system of record: money status on the account

Invoice and payment state from SAP S/4HANA shows on the account in Xactly, so reps see balances before promising the next order.

What you can sync between SAP S/4HANA 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 S/4HANA objects Xactly objects How this pairing syncs
Purchase Orders Procurement documents shared with supplier portals and spend-management tools. 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. Purchase Orders is specific to SAP S/4HANA and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side.
Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. 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. Products / Materials is specific to SAP S/4HANA and Participants (Payees) to Xactly — each maps to any object or custom field on the other side.
Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. 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. Billing Documents (Invoices) is specific to SAP S/4HANA and Positions & Titles to Xactly — each maps to any object or custom field on the other side.
Deliveries Outbound delivery status synced to customer-facing systems for order tracking. 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. Deliveries is specific to SAP S/4HANA and Quotas / Targets to Xactly — each maps to any object or custom field on the other side.
Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. Journal Entries is specific to SAP S/4HANA and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side.
Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. 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. Customer / Supplier Roles is specific to SAP S/4HANA and Products & Customers to Xactly — each maps to any object or custom field on the other side.

How changes propagate between SAP S/4HANA 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 S/4HANA Xactly 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 applied to Xactly as a row-level write, with types converted between the two schemas.

Xactly SAP S/4HANA 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 S/4HANA through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
  • 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 S/4HANA ⇄ Xactly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP S/4HANA 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 S/4HANA or Xactly record.

Observability

Monitoring

Track your SAP S/4HANA ⇄ 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 S/4HANA and Xactly.

How the SAP S/4HANA and Xactly connectors work

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

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 S/4HANA 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 S/4HANA 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 S/4HANA connected
    Xactly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP S/4HANA 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 S/4HANA ⇄ 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 S/4HANA Xactly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

SAP S/4HANA 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 532 integrations available for SAP S/4HANA and Xactly.

Popular · 5 of 532
Coworkers laughing in front of a laptop in a casual office setting

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