SAP Business One and Chargebee integration

What moves between them

The main flow runs from SAP Business One into Chargebee. Customer records (BusinessPartners) from SAP Business One are mapped and written as Chargebee customers on a daily schedule or when updated in the source. Invoices (Invoices from SAP Business One) are sent to Chargebee as invoices tied to the matching customer, so your subscription billing draws from the same customer roster and invoice history as your ERP. SAP Business One is pull-only via polling, while Chargebee accepts the data via REST writes. Reference data such as customer status and item codes are aligned so invoice line items and subscription customers are always valid in both systems.

How ml-connector handles it

ml-connector stores both credential sets encrypted and reuses SAP Business One session tokens across requests within the 30-minute window, re-authenticating only when needed or when a -5002 timeout error occurs. Chargebee calls use HTTP Basic Auth with the API key encoded in the header on every request. The connector polls SAP Business One on a customer-defined schedule (e.g., daily) using the OData UpdateDate filter to capture only new and changed records, then writes them to Chargebee via POST and PATCH operations. Customer IDs from SAP Business One (BusinessPartner codes) are mapped to Chargebee customer IDs; invoice numbers are prefixed or tagged to avoid collisions if data flows from multiple SAP instances. ml-connector respects Chargebee's rate limits (150 to 3500 requests per minute depending on plan tier) by batching writes and backing off on 429 responses. Every poll, write, and credential refresh is logged in the audit trail so failed syncs can be replayed.

A real-world example

A SaaS company that uses SAP Business One for accounting and operations and Chargebee for subscription billing has been manually exporting customer lists and invoices from SAP Business One and uploading them into Chargebee each month to keep the two systems aligned. The finance team spends hours reconciling differences when a customer updates their billing address in SAP Business One but not in Chargebee, or when an invoice is generated in SAP Business One before the subscription renewal invoice appears in Chargebee. With SAP Business One and Chargebee connected, every new customer or invoice change in SAP Business One flows into Chargebee within hours of the change. Billing and accounting data stay synchronized without manual work, and month-end reconciliation is faster because both systems reference the same customer and invoice records.

What you can do

• •Sync customer records from SAP Business One (BusinessPartners) into Chargebee as customers on a daily schedule or on demand.
• •Post invoices from SAP Business One into Chargebee tied to the correct subscription customer, keeping billing and ERP invoices in alignment.
• •Manage SAP Business One session token lifecycle and authenticate Chargebee with HTTP Basic Auth, abstracting the different auth schemes.
• •Poll SAP Business One on a schedule using OData UpdateDate filters to capture only new and changed records efficiently.
• •Track every customer and invoice sync in the audit trail and replay failed records without duplicating or losing data.

Questions

Which direction does data move between SAP Business One and Chargebee?

The main flow is from SAP Business One into Chargebee. Customer records and invoices are read from SAP Business One and written to Chargebee. Reference data such as customer status and item codes are aligned so that billing records in Chargebee always reference valid customer and item records from SAP Business One. Chargebee does not write back into SAP Business One.

How does ml-connector handle SAP Business One's 30-minute session timeout and customer-specific URL?

ml-connector reuses the session token across multiple requests within the 30-minute window, re-authenticating only when a -5002 timeout error occurs or the window expires. Each customer provides their own SAP Business One Service Layer URL, so ml-connector stores that URL encrypted and uses it as the base for all OData queries. If session reuse is not viable, each request can authenticate independently, trading latency for simplicity.

What happens when Chargebee rate limits are hit?

Chargebee returns HTTP 429 when the request rate exceeds the plan tier limit (150 to 3500 requests per minute). ml-connector detects 429 responses, backs off with exponential jitter, and retries the batch. The audit trail logs the backoff and retry so you can see rate-limit events and adjust the polling schedule or batch size if needed.