Oracle Fusion Cloud ERP and Chargebee integration

What moves between them

The integration pulls Chargebee customers and subscription events via webhooks and converts them to Fusion customer records with revenue dimensions. Every time Chargebee generates an invoice, the invoice and its line items flow into Fusion, mapped to GL accounts and cost centers based on Chargebee item codes. Payment records and credit notes also flow from Chargebee into Fusion. The primary direction is Chargebee into Fusion; Fusion customer master data can sync back to Chargebee as a reference update but does not drive transaction creation.

How ml-connector handles it

ml-connector receives Chargebee webhook notifications for customer, subscription, invoice, and payment events in real time, verifies them against the Chargebee API for freshness, and transforms them into Fusion journal lines and customer records. On the Fusion side, it uses OAuth 2.0 to obtain a bearer token and posts journal batches with the GL account and cost center mappings encoded per subscription type and Chargebee item. Because Chargebee webhooks push events immediately, ml-connector processes updates as they occur rather than polling on a schedule. If a Chargebee webhook delivery fails, Chargebee retries up to 2 days, and ml-connector idempotently accepts the redelivery using Chargebee's event ID. Fusion rate limits are not documented in the public API, but ml-connector backs off on HTTP 429 and retries with exponential backoff, and it tracks Fusion token expiry to refresh before a call fails. Custom mappings define which Chargebee items map to which Fusion GL accounts, and which customer attributes populate Fusion customer segments.

A real-world example

A mid-market SaaS company runs Oracle Fusion Cloud ERP for accounting and finance, and Chargebee for subscription billing across several product tiers and regions. Before the integration, the finance team exported Chargebee invoices weekly and hand-entered them into Fusion, allocating line items to GL accounts by SKU and customer segment. Month-end close required a full reconciliation between Chargebee revenue and Fusion's GL, and timing differences between billing and revenue recognition created weeks of rework. With Oracle Fusion and Chargebee connected, each Chargebee invoice posts to Fusion automatically on the day it is issued, line items land on the correct GL accounts by product tier, and customer records update automatically when subscriptions start or upgrade. Revenue is recognized in the same period Chargebee generates it, and month-end close starts with the revenue accounts already reconciled.

What you can do

• •Sync Chargebee customers and subscriptions into Oracle Fusion Cloud ERP as customer master records with billing attributes.
• •Post every Chargebee invoice, credit note, and payment into Fusion's GL, allocated to the correct revenue and receivables accounts.
• •Map Chargebee item codes and customer segments to Fusion GL account combinations so billing flows to the right dimensions.
• •Authenticate Chargebee with HTTP Basic Auth and Fusion with OAuth 2.0 Client Credentials, bridging the different credential models.
• •Receive Chargebee webhook events in real time, idempotently handle retries up to 2 days, and back off on Fusion rate limits.

Questions

Which direction does data move between Oracle Fusion Cloud ERP and Chargebee?

The primary direction is Chargebee into Fusion. Customers, subscriptions, invoices, payments, and credit notes all flow from Chargebee to Fusion. Fusion customer master data can be sent back to Chargebee as a reference sync but does not create transactions. This keeps Fusion's GL and AR current with billing without duplicating invoices or payments.

How does ml-connector handle the different authentication schemes?

Chargebee uses HTTP Basic Auth with an API key; Fusion uses OAuth 2.0 Client Credentials. ml-connector stores both credential sets encrypted and uses the Chargebee API key to receive webhook notifications, while it obtains a Fusion bearer token on every session and refreshes when the token expires. The two auth flows are isolated, so a change to one credential does not affect the other.

Does ml-connector use Chargebee webhooks or polling?

ml-connector receives Chargebee webhooks in real time for customer, subscription, invoice, and payment events, so updates flow to Fusion immediately as they occur. Chargebee retries webhook delivery up to 2 days if ml-connector is unavailable, and ml-connector idempotently processes each event using Chargebee's event ID to prevent duplicates. There is no polling schedule; events drive the sync.