About Yong

Yong

The issue tracked in TOK-815 has been fixed in R270. Reference https://knowledgecenter.zuora.com/Zuora_Release_Notes/A_Zuora_Billing_Release_Notes/21_2020_New_Features/35_Zuora_Billing_Release_270%2C_March_2020

Yong · ‎02-27-2020

Credit Memos are used to correct charge mistakes on invoices and manage the balance on a particular invoice or customer account. In this video, I’ll go over the 3 ways to generate Credit Memos. Feel free to ask your questions below. Reference Create Credit and Debit Memos Rules for Generating Invoices and Credit Memos Invoice Settlement Migration Checklist and Guide Known Limitations in Invoice Settlement

Yong · ‎02-17-2020

The scheduled maintenance has completed.

Yong · ‎02-17-2020

The scheduled maintenance has started.

Yong · ‎02-04-2020

We plan to perform a 360+ Sync service maintenance operation in our US, EU, and NA PRODUCTION Environment on February 17 between 9:00 PM - 9:30 PM PST. This maintenance is necessary as we need to upgrade our 360+ Sync database certificates. During the maintenance window, 360+ Sync service will experience disruption as well as sync latency for approximately 10 minutes. Any Zuora objects modified during this time will be synced automatically after the 360+ Sync service is resumed. The scheduled maintenance has completed.

Yong · ‎01-17-2020

Hi @sramineni, this community solutions article will help probably. https://community.zuora.com/t5/Billing-Payments/How-to-only-credit-back-the-invoice-taxation-item/td-p/29464

Yong · ‎01-17-2020

You're right @Ajayas4 If this is a renewal subscription, termStartDate is different from the subscription start date. Reference https://www.zuora.com/developer/api-reference/#operation/PUT_Subscription

Yong · ‎01-12-2020

Hi @Ajayas4, TermStartDate is only required if the Type field is set to TermsAndConditions, I think that is why you must pass the field in your case. https://www.zuora.com/developer/api-reference/#operation/Action_POSTamend

Yong · ‎01-12-2020

Hi @achava02 Hope this article helps "Bulk data extraction from Zuora using AQuA". https://knowledgecenter.zuora.com/Developer_Platform/API/AB_Aggregate_Query_API/Bulk_data__extraction_from_Zuora_using_AQuA Feel free to let me know if you have further questions.

Yong · ‎12-29-2019

How about something like this? AmendmentType !=null

Yong · ‎12-17-2019

Hi @daquino, I'm sorry to hear Termiate Bill Run does not work for that specific bill run. Could you open a ticket via support portal https://support.zuora.com and our support team can assist you terminiate that bill run and update the bill run status from our backend. Reference https://knowledgecenter.zuora.com/CB_Billing/J_Billing_Operations/G_Bill_Runs/Terminate_bill_runs

Yong · ‎12-12-2019

I think you can get Bill Run and Invoice together via fields Source and Source ID from Invoice object. Feel free to try it and let me know if that works. Thanks.

Yong · ‎12-11-2019

Issue - Why the Fixed Amount Discount is prorated if "Fixed Period after the Charge is triggered" is used The sample subscription activation date is 02/28/2019. It has two charges. Charge 1 Recurring charge Flat Fee Charge 2 Discount-Fixed Amount End Date: Fixed Period after the Charge is triggered - 3 Billing Periods Billing Day: Default from Customer Account(Customer Account Billing Cycle day is using End of Month) The discount amount in the generated invoice service period 04/30/2019 is -9.03, the expected result is 10.00. In the above case, the fixed amount discount charge end date is 05/28/2019, not 05/30/2019, plus the discount charge trigger day is Default from Customer Account. That is the reason why it is prorated in the third billing period. Reference https://knowledgecenter.zuora.com/CB_Billing/WA_Dates_in_Zuora/D_Product_Catalog_Dates%3A_Product_Rate_Plan_Charge_Date_Attributes The resolution to the issue is set the discount charge Billing Day to Charge Trigger Day. It aligns with the recurring charge Flat Fee and there is no proration issue anymore. The generated invoice will look like this.

Yong · ‎12-11-2019

