We need the ability to pre-select back-end discounts which should be automatically applied during the bill run. These discounts should be configurable on each subscription rate plan charge, preferably managed as a percentage.
The existing functionality is not sufficient to meet our requirements.
Existing option 1 (invoice item adjustment) - We need to apply these discounts before applying minimum pricing, so it cannot be handled as a credit memo/ invoice item adjustment (after bill run). If we wait, the minimum pricing calculation will be incorrect.
Existing option 2 (amendment) - we do not want these discounts to be visible to the customer or salesperson, as it would be confusing for them. These back-end discount amounts are actually still billed to the customer through a partner.
Zuora returns error "Resume Date cannot be later than the Term End Date." when trying to suspend/resume a subscription past its term end date. There is an option to "Extend the current term by the number of days (*) suspended.", but that does not resolve the error because Zuora checks for the resume date before extending the current term. I think if the option is checked, the error should not appear.
The current schema (PO Number is on Account) seems to assume that the Zuora user has only one PO with any account. In our case, we have customers with multiple subscriptions, and they issue a PO per subscription. Not only that, they issue a PO for an amendment.
This feels like a bug report, but Patrick Seet from Zuora Global Support has asked us to request it here:
We confirmed that passing a custom authorizationAmount to our hosted payment page does not work for Braintree gateways:
Feature Request: display the Invoice Item for Overage if the Tiered w/ Overage Rate Plan Charge Tier has a $0 Overage Price (bonus) so that it can be map as well on Invoice PDF.
Status: currently being evaluated by our Product Management.
Reference Number: DE9997
Business Need: the concept of bonus impression ($0) is standard use case in the Internet Advertising agency. Dependencing on how the contract is written, the ability to bill under a declining balance or capped usage model is key in the Ad industry.
I have added a new subscription and activate it with 01/01/2017.
While adding the product, I set the end date = 02/12/2018 and expecting the invoice service period date will be 19/01/2017 to 01/12/2018 but I am not getting the invoice with the specific date i.e. 01/12/2018. It comes with 31/12/2018. I want to charge for two years.
Please let me know if I missed something.
I need a way to Quickly adjust ALL invocies for an account to zero.
it takes too long to do this one by one for each account
BTW.. your solution to import CSV files for everything borders on .. i dont have resources for GUI developement
Feature Request: cloning Product Rate Plans should left the NetSuite custom fields blank.
Status: under evaluation
Reference Number: PMT-491
Business Need: If you fail to change the ID when you clone it, Z-Billing will sync two Z-Billing charges to the same NS Item causing lots of data issues with financial impact.
I tried your technical support team, and was told that this feature is not supported. So, they suggested me to submit idea to create this feature.
Basically, we tried Zuora Soap API and Rest API to generate Invoice Preview, and the Invoice Items are always returned as 1 huge big list. For exmaple, if I preview for 3 months of a montly subscription, I get back 1 list of Invoice Items for all 3 months. Then, I have to somehow figure out a rule to seperate them into 3 groups, and display properly for my client. It's not an easy job. I could never figure out your full rule to group these Invoice Items to be the same as what Zuora shows on Zuora web UI. It's a big frustration for both our development team and our clients who rely on us.
Would you please return grouped Invoice Items?
These are 3 APIs I tried. Please take a look at their returned InvoiceItems. It's really hard to use these data.
We currently have 16 billing batches that our customers are separated out into based on payment method, subsidiary, etc. We have to run daily bill runs for almost all of these batches. It is tedious having to complete the same thing (but the batch # is different each time) 9 times in a row. It would be helpful if we could select certain batches that we want to run and then enter in the invoice date and target date for all the selected batches.
We need the ability to run a BR for a specific subscription (i.e., the client wants to prepay one subscription for the next 24 months, but wants to leave another paid monthly). We'd be very grateful if this feature could be added to the bill run parameters.
We are experiencing major reconcilation issues given the lack of connect for ACH reversals and chargebacks. This seems to be yet another feature not supported with Cybersource. Please provide the Gateway Reconcilation for the Cybersource gateway.
Business Problem :
We use the payment run completion event to trigger a external custom payment run process that interfaces with payment gateways not supported out of the box by Zuora ( Buckaroo, Heidelpay, Ogone ... ). This allows customers to schedule the external payment runs from with in the Zuora UI. However none of the payment run selection parameters that can be defined for a payment run are available in the call-out notification.
Customer can not execute scheduled/adhoc specific external payment runs from within Zuora as the selection parameters are not available to the external payment run process.
Create a custom web page on which the user customer can create specific external payment run. This how requires developing and hosting a custom website and pulls the user out of the Zuora UI.
Extended the call-out parameters for the payment run completion with all selection parameters that can be set by the user in the new payment run screen:
- All customers accounts
- Selected Accounts
- Batch Filter
- Bill Cycle Day
- Payment Gateway
- Bill Run
- Apply Credit Balance
- Process a single payment
- Target Date
It was confirmed by a Zuora Support rep that the product does not currently support negative usage. This is a real use case for us. We currently import usage on a daily basis. In some cases, one-off adjustments need to be made for usage already submitted to Zuora. Because Zuora does not support the import of negative usage, the total counts are inflated and require manual intervention on the individual usage entries or on invoices. No alternative solution or best practice alternatives was offered by Zuora. It has been considered to send a single usage stat every month before a customer's billing date but this causes challenges with timing.
Internal RFE Request:
Feature Request: Ability for payment gateway to failover
Reference Number: DE5566/PMT-489
Business Need: Some customers are looking for the ability for payment gateway to failover. For example, in case Payment Gateway A is down or unavailable, after reaching maximum number of payment failures, Zuora will let gateway to failover from Gateway A to Gateway B, so that customer can collect payment through another gateway.
Feature Request: Ability to create and define new Unit Of Measure (UOMs) using the Zuora API
Business Need: Currently it is difficult to manage product catalog through only the API. In order to create and define UOM you must login through the UI and create and define UOMs. The ability to pro-grammatically create and define UOMs though API script can help speed up releasing new subscriptions.