Once the quote gets accepted and the subscription is created, the subscription shows incorrect 'Contract Subscription renews for 'X' billing cycles on 'mm/dd/yy' data
The merchant may create a quote for subscription creation with contract terms. The subscription is set to renew for certain billing cycles once the contract ends. Once the quote gets accepted and the subscription is created, the subscription shows incorrect 'Contract Subscription renews for 'X' billing cycles on 'mm/dd/yy' data
For example, The quote was created with On contract term end > Contract end > 'no. of billing cycles on renewal' set as 1. But after the subscription creation, the Subscription shows 'Contract Subscription renews for '2' billing cycles on 'mm/dd/yy' date. Screenshot attached. This is misleading.
Steps to debug:
Check the events of this customer,
Point 1 -Look into the 'quote created' event and note the contract term dates. 
Point 2 - Look for the action_at_term_end and contract_term_billing_cycle_on_renewal
In this case, action_at_term_end is set to renew with the remaining billing cycles set to 1 and contract_term_billing_cycle_on_renewal=2 in the Contract term created
From the events of the merchant’s subscription, could see that the action_at_term_end is given as Renew only, NOT as Contract END. This is evident from looking into the quotes_properties table.
Therefore, while looking into such issues, a close investigation of events and all the tables relevant to the use-case ( quotes, quote_properties ) is much required.
Steps to replicate this use case:
Step 1: Created a quote for a New subscription with the below settings.
Step 2: Updated the quote status to “Accepted“.
Step 3: Created a new sub via this quote. This step created a Future subscription.
Step 4: In the “Edit Subscription“ page, you could see the below configs and it is seen as a replica of the screenshot attached in the problem statement.
From the events of the merchant’s subscription, could see that the action_at_term_end is given as Renew only, NOT as Contract END. This is evident from looking into the quotes_properties table.
Therefore, while looking into such issues, a close investigation of events and all the tables relevant to the use-case ( quotes, quote_properties ) is much required.
Reference Jira
https://mychargebee.atlassian.net/browse/ASEL2-18090