Can you integrate Rillet with Xactly?

Explore a Rillet and Xactly integration with a Stacksync engineer. Stacksync support for Xactly is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Rillet and Xactly sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Rillet and Xactly initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Generate an API key in Rillet Organization Setting > API Access. Identify the Xactly account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Rillet to Xactly sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Rillet fields to Xactly?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Rillet and Xactly integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Rillet and Xactly pilot start with?

Start by reviewing Invoice in Rillet and Orders in Xactly. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

Accounting and finance / CRM · Two-way sync platform

Rillet and Xactly integration

Plan how Rillet and Xactly should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Rillet

Xactly

Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Sales order process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Rillet Invoice or Xactly Orders needs a defined result in the other system.

Start with Rillet Invoice and Xactly Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Rillet and Xactly
Rillet record	Xactly record	Record matching	Field ownership
InvoiceDocumented record: Incremental: ; historical: ; delete detection:Business process handoff	OrdersProposed record; confirm Stacksync object support.	Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.	Finance owns invoice posting; the order system supplies the approved commercial context.
Invoice PaymentDocumented record: Incremental: ; historical: ; delete detection:Record matching	Payment Summary (Payable)Proposed record; confirm Stacksync object support.	Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.	Keep payment authorization, settlement, and accounting allocation distinct.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Rillet

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Customer Invoice Vendor Credit Memo Bill Journal Entry Invoice Payment Charge Reimbursement Custom Field	Incremental: ✅; historical: ✅; delete detection: ✅. Confirm field permissions and sync direction.
Account	Incremental: ✅; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction.
Subsidiary Tax Rate Product Contract Bank Account	Incremental: ❌; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction.
Bank Transaction	Incremental: ❌; historical: ✅; delete detection: ✅ Every 4h. Confirm field permissions and sync direction.

Read the Rillet connector guide

Xactly

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Orders Credits Transactions (Commission & Bonus) Participants (Payees) Positions & Titles Quotas / Targets	Confirm support for this record type and the direction you need.

Discuss Xactly requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Rillet	Xactly
Integration interface	REST API (OpenAPI-specified, with production and sandbox environments)	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	API key generated in Rillet	Confirm the credentials, API plan, and permissions required for Xactly.
Change detection	Historical and incremental syncs are documented by object.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Available for supported records	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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
DPF US-EU-UK-CH

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Rillet

Integration interface: REST API (OpenAPI-specified, with production and sandbox environments)
Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only to enable writes for two-way sync; check Read Only to prevent write-back
Change detection: Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Generate an API key in Rillet Organization Setting > API Access.
For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.

Limitations to check

Some objects have historical sync only; deletion checks for supported objects can run at different intervals.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Rillet setup guide

Xactly

Integration interface: 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: Confirm the credentials, API plan, and permissions required for Xactly.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Xactly account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Xactly, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Xactly and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Technical documentation

Xactly vendor API documentation

Prepare Rillet and Xactly access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Rillet setup checklist

Generate an API key in Rillet Organization Setting > API Access.
For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.

Setup guides: Authorize Rillet Connection

Xactly setup checklist

Identify the Xactly account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Xactly, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Rillet and Xactly planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Business process

Invoice / Orders

Order-to-invoice handoff: Xactly Orders provides context for Rillet Invoice. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rillet: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Xactly: Object support to establish
Record identity: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
Field ownership: Finance owns invoice posting; the order system supplies the approved commercial context.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: Rillet: Invoice documentation Xactly: Orders documentation

Record matching

Invoice Payment / Payment Summary (Payable)

Compare whether Rillet Invoice Payment and Xactly Payment Summary (Payable) describe the same payment or settlement in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rillet: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Xactly: Object support to establish
Record identity: Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Field ownership: Keep payment authorization, settlement, and accounting allocation distinct.

Fields to include

Source transaction ID
Invoice references
Amount and currency
Settlement status
Reversal reference

Record dependencies: Resolve the affected invoices and cash/account references before allocating the payment.
Validation: Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
Recovery: Look up the original transaction before retrying to prevent duplicate allocation or charging.

References: Rillet: Invoice Payment documentation Xactly: Payment Summary (Payable) documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Invoice / Orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Rillet and Xactly record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Invoice / Orders, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Invoice / Orders handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Rillet / Xactly migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Sales order process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Invoice or Orders record needs a defined result in the other system.

Start with Rillet Invoice and Xactly Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Payment or settlement sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Invoice Payment or Payment Summary (Payable) record needs a defined result in the other system.

Start with Rillet Invoice Payment and Xactly Payment Summary (Payable). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the affected invoices and cash/account references before allocating the payment.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.

If it fails: Look up the original transaction before retrying to prevent duplicate allocation or charging.

Reconcile Rillet business records with Xactly

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Rillet needs operational visibility through Orders or Payment Summary (Payable).

Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in Xactly; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated sales order change

Investigate

Inspect Rillet Invoice and Xactly Orders, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Rejected or repeated payment or settlement change

Investigate

Inspect Rillet Invoice Payment and Xactly Payment Summary (Payable), their IDs, and the destination error.

Next action

Look up the original transaction before retrying to prevent duplicate allocation or charging.

A record type or update is unavailable

Investigate

Check the Rillet and Xactly connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Rillet and Xactly

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Rillet Xactly Direction requires confirmation

Detect changesHistorical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.

Apply updatesConfirm that Stacksync can create or update the records you need in Xactly.

Xactly Rillet Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Rillet.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