Issue - Why preview on subscription shows Tax, but upon actual bill run no tax is applied Tax calculation result is managed on the 3rd party tax engine based on the api request sent from Zuora to the tax engine. Take Avalara for example, SalesOrder and SalesInvoice are different. Reference https://www.avalara.com/us/en/blog/2016/11/types-of-transactions.html On Zuora end, SalesInvoice will be used when posting an invoice. For other cases, such as subscription preview, SalesOrder will be used. That is the reason why preview on subscription shows Tax, but upon actual bill run no tax is applied. If you have a concern about the tax calculation result returned from 3rd party tax engine, you can contact Avalara Support for further clarification. https://help.avalara.com/Contact_Avalara

Yong · ‎12-09-2019

Hi @kbarins Thanks for your feedback. You are correct, when tax inclusive is used when you are trying to create an IIA and Avalara integration is used, this 0.01 rounding issue could happen because IIA "taxInclued = false" is hardcoded in zuora application. The workaround is turn off "calculate IIA tax with Avalara" temporarily. Our product roadmap is using Invoice Settlement feature to replace IIA, so our apologies that we cannot provide an ETA of the IIA+Avalara integration fix/improvement ETA yet. Reference https://knowledgecenter.zuora.com/CB_Billing/Invoice_Settlement Invoice Settlement is in limited availability status, if you are interested, please reach out to your Zuora account manager for more information. Please also note Invoice in Tax Inclusive Mode has limitation when created from invoices. https://knowledgecenter.zuora.com/CB_Billing/Invoice_Settlement/B_Credit_and_Debit_Memos/Tax_Calculation_for_Credit_and_Debit_Memos The workaround is much easier. You can check https://community.zuora.com/t5/Billing-Payments/How-to-only-credit-back-the-invoice-taxation-item/m-p/29474 Feel free to let us know if you have further concerns.

Yong · ‎12-09-2019

Hello @Madalina One workaround I can think of is adding Usage Summary Fields in the invoice template so the end customer has more visibility of the billed usage in the second invoice https://knowledgecenter.zuora.com/CB_Billing/IA_Invoices/Creating_a_Custom_Invoice_Template/Merge_Fields_for_Invoices#Usage_Summary_Fields One more suggestion is you can bring your concern to your zuora account manager and they will help you seek further assistance from zuora Subject Matter Expert in invoice template domain.

Yong · ‎12-09-2019

I think Using Developer Tools is a better choice as it has more detailed logs and output file to let you know which subscription update custom filed request failed and why. Reference https://knowledgecenter.zuora.com/Marketplace/Market_Apps/Developer_Tools https://knowledgecenter.zuora.com/Marketplace/Market_Apps/Developer_Tools/Configure_API_Loader_for_Specific_Zuora_Objects

Yong · ‎10-24-2019

@jv_6 , here is the Release 260 note. https://knowledgecenter.zuora.com/A_Zuora_Release_Notes/A_Zuora_Billing_Release_Notes/22_2019_New_Features/16_Zuora_Billing_Release_260%2C_October_2019 If you have further questions, please raise a support ticket with us at support.zuora.com

Yong · ‎10-14-2019

Here is what will be validated after a payment run is triggered. Step 1. Payment run collects documents (invoices and debit memos). Account’s Auto-Pay flag is enabled or not. Document’s Auto-Pay flag is enabled or not. Document is not locked by other transactions. (For example, in a very rare case, if the payment run is trying to apply a payment to a specific invoice and you triggered another apply payment API call at that time, the payment run could skip the payment creation because it has been paid off by the api created payment already. ) Documents balance is not zero. Documents Due date <= payment run target date. Step 2. After payment run collects the documents, here are the payment validations. All the above conditions again. This time is at payment level. Account’s payment method is active. Account’s gateway is active. When a payment run is triggered, if any condition from the above is not met, that speific document will not be picked up by the payment run and no payment will be generatred. Reference https://knowledgecenter.zuora.com/CB_Billing/K_Payment_Operations/CA_Payment_Runs/A_Introduction_to_Payment_Runs

Yong · ‎10-13-2019

The issue will be fixed in Release 259.

Yong · ‎10-11-2019

