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 · Two-way sync platform

Rillet connector for two-way sync.

Keep Rillet and your business systems aligned with Stacksync. Sync Customer, Invoice and Bill within the connector’s object and field requirements, with two-way sync for eligible records.

Set this up from Claude or ChatGPT
  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Rillet

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Rillet objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Customer
Incremental: Yes; historical: Yes; delete detection: Yes
Invoice
Incremental: Yes; historical: Yes; delete detection: Yes
Bill
Incremental: Yes; historical: Yes; delete detection: Yes
Invoice Payment
Incremental: Yes; historical: Yes; delete detection: Yes
View all 17 object types and restrictions
Account
Incremental: Yes; historical: Yes; delete detection: Yes, every 1h
Subsidiary
Incremental: No; historical: Yes; delete detection: Yes, every 1h
Tax Rate
Incremental: No; historical: Yes; delete detection: Yes, every 1h
Vendor
Incremental: Yes; historical: Yes; delete detection: Yes
Product
Incremental: No; historical: Yes; delete detection: Yes, every 1h
Contract
Incremental: No; historical: Yes; delete detection: Yes, every 1h
Credit Memo
Incremental: Yes; historical: Yes; delete detection: Yes
Journal Entry
Incremental: Yes; historical: Yes; delete detection: Yes
Charge
Incremental: Yes; historical: Yes; delete detection: Yes
Reimbursement
Incremental: Yes; historical: Yes; delete detection: Yes
Bank Account
Incremental: No; historical: Yes; delete detection: Yes, every 1h
Bank Transaction
Incremental: No; historical: Yes; delete detection: Yes, every 4h
Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes

Read the Rillet object and setup guide

Connection setup

Rillet connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
REST API (OpenAPI-specified, with production and sandbox environments)
Account access
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
How changes are detected
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.

Sync directions

  • Read data Documented
  • Write data Documented
RilletStacksync setup guide
Setup prerequisites for your administrator
  • 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.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Rillet integration.

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
RilletSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Preserve the financial record ID and subsidiary context. Keep Invoice, Invoice Payment, and Journal Entry identities separate when comparing totals or reflecting a payment status elsewhere.
Load related records in the right order
Resolve Customer, Vendor, Product, and account references required by the selected financial object. Check its support for later updates independently of historical loading.

Mapping checks by record type

Customer

Incremental: Yes; historical: Yes; delete detection: Yes

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.
Fields to consider
Source customer ID · Person/company classification · Legal entity or business unit · Destination identity reference
Related records to resolve first
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test before going live
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Invoice

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Fields to consider
Source invoice ID · Customer or supplier reference · Line totals · Currency · Posting/payment status
Related records to resolve first
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test before going live
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Bill

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Fields to consider
Source bill ID · Supplier reference · Entity · Line amounts and currency · Approval/posting state
Related records to resolve first
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test before going live
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Invoice Payment

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Fields to consider
Source transaction ID · Invoice references · Amount and currency · Settlement status · Reversal reference
Related records to resolve first
Resolve the affected invoices and cash/account references before allocating the payment.
Test before going live
Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.

Journal Entry

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Retain journal ID and line IDs within the legal entity and accounting period.
Fields to consider
Source journal ID · Account references · Debit/credit amounts · Entity · Accounting period
Related records to resolve first
Resolve chart-of-account, currency, entity, and dimension references before lines.
Test before going live
Verify balanced debits and credits, dimension requirements, and rejection for a closed period.

Vendor

Incremental: Yes; historical: Yes; delete detection: Yes

Identity
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Fields to consider
Source supplier ID · Legal name · Entity reference · Payment terms · Active status
Related records to resolve first
Resolve business-unit and payment-term references before purchasing transactions.
Test before going live
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Rillet integration in four steps.

Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

View the four setup tests and expected results

  1. Verify Rillet credentials and resource scope

    Use the documented setup with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object.

    Expected result: The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner.

  2. Distinguish historical loading from ongoing changes

    Select an object with the required incremental support, load a test record, and update it. For write-back, verify that the API key’s Read Only setting is cleared.

    Expected result: The observed operation matches both the object matrix and the API key permission; historical-only objects have a separate refresh plan.

  3. Test writes in the directions you need

    Select one eligible Rillet object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Rillet records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Rillet integration.

Diagnose record matching, delayed changes, and rejected operations
A historical record appears but later edits do not
Check that object’s incremental support and the API key permission. Do not infer ongoing capture or uniform deletion timing from a successful backfill.
The first load looks correct but later results differ
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Rillet object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Rillet workflow with an engineer

Rillet integration guides

FAQ

Rillet connector FAQ

How should I plan an integration with Rillet?

API-key write permissions and object-specific history, incremental, and deletion support must agree. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Rillet connector write changes back?

Stacksync supports reads and writes for eligible Rillet objects. Check the selected fields, account permissions, and the other system’s connector. Select an object with the required incremental support, load a test record, and update it. For write-back, verify that the API key’s Read Only setting is cleared.

Which identifiers should I preserve for Rillet data?

Preserve the financial record ID and subsidiary context. Keep Invoice, Invoice Payment, and Journal Entry identities separate when comparing totals or reflecting a payment status elsewhere.

Which related records should I load first for Rillet?

Resolve Customer, Vendor, Product, and account references required by the selected financial object. Check its support for later updates independently of historical loading.

What should I check if Rillet data is missing or delayed?

Check that object’s incremental support and the API key permission. Do not infer ongoing capture or uniform deletion timing from a successful backfill.

What will we cover in a Rillet integration demo?

Start with one workflow and a sample record from Customer, Invoice and Bill. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

Set up Rillet 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 another app or database.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Rillet. 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 Rillet 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.

Explore Rillet connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

175 integration guides

CRM · 32

ERP · 31

Database · 23

Data warehouse · 14

Business productivity · 26

Accounting and finance · 15

Analytics · 2

E-commerce · 6

Human resources · 12

Marketing · 8

Security and identity · 6

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started