Skip to content
Database ⇄ Accounting and finance

InterSystems IRIS to Zuora integration — real-time, two-way sync

Keep InterSystems IRIS and Zuora 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 InterSystems IRIS and Zuora

Work with Zuora's financial data straight from InterSystems IRIS: 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 Subscription, Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice from Zuora into Stored Procedures, Tables, Views, Schemas in InterSystems IRIS and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against InterSystems IRIS, and rows your code writes or updates flow back into Zuora with validation, so the finance system stays the system of record.

Common use cases

  • 01 Master the Product Catalog (Products and Product Rate Plans) in a database or PIM and write pricing changes into Zuora.
  • 02 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
  • 03 Keep reference data consistent between an IRIS-based clinical or financial application and downstream SaaS tools
  • 04 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Zuora live in InterSystems IRIS as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on InterSystems IRIS; Stacksync handles the API calls, rate limits, and retries against Zuora.

Write back safely

Updates written to the synced tables in InterSystems IRIS propagate into Zuora, so automations can create or correct finance records without custom integration code.

What you can sync between InterSystems IRIS and Zuora

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.

InterSystems IRIS objects Zuora objects How this pairing syncs
Namespaces Namespaces partition databases and determine the connection context for integrations. Product and Product Rate Plan (Product Catalog) The catalog of sellable products and their pricing; usually mastered elsewhere and written into Zuora, or read to map subscription charges. Namespaces is specific to InterSystems IRIS and Product and Product Rate Plan (Product Catalog) to Zuora — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Invoice Billing documents generated from rate plan charges and order line items; typically read out into an ERP or GL for revenue recognition and reconciliation. Stored Procedures is specific to InterSystems IRIS and Invoice to Zuora — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. Tables is specific to InterSystems IRIS and Payment to Zuora — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. Views is specific to InterSystems IRIS and Usage to Zuora — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Order and Amendment Records of subscription create and change actions; written to Zuora to drive quote-to-cash and read for subscription change history. Schemas is specific to InterSystems IRIS and Order and Amendment to Zuora — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Account (Billing Account) The customer billing entity holding contacts, payment methods, and billing settings; synced two-way as the parent record most other Zuora objects hang off. Persistent Classes is specific to InterSystems IRIS and Account (Billing Account) to Zuora — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Zuora

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.

InterSystems IRIS Zuora Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

Zuora InterSystems IRIS Sub-second propagation

DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.

DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with InterSystems IRIS ⇄ Zuora

Connect InterSystems IRIS and Zuora for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Zuora connection.

Real-time

Two-way sync

Changes in InterSystems IRIS or Zuora instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Zuora 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 InterSystems IRIS or Zuora record.

Observability

Monitoring

Track your InterSystems IRIS ⇄ Zuora sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Zuora.

How the InterSystems IRIS and Zuora connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

Zuora

Integration surface
REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
Authentication
OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
Change detection
Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
Capabilities
read · write · webhooks
Rate limits
Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works

How to connect InterSystems IRIS to Zuora — 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 InterSystems IRIS and Zuora 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
    InterSystems IRIS connected
    Zuora connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

InterSystems IRIS and Zuora 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 462 integrations available for InterSystems IRIS and Zuora.

Popular · 7 of 462
All InterSystems IRIS integrations All Zuora 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