Real-time
Two-way sync
Changes in Active Directory or Coupa instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Active Directory to Coupa integration — real-time, two-way sync
Keep Active Directory and Coupa 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 Active Directory and Coupa
Keep the people who can act on financial records in Coupa matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.
Coupa runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.
Stacksync keeps Requisitions, Purchase Orders, Invoices, Suppliers in Coupa aligned with Groups, Group memberships, Devices, Directory roles in Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.
For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.
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 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
People attributes for allocation and approvals
Department, manager, and employee identifiers carried in Active Directory flow to Coupa, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.
Where Active Directory is the identity source: offboarding reaches the books
When a person is deactivated in Active Directory, their matching user in Coupa is disabled in the same motion, so departed employees keep no standing access to financial records.
One user roster across both systems
People, their status, and their contact details stay matched between Coupa and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.
What you can sync between Active Directory and Coupa
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.
| Active Directory objects | Coupa objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Users Employee and user accounts with roles and content groups; provisioned and updated from an HRIS or identity provider. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Requisitions Employee purchase requests with lines and approval chains; read out to warehouses, or created via the API from upstream intake tools. | Groups is specific to Active Directory and Requisitions to Coupa — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | 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. | Group memberships is specific to Active Directory and Purchase Orders to Coupa — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | 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. | Devices is specific to Active Directory and Invoices to Coupa — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Suppliers Supplier master records; kept aligned with an ERP vendor master and onboarding tools, synced two-way on the /suppliers resource. | Directory roles is specific to Active Directory and Suppliers to Coupa — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Accounts Chart-of-accounts segments and GL codes; usually mastered in the ERP and written into Coupa so requisitions and invoices code correctly. | Service principals & applications is specific to Active Directory and Accounts to Coupa — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Coupa
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.
Active Directory Coupa Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Coupa through its API, with automatic retries and rate-limit backoff.
Coupa Active Directory 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 written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- 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.
What ships with Active Directory ⇄ Coupa
Connect Active Directory and Coupa for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Coupa connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Coupa 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 Active Directory or Coupa record.
Observability
Monitoring
Track your Active Directory ⇄ Coupa sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Coupa.
How the Active Directory and Coupa connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
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.
How it works
How to connect Active Directory to Coupa — 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.
- 01
Connect your apps
Authenticate Active Directory and Coupa with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Coupa
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Coupa 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.
objects · Active Directory ⇄ CoupaCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Active Directory CoupaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Coupa integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Coupa: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On Coupa: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Coupa side: Requisitions, Purchase Orders, Invoices, Suppliers, plus custom fields where Coupa exposes them. On the Active Directory side: Groups, Group memberships, Devices, Directory roles. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Active Directory and Coupa: People attributes for allocation and approvals; Where Active Directory is the identity source: offboarding reaches the books; One user roster across both systems. Department, manager, and employee identifiers carried in Active Directory flow to Coupa, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.
-
Active Directory: Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS). Authentication: OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS. Coupa: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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
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 499 integrations available for Active Directory and Coupa.
Popular · 8 of 499
-
Active Directory ⇄ Zuora -
Active Directory ⇄ Adyen -
Active Directory ⇄ Logisense -
Active Directory ⇄ Bill -
Coupa ⇄ Auth0 -
Coupa ⇄ Jumpcloud - Coupa ⇄ Azure Active Directory
-
Coupa ⇄ Okta
No integrations match .
