Is it possbile to have consistency in Zuora UI to show customer subscription start and end dates align, so that the end date is not the same as the start date of the following term? I.e. a 1-yr subscription in 2019 should show as start: 1/1/2019, end 12/31/2019 vs what sometimes the UI shows - end: 1/1/2020
... View more
PML - Zuora's account management structure isn't geography based, but rather it's based on specific customer cohorts (which could happen to be regional), so that the right account managers are matched with the right customers based on things like needs, size, scale, and support so that Zuora can best support based on need, rather than grouping only by geography. We will continue to assess how we can deliver best-in-class customer account management and support.
... View more
How to create a discount rate plan that is to be applied to a one-time charge.
Discounts, whether fixed amount or percentage are only available under the monthly plan.
You can specify that the discount be applied to just the one-time charge, but it will show up on the invoice under the monthly charges.
This can be confusing - are there plans to change this so a discount can be applied to a one-time charge that does not show up as monthly on an invoice?
... View more
Is there a standard template for workflow to do an automatic mass price lift for all customers upon their renewal date, and notifying them 30-35 days in advance with a preview of the new amount?
... View more
Has the Zuora team thought about automating the multi-threading of bill runs to manage the elasiticity of a company's demand on peak vs. low volume bill run days/time periods? This would reduce human error from the Zuora customer side in managing and parallelizing bill runs potentially.
... View more
i.e. having one as a primary and one as a failover. If working w/ 2 tax automation platforms, and using 2 zuora tax vendor connectors, is this possible?
... View more
An ACH/Echeck.Net transaction is held for review due to an automated Risk flag. The transaction is successfully received by Authorize.Net however an Approval nor a Decline can immediately be returned at the time the response is sent. It is subsiquently reviewed and then decisioned with an approval or decline. However on the Zuora side, your application is displaying an error message which is not clear to the end user and subsequently transactions are re-attempted causing potential duplicate charges or duplicated refund requests which are causing reconciliation discrepancies and potential inbound customer contacts into our mutual client and/or potential chargebacks.
The same type of risk hold also occurs with the following Response Reason Codes and is not new behavior from Authorize.Net:
104
105
106
107
108
109
110
193
Zuora will need to make an update to gracefully handle these Response Reason Codes to display a “Pending Review” status rather than an error. By mapping to Response Reason Code instead of Response Code alone, your solution would be able to provide more specificity to the issue (aligning with our response string and description of the code as in your reference). From there, by leveraging our Transaction Details API allows Zuora clients to query for updated status.
... View more
