How do I fix Salesforce customer sync blocked by Account Business Entity?
Problem Statement
A Chargebee customer does not sync to Salesforce, and subscriptions for that customer stay out of sync because the customer has not synced. This can happen when account-matching rules find an existing Salesforce account (for example, using a shared external ID) and that account has only the Business Entity lookup populated. Changing the lookup to a different business entity does not clear the failure.
Related Scenarios
- Retrieve Data or customer remapping does not resync the customer.
- Duplicate-account or duplicate-rule errors were ruled out, but the customer still does not sync.
- Multi Business Entity is enabled on the Chargebee site and multiple entities are connected to Salesforce.
Solution
This flow applies when Multi Business Entity is enabled on your Chargebee site and the Chargebee-Salesforce integration is already connected. Use the Salesforce integration guide for sync health, sync logs, and the CB Sync Logs object before you change data in Salesforce.
- In Salesforce, open Chargebee Settings (from the Chargebee for Salesforce app) and open the sync log for the business entity. Find the failed customer by Chargebee ID.
- Identify the Salesforce Account that your sync rules match to the Chargebee customer (for example, via your configured matching fields).
- On that Account record, open the Business Entity lookup field (mapped as Lookup(CB Business Entity) in the Account field map).
- Clear the value in the Business Entity field on the Account. Save the Account. Do not only change the business entity to a different value; clearing the field and retrying is required when this lookup is blocking sync.
- On that sync log, select the failed customer row and click Retry Sync.
- After the customer sync succeeds, retry any subscriptions that failed because the customer had not synced.
The customer's sync status should show success, and dependent subscriptions can sync on the next run.
Important Notes
- If the matched account should map to a different Chargebee customer, use customer remapping instead of only editing Business Entity.
- If the failure reason is DUPLICATE_CUSTOMER or duplicate-rule errors from Salesforce, see matched account already linked or duplication rules.
- Targeted resyncs do not automatically fix subscriptions and invoices that were synced under an earlier mapping; plan a separate retry for those objects after the customer sync succeeds.