Odoo and Coupa integration

What moves between them

The primary flow moves purchase orders from Odoo into Coupa for approval and spend control. After a purchase order is created or updated in Odoo, ml-connector polls at a configurable interval, identifies new or changed orders via write_date timestamp, and posts them to Coupa with supplier and line-item details. Approved invoices and payment status flow back from Coupa into Odoo's accounts payable and GL accounts. Supplier master data is synced bidirectionally so vendor master records remain consistent across both systems. Payment records from Coupa update the matched invoice status in Odoo.

How ml-connector handles it

ml-connector polls Odoo using its write_date high-water-mark strategy on the purchase.order and account.move models, extracting new or modified records at a schedule you define. It authenticates to Odoo with the configured API key and username, handling both XML-RPC and JSON-2 transports depending on your Odoo version. On the Coupa side, it exchanges the OAuth2 client credentials for a bearer token, then posts purchase orders and invoices with supplier and cost-center mappings so each line item references a valid Coupa vendor and account. It receives Coupa payment and invoice-event webhooks, verifies the HMAC-SHA256 signature, and writes the approval and payment status back into Odoo's account.move records. Supplier names and codes are mapped first so every PO line references an existing Coupa vendor, and retries are applied on 5xx and 429 responses from Coupa. Every transaction is audited with a full record of the payload, the direction of sync, and any mapping or validation errors.

A real-world example

A mid-market manufacturing company runs Odoo for accounting and purchase planning, and uses Coupa for supplier approval, spend visibility, and compliance. Before the integration, the procurement team created purchase orders in Odoo, then had to manually enter them into Coupa for approval routing and capture. Once approved, the team re-entered invoice data from Coupa back into Odoo for accounts payable matching, causing delays in month-end close and supplier payment reconciliation. With Odoo and Coupa connected, new purchase orders flow into Coupa automatically, move through the approval workflow, and approved invoices sync back into Odoo's accounts payable with payment status updated. The spend team gains real-time visibility in Coupa while the accounting team receives pre-mapped invoice lines ready for GL posting.

What you can do

• •Sync purchase orders from Odoo to Coupa for approval and spend control, mapped to supplier records.
• •Post approved invoices from Coupa back into Odoo's accounts payable with payment status and GL mappings.
• •Keep supplier master data aligned bidirectionally between Odoo and Coupa so vendor names, codes, and payment terms match.
• •Authenticate Odoo via API key and username with support for both XML-RPC and JSON-2 transports, and Coupa via OAuth2.
• •Poll Odoo on a schedule with write_date high-water-mark filtering, verify Coupa webhook signatures, and replay failed records.

Questions

How does the integration handle Odoo's API key authentication and polling?

ml-connector stores the Odoo API key and username encrypted, uses them to authenticate via XML-RPC or JSON-2 depending on your Odoo version, and polls the purchase.order and account.move models at a configurable interval using write_date to identify new or changed records. This avoids the need for production-grade webhooks, which are not available in most Odoo editions.

Which direction do purchase orders and invoices flow between Odoo and Coupa?

Purchase orders and supplier invoices flow from Odoo into Coupa for approval, visibility, and compliance. Approved invoices, payment status, and approval workflow updates flow back from Coupa into Odoo's accounts payable. Supplier master data is synced bidirectionally to keep vendor names, codes, and terms consistent.

What happens if a supplier code in Odoo does not exist in Coupa?

ml-connector maps supplier records first before posting any purchase order line items. If a supplier code in Odoo does not have a matching Coupa vendor, the record is flagged with a mapping error and held for manual review. The audit trail shows exactly which supplier caused the failure and which field is missing, so your procurement team can add the vendor in Coupa and replay the order.