Oracle E-Business Suite and Chargebee integration

What moves between them

The flow runs from Chargebee into Oracle E-Business Suite. ml-connector reads Chargebee invoices once they reach a posted or paid status and loads them as Receivables transactions through the EBS AutoInvoice interface, with each line mapped to the correct transaction type and revenue account. Chargebee customers flow the same direction so EBS Receivables customers stay aligned with billing accounts. Successful Chargebee payments and refunds post into the EBS general ledger as journal entries against the matching accounts. Chargebee is the system of record for billing and EBS is the ledger of record, so ml-connector does not write financial postings back into Chargebee. Webhooks trigger the work as billing activity happens, and a scheduled poll backfills anything a webhook missed.

How ml-connector handles it

ml-connector stores both credential sets encrypted and authenticates each side natively: it sends the Chargebee API key as the basic-auth username with an empty password, and on the EBS side it obtains a session token at startup, includes the responsibility and operating unit org id on every request, and re-authenticates when a call returns 401. Because EBS publishes no shared base URL, it accepts the full instance hostname and the admin-chosen service aliases per customer. Chargebee webhooks carry no HMAC signature, so each event is re-fetched from the Chargebee events API before processing and the event id is used to dedupe within the recommended window. EBS writes are two-step, so a POST into the AutoInvoice or GL interface table is followed by triggering or waiting on the concurrent program, and the connector polls the base tables to confirm the import rather than treating the insert as done. The interface source column is set to a unique connector identifier and combined with the invoice number to prevent duplicate imports, since EBS has no idempotency key. EBS has no rate limiter and is a shared system, so syncs run at low concurrency in off-peak windows, and Chargebee 429 responses are honored with backoff. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized B2B software company with a few hundred customers bills monthly and annual subscriptions in Chargebee and keeps its corporate books in Oracle E-Business Suite. Before the integration, the finance team exported Chargebee invoice and payment reports each week and re-keyed the totals into EBS Receivables and the general ledger, then spent the first days of month-end close chasing differences between billed revenue and the ledger. With Oracle E-Business Suite and Chargebee connected, each posted invoice flows into Receivables through AutoInvoice and each settled payment posts as a journal automatically, allocated to the right accounts. Month-end close starts with subscription revenue already recorded, and the manual re-keying step is gone.

What you can do

• •Load posted Chargebee invoices into Oracle E-Business Suite Receivables through the AutoInvoice interface after they are billed.
• •Keep EBS Receivables customers aligned with Chargebee billing customers using the TCA customer model.
• •Post successful Chargebee payments and refunds into the EBS general ledger as journal entries against the correct accounts.
• •Authenticate Chargebee with its API key and Oracle E-Business Suite with a session token, including the operating unit org id on every call.
• •React to Chargebee webhooks, re-fetched and deduped by event id, with backoff on rate limits and a full audit trail on every record.

Questions

Which direction does data move between Oracle E-Business Suite and Chargebee?

The flow is Chargebee into Oracle E-Business Suite. Invoices, customers, and settled payments move from Chargebee into EBS Receivables and the general ledger. Chargebee is the billing system of record and EBS is the ledger of record, so ml-connector does not write financial postings back into Chargebee.

Does Chargebee provide vendors or purchase orders for Oracle E-Business Suite?

No. Chargebee is a subscription billing platform and has no vendors, purchase orders, or general ledger accounts. What it provides is customers, subscriptions, invoices, payments, and credit notes, and ml-connector maps that billing activity into EBS as Receivables transactions and journal entries rather than as procurement documents.

How does the integration handle EBS two-step writes and Chargebee webhooks?

EBS writes insert into an interface table and then a concurrent program such as AutoInvoice or Journal Import processes the batch, so ml-connector confirms the import against the base tables instead of trusting the insert. Chargebee webhooks have no HMAC signature, so each event is re-fetched from the Chargebee API and deduped by event id before anything is loaded into EBS.