Why is there a discrepancy in 'Billing Cycles' between Chargebee and Salesforce?
Problem Statement
Merchants may notice a difference between the number of billing cycles shown in Chargebee and the value in the Billing Cycles field on the CB Contract Term object in Salesforce. This can cause confusion when comparing subscription details across both systems.
Solution
The Billing Cycles field on the CB Contract Term object in Salesforce reflects the contract term billing cycles from Chargebee. It does not represent the billing cycles shown in the subscription terms.
A contract term defines the entire duration of the customer's commitment. That duration may span multiple subscription billing cycles, so the number of billing cycles in a contract term can be higher than the billing cycles defined for the subscription.
Example
If a contract term spans 53 months and the subscription within that term is set for 36 billing cycles, Salesforce displays 53 because it mirrors the contract term length—not the subscription's billing cycle count.
Additional Information
- Contract terms and subscription terms track different timelines in Chargebee.
- The Billing Cycles field in Salesforce always reflects the total number of months (or cycles) covered by the contract term.
- A difference between Chargebee subscription billing cycles and Salesforce contract term billing cycles does not indicate a data sync issue.
Related Articles
Was this article helpful?