WSDL support for Finance related custom fields in WSDL, currently such fields are not added to the WSDL automatically. Requires workaround of adding the fields into the WSDL manually.
Support NetSuite Revenue Recognition Templates for Zuora Discount Charge Models
We were informed that the "Download Summary Tab Information" in the Accounting Period will be soon phased out. Is there a way to request that this be retained in our production tenant? We find this to be more concise and useful plus it gives us a clear representation/snapshot of the monthly movements in the Accounting Period. The exported "Journal Entry Item" report/extract has too many details and I don't think the numbers are reconciled with the figures as presented by the "Download Summary Tab Information" in the Accounting Period.
Thanks and hope this can be considered.
Currently, Zuora does not provide the option to set up a revenue recognition rule that allows for the use of the model "Monthly Recognition over time" to recognize one-time charges over the life of a subscription. The only option that enables the proper revenue recognition of one-time charges over the life of a subscription is to use of the "Daily Recognition over time" model. This model does not allow for a smoothed revenue option. I have spoken with other Zuora users & all are in agreement that this is a critical option that is missing. In order to achieve the desired revenue recognition model, we are spending countless hours redistributing revenue each month, negating the purpose of the productivity tool that we had expected from the software. I strongly urge you to consider updating your "Monthly Recognition over time" to include the option to set the Recognition Term End Date to Subscription End Date.
We need to run the Trial Balance Report in Zuora every Tuesday at 5:30am AEST. Since we perform the activities out of India, we have to log in early just to run this report. Also, it takes a long time to generate the report when we initiate it from India (refer ticket (#87843) & (#87945)).
Hence the request is to have an enhancement to be able to auto schedule this report at a specified time at a specified frequency.
Please help us by adding this feature to the Zuora interface.
Want to be able to close the current accounting period and run a trial balance on the closed accounting period at the start of the new accounting period.
For example: the on June 1st 12:01am the accounting period for May will be closed and the trial balance for May will be run.
This way finance teams will not have to wait on the trial balance being calculated at the crucial month end period.
Feature Request: Make additional Account and Invoice fields available on the AR Aging Datasource
Reference Number: DE7928
1. Provides additional reporting information regarding account and invoice data
2. Current design requires that two reports be run then combined to pull relevant account data (such as credit balance)
3. Multiple reports required to create a detailed AR aging at the invoice level
Currently the invoice API only allows the transferred to accounting field to be set to Yes, Ignore, Error, or Processing.
We need the limitation to be removed, so that we can also set the field back to No.
Once this is removed, we will be better able to reprocess records in case of failure.
In Europe, VAT is reported into separate GL accounts for each country and sometimes product type.
Zuora is limited to assigning a single accounting code for all VAT.
Ability to assign multiple accounting codes for VAT tax‰Û¡ÌÝÌÏ
Ability to assign accounting codes at Tax Rate level.
The finance team of our organization require that the amount generated by the report "Invoice Payments Processed Successfully" less the amount generated by "Refunds Processed Successfully" should always match the Subtotal Invoices of the Trial Balance. I opened a ticket to review that topic but the answer was "PM doesn't find a need to make changes to accounting period summary or account period balances. However, we do have a Product Feedback forum where you can post your feature request"
The thing is Accounts Receivable don't make sense to our business case and we don't want it to be reflected in Trial Balance at least.
1 Summary of the enhancement?
Allow rate calculation for volume based rate plans to be based on the aggregate of the quantities of all child accounts.
2. What is the business problem?
We use volume based recurring pricing models.
Our enterprise customers want to aggregate the total quantity subscribed to across the enterprise in order to calculate the appropriate volume pricing level, but have separate charges for each department.
e.g. if we have volume pricing levels for up to 100 widgets at $10 per widget;
100 to 200 widgets at $7 per widget for all widgets.
If company has department A with 50 widgets, department B with 90 widgets, they want to receive an invoice with all quantities priced at $7 per widget (which would be the recurring price if departments A and B's volume was combined), but separate line items for department A ($7 x 50) and department B ($7 x 90).
What is the business impact?
Without this ability, we have to bill such clients outside of Zuora. Which leads to manual work on our side, and of course removes our biggest customers from being billed through Zuora, which impacts the use of the Zuora reports, etc (and of course reduces Zuora's revenue based on our billing)
What is the proposed solution?
For child accounts, when defining a subscription, allow the selection of a subscription from the parent account. Quantity is reported in the child accounts, but the billing quantity is aggregated for all child accounts sharing the same subscription; the appropriate rate calculated; and the apportioned amount applied to the child account subscriptions. (The child account could be an informational invoice, of zero dollar, to avoid double billing.)
Feature Request: Rev Rec fields not available in the RatePlanCharge object
Reference Number: DE7633
The RevRecCode and RevRecTrigger fields are not available in the RatePlanCharge object in the API. These fields are available in the ProductRatePlanCharge and the InvoiceItem objects. -- This prevents any changes from being made to the Rev Rec values through the API.
Feature Request: ability to cancel 'out of term' subscriptions from locked accounting periods that do not initiate any invoices or impact any financial data.
Reference Number: DE10714
Business Need: cannot manage accounts that should be closed because the subscription cannot be cancelled.
When we sync products and charges to Netsuite, there is a field in Netsuite (Display Name) that does not exist in Zuora. If you change that product's name, it changes all of the related names in Netsuite EXCEPT for the Display Name. So all of the charge related fields show one name and the display name shows another. That field should be supported by the integration. There should be a "Netsuite Display Name" custom field that we can change when we change the charge names.
Customers are interested in syncing reason codes and additional standard or custom fields to Z-Suite, specifically payment, refund, and IIA transactions. Suggest making Z-Suite extensible to include additional fields for the customer to sync.
Can we enhance Z-Suite to support syncing credit balance adjustments to NetSuite? This is a major gap that customers struggle with and end up deciding not to use credit balances.
Currently the aging report calculates the home currency of the last day of the month (accounting period) exchange rate. The date of the invoice (billing date) is the proper exchange rate to use as that is when clients are billed.
Currently, this only is allowed through the REST API.