Problem: Why is amendment changing discount not taking effect on service activation date?  The amendment changing the discount in mid-month is not taking effect.   Background of the issue: An Update product amendment was created in the subscription to change the discount percentage from 22.2222% to 12.2222% with the effective date Feb 12(mid of the month) but still, the old discount percentage(22.222%) was applied for the entire service period(Feb). The Price is not prorating based on the dates.   Solution: The Customer's use case is, Initially, the percentage discount of 22.2222% is set to apply on the recurring charge. After that, they have changed the percentage through amendment to 12.2222% with the effective date Feb 12. When invoicing for the period 02/01/2020 to 02/11/2020, the discount percentage is 22.2222%*11/31 and when invoicing for the period 02/12/2020 to 02/29/2020, the discount percentage is 12.2222%*18/31. Basically, if this is the use case, then Zuora does not support such functionality. The Discount Percentage cannot be prorated.  In this case, the discount is 22.2222% from 02/01 to 02/31 which means that the percentage is 22.2222% for any charges billed in this period. The discount applied does not depends on the period length and it does not contain a partial concept.  The explanation for this behavior is due to the type of discount. It is  a percentage discount and auto-renew is set to Yes. The original discount term end date is replaced by the fact that the term has now entered into the renewal period. In cases where the term is extended beyond the end date, percentage discounts do not prorate, and instead apply to the entire month. If you want the discount to apply to just that portion of the month, you could set up the discount to be a flat fee amount which could be properly prorated. Or you can set the Auto-renew to No after the Invoice has been generated for the period up to 02/11, and then you can create a renewal amendment, create an update product amendment to update the discount. I have tested this and it worked fine. Please refer to the screenshot for reference, ... View more

Problem: BillRun BR-0000XXXX  picked account 8a28828d6c750fdxxxxxxxxxxxxx. However, no invoice is produced for that account through that BR on 12/01, so why is it picked up. If we look at the subscriptions, nothing seems to have changed... so I'd need to understand why it was picked up? Solution:  Looking into the bill run, the setting "Renewal Triggering" was set to TRUE. So, the bill run will not filter the account by Next Charge Date. And, it would pick up all active accounts. The Accounts which are picked up in the bill run can be viewed under the  Bill run Page --> 'Selected Customer Accounts' tab. Basically the account which is being picked up in the bill run is based on the account's next charge date also known as NCD. And our rating and billing engine picks the account by comparing the next charge date and target date. This is the ultimate filter condition in the bill run. Auto-renew also plays a special role in this. The system first checks whether the charges are renewable before checking NCD. That is, it will iterate all accounts if renew is on and use NCD to decide if the account is being picked for rating and billing processing or not. This is for performance optimization, if the system processes every account every day and assuming it's only billable every month, it's a huge performance waste. ... View more

Problem:  When extracting rateplancharge object from data sources export, some of the rateplancharge records do not have account id nor subscription id. Are these bugs since there's no way to link to the account/subscription. Solution: When an update product or remove product amendment is in draft or pending acceptance status, then that rate plan charge will not be associated with any of the customer accounts/subscriptions until the user activates the amendment. One can check this by using the amendment fields in rate plan charge data source export to check the amendment type and status of the amendment as shown below,   ... View more

Problem: When we are trying to cancel the credit balance adjustments, getting the below error- [INVALID_VALUE] The available Credit Balance is insufficient to cancel this transaction.   Background of the issue: A customer account has a negative invoice(-200) and it has been transferred to the credit balance, during this process a credit balance adjustment(CBA00000001) was created. And again a new credit balance adjustment(CBA00000002) was created when that credit balance(200) was applied to another invoice. Hence there are two CBA transactions for this account. When the user is trying to delete the previous credit balance adjustment(CBA00000001), they get the above error. Solution: In order to cancel the previous credit balance adjustment, the possible solution will be deleting the recent credit balance adjustment(CBA00000002), which is created when applying the credit balance to the invoice and then canceling the previous credit balance adjustment(CBA00000001) which is created to transfer the amount in the negative invoice to the credit balance. ... View more