MYOB and Chargebee integration

What moves between them

Customer records flow one direction: from MYOB contacts (suppliers and customers) into Chargebee customers on a polling schedule. Sales invoices from MYOB map to Chargebee invoices, so MYOB billing records are reflected in your Chargebee ledger. Contact names, email, and billing addresses are synced from MYOB; invoice amounts, dates, and line items are pushed from MYOB into Chargebee as new invoice records or updates to existing ones. The sync runs on a schedule you define; no real-time push is possible because MYOB has no webhook system.

How ml-connector handles it

ml-connector stores MYOB's OAuth2 access token and company file credentials encrypted. On each poll cycle, it refreshes the OAuth2 token if it is within 5 minutes of expiry to avoid token-expired 401 errors mid-request. Every API call includes the x-myobapi-cftoken header with the company file credentials Base64-encoded. When Chargebee returns a 429 rate limit, ml-connector backs off and retries with exponential jitter. Contacts are mapped to Chargebee customers by email address or MYOB UID to avoid duplicates; invoices are linked to the matching customer and written as new invoice records or updated if the same invoice UID already exists in Chargebee. All contacts and invoices carry a LastModified timestamp in MYOB, so ml-connector uses OData $filter to poll only changed records since the last sync, minimizing API calls. Every record carries a full audit trail and can be replayed if a downstream write to Chargebee fails.

A real-world example

A small professional services firm in Australia uses MYOB to manage their accounting, customers, and invoicing. They have recently started a recurring subscription model and chosen Chargebee to manage recurring billing and payment collection. Before the integration, the finance team manually exported customer lists and invoices from MYOB each week and re-entered them into Chargebee by hand. With MYOB and Chargebee connected, new customers added to MYOB automatically appear in Chargebee within the polling window, and the monthly invoices MYOB generates flow directly into Chargebee as billing records. The two systems stay in sync with no manual data entry.

What you can do

• •Sync MYOB contacts into Chargebee customers, mapped by email address or UID to prevent duplicates.
• •Push MYOB sales invoices into Chargebee as subscription invoices with line items and amounts.
• •Handle MYOB OAuth2 token refresh every 20 minutes and the required company file credential header on every API call.
• •Poll MYOB for changes using OData LastModified filters to minimize API calls and respect the 8 req/sec rate limit.
• •Retry on Chargebee rate limits (150 to 3500 req/min depending on tier) with exponential backoff and a full audit trail per record.

Questions

Which direction does data move between MYOB and Chargebee?

Customers and invoices flow one direction: from MYOB into Chargebee. MYOB contacts (customers and suppliers) are synced to Chargebee customers, and MYOB sales invoices are pushed to Chargebee as invoice records. Chargebee payment and subscription events are read-only in this integration, so no data flows back to MYOB.

How does ml-connector handle MYOB's dual authentication requirement?

MYOB requires both an OAuth2 Bearer token and a company file credential header (x-myobapi-cftoken) on every API call. ml-connector stores both encrypted, refreshes the OAuth2 token when it approaches expiry (20-minute window), and includes the company file credentials Base64-encoded on every request. If the company file token expires or is invalid, the API returns 401 and ml-connector surfaces the error.

What happens if MYOB or Chargebee rate-limits the connection?

MYOB enforces 8 requests per second and 1,000,000 requests per day per API key. Chargebee's limits range from 150 to 3500 requests per minute depending on your subscription tier. ml-connector respects both by checking response headers, backing off with exponential jitter when it receives a 429, and retrying. Long-running syncs of large contact or invoice lists may need scheduling outside peak hours.