IFS Cloud and Chargebee integration

What moves between them

Customer and subscription data flows from Chargebee into IFS Cloud. New or updated customers in Chargebee sync to IFS Cloud as customer records, and active subscriptions sync as sales orders with GL dimensions tied to the subscription product and renewal period. Invoice data from Chargebee flows into IFS as revenue transactions for GL posting. The sync runs on a schedule aligned with your billing cadence, typically daily or after major subscription changes, and can also be triggered by Chargebee webhook events.

How ml-connector handles it

ml-connector stores Chargebee API credentials and IFS OAuth2 client credentials encrypted, and refreshes the IFS token as needed since it expires every 60 minutes. For each Chargebee customer or subscription update, it reads the full record via API, checks for an existing match in IFS by reference number or external ID to prevent duplicates, and then writes to IFS using the required ETag header for optimistic concurrency. Chargebee rate limits are respected with exponential backoff on HTTP 429; IFS limits are handled similarly. Customer and subscription records are mapped to IFS customer records and sales orders, with invoice and transaction data aligned to GL accounts and company codes as configured. Every sync operation is logged with timestamp, record IDs, and outcome for full audit and replay.

A real-world example

A mid-market SaaS company runs IFS Cloud for project accounting and cost allocation across multiple service lines. They use Chargebee for subscription billing and recurring revenue management across hundreds of customers on different contract terms. Before the integration, finance exported customer lists and invoices from Chargebee and manually entered them into IFS each month, creating reconciliation work and delays in revenue recognition. With Chargebee and IFS Cloud connected, every new customer, subscription change, and invoice syncs automatically into IFS within minutes of being generated in Chargebee, so the finance team sees accurate, up-to-date revenue data and closes month-end faster without manual re-entry.

What you can do

• •Sync customers and subscriptions from Chargebee into IFS Cloud as customer records and sales orders.
• •Map Chargebee invoice data into IFS GL postings and revenue recognition transactions.
• •Handle Chargebee rate limits and retries with exponential backoff, and refresh IFS OAuth2 tokens on each sync.
• •Enforce ETag-based optimistic concurrency on IFS writes and deduplicate customers by external ID to prevent doubles.
• •Keep a full audit trail of every customer and subscription sync, with timestamp and outcome for replay and reconciliation.

Questions

Which direction does data move between Chargebee and IFS Cloud?

The main flow is from Chargebee into IFS Cloud. Customers, subscriptions, and invoices sync from Chargebee into IFS Cloud as customers, sales orders, and revenue transactions. Reference data such as company codes and GL accounts flows the opposite direction to ensure all synced records map to valid IFS dimensions.

How does the integration handle Chargebee webhooks and IFS polling limitations?

ml-connector uses Chargebee webhooks to detect customer and subscription changes in real time, but also polls Chargebee on a regular schedule to catch any missed events and ensure completeness. IFS Cloud does not expose webhooks, so ml-connector polls IFS to verify that records were written correctly and handles ETag-based optimistic concurrency errors by re-fetching and retrying.

What happens if a Chargebee customer already exists in IFS Cloud?

ml-connector deduplicates customers by checking for existing records in IFS before writing new ones, typically using an external ID or reference number stored in a custom field. If the customer exists, it updates the record with the latest data from Chargebee using the ETag header to prevent concurrent edit conflicts.