Microsoft Dynamics NAV and Chargebee integration

What moves between them

Customer and subscription data flows in both directions: new customers created in Chargebee are synced to NAV's customer master, and updates to existing customers are reflected in NAV. Invoices and transactions move from Chargebee to NAV, where each revenue-related transaction is mapped to the subscription contract line and the customer dimension in NAV and posted to the GL as a revenue recognition journal. NAV's GL accounts and dimensions are reference tables pulled at setup time and do not flow back into Chargebee. Chargebee webhook events trigger the sync where enabled; polling is used as a fallback for entities outside the webhook subscription list.

How ml-connector handles it

ml-connector uses Chargebee's REST Basic Auth on every request and refreshes the auth token per request as needed. On the NAV side, it connects to the tenant-specific OData endpoint and authenticates with the Entra ID OAuth 2.0 credentials provided per customer. Since NAV webhook subscriptions expire after 3 days, ml-connector tracks subscription renewal and re-subscribes before expiry to maintain continuous push notifications. For entities not in NAV's webhook list (such as purchase orders if needed), it falls back to polling on a configurable schedule. Before posting a revenue transaction to NAV's general ledger, ml-connector maps the customer to NAV's customer dimension, the transaction amount to the revenue GL account, and tags the journal with the subscription contract for traceability. Chargebee rate limits are handled with exponential backoff and jitter. Every transaction carries the source document reference (Chargebee invoice ID) and can be traced in both systems via audit logs.

A real-world example

A software company built on Chargebee for SaaS billing runs its finance, AR, and customer records in Microsoft Dynamics NAV on-premises. Previously, each month the finance team exported subscription invoices from Chargebee, reviewed the customer list for new signups and changes, updated the NAV customer master by hand, and re-entered revenue totals into the NAV journal. With Chargebee and NAV connected, new customers appear in NAV automatically, invoice amounts post to the revenue account each billing cycle, and the reconciliation at month-end close takes minutes instead of days because the GL is already balanced.

What you can do

• •Sync new and updated customers from Chargebee into Microsoft Dynamics NAV's customer master with dimension mapping.
• •Post Chargebee invoices and transactions to NAV's general ledger as revenue recognition journals, mapped to the correct GL accounts and customer dimensions.
• •Refresh NAV webhook subscriptions automatically before the 3-day expiry window to keep the sync continuous.
• •Authenticate Chargebee via Basic Auth and Microsoft Dynamics NAV via Entra ID OAuth 2.0, storing credentials encrypted.
• •Reconcile subscription billing to the general ledger with full audit trails and re-playable transaction records.

Questions

How does ml-connector handle NAV's 3-day webhook subscription expiry?

ml-connector tracks the subscription creation time and renewal deadline, and triggers a refresh of the subscription before it expires. If the subscription cannot be renewed, ml-connector switches to polling until the subscription is re-established, ensuring no missed transactions.

Can ml-connector sync customers in both directions between Chargebee and NAV?

Yes. New customers created in Chargebee are synced to NAV's customer master, and updates to existing customer records (name, email, address) flow from Chargebee into NAV. NAV's customer dimension codes are read from NAV and used to tag records but do not push back into Chargebee.

Which Chargebee transactions post to NAV's general ledger?

Invoices, payments, and credit notes from Chargebee are posted to NAV's revenue account and receivables account, mapped to the customer dimension and tagged with the Chargebee invoice ID for traceability. GL entries in NAV are immutable once posted, so ml-connector maintains an audit trail and supports reversal and replay on failure.