About Yong

Yong

Please use the provided workarounds before SET-2036 is fixed.

Yong

Known Issue When applying a Credit Memo to multiple documents, such as Invoices or Debit Memos, error "Allocate result is -0.01 which is invalid" happens. This issue happens both in UI and API in some cases. It could be -0.02 or other very small values. Status Zuora Engineering Team is currently working to fix this issue. Reference Number SET-2036 ETA of the Fix We cannot provide an ETA yet. Reproduce Steps 1. Create a standalone Credit Memo (CM 1) with 3 Credit Memo Items (CMI 1) with individual amount 25 and the Credit Memo unapplied amount is 75 in total. 2. Create 3 standalone Debit Memos (DM 1, DM 2 and DM 3) with individual amount 25. Each Debit Memo has one Debit Memo Item. 3. Apply the CM 1 to the 3 DMs at the same time in UI, error "Allocate result is -0.02 which is invalid. " happens. Cause If your "Default application rule for apply" is proration, when applying CM 1 to a DM 1 with one DM item (DMI 1) and amount 25, the formula will be: 25*25/(25+25+25)=8.333333... CMI is short for Credit Memo Item. DMI is short for Debit Memo Item. 8.33 from CMI 1 will be applied to DMI 1. 8.33 from CMI 2 will be applied to DMI 1. 8.34 from CMI 3 will be applied to DMI 1. At this time, CMI 1 unapplied amount is 16.67. CMI 2 unapplied amount is 16.67 CMI 3 unapplied amount is 16.66. When our application applies the remaining amount of each CMI to the next DM 2, the same process will happen again. That is why -0.02 rounding issue might happen in some cases. Workarounds 1. If the above error happens, apply CM to documents one by one, not at the same time. 2. Go to Payment setting, Update "Default application rule for apply" from Proration to First in First out. https://knowledgecenter.zuora.com/CB_Billing/Payments_Settings/Default_Application_Rule

Yong

Some fields can only be used in a specific wsdl version. The full list can be found in https://knowledgecenter.zuora.com/DC_Developers/G_SOAP_API/Zuora_SOAP_API_Version_History You will need to include X-Zuora-WSDL-Version in the header. It looks like: Reference: https://knowledgecenter.zuora.com/DC_Developers/BB_Export_ZOQL https://www.zuora.com/developer/api-reference/#operation/Object_POSTExport

Yong

Why do I get INVALID_VALUE error when making CRUD: Create Export call? Sample request: Request: POST https://rest.apisandbox.zuora.com/v1/object/export Body: { "Format": "csv", "Name": "test_Export", "Query": "SELECT CreditTaxationItem.Name, CreditTaxationItem.Jurisdiction, CreditTaxationItem.TaxRate, CreditTaxationItem.TaxRateType, CreditTaxationItem.TaxDate, CreditTaxationItem.TaxRateDescription, CreditTaxationItem.RefundAmount, CreditTaxationItem.Id, CreditMemoItem.Id, CreditMemo.Id FROM CreditTaxationItem WHERE CreditMemo.Balance = 0 AND CreditMemo.Status = 'Posted'" } Response: { "Errors": [ { "Code": "INVALID_VALUE", "Message": "You cannot use all of these objects in the same query: Account, CreditMemoItem, CreditMemo, CreditTaxationItem." } ], "Success": false }

Yong

Hi ankurlalit, Please create a support ticket via our support portal support.zuora.com and request terminate the processing BPR. Regards,

Yong · ‎04-12-2019

