Skip to content
Accounting and finance ⇄ Database

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

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

Work with Coupa'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 Requisitions, Purchase Orders, Invoices, Suppliers from Coupa into Globals, Namespaces, Stored Procedures, Tables 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 Coupa with validation, so the finance system stays the system of record.

Common use cases

  • 01 Export approved Invoices and their lines from Coupa into an accounting/ERP system to drive the AP pay cycle and GL posting.
  • 02 Push chart-of-accounts segments and cost centers from the ERP into Coupa Accounts so Requisitions and Invoices code to the right GL.
  • 03 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 04 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access

Common sync patterns

Write back safely

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

React to financial events

Changes in Coupa 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 Coupa live in InterSystems IRIS as regular tables or collections your team can join, index, and query.

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

Coupa objects InterSystems IRIS objects How this pairing syncs
Purchase Orders PO headers and lines; synced two-way with ERPs so orders raised in Coupa flow to the ledger and status updates flow back on the /purchase_orders resource. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Purchase Orders is specific to Coupa and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side.
Invoices Supplier/AP invoices with lines and approval status; polled out to accounting and ERP systems for the pay cycle, or created through the API. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Invoices is specific to Coupa and Tables to InterSystems IRIS — each maps to any object or custom field on the other side.
Suppliers Supplier master records; kept aligned with an ERP vendor master and onboarding tools, synced two-way on the /suppliers resource. Views SQL views expose curated slices of data for outbound replication. Suppliers is specific to Coupa and Views to InterSystems IRIS — each maps to any object or custom field on the other side.
Users Employee and user accounts with roles and content groups; provisioned and updated from an HRIS or identity provider. Schemas Schema organization scopes which tables a sync connection can see. Users is specific to Coupa and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side.
Accounts Chart-of-accounts segments and GL codes; usually mastered in the ERP and written into Coupa so requisitions and invoices code correctly. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Accounts is specific to Coupa and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side.
Contracts Supplier contract records with terms and dates; read out for reporting or created from a CLM system. Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Contracts is specific to Coupa and Globals to InterSystems IRIS — each maps to any object or custom field on the other side.

How changes propagate between Coupa 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.

Coupa InterSystems IRIS Interval-based propagation

DetectionStacksync polls Coupa for changes on an incremental schedule, reading only records changed since the previous pass. Polling on updated-at and created-at filters (e.g.

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

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

Rate-limit considerations

  • Coupa: Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Coupa ⇄ InterSystems IRIS

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Coupa ⇄ 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 Coupa and InterSystems IRIS.

How the Coupa and InterSystems IRIS connectors work

Coupa

Integration surface
REST Core API (JSON or XML)
Authentication
OAuth 2.0 / OIDC via the client-credentials grant; scopes take the service.object.right form (e.g. core.accounting.read, core.accounting.write). Legacy API keys are being retired (no new keys since R34; API-key auth unsupported from R36). Access tokens last 24 hours.
Change detection
Polling on updated-at and created-at filters (e.g. updated-at[gt]=<timestamp>); Coupa has no native webhook subscriptions, though admins can configure outbound Call Out / external notifications.
Capabilities
read · write
Rate limits
Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.

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

    Choose tables

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

Coupa 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.

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

Popular · 7 of 462
Coworkers laughing in front of a laptop in a casual office setting

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