When previewing a subscription, you might get a message "The tax calculation call to Zuora Connect returned the following error: unknown error." Root Cause: The subscription preview must finish within 120 seconds. If this is a very large subscription and the preview periods is long, the number of line items will be high. When tax app is used to calculate the tax, zuora will send the tax calculation request to tax vendor. Tax vendor might not send the response in time and cause the subscription preview issue. https://knowledgecenter.zuora.com/Marketplace/Market_Apps/Tax A single tax calculation request sent to a tax connector app can have a maximum of 15,000 taxable items. If a tax calculation request contains more than 15,000 taxable items and is sent to a tax connector app, the request will fail and an error message will be returned. https://knowledgecenter.zuora.com/Zuora_Central/Billing_and_Payments/J_Billing_Operations/L_Taxes/Connect_Tax_Engines Workarounds: 1. Shorten the preview billing periods. By default, it is 3 billing periods. That will make the number of line items in the request smaller too. 2. Separate the big subscriptions into smaller ones, so when preview, the number of line items in the preview request will be much smaller.

Yong · ‎10-10-2019

Hi @MaggieL Here is the Zuora for Salesforce (Quotes) release note https://knowledgecenter.zuora.com/A_Zuora_Release_Notes/BA_Zuora_for_Salesforce_Quotes_Release#Maintenance_Release_9.18_(Release_Date:_2019-09-23) https://community.zuora.com/t5/Release-Notifications/Zuora-for-Salesforce-Release-Quotes-9-18-Push-to-all-9-17-Orgs/ba-p/30637 Here is the Zuora billing release note homepage https://knowledgecenter.zuora.com/A_Zuora_Release_Notes Here is the Zuora billing R258 release note https://knowledgecenter.zuora.com/A_Zuora_Release_Notes/A_Zuora_Billing_Release_Notes/22_2019_New_Features/18_Zuora_Billing_Release_258%2C_October_2019

Yong · ‎10-07-2019

Known Issue In the invoice or payment list page, when clicking the search button again and again very quickly, for example, 4 or 5 times per second, the result might not be expected. Sometimes the full list displays. The expected result is only INV00000279 is on the list. Status This issue has been identified as a defect. Reference Number INV-1782 ETA of the Fix Currently, we cannot provide the EAT of the fix. Workaround When searching the invoice or payment, do not click the search button too quickly.

Yong · ‎09-27-2019

Why does the number of invoices created not match that is created by bill run? For example, BR-00000722 generated 3 invoices, but on the list, there are only 2 invoices. It happened because an invoice was canceled and deleted. The number of invoices won't change upon such deletion, because that number reflects the actual output of this bill run. When the bill run completed, if the Number of Invoices Created is 3, then it will be always 3.

Yong · ‎09-20-2019

Our SSL Cert deployment in NA Production completed successfully.

Yong · ‎09-09-2019

Hope this document will help Support Multiple Languages in Invoice Template

Yong · ‎09-09-2019

Please go to Zuora support portal support.zuora.com (suggested method), or send an email to support@zuora.com to create a support ticket.

Yong · ‎08-26-2019

Tax amount calculated and the rate used is included in the response from Avalara. In the Zuora to Avalara request, there are no tax amount and tax rate. We have two avalara integration solutions: https://knowledgecenter.zuora.com/CB_Billing/J_Billing_Operations/L_Taxes/B_Avalara_Integration/A_Configure_Integration_with_Avalara https://knowledgecenter.zuora.com/CB_Billing/J_Billing_Operations/L_Taxes/Connect_Tax_Engines The provided sample is using the first solution. The second solution is much flexible compared to the first one.

Yong · ‎08-25-2019

