Skip to content
Accounting and finance

Recurly to Rillet integration — real-time, two-way sync

Keep Recurly 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 Recurly and Rillet

Keep the customer, invoice, and payment records that Recurly and Rillet share consistent in real time, whether the two systems split your finance stack or one is replacing the other.

Two finance systems in one company usually means one of two setups. Either the systems divide the work, with one issuing invoices or serving a business unit while the other holds the books, or one is on its way out and both must stay accurate during the transition. In both cases, the customer, invoice, and payment records the two systems share start to drift the moment updates are keyed twice or moved by hand.

Stacksync syncs Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly with Customer, Vendor, Invoice, Credit Memo in Rillet bi-directionally and in real time. A record created or corrected in either system appears in the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most at close. When both systems agree on who was billed, what was paid, and what is outstanding, reconciliation stops being a hunt for which copy of the truth is current.

Common use cases

  • 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • 04 Push billing events from a product or usage-metering system into Rillet for revenue recognition.

Common sync patterns

Entity or business-unit roll-up

Where each system serves a different entity or unit, sync the shared records so group-level reporting starts from consistent data.

Where Recurly issues invoices and Rillet holds the books

Invoices and payments recorded on the billing side land in the system of record automatically, so revenue is captured once and correctly.

Parallel run during a migration

When one system is replacing the other, keep both live and matching through the cutover, so no transaction falls between the last export and go-live.

What you can sync between Recurly 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.

Recurly objects Rillet objects How this pairing syncs
Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Account Synced with incremental and full sync per the Stacksync docs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Invoice Synced with incremental and full sync per the Stacksync docs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Charge Synced with incremental and full sync per the Stacksync docs. Billing Info is specific to Recurly and Charge to Rillet — each maps to any object or custom field on the other side.
Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Reimbursement Synced with incremental and full sync per the Stacksync docs. Measured Units and Usage is specific to Recurly and Reimbursement to Rillet — each maps to any object or custom field on the other side.
Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Custom Field Synced with incremental and full sync per the Stacksync docs. Subscriptions is specific to Recurly and Custom Field to Rillet — each maps to any object or custom field on the other side.
Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Customer Synced with incremental and full sync per the Stacksync docs. Plans is specific to Recurly and Customer to Rillet — each maps to any object or custom field on the other side.

How changes propagate between Recurly and Rillet

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Recurly Rillet Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.

Rillet Recurly Sub-second propagation

DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
  • Rillet: Subject to the platform's API rate limits.
What ships with Recurly ⇄ Rillet

Connect Recurly and Rillet for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Recurly 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 Recurly or Rillet record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Recurly and Rillet.

How the Recurly and Rillet connectors work

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.

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 Recurly 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 Recurly 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
    Recurly connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Recurly 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 · Recurly ⇄ 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
    Recurly Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Recurly and Rillet integration FAQ

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
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 422 integrations available for Recurly and Rillet.

Popular · 8 of 422
All Recurly integrations All Rillet integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own