Can you integrate Rillet with SAP?

Explore a Rillet and SAP integration with a Stacksync engineer. Stacksync support for SAP 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 SAP 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 SAP 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 SAP 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 SAP 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 SAP?

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 SAP 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 SAP pilot start with?

Start by reviewing Customer in Rillet and Business Partners in SAP. 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 / ERP · Two-way sync platform

Rillet and SAP integration

Plan how Rillet and SAP 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

SAP

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

Customer sync test

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

Starting eventA change involving Rillet Customer or SAP Business Partners needs a defined result in the other system.

Start with Rillet Customer and SAP Business Partners. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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 an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

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 SAP
Rillet record	SAP record	Record matching	Field ownership
CustomerDocumented record: Incremental: ; historical: ; delete detection:Record matching	Business PartnersProposed record; confirm Stacksync object support.	Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
InvoiceDocumented record: Incremental: ; historical: ; delete detection:Business process handoff	Sales 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.
Journal EntryDocumented record: Incremental: ; historical: ; delete detection:Record matching	GL Accounts and Journal EntriesProposed record; confirm Stacksync object support.	Retain journal ID and line IDs within the legal entity and accounting period.	The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.

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

SAP

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Business Partners Materials (Products) Sales Orders Purchase Orders Outbound Deliveries Billing Documents	Confirm support for this record type and the direction you need.

Discuss SAP 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	SAP
Integration interface	REST API (OpenAPI-specified, with production and sandbox environments)	OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication	API key generated in Rillet	Confirm the credentials, API plan, and permissions required for SAP.
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

SAP

Integration interface: OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication: Confirm the credentials, API plan, and permissions required for SAP.
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 SAP account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for SAP, including read/write support, authentication, and initial-load limits.

Limitations to check

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

Prepare Rillet and SAP 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

SAP setup checklist

Identify the SAP account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for SAP, 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 SAP 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

Record matching

Customer / Business Partners

Compare whether Rillet Customer and SAP Business Partners describe the same customer 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: ✅
SAP: Object support to establish
Record identity: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: Rillet: Customer documentation

Business process

Invoice / Sales Orders

Order-to-invoice handoff: SAP Sales 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: ✅
SAP: 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

Record matching

Journal Entry / GL Accounts and Journal Entries

Compare whether Rillet Journal Entry and SAP GL Accounts and Journal Entries describe the same journal or ledger entry 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: ✅
SAP: Object support to establish
Record identity: Retain journal ID and line IDs within the legal entity and accounting period.
Field ownership: The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.

Fields to include

Source journal ID
Account references
Debit/credit amounts
Entity
Accounting period

Record dependencies: Resolve chart-of-account, currency, entity, and dimension references before lines.
Validation: Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
Recovery: Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.

References: Rillet: Journal Entry documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Customer / Business Partners 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: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. 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 SAP 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 Customer / Business Partners, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Invoice / Sales 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 / SAP 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

Customer sync test

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

Starting event: A change to the selected Customer or Business Partners record needs a defined result in the other system.

Start with Rillet Customer and SAP Business Partners. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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 an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

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 Sales Orders record needs a defined result in the other system.

Start with Rillet Invoice and SAP Sales 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.

Journal or ledger entry sync test

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

Starting event: A change to the selected Journal Entry or GL Accounts and Journal Entries record needs a defined result in the other system.

Start with Rillet Journal Entry and SAP GL Accounts and Journal Entries. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve chart-of-account, currency, entity, and dimension references before lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Verify balanced debits and credits, dimension requirements, and rejection for a closed period.

If it fails: Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.

Reconcile Rillet business records with SAP

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

Starting event: A finance-owned record in Rillet needs operational visibility through Business Partners or Materials (Products).

Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in SAP; 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 customer change

Investigate

Inspect Rillet Customer and SAP Business Partners, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated sales order change

Investigate

Inspect Rillet Invoice and SAP Sales 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 journal or ledger entry change

Investigate

Inspect Rillet Journal Entry and SAP GL Accounts and Journal Entries, their IDs, and the destination error.

Next action

Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.

A record type or update is unavailable

Investigate

Check the Rillet and SAP 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 SAP

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

Rillet SAP 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 SAP.

SAP 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