Hi @kbarins When Avalara integration is used, Zuora uses api call to get the tax information from Avalara. Here is a sample request to Avalara. The rounding algorithm is controlled by Avalara. The same logic is used for both INV and IIA transactions. { "addresses":[ { "country":"", "zipCode":"", "city":"", "address2":"", "address1":"", "id":"TaxOriginalAddressCode", "state":"" }, { "country":"US", "zipCode":"30305", "ShippingCity_c":"Foster", "ShippingStatec":"RI", "ShippingPostalCodec":"02825", "city":"Atlanta", "address2":"", "ShippingAddress1c":"xxxx Road", "ServiceCountryc":"United States", "address1":"xxxx Road", "county":"", "ServicePostalCodec":"94403", "taxRegion":"", "ServiceAddress1c":"xxxx Road", "ServiceCityc":"San Mateo", "ShippingCountryc":"United States", "ServiceStatec":"CA", "id":"2c92c0f9652ad8f901653594efb3xxxx", "state":"Georgia" } ], "subscriptions":[ { "id":"2c92c0f86524468701655f00ae30xxxx" } ], "documents":[ { "SerialNumberc":"", "id":"2c92c085652a7d4801655f018707xxxx" } ], "documentOwners":[ { "id":"2c92c0f9652ad8f901653594efafxxxx" } ], "productRatePlanCharges":[ { "id":"2c92c0f8644618e8016461b24b96xxxx" }, { "id":"2c92c0f864b6edb60164b8c52397xxxx" } ], "invoice":{ "SerialNumberc":"", "invoiceItems":[ { "productRatePlanChargeId":"2c92c0f8644618e8016461b24b96xxxx", "taxExemptStatus":0, "originalAddressId":"TaxOriginalAddressCode", "taxExemptCertificateType":"", "taxCompanyCode":"test", "amount":"1899", "taxExemptCertificateID":"", "quantity":"1", "vatId":"", "discountAmount":"0", "subscriptionRatePlanChargeId":"2c92c0f86524468701655f00ae48xxxx", "taxExemptEntityUseCode":"", "taxCode":"P0000000", "taxCalculationOwnerOption":0, "taxDate":"2018-08-21", "subscriptionOwnerId":"2c92c0f9652ad8f901653594efafxxxx", "taxExemptIssuingJurisdiction":"", "documentOwnerId":"2c92c0f9652ad8f901653594efafxxxx", "taxMode":0, "subscriptionName":"A-S00000033", "documentId":"2c92c085652a7d4801655f018707xxxx", "id":"2c92c085652a7d4801655f01870fxxxx", "subscriptionId":"2c92c0f86524468701655f00ae30xxxx", "destinationAddressId":"2c92c0f9652ad8f901653594efb3xxxx" }, { "productRatePlanChargeId":"2c92c0f864b6edb60164b8c52397xxxx", "taxExemptStatus":0, "originalAddressId":"TaxOriginalAddressCode", "taxExemptCertificateType":"", "taxCompanyCode":"test", "amount":"1000", "taxExemptCertificateID":"", "quantity":"1", "vatId":"", "discountAmount":"0", "subscriptionRatePlanChargeId":"2c92c0f86524468701655f00ae48xxxx", "taxExemptEntityUseCode":"", "taxCode":"FR000000", "taxCalculationOwnerOption":0, "taxDate":"2018-08-21", "subscriptionOwnerId":"2c92c0f9652ad8f901653594efafxxxx", "taxExemptIssuingJurisdiction":"", "documentOwnerId":"2c92c0f9652ad8f901653594efafxxxx", "taxMode":0, "subscriptionName":"A-S00000033", "documentId":"2c92c085652a7d4801655f018707xxxx", "id":"2c92c085652a7d4801655f018710xxxx", "subscriptionId":"2c92c0f86524468701655f00ae30xxxx", "destinationAddressId":"2c92c0f9652ad8f901653594efb3xxxx" } ], "invoiceNumber":"INV00000032", "id":"2c92c085652a7d4801655f018707xxxx", "invoiceDate":"2018-08-21" }, "subscriptionRatePlanCharges":[ { "ContactTaxTypec":"ShippingAddress", "id":"2c92c0f86524468701655f00ae48xxxx" }, { "ContactTaxType_c":"ServiceAddress", "id":"2c92c0f86524468701655f00ae48xxxx" } ], "version":"2.0", "account":{ "crmAccountId":"", "currency":"USD", "id":"2c92c0f9652ad8f901653594efafxxxx", "accountNumber":"A00000001" }, "subscriptionOwners":[ { "crmAccountId":"", "currency":"USD", "id":"2c92c0f9652ad8f901653594efafxxxx", "accountNumber":"A00000001" } ] }

Yong · ‎08-09-2019

@rferriz Could you create a customer support ticket on support portal support.zuora.com and so we can assist you to troubleshoot the Integration Pages 2.0 issue?

Happy Business Starts Here