I have a utility which allows our finance team to update rateplans for selected subscriptions. The update request sets a future date for the ContractEffectiveDate field, but since the update API was migrated from the SOAP API request, this can't be updated except when the subscription is in "Draft" status. As a result, I have to rely on updating individual subscriptions which works fine, but is much less performant considering we are updating several 1000's of records each month.
The request body for the action/update POST request (https://rest.zuora.com/v1/action/update) looks like this:
The response that is returned from Zuora is "INVALID_VALUE: The Service Activation Date must be later than the Contract Effective Date."
When I send a PUT request to update the subscription directly with the exact same values, the request is successful. (https://api.zuora.com/rest/v1/subscriptions/<subscription_id>)
Is there anyway I can export ProductRatePlanCharge DiscountClass using ZOQLExport ? Is this field only available in ZOQL ? If it is then it's really painful to switch between ZOQL and ZOQLExport just for a few fields. I know there are some fields that are not available in ZOQLExport but they are available in the prejoined object which is fine for our usecase.
I faced sometimes to use cases which exist on a business with big company which have several entity.
Often, Large Company which have several entity manage annual contract with an other company for Services.
Annual Contract are sign but each entity is considered as a customer account on Zuora. In case of renewal, if the Company sign for the evolution of the contract, users have to amend each subscription for each entity. It's too long.
There is on Zuora the parent Account, and the Invoice owner. Maybe Zuora can Manage that use case.
If Tomorrow Parent Account have a real fonction on Zuora, It could be nice to enable for parent account the ability to create subscription and clone these subcriptions for each entity with for exemple a checkbox.
If the parent account is invoice owner, he will manage all invoices of each entity, if not, all customer account will manage there own invoices.
Currently contracted MRR shows amount without discount and doesn't consider discount sku amount. It should be amount after applying discount.
In the following example it is showing 10,080/12= 840 however, it should be really 10,080-2,580= 7,500/12 = 625. Please look into this !
Create functionality to allow an effective date for rate plan pricing. This functionality would allow pricing to be entered in advance of the "go live" date and would be a building block for future functionality around communication of pricing increases for renewals to customers ahead of time; the ability to get a correct price if increases are coming and there are amendments taking affect during the next renewal cycle; as well as forcasting revenue with future pricing included
We have a general problem with the dates in zuora.
We have a lot of customer that sometimes order wrong amount, wrong type of users, more of the same user in the same month and such.
So the problem are that we aren't aloud to add on more users and so with an earlier contract effective date than the last customer acceptance date (on the same product/user).
This is incredibly important for us as we have many customers who like to order the same product / users multiple times during a month and we then get problem with the admission with regard to the dates.
The subscriptions that are not renewed ( either manual or auto) on the renewal due date should be marked as 'expired' once the renewal due date is past.
Currently, it continues to be displayed as 'Active' which is misleading.
Current functionality with Subscription Amendments in the UI is that only a single Product Rate Plan can be Added / Edited / Removed per Subscription Amendment. This results in multiple amendments to start, amend, or end a subscription when multiple rate plans are being processed together. It would be very useful to be able to Select Multiple Specific / All when Remove Product amendment is selected, and be able to add / edit multiple rate plans per New Product / Update Product amendment.
We have a custom field on the Amendment object used to track attrition reason. It would be very helpful if that could be a field on the popup window when selecting Cancel from the subscription, rather than having to do it manually to the amendment afterwards. Would it be possible to get custom fields added to that workflow?
The Billing Period Alignment options allow for "Align to Charge" and "Align to Term." However, if you want all of your recurring charges to invoice on the same schedule, no matter what the renewal term or billing term, there is no setting.
We use "Align to Term" now and if customers have matching Billing Period and Renewal Term (Monthly billing and 1 month Renewal, for example), a mid-term change will generate a prorated invoice for the remainder of the month and then pick up all charges at the next billing period. This works great. But when we have a customer that has Quarterly billing period and monthly renewals for example, a mid-term change misaligns those same charges with the same settings. Since charges are configured by Billing Frequency, we only have the ability to configure our Quarterly charge with one option. So changes for this customer are manual every time.
The Subscribe call includes Invoice processing options which only allow for:
1. Invoice Date
2. Invoice Target Date
3. Processing Scope - Account or Subscription level
This does not allow for the optional filtering of which charge types you want to appear on this invoice i.e. Recurring, One-Time or Usage charges only or a combination of all 3. The Generate Invoice call does include these options with the inclusion of the following fields:
1. IncludesOneTime = Set to True or False
2. IncludesRecurring = Set to True or False
3. IncludesUsage = Set to True or False
Could the Susbcribe call be extended to include these fields?
We'd like to be able to have a template to mass update the following field:
Create a new amendment type of "Upgrade" or "Downgrade" that combines a Remove Product and New Product amendment. This would be more convenient than trying to figure out if the two amendments (Remove + New) are related and what direction (Up or Down) the change is going.
Currently, we use delta MRR to see if it's an upgrade (positive MRR) or downgrade (negative MRR). But there are some cases where the delta MRR is 0, but from a product standpoint, it may be an upgrade or downgrade.
Thanks for reading!
I'm making a report of Subscriptions with rateplans depending on pending customer acceptance. Because I want amounts, I'm starting with RatePlanChargeTier. There's no way to get the Account name into the report.
Please add Account to the RatePlanChargeTier datasource!
We are just coming into Zuora, and we have many scenarios where our customers may have multiple products with multiple different renewal dates. This is translating into multiple subscriptions as we get them loaded into the system.
Going forward, our reps would love to be able to combine and co-terminate these subscriptions to make things simpler for our customers where possible, but at the moment we're telling them that they have to manually transfer all of the lines from the old subscriptions to the new subscriptions because there is no capacity to join these together.
This would be a great help for us, and I'm sure for many other new customers coming on to the Zuora platform!
in B2C businesses we often find that we need to cancel a subscription due to nonpayment ... An issue arises when a customer then makes a payment on the open invoice. We are unable to remove a cancellation once it is made. If we were able to remove the cancellation it would allow us to reinstate the subscription service without overly complicating the data with a newly created subscription.
I'm using the product catalog call to return the entire catalog of products to show all available prodcuts in an application.
However I'd only need the products currently active (see "Effective Start" and "Effective End").
For subscriptions there is an option in the call to filter for active subscriptions (using ?charge-detail=current-segment).
I suggest implementing a similar option for the product catalog, e.g.:
which should only return products where the "Effective Start" date is after and the "Effective End" date is before the current date.
The Mass Order Entry function currently uses Product.Name + RatePlan.Id as a composite proxy key for current charge lines on a subscription. This is a bad proxy because the same product and rate plan may occur multiple times on the same subscription. The Mass Order Entry function fails when it encounters these subscriptions.
Ideally, the function would instead use a primary key that uniquely identifies the current version of a charge line. Absent this, it would use a better proxy key. For example, the Mass Order Entry Template already includes RatePlanCharge.ChargeNumber under the heading "Charge Name." The proxy composite key RatePlanCharge.ChargeNumber + RatePlanCharge.IsLastSegment = TRUE more accurately identifies the current charge lines on a subscription.
Zuora could implement this chage without impacting customers that rely on the current Mass Order Entry function by switching to a new proxy key based on the current template requirements. If the development team has concerns about this approach, you could invoke the new proxy key only when the current proxy key returns an error.