Sage Intacct and Coupa integration

What moves between them

The main flow is from Coupa into Sage Intacct. Supplier events from Coupa are matched to Sage Intacct vendors, purchase order and invoice events flow into Intacct's GL accounts mapped to cost centers, and payments are posted to the AP transaction log. Dimension data such as cost centers and departments is validated in Intacct before invoice lines are allocated, so every line lands on a valid GL account and cost center. Payments processed in Sage Intacct can be synced back to Coupa as status updates.

How ml-connector handles it

ml-connector caches the Sage Intacct session for 50 minutes and refreshes it automatically on the next call if it expires. Coupa webhook signatures are verified by computing HMAC-SHA256 with the shared secret and comparing to the X-Coupa-Signature header. Because Sage Intacct requires all operations to serialize through a single XML gateway, ml-connector queues requests and executes them in order, appending the uniqueid flag to each operation for server-side deduplication if a retry is needed. Forbidden XML control characters are stripped before the XML is sent. Coupa rate-limit responses (HTTP 429) trigger exponential backoff with jitter, capped at 30 seconds. Webhook events from Coupa are buffered, deduplicated by Coupa-Signature, and replayed if a downstream Intacct call fails, ensuring no invoice is lost in the sync.

A real-world example

A mid-sized manufacturing company runs Sage Intacct for accounting and finance, and uses Coupa for procurement across multiple plants and departments. Before the integration, supplier data had to be re-entered into Intacct by hand whenever procurement added a new vendor or changed terms in Coupa. Purchase orders created in Coupa required manual entry into Intacct's AP module, and invoice lines had to be matched and allocated to the correct cost center and GL account in Intacct before payment. With Sage Intacct and Coupa connected, supplier master changes flow automatically into Intacct's vendor table, invoice lines are allocated to the correct cost centers by the integration rules, and the AP team can match and approve invoices in Intacct with confidence that line items are already synced.

What you can do

• •Sync supplier records from Coupa into Sage Intacct vendor master, keeping new suppliers and vendor changes in step across both platforms.
• •Flow purchase order and invoice data from Coupa into Sage Intacct's general ledger, allocated to the correct GL accounts and cost centers.
• •Validate cost centers and dimensions in Sage Intacct before invoice lines are posted, so every line lands on a valid account.
• •Handle Sage Intacct session caching and automatic refresh, XML control-character stripping, and Coupa webhook signature verification.
• •Retry failed operations with exponential backoff and full audit replay on both systems, ensuring no invoice is lost.

Questions

Which direction does data move between Sage Intacct and Coupa?

The main flow is from Coupa into Sage Intacct. Suppliers, purchase orders, and invoices flow from Coupa into Intacct, where they are allocated to GL accounts and cost centers. Payments processed in Sage Intacct can be posted back to Coupa as status updates. Sage Intacct does not push data to Coupa; the integration receives webhook events from Coupa to trigger the sync.

How does the integration handle Sage Intacct's session-based authentication and single XML gateway?

ml-connector manages the Sage Intacct session by exchanging credentials for a sessionid on the first call, caching it for 50 minutes, and refreshing it automatically if it expires on a subsequent call. Because Sage Intacct requires all operations to serialize through a single XML gateway endpoint, ml-connector queues requests and executes them in order, appending a uniqueid flag to each operation for server-side deduplication if a retry is needed.

What happens if Coupa rate-limits the integration or a webhook signature does not match?

Coupa rate-limit responses (HTTP 429) trigger exponential backoff with jitter, capped at 30 seconds. Webhook signatures are verified by computing HMAC-SHA256 with the shared secret and comparing to the X-Coupa-Signature header; a mismatch is rejected as untrusted. Both situations are logged and can be reviewed in the full audit trail.