A contract modification rule is designed to identify what type of change that has occurred and trigger a revenue allocation treatment for a revenue contract. When the Skip Contract Modification Rules toggle is switched to Yes, Zuora Revenue automatically skips the contract modification rules and does the reallocation based on the existing treatment.
When the Skip Contract Modification Rules toggle is switched to No, Zuora Revenue performs allocation treatment based on the configuration modification rules that are set on the Contract Modification page.
Predefined contract modification rules
Predefined contract modification rules are provided and categorized as follows:
Cancelation/Returns: This rule is triggered when the amendment of a contract is caused by the cancelation or return that occurs in the contract.
New POB: This rule is triggered when a new POB is added during the contract revision timeline as the amendment for the revenue contract.
New Transaction: This rule is triggered when a new line is added to the existing POB during the contract revision timeline as the amendment for the revenue contract.
Price Modification: This rule is triggered when there is a change in price in the contract as the amendment.
Quantity Modification: This rule is triggered when there is a change in quantity in the contract as the amendment.
Term Modification: This rule is triggered when there is a change in the term in the contract as the amendment.
Others: The rule is triggered for the change in the contract value that is caused by linking, delinking, material rights, and variable change.
For more information, see Predefined contract modification rules.
Default allocation treatment is provided for the contract modification rule. However, the default allocation treatment might not suit your business needs. Ensure that you have reviewed the default allocation treatment and made adjustments as needed.
Complete the following steps to configure contract modification rules in Zuora Revenue:
Navigate to Policies > Contract Modification. The Contract Modification page opens.
In the Contract Modification Timeline section, switch the Skip Contract Modification Rules toggle to either of the following options:
No: Apply the contract modification rules, which you will configure later in the Contract Modification Rules section, to determine the contract modification allocation treatment.
Yes: All the contract modification rules that are configured in the Contract Modification Rules section are ignored.
If you select Yes in the previous step, select Prospective or Retrospective for the Default Allocation Treatment field. If you select No, proceed to the next step.
In the Initial Contract Timeline section, specify the fields as documented in Initial Contract Timeline Fields.
In the Revision Timeline section, specify the fields as documented in Revision Timeline Fields.
In the Contract Modification Rules section, select the appropriate allocation treatment from the drop-down list in the Modification Treatment column for each rule.
If you select New Revenue Contract for the new POB rules, you also need to further specify the treatment for the newly created RC. Valid options are:
- Create and Keep Open
- Create and Close RC
If a window does not pop up for you to select, hover the mouse over the line and click .
Click the save icon to save your settings.
After the contract modification rules are set up, when a change comes for a transaction line during the contract revision timeline, Zuora Revenue automatically applies the corresponding treatment for the contract based on the rules that you set up.
When multiple amendments that trigger different types of treatments occur during one single revision timeline, the final treatment is retrospective if the following two conditions are BOTH met:
- The treatment is distinct.
- The system-level value of the ENABLE_RETRO_PROSPECTIVE profile is NO.
Impact of SKIP_CT_MOD_FLAG field
Flexibility is also provided in Zuora Revenue for you to restrict a specific transaction line from triggering contract modification rules due to amendments. When you set the SKIP_CT_MOD_FLAG field to Yes for a transaction line, the system only performs the re-allocation and does not trigger contract modification rules for prospective or retrospective allocation.