Can you integrate Rillet with Salesforce?

Stacksync connects Rillet and Salesforce with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.

Can Rillet and Salesforce sync in both directions?

Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.

What should be ready before the Rillet and Salesforce 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. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Rillet to Salesforce 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 Salesforce?

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

Start by reviewing Customer in Rillet and Accounts in Salesforce. 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 Salesforce integration — two-way sync

Keep supported Rillet and Salesforce records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.

Field mappings and sync direction under your control
Inspect and resolve record errors in one dashboard

Two-way sync for supported objects

stacksync.com

Rillet

Salesforce

Explore record coverage

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

Example workflow

Customer sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting eventA change involving Rillet Customer or Salesforce Accounts needs a defined result in the other system.

Start with Rillet Customer and Salesforce Accounts. 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

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Example record relationships between Rillet and Salesforce
Rillet record	Salesforce record	Record matching	Field ownership
CustomerDocumented record: Incremental: ; historical: ; delete detection:Customer identity assessment	AccountsProposed 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.
CustomerDocumented record: Incremental: ; historical: ; delete detection:Customer identity assessment	ContactsProposed 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.

Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.

Why teams connect Rillet and Salesforce

Put your Rillet and Salesforce data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Rillet and Salesforce workflow to test, define what success looks like, and decide who handles failed updates.

Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

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

Salesforce

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Writable standard objects (subject to detection mode) Writable custom objects (subject to detection mode)	See connector requirements. Confirm field permissions and sync direction.

Read the Salesforce connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits

Connection requirement	Rillet	Salesforce
Integration interface	REST API (OpenAPI-specified, with production and sandbox environments)	REST, SOAP, and Bulk APIs
Authentication	API key generated in Rillet	OAuth login via a Salesforce user
Change detection	Historical and incremental syncs are documented by object.	Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used.
Read access	Available for supported records	Available for supported records
Write access	Available for supported records	Available for supported records

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

Salesforce

Integration interface: REST, SOAP, and Bulk APIs
Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection: Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
Test in a sandbox and make the intended objects and fields visible to the connected user.

Limitations to check

Object eligibility depends on write access and the selected detection mode. Non-triggerable objects cannot use trigger mode.
Read-only and formula fields need separate handling; a Salesforce platform capability does not establish support for every object.

Technical documentation

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

Salesforce setup guide

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

Salesforce setup checklist

Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
Test in a sandbox and make the intended objects and fields visible to the connected user.

Setup guides: Authorize Salesforce

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 Salesforce planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Customer identity

Customer / Accounts

Before linking Rillet Customer to Salesforce Accounts, check whether the customer is an individual or a company. Match the correct record type in each system.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Rillet: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Salesforce: 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 Salesforce: Accounts documentation

Customer identity

Customer / Contacts

Before linking Rillet Customer to Salesforce Contacts, check whether the customer is an individual or a company. Match the correct record type in each system.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Rillet: Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Salesforce: 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 Salesforce: Contacts documentation

Compare integration approaches

Use Rillet Customer and Salesforce Accounts for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.

Stacksync managed sync

Best fit: Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
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 Salesforce 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 / Accounts, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Rillet and Salesforce need a transformation, approval, or action outside a direct record sync.
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 / Salesforce 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

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

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

Start with Rillet Customer and Salesforce Accounts. 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.

Customer sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

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

Start with Rillet Customer and Salesforce Contacts. 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.

Reconcile Rillet business records with Salesforce

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A finance-owned record in Rillet needs operational visibility through Accounts or Contacts.

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

Investigate

Inspect Rillet Customer and Salesforce Contacts, their IDs, and the destination error.

Next action

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

A record type or update is unavailable

Investigate

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

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

Rillet Salesforce Timing depends on the connected systems

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

Apply updatesSelected writable fields update in Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Salesforce Rillet Timing depends on the connected systems

Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.

Apply updatesSelected writable fields update in Rillet. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

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.

FAQ

Rillet and Salesforce integration FAQ

Guides and resources

Next step

See your workflow in Stacksync

Walk through your Rillet and Salesforce records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing

Rillet and Salesforce integration — two-way sync

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

Rillet

Salesforce

Compliance and data transfers

SSO & SCIM

Alerts

Secure connection options

Record-level recovery

Authentication, permissions and API limits

Connection requirements and limits

Rillet

Setup requirements

Limitations to check

Technical documentation

Salesforce

Setup requirements

Limitations to check

Technical documentation

Rillet setup checklist

Salesforce setup checklist

Prepare to go live

Record identity and field ownership

Customer / Accounts

Customer / Contacts

Compare integration approaches

Stacksync managed sync

Native vendor integration

Custom API or workflow

File or scheduled snapshot

Workflow scenarios and expected results

Customer sync test

Customer sync test

Reconcile Rillet business records with Salesforce

Initial load and acceptance testing

Customer / Accounts

Customer / Contacts

Direction and permissions

Freshness and reconciliation

Failed updates, retries and recovery

Rejected or repeated customer change

Rejected or repeated customer change

A record type or update is unavailable

Source and destination disagree after a retry

Change detection and update delivery

How updates move between Rillet and Salesforce

Update timing and record limits

More connections to explore