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
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'd like to be able to have a template to mass update the following field:
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.
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 !
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?
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.
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.
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 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.
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!
In current UI functionality if a One-Time rate plan charge has been added to a subscription but not yet billed, there is no way to Amend the value of the One Time Fee. The Update Product amendment will not allow you to change either the price or quantity. While I can understand this if it was already invoiced, not being able to update an unbilled One-Time fee is a real issue. The only workaround i have been able to find is to remove the product and add it back again, requiring two amendments (Remove Product and New Product) instead of one (Update Product).
It would be really helpful if we could add/remove columns under Subscriptions & Amendments - Subscriptions-Owned on the customer account. Example: if we wanted to remove the List of Products column and replace it with the rate card instead.
On the account screen when you click on View All for Subscriptions this list should include the Subscription/Product Name.
Currently this is missing, making it difficult to distinguish/pick the correct the subscription.
This should be easy as these names already exist on the table visible from the account screen.
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!
Currently, if an amend() call is made, the Zuora API will sometimes respond with a 504 - Gateway Timeout. However, the amend continues in the background for an indeterminate period of time until it completes. The problem is that when we receive an error from Zuora, we assume it failed, so we attempt to retry it until it succeeds. This leads to billing the customer multiple times for the same item, since we don't know if it succeeded or failed.
We've attempted to use a read-ahead before doing the amendments to ensure that the rate plan charges do not exist on the subscription, but that doesn't work when the amend call is still running in the background for some indeterminate period of time. Since there's no way to know how long is "long enough" to wait for it to finish, the only way for client code to guarantee that something is billed exactly once is to amend until it succeeds, then read the subscription back afterwards and remove duplicate rate plan charges that may have been created accidentally.
Since that solution is very onerous to all clients, instead the Zuora amend API should be transactional - that is, if an error code is sent to the client, the entire operation should fail and roll back. This is the typical, expected pattern when it comes to billing software.
The client has reported the following quirks in the Zuora UI. They are not show-stoppers, rather quality of life issues that make "managing the Zuora product catalog an unpleasant experience".
When viewing the product catalog, the List View only shows 6 items at a time unless you click the Expanded View tab and then move back to the list view tab, then it shows 25 items. Why can't it show 25 items by default?
Proposed Solution - Make the product catalog via show 25 items by default
After selecting a catalog view, if you then select an item in the catalog and then select ‰Û¡ÌÝÌ back to Product Catalog List‰Û¡ÌÝå , you are not brought back to the view you left, but are instead brought back to the default catalog view. This makes managing the product catalog maddening when you have lots of products, especially when combined with the next item.
Proposed Solution - Selecting "back to Product Catalog List" should take users to the previous view, not the default view
When selecting a catalog view, it takes two clicks (4 if you count clicking between expanded and list views) to get to the view. You must first expand the items under Base/Addon/Misc, and then select Current underneath. It would be much better to just select (for instance) Base Products and be shown all the active base products.
Proposed Solution - When selecting a catalog view, users should be able to just select, for instance, Base Products and all active base products should be shown. The number of clicks should be reduced.
It would be helpful to us if we could define additional product categories. For now we are just dumping all the categories not supported under misc, but it would be better if we could define new categories and have them show up under Catalog Views. This would make it much easier to manage things like hardware, setup fees, etc.
Proposed Solution - Users can create custom product categories
Reference Number: DE7635
Business Need: Users are spending more time than needed to navigate through the product catalog.