Skip to content
Accounting and finance ⇄ Database

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

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

Work with Bill'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 Customers, Payments, Chart of Accounts, Bank Accounts from Bill into Tables, Views, Schemas, Persistent Classes 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 Bill with validation, so the finance system stays the system of record.

Common use cases

  • 01 Sync Customers and Invoices from BILL AR into a CRM or ERP so sales and finance see billing and payment status on the account.
  • 02 Write Vendors created during ERP onboarding into BILL so new payees are ready to pay without manual re-entry.
  • 03 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
  • 04 Replicate IRIS tables to Postgres so application teams can build against a familiar database

Common sync patterns

React to financial events

Changes in Bill appear in InterSystems IRIS 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 Bill 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 Bill.

What you can sync between Bill and InterSystems IRIS

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.

Bill objects InterSystems IRIS objects How this pairing syncs
Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. Views SQL views expose curated slices of data for outbound replication. Customers is specific to Bill and Views to InterSystems IRIS — each maps to any object or custom field on the other side.
Payments Outgoing vendor payments and received customer payments; read for reconciliation and created to schedule bill pay. Schemas Schema organization scopes which tables a sync connection can see. Payments is specific to Bill and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side.
Chart of Accounts GL accounts used to code bills and invoices; typically mastered in the accounting system and written into BILL for consistent coding. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Chart of Accounts is specific to Bill and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side.
Bank Accounts Funding and deposit accounts; read to reconcile payments and posted transactions against the ledger. Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Bank Accounts is specific to Bill and Globals to InterSystems IRIS — each maps to any object or custom field on the other side.
Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. Namespaces Namespaces partition databases and determine the connection context for integrations. Vendor Credits and Credit Memos is specific to Bill and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side.
Bills Accounts-payable amounts owed to vendors, with bill line items; read and created via /v3/bills and pulled incrementally by filtering on createdTime/updatedTime. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Bills is specific to Bill and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side.

How changes propagate between Bill and InterSystems IRIS

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.

Bill InterSystems IRIS Sub-second propagation

DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.

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

InterSystems IRIS Bill 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 Bill through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Bill ⇄ InterSystems IRIS

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Bill and InterSystems IRIS connectors work

Bill

Integration surface
REST/JSON (BILL v3 Connect API)
Authentication
Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
Change detection
Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
Capabilities
read · write · webhooks
Rate limits
20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.

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
How it works

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

    Choose tables

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

Bill and InterSystems IRIS 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 461 integrations available for Bill and InterSystems IRIS.

Popular · 8 of 461
All Bill integrations All InterSystems IRIS 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