Root cause It is a known issue caused by 3rd party Avalara (tracking number 15764793, scheduled to be fixed in the first half of 2019). Avalara is not sending Zuora all the tax line items. The issue is resulting in small differences between tax reporting available in Zuora and AvaTax calculations. These small differences result from the display of incomplete tax details for a limited number of state-level jurisdictions—like Tennessee—where there are multiple components to the state-level tax. While the breakout of taxes by jurisdiction may be incorrect, the total tax calculated for invoicing, and the tax detail amounts recorded by Avalara and displayed in the AvaTax UI are correct. The issue on the Avalara side is with Avalara batch(async) API call, and not with the real-time(sync) API call. So the issue might happen when a batch call response is sent by Avalara. For real-time UI and API call, it works fine. Workaround For the affected customer accounts, such as the state is Tennessee, post the draft invoice in UI manually or with below API call. You can also un-post the invoice and then post it again via UI or API. Please note this workaround only applies when the invoice item number of a specific invoice does not exceed 3,000. REST call - https://rest.zuora.com/v1/object/invoice/{id} Reference: https://www.zuora.com/developer/api-reference/#operation/Object_PUTInvoice SOAP call - update() Invoice Reference: https://knowledgecenter.zuora.com/DC_Developers/G_SOAP_API/E1_SOAP_API_Object_Reference/Invoice

Yong · ‎04-12-2019

We came across this Invoice where the Tax posted on the Invoice in Zuora was reflected as below: County: 2.25% on 1600 = $36 City: 0.5% on 1600 = $8 State: 2.75 % on 399 = $10.97 However, in Avalara it is reflected as following. County: 2.25% on 1600 = $36 City: 0.5% on 1600 = $8 State: 7% on 1999 = $139.93 State: 2.75 % on 399 = $10.97 Why is it missing the state tax for 7% on 1999? Three tax items are on Zuora end. Four tax items are on Avalara end.

Yong · ‎04-01-2019

After Invoice Settlement is enabled, you might see the above message. Steps: 1. Create a payment and do not apply it to any invoice or DM. 2. Apply a partial amount to an invoice and set Effective Date to 04/30/2019 (Today is 04/02/2019). 3. Try to apply the rest amount to another invoice and set the Effective Date earlier than Effective Date, such as 04/02/2019. You will get error "The specified effective date should be later than or equal to the latest date of the application group." If you use Data Source Exprot to export object Payment Application and apply filter payment number equals to the sample payment number, you will see the first applied "Payment Application: Effective Date" has been set to 04/30/2019. Resolution: When apply the payment to another invoice, the Apply Payment Effective Date cannot be ealier than the previous "Payment Application: Effective Date", in this case 04/30/2019.

Yong · ‎04-01-2019

When apply a payment, why do I get "The specified effective date should be later than or equal to the latest date of the application group."?

Yong · ‎03-27-2019

