Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
Accounting and finance / ERP · Two-way sync platform

Rillet and Rootstock ERP integration

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

Set this up from Claude or ChatGPT
  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
Rillet
Rootstock ERP
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

Supplier bill sync test

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

Starting eventA change involving Rillet Bill or Rootstock ERP Bills of Material needs a defined result in the other system.

  1. Start with Rillet Bill and Rootstock ERP Bills of Material. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.

  3. 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 duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Review records and field ownership

AI assistant

Set up Rillet and Rootstock ERP from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Rillet and Rootstock ERP.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Rillet and Rootstock ERP. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Rillet record changes.”
  • “Create a Genie that answers questions about our Rootstock ERP data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

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 Rootstock ERP
Rillet recordRootstock ERP recordRecord matchingField ownership
BillDocumented record: Incremental: Yes; historical: Yes; delete detection: YesRecord matchingBills of MaterialProposed record; confirm Stacksync object support.Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.
InvoiceDocumented record: Incremental: Yes; historical: Yes; delete detection: YesBusiness process handoffSales 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.

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 typesCoverage and requirements
  • Customer
  • Invoice
  • Vendor
  • Credit Memo
  • Bill
  • Journal Entry
  • Invoice Payment
  • Charge
  • Reimbursement
  • Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes. Confirm field permissions and sync direction.
  • Account
Incremental: Yes; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Subsidiary
  • Tax Rate
  • Product
  • Contract
  • Bank Account
Incremental: No; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Bank Transaction
Incremental: No; historical: Yes; delete detection: Yes, every 4h. Confirm field permissions and sync direction.

Read the Rillet connector guide

Rootstock ERP

Connection and object support require review

Record types to review with Stacksync

Record typesCoverage and requirements
  • Sales Orders
  • Work Orders
  • Purchase Orders
  • Items / Products
  • Bills of Material
  • Inventory Balances
Confirm support for this record type and the direction you need.

Discuss Rootstock ERP 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 requirementRilletRootstock ERP
Integration interfaceREST API (OpenAPI-specified, with production and sandbox environments)Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
AuthenticationAPI key generated in RilletConfirm the credentials, API plan, and permissions required for Rootstock ERP.
Change detectionHistorical and incremental syncs are documented by object.Confirm how Stacksync detects changes for this connector and the objects you need.
Read accessAvailable for supported recordsConfirm with Stacksync
Write accessAvailable for supported recordsConfirm 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
Rootstock ERP
Integration interface
Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication
Confirm the credentials, API plan, and permissions required for Rootstock ERP.
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 Rootstock ERP account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for Rootstock ERP and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Rillet and Rootstock ERP 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

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

Bill / Bills of Material

Compare whether Rillet Bill and Rootstock ERP Bills of Material describe the same supplier bill in your business.

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

Rillet
Documented record · Incremental: Yes; historical: Yes; delete detection: Yes
Rootstock ERP
Object support to establish
Record identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership
Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Fields to include

  • Source bill ID
  • Supplier reference
  • Entity
  • Line amounts and currency
  • Approval/posting state
Record dependencies
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

References: Rillet: Bill documentation

Business process

Invoice / Sales Orders

Order-to-invoice handoff: Rootstock ERP 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: Yes; historical: Yes; delete detection: Yes
Rootstock ERP
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

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Bill / Bills of Material 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: Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. 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 Rootstock ERP 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 Bill / Bills of Material, 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 / Rootstock ERP 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

Supplier bill sync test

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

Starting event: A change to the selected Bill or Bills of Material record needs a defined result in the other system.

  1. Start with Rillet Bill and Rootstock ERP Bills of Material. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
  3. 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 duplicate supplier document number in another entity, a partially paid bill, and a closed period.

If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

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.

  1. Start with Rillet Invoice and Rootstock ERP Sales Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
  3. 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.

Reconcile Rillet business records with Rootstock ERP

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

Starting event: A finance-owned record in Rillet needs operational visibility through Sales Orders or Purchase Orders.

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

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Bill / Bills of Material

Test case

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Expected result

The expected supplier bill relationship is preserved with no duplicate action or unintended write.

Invoice / Sales Orders

Test case

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

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

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

Rejected or repeated supplier bill change

Investigate

Inspect Rillet Bill and Rootstock ERP Bills of Material, their IDs, and the destination error.

Next action

Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Rejected or repeated sales order change

Investigate

Inspect Rillet Invoice and Rootstock ERP 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.

A record type or update is unavailable

Investigate

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

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

Rillet Rootstock ERP 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 Rootstock ERP.

Rootstock ERP 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

Rillet and Rootstock ERP integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

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

Talk to an engineer Explore plans and pricing