Understanding the "Billing Cycles" Field on the CB Contract Term Object in Salesforce

Problem statement

Merchants may notice differences between the number of billing cycles shown in Chargebee (screenshot) and the value displayed in the Billing Cycles field on the CB Contract Term object in Salesforce. This can lead to 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 within the subscription terms.

A contract term defines the entire duration of the customer’s commitment. This 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 within a subscription.

Example

If a contract term spans 53 months and the subscription within that term is set for 36 billing cycles, Salesforce will display 53 because it mirrors the contract term’s 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.
Differences between Chargebee subscription billing cycles and Salesforce contract term billing cycles do not indicate a data sync issue.