SAP Business One and Coupa integration

What moves between them

The main flow runs from SAP Business One into Coupa. Purchase orders and supplier invoices created in SAP Business One are read via scheduled polling (or webhooks if enabled) and pushed into Coupa, keeping procurement records current. Suppliers (business partners) are synchronized in both directions so buyers see the vendor master data as it exists in SAP Business One. Invoice records include line-item detail, amounts, and line-of-business codes so Coupa can match against purchase orders and manage payment workflows. Changes in SAP Business One within each polling interval are captured and reflected in Coupa within minutes.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages the session lifecycle on the SAP Business One side: it logs in once, reuses the session until the 30-minute inactivity timer expires (catching the -5002 error), and refreshes automatically on timeout. On the Coupa side, it obtains an OAuth 2.0 bearer token and pins the X-Coupa-API-Version header on each call. Because SAP Business One is on-premise with no global endpoint, ml-connector accepts the customer's Service Layer URL and port and validates it on startup. Polling happens on a schedule tied to business need (hourly or daily for most setups); if webhooks are enabled on the SAP Business One instance, ml-connector can listen for Create/Update/Delete events instead. Supplier records in Coupa are matched to SAP Business One business partners by the business partner ID, and purchase orders and invoices are matched by their document number to prevent duplicates on retry. Rate-limit 429 responses from Coupa trigger exponential backoff, and every transaction carries a full audit trail so records can be replayed if a downstream call fails.

A real-world example

A mid-sized industrial distribution company runs SAP Business One on-premise for purchasing and inventory, and uses Coupa in the cloud for vendor management and spend analytics. Before the integration, buyers reviewed purchase orders in SAP Business One and manually re-entered key details into Coupa for spend visibility, a process that was error-prone and delayed reporting. With SAP Business One and Coupa connected, new purchase orders and supplier invoices flow automatically from SAP Business One into Coupa within minutes of creation, keeping the procurement view in sync with the financial reality and eliminating re-keying. Finance can now match invoices in Coupa directly against SAP Business One purchase orders, and spend analytics in Coupa reflect the current state of commitments.

What you can do

• •Sync purchase orders from SAP Business One to Coupa on a schedule or webhook event, keeping procurement visibility current.
• •Push supplier invoices and payment records from SAP Business One into Coupa for invoice matching and spend analytics.
• •Synchronize supplier master data (business partners) between SAP Business One and Coupa so vendor details stay aligned.
• •Authenticate SAP Business One with session tokens and handle 30-minute inactivity timeouts automatically, and bridge Coupa OAuth 2.0 client credentials.
• •Poll on a schedule or receive webhook events, with exponential backoff retries on rate limits and a full audit trail on every record.

Questions

Does ml-connector work with SAP Business One in the cloud, or only on-premise?

ml-connector supports both on-premise and partner-hosted SAP Business One deployments. Because there is no global SaaS endpoint, the customer must provide the Service Layer URL and port. The connector accepts this URL per customer and connects to it directly.

How does SAP Business One's 30-minute session timeout affect the integration?

ml-connector logs in once and reuses the session until the inactivity timer expires. When the server returns error code -5002 (timeout), ml-connector automatically logs back in and retries the request. The session is never expired mid-transaction because ml-connector refreshes before the 30-minute window closes.

Can the integration use SAP Business One webhooks, or does it have to poll?

If the customer's SAP Business One instance is running v10.0 FP 2602 or later and has the Webhook Messenger Service activated, ml-connector can listen for Create/Update/Delete events instead of polling. Otherwise, polling on a scheduled interval is the default, capturing all changes within the polling window.