From your mail server log, if you can see "Unauthenticated email from zuora.com is not accepted due to domain's 5.7.1 DMARC policy", it means it is rejected due to DMARC policy. Here is the sample log recorded on Zuora end. Feb 18 18:19:43 appmail01 postfix/smtp[9497]: 24F9187E7F: to=abc@abc.com, relay=abc.barracudanetworks.com[64.235.153.xx]:25, delay=1.7, delays=0.03/0/0.69/0.98, dsn=5.0.0, status=bounced (host abc.barracudanetworks.com[64.235.153.xx] said: 550 permanent failure for one or more recipients (abc@abc.com:550 5.7.1 Unauthenticated email from zuora.com is not accepted due to domain's 5.7.1 DMARC policy. Ple...) (in reply to end of DATA command)) From dmarc org site https://dmarc.org/overview/ The bounced issue happens due to the receiver's dmarc policy. After the email is sent from zuora end, the dmarc is controlled by the receiver. To resolve the issue, you will need to work with your email service administrator to find out why the email from support@zuora.com and update your mail setting to resolve the issue. Here is one sample solution provided by Google if you are using Gsuite as your mail service provider. Set up and inbound gateway, this helps to ensure that Gmail determines the proper source IP for email authentication. You can follow the steps bellow or visit the next Help Center article for more details: https://support.google.com/a/answer/60730?hl=en. Normally changes done in the admin console take up to 24 hours to propagate. 1. From the admin console (admin.google.com) 2. Select Apps > G Suite > Gmail > Advanced settings 3. Scroll to the Inbound gateway setting in the Spam section. Hover over the setting and click Configure to create a new setting. 4. Enter a description. 5. Under Gateway IPs, click Add and enter the IP address or range of addresses. 6. Select Automatically detect external IP. 7. (Optional) To reject connections from IP addresses in the Gateway IPs list if the connections don’t use (TLS), check the Require TLS for connections from the email gateways listed above box. 8. Click Add Setting and Save. 9. At the bottom, click Save again If you can get the email but your customer cannot, you might follow this doucment to Configure Your SPF Record following https://knowledgecenter.zuora.com/kb/How_do_I_stop_customer_emails_from_getting_sent_to_spam_or_junk_filters%3F

Yong · ‎03-27-2019

Why cannot I receive the email from support@zuora.com, such reset password or Bill Run Notification?

Yong · ‎03-21-2019

Hi @crengutam I believe I have figured out what happened. InvoiceItemId 2c92a0986976677301697812b75c73da amount is -3.33. You cannot make another 0.07 credit against it. This will make the amount -3.40 which is against the IIA creation logic. To resolve this, you can make the 0.07 credit against the other InvoiceItem which has the positive amount.

Yong · ‎03-21-2019

Resolution: Check the "status" field in the payment transaction log. The unexpected result is "status":"new". The expected response is "status":"verified" from Stripe. You can update the account status to verified status on Stripe gateway or reach out to Stripe payment gateway team for further assistance. After the status is updated on Stripe end, you should be able to add the ACH payment method on Zuora successfully.

Yong · ‎03-21-2019

Why does Payment gateway Stripe ACH gives error "200 - The bank account must be in verified status" when adding new ACH payment method in the customer account page?

Yong · ‎03-14-2019

Hi muhammadalich, I have tested below export zoql and it works. You can convert it to zoql and give it a try. select RatePlanChargeTier.Id, RatePlanChargeTier.Price, Product.SKU, RatePlanCharge.ChargeNumber from RatePlanChargeTier

Yong · ‎03-11-2019

In order to increase capacity and reliability, we will be conducting a network maintenance in our Performance Test (PT1) infrastructure from Wednesday, March 13 2019 10:00PM PDT to Thursday, March 14, 12:00 AM PDT. API and UI functionality will be unavailable for brief periods during the maintenance window. A maintenance status message will be posted upon completion of the activity. Update: The scheduled maintenance completed successfully at 11:32 PM PDT on March 13th.

Yong · ‎03-08-2019

Hi @KishorePradeep There is no known outage at Zuora end that is going on due to this release. Please subscribe Zuora trust page https://trust.zuora.com/ to get the latest update about incident. If the Error Message in your APP still occurs, you can reach out to Zuora support via support.zuora.com or post a new discussion in https://community.zuora.com/t5/Admin-Settings/bd-p/AdminAndSettings. Regards, Yong

Yong · ‎03-07-2019

The first thing to check is the affected user's Billing role. If the user has Change Revenue Recognition Rule and Manage Product Catalog permissions. https://knowledgecenter.zuora.com/CF_Users_and_Administrators/A_Administrator_Settings/User_Roles/d_Billing_Roles#Billing_Permissions After give the above two permissions, if the user still has the issue. Go to the user's platform role and enable Extension Platform Access. Background: Extension Platform role will display in the platform role only if you have enabled a tenant level backend permission called 'Extension Platform' via customer support ticket. It is used by Connect Tax app and Connect Prepaid Drawdown app.

Yong · ‎03-06-2019

Why can't I update Product Rate Plan Charge and get error "You do not have permission to perform this operation."?

Yong · ‎03-03-2019

Hi rdeloach, InvoiceItem.ChargeModel is the supported Invoice merge field, I nvoiceItem_Details.ChargeModel is not. Refrence https://knowledgecenter.zuora.com/CB_Billing/IA_Invoices/Creating_a_Custom_Invoice_Template/Merge_Fields_for_Invoices The invoice templated design related issue is usually complicated. `!Undefined Bookmark` is given by Microsoft Word which indicates some formula is wrong.

Yong · ‎03-03-2019

Hi peterscheen, The Billing ootb feature cannot satisfy this requirement yet. One workaround I can think of is to use the Connect App Workflow to query the charges and check if they exceed the given amount, if yes, trigger an amendment. Reference https://knowledgecenter.zuora.com/CE_Workflow https://knowledgecenter.zuora.com/CE_Collect/C_Setup_and_Administration/BA_Set_Up_the_Workflow_Feature

Yong · ‎03-03-2019

Hi stevenreedkelly, When creating the add product amendment, you can lock in a rate for a subscription by overwriting the default price from the product catalog. But the limitation is the new amendment price will only take effect to the new added product, the price will not take effect on the price of the existing charge. The commonly used method is create an update product amendment to update the price and amount of the existing charge. When a bill run is triggered, most likely it will generate a negative charge to give back the overcharged part to the customer and generate a new positive amount based on the new updated price and amount.

Yong · ‎03-03-2019

Hi JoshPM, Connect app Workflow might be the best option to achieve this. The ootb notification does not have IIA event trigger. You may reach out to you zuora account manager for more information about Workflow. Here are some reference docs https://knowledgecenter.zuora.com/CE_Workflow https://knowledgecenter.zuora.com/CE_Collect/C_Setup_and_Administration/BA_Set_Up_the_Workflow_Feature

Yong · ‎02-21-2019

The permission "Do bill run for multiple accounts" is under Billing role.

Yong · ‎02-18-2019

In order to increase capacity and reliability, we will be conducting a network maintenance in our Performance Test (PT1) infrastructure on Wednesday, February 20 2019 from 8:00PM PST to 10:00PM PST. API and UI functionality will be unavailable for brief periods during the maintenance window. A maintenance status message will be posted upon completion of the activity. Update: The maintenance has completed.

Yong · ‎02-17-2019

From the processId C91C98162652254D, from our backend log, we find the endpoint you tried to use is requestUrl=/rest/v1/orders I think it needs to be /v1/orders/preview

Yong · ‎02-17-2019

Hi Rajeev, One easy way I can think of to achieve this is to create 3 separate remove amendments. The first one with date 03/01, create the first credit memo for Mar. The second one with date 02/01, create the second credit memo for Feb. The last one with date 01/01, create the third credit memo for Jan. Hope that helps somehow.

Yong · ‎02-14-2019

In order to increase capacity and reliability we will be conducting a network maintenance in our Performance Test (PT1) infrastructure on Sunday, February 17 2019 from 8:00PM PST to 10:00PM PST. API and UI functionality will be unavailable for brief periods during the maintenance window. A maintenance status message will be posted upon completion of the activity. Update: We have completed the maintenance.

Yong · ‎02-14-2019

Totally agreed on we should have a full list of error code. 8495C7ADA1E0A34D is used for Zuora Support team troubleshoot. To investigate the issue further, could you raise a support ticket via support.zuora.com with us? After we confirmed the root cause, we can engage in our internal team to update the error code. Thanks.

Yong · ‎02-13-2019

Hi Ridhima, The error code suggests it is a rest call from the first digit 5. For the object digit 810, it is not listed in the error code page indeed. I think it is a POST_PreviewOrder probably. endpoint `https://rest.zuora.com/v1/orders/preview` Reference https://www.zuora.com/developer/api-reference/#operation/POST_PreviewOrder It could be caused by the type of "renewalTerms" is array, the correct request format is like: [{ "period":"1", "periodType":"Year" }] Could you help provide the endpoint, request and response in json format so we can further investigate at our end? Thanks.

Happy Business Starts Here