QuickBooks Online and Chargebee integration

What moves between them

The main flow is from QuickBooks Online into Chargebee. ml-connector polls QuickBooks Online for new and updated invoices and customers, then creates or updates corresponding Chargebee invoices and customer records. Customer records map from QuickBooks Online vendors or customers to Chargebee customers so subscription billing is associated with the right entity. Invoices map to Chargebee subscriptions or payment records. Payment records flow back from Chargebee to QuickBooks Online to mark invoices as paid and reconcile the general ledger. The sync runs on a configurable schedule, typically daily or weekly depending on billing cadence.

How ml-connector handles it

ml-connector stores both credential sets encrypted and handles the authentication chains separately. On the QuickBooks Online side, it refreshes the OAuth2 access token when a request returns 401, and tracks the refresh token rotation cycle to avoid stale-token revocation. It polls the CDC endpoint to detect new and changed invoices and customers in QuickBooks Online, then fetches full records via the Accounting API. It normalizes QuickBooks Online customers and vendor records to Chargebee customer entities, mapping the customer display name and contact details. For each invoice, it maps the billed-to entity, line items, amounts, and invoice date to Chargebee invoice or subscription records. On the Chargebee side, it respects rate limits by backing off on 429 responses and retrying with exponential jitter. Chargebee's lack of HMAC-signed webhooks means ml-connector re-fetches events via the GET /api/v2/events endpoint for verification instead of trusting the webhook payload. Payment records from Chargebee are synced back to QuickBooks Online as payments against the original invoices, and the sync maintains a full audit log of every customer, invoice, and payment record with timestamps and status.

A real-world example

A mid-market SaaS company runs QuickBooks Online to track its operating expenses and uses Chargebee for its subscription billing and payment collection. Before integration, the finance team exported QuickBooks Online customer lists and invoices every pay period and manually created the matching Chargebee invoices, then waited for Chargebee to process payments and reconciled the records back into QuickBooks Online. This manual workflow caused invoice creation delays, mismatches between the two systems, and delayed revenue recognition. With QuickBooks Online and Chargebee connected, each new customer and invoice automatically flows from QuickBooks Online to Chargebee, billing is accurate and timely, and payments received in Chargebee are marked in QuickBooks Online within hours, so month-end revenue reconciliation is clean and the manual re-entry step is gone.

What you can do

• •Poll QuickBooks Online invoices and customers and create or update matching records in Chargebee without manual entry.
• •Map customer entities from QuickBooks Online to Chargebee subscription records with address, contact, and payment source details.
• •Sync Chargebee payments back to QuickBooks Online as payment records against the original invoices for GL reconciliation.
• •Handle OAuth2 token refresh cycles on QuickBooks Online and HTTP Basic Auth rate limits on Chargebee with automatic backoff and retries.
• •Maintain a full audit trail of every invoice, customer, and payment movement with timestamps and status for reconciliation and compliance.

Questions

Which direction does data move between QuickBooks Online and Chargebee?

The main flow is QuickBooks Online to Chargebee. Customer and invoice records move from QuickBooks Online into Chargebee subscriptions and invoices. Payment records flow back from Chargebee into QuickBooks Online as payments against the original invoices so the general ledger reflects what was actually collected.

How does ml-connector handle QuickBooks Online's OAuth2 token rotation?

ml-connector stores the OAuth2 access token and refresh token encrypted and refreshes the access token when a QuickBooks Online API call returns 401. It tracks the refresh token rotation cycle (every 24-26 hours) and re-authenticates before the token expires, so a stale refresh token does not cause an outage.

Does Chargebee's lack of HMAC webhook signatures affect the integration?

Yes. Chargebee does not sign webhooks with HMAC, so ml-connector cannot verify webhook authenticity by checking a signature. Instead, it re-fetches the event record using GET /api/v2/events/{event_id} with the API key to confirm the event before processing it.