Real-time
Two-way sync
Changes in Coupa or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Coupa to Salesforce integration — real-time, two-way sync
Keep Coupa and Salesforce 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 Salesforce
Sync customers, invoices, and payment status between Coupa and Salesforce in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Salesforce knows the relationship: who the contacts are and what is in motion with the account. Coupa knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Purchase Orders, Invoices, Suppliers, Users in Coupa to Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
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 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- 04 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
Common sync patterns
Payment status on the account
Invoice and payment status from Coupa appears on the account in Salesforce, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Salesforce, Coupa gets the update before the next invoice goes out.
Collections with context
Finance sees the account owner and relationship history from Salesforce when chasing a balance, and sales sees that the chase is happening.
What you can sync between Coupa and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Chart-of-accounts segments and GL codes; usually mastered in the ERP and written into Coupa so requisitions and invoices code correctly. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | 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. | |
| 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. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Purchase Orders is specific to Coupa and Custom Objects to Salesforce — 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. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Invoices is specific to Coupa and Contacts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Suppliers is specific to Coupa and Leads to Salesforce — 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Users is specific to Coupa and Opportunities to Salesforce — 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. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Contracts is specific to Coupa and Cases to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Coupa and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Coupa Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Coupa ⇄ Salesforce
Connect Coupa and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Coupa–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Coupa or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Coupa ⇄ Salesforce 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 Salesforce.
How the Coupa and Salesforce 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.
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Coupa to Salesforce — 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 Coupa and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Coupa
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Coupa and Salesforce 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 · Coupa ⇄ SalesforceCustomers 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.
Coupa SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Coupa and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Coupa and Salesforce: authenticate both systems, choose the objects to sync (such as Coupa's Accounts and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Coupa and Salesforce. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Coupa side: Purchase Orders, Invoices, Suppliers, Users, plus custom fields where Coupa exposes them. On the Salesforce side: Campaigns, Tasks and Events, Products and Price Books, Custom Objects. 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 Coupa and Salesforce: Payment status on the account; Billing detail changes flow back; Collections with context. Invoice and payment status from Coupa appears on the account in Salesforce, so reps see overdue balances before they promise the next order.
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 532 integrations available for Coupa and Salesforce.
Popular · 7 of 532
-
Coupa ⇄ Outreach -
Coupa ⇄ Salesloft -
Coupa ⇄ SAP Sales Cloud -
Salesforce ⇄ Hyperline -
Salesforce ⇄ Pigment -
Salesforce ⇄ QuickBooks -
Salesforce ⇄ Stripe
No integrations match .
