Two-way sync
Changes in Rillet or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Keep Rillet and SQL Server in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Journal Entry, Invoice Payment, Charge, Reimbursement from Rillet into CDC Change Tables, Stored Procedures, Databases, Schemas in SQL Server and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against SQL Server, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Changes in Rillet appear in SQL Server as row changes, so you can trigger downstream logic with the database tooling you already use.
Customers, invoices, and payments from Rillet live in SQL Server as regular tables or collections your team can join, index, and query.
Build dashboards and back-office tools directly on SQL Server; Stacksync handles the API calls, rate limits, and retries against Rillet.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Rillet objects | SQL Server objects | |
|---|---|---|
| Customer Synced with incremental and full sync per the Stacksync docs. | CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. | |
| Vendor Synced with incremental and full sync per the Stacksync docs. | Stored Procedures T-SQL logic that can validate or post-process synced rows. | |
| Invoice Synced with incremental and full sync per the Stacksync docs. | Databases Instance-level databases that scope a sync's reads and writes. | |
| Credit Memo Synced with incremental and full sync per the Stacksync docs. | Schemas Namespaces (dbo and custom) used to organize synced tables. | |
| Bill Synced with incremental and full sync per the Stacksync docs. | Tables The primary sync target; rows map to records in connected systems. | |
| Journal Entry Synced with incremental and full sync per the Stacksync docs. | Views Read-side projections used as outbound sync sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rillet–SQL Server connection.
Changes in Rillet or SQL Server instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rillet or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Rillet or SQL Server record.
Track your Rillet ⇄ SQL Server sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rillet and SQL Server.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Rillet and SQL Server with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Rillet and SQL Server objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Rillet and SQL Server: authenticate both systems, choose the objects to sync (such as Rillet's Customer and Vendor), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Rillet and SQL Server. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). On SQL Server: SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Rillet side: Journal Entry, Invoice Payment, Charge, Reimbursement, plus custom fields where Rillet exposes them. On the SQL Server side: CDC Change Tables, Stored Procedures, Databases, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Rillet and SQL Server: React to financial events; Query finance data like any other data; Internal tools without API plumbing. Changes in Rillet appear in SQL Server as row changes, so you can trigger downstream logic with the database tooling you already use.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Rillet and SQL Server.