Skip to content
Database ⇄ Accounting and finance

Azure SQL Database to Rillet integration — real-time, two-way sync

Keep Azure SQL Database and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

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
Why teams connect Azure SQL Database and Rillet

Work with Rillet's financial data straight from Azure SQL Database: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

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 Vendor, Invoice, Credit Memo, Bill from Rillet into Tables, Views, Schemas, Rows and columns in Azure SQL Database and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Azure SQL Database, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.

Common use cases

  • Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • Sync AR and collection status back to customer success tools ahead of renewals.
  • Expose SaaS data (billing, support tickets) as tables in Azure SQL for reporting teams already on Microsoft tooling.
  • Replicate Azure SQL tables to a warehouse without building custom CDC pipelines.

Write back safely

Updates written to the synced tables in Azure SQL Database propagate into Rillet, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Rillet appear in Azure SQL Database as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Rillet live in Azure SQL Database as regular tables or collections your team can join, index, and query.

What you can sync between Azure SQL Database and 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.

Azure SQL Database objects Rillet objects
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. Journal Entry Synced with incremental and full sync per the Stacksync docs.
Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. Invoice Payment Synced with incremental and full sync per the Stacksync docs.
Change tracking / CDC tables System-maintained change records used to drive incremental sync. Charge Synced with incremental and full sync per the Stacksync docs.
Tables The primary sync target; rows map one-to-one to records in the paired system. Reimbursement Synced with incremental and full sync per the Stacksync docs.
Views Read-only projections used when the sync should expose a curated shape rather than raw tables. Custom Field Synced with incremental and full sync per the Stacksync docs.
Schemas Namespaces that organize tables and control which objects a sync user can reach. Account Synced with incremental and full sync per the Stacksync docs.
What ships with Azure SQL Database ⇄ Rillet

Connect Azure SQL Database and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure SQL Database–Rillet connection.

Real-time

Two-way sync

Changes in Azure SQL Database or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure SQL Database or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure SQL Database or Rillet record.

Observability

Monitoring

Track your Azure SQL Database ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Rillet.

How the Azure SQL Database and Rillet connectors work

Azure SQL Database

Integration surface
SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
Authentication
SQL authentication (database credentials) or Microsoft Entra ID authentication
Change detection
Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback
Capabilities
read · write · CDC

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect Azure SQL Database to Rillet — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Azure SQL Database and Rillet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure SQL Database connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure SQL Database and Rillet 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure SQL Database ⇄ Rillet
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure SQL Database Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure SQL Database and Rillet integration FAQ

SECURITY

Security teams love 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.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Azure SQL Database and Rillet.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.