About Aberna

Aberna

Hi , Please be informed for electronic payments the time frame for Refund is controlled by the payment gateway and not at Zuora. Typically, a payment can be refunded for up to 90 days, but every gateway is different and some gateways do not allow refunds after 30 days. When processing a refund for electronic payments, Zuora will attempt the refund at the gateway. If the refund is allowed by the gateway, the refund will be processed. However, if the time period in which a refund can performed has passed, then the gateway might return an error. The above information can be found in the below KC article as well. https://knowledgecenter.zuora.com/Billing/Billing_and_Payments/K_Payment_Operations/Refunds/Creating_Refunds

Aberna

Question: How would I run either a Report or a Data Query to allow me to see all the customer's emails, dates, and times that they have logged into the Subscriber Portal on a Daily basis? Solution: You could extract the data from the Subscriber portal dashboard in User logs to view the login details.

Aberna

Problem: "Issue Base Calendar" is not recognizing Revenue for a few subscriptions as expected. Reason: invoice line items for this subscription are created for the period 05/02/2020 to 05/31/2020. The Calendar setup for this rate plan charge is as shown below. Based on this the revenue has to be distributed on the below-given dates as 05/02/2020 does not fall on the 1st it is not distributed. As a workaround, please use the mass updater tool to distribute the revenue which is having this issue. https://knowledgecenter.zuora.com/CC_Finance/Mass_Updater

Aberna

Issue: For Credit Memo's when Revenue is Recognized, the amount for each full is not the same as recognized in the corresponding Invoices. Scenario: Subscription started 2020-01-15 Invoiced for a Year: 2020-01-15 – 2021-01-14 Subscription is canceled in April (2020-04-09) with a cancellation date of 2020-03-05 Subscription billed 2020-04-09 and a Credit Memo was generated for the period 2020-03-05 – 2021-01-14 Question: Why is the amount credited in the Credit Memo revenue schedule higher for the period 2020-05 to 2020-10 than the Invoice revenue schedule? This would mean that even though the subscription is canceled we will have net revenue schedule transactions in the General ledger for these periods. Two revenue Schedules created: On Invoice, INV00026*** On Credit Memo, CM000031**, as below: Reason: The recognition for Credit Memo will be based on the CM value and revenue recognition rules. It does not depend on the invoice revenue distribution. Please do note: There are a few changes in the current design of Revenue Recognition for Credit Memo and is being handled in FNR-10030. I will be updating this post with the changes once it is in place.

Aberna

Problem: Subscription: A-S01271822 was created on 03/10/2020 12:22:41 SGT Contract Effective Date: 04/23/2020 Service Activation Date: 04/23/2020 Customer Acceptance Date: 04/23/2020 Amendment A-AM01153331, to update Term - from Evergreen to Termed, was done on 03/17/2020 14:42:00 SGT Contract Effective Date: 04/23/2020 Service Activation Date: 04/23/2020 Customer Acceptance Date: 04/23/2020 A-S01271822 Version 2) was created after the amendment. Bill run for the subscription done on 04/06/2020 17:45:52 SGT (invoice INV07114461) Revenue Schedules were created for Version1, We are expecting Revenue Schedules to be created for Version2 as this is the active subscription version. Reason: When a Revenue gets created it is based on the charge number in the subscription, Your revenue schedule will always point to the first version of the charge even though there is multiple version of the charge created the revenue schedule will always point to the very first version. For Eg you could see there are different amendments created and multiple invoices for the same charge, but all the revenue schedule points to the first version of the charge's subscription.

Aberna

Question: Internal Error when sending a callout notification in Workflow. Request https://rest.apisandbox.zuora.com/v1/subscriptions { "accountKey": "XXX", "autoRenew": true, "contractEffectiveDate": "2020-04-06", "initialTerm": null, "initialTermPeriodType": "Month", "renewalTerm": null, "renewalTermPeriodType": "Month", "subscribeToRatePlans": [ { "chargeOverrides": [ { "billingTiming": "IN_ADVANCE", "listPriceBase": "Per_Billing_Period", "quantity": "0.000000000", "triggerDate": null, "triggerEvent": null, "productRatePlanChargeId": "XXX", "billCycleType": "ChargeTriggerDay", "billCycleDay": null, "billingPeriod": "Month", "billingPeriodAlignment": "AlignToCharge", "upToPeriods": null, "endDateCondition": "Subscription_End", "upToPeriodsType": null, "specificBillingPeriod": null, "specificEndDate": null, "weeklyBillCycleDay": null, "description": "Shadow Charge", "ChargeShadowId__c": "600" } ], "productRatePlanId": "XXX" }, { "chargeOverrides": [ { "quantity": "0.000000000", "triggerDate": null, "triggerEvent": null, "productRatePlanChargeId": "XXX", "weeklyBillCycleDay": null, "description": "Shadow Charge", "ChargeShadowId__c": "601" } ], "productRatePlanId": "XXXXX" } ], "termType": "EVERGREEN", "invoiceOwnerAccountKey": "XXX" } Below is the error message in the response body. { "success": false, "processId": "BB2815D737831C75", "reasons": [ { "code": 53000000, "message": "Oops, internal error occurred, please try it again, and if it still doesn't work, please contact Zuora support." } ] } Reason for failure: If you are giving USD as yo ur Trigger Event, then there should be a date given in the trigger date. Solution: If you want the system to use the contract effective date as the trigger date, please pass "UCA" as the trigger event.

Aberna

The scheduled maintenance in US Production environment has been finished. All systems are operational.

Aberna

The scheduled maintenance has started as per the schedule and in progress.

Aberna · ‎05-03-2020

Problem: In the revenue schedule data source of a Revenue Schedule , the subscription ID is of the previous version of the subscription and not the version for which the invoice was generated. Reason: This is by design, When a Revenue gets created it is based on the charge number, Your revenue schedule will always point to the first version of the charge even though there is multiple version of the charge created. Eg: Invoice is created for the correct subscription version (version 2) But the Revenue schedule data source points to the Version 1 of subscription Version 1 of the Charge, Version 1 of the subscription Version 2 of the subscription. By Design, the Revenue schedule will always point to the subscription version which has the first version of the charge.

Aberna · ‎05-02-2020

Problem: Trying to get the rate plans info via the rest api endpoint /subscriptions/account The scenario is the following: 1- I added a new product to the subscription via amendment with contract effective date today (04.03.2020) 2- Then, I update the pricing charge via amendment with contract effective date 06.24.2020. 3- And then, I remove the Add via amendment with contract effective date 04.24.2020. In the response of the subscriptions/account, I am getting the following: "ratePlans" : [ { "id" : "2c92c0f87129861601713089a2e1217a", "lastChangeType" : "Remove", "acceptanceDateC" : null, "ratePlanCharges" : [ { ……... "segment" : 2, "effectiveStartDate" : "2020-06-24", "effectiveEndDate" : "2020-06-24", "processedThroughDate" : null, "chargedThroughDate" : null, "done" : false, "triggerDate" : null, "triggerEvent" : "ContractEffective", "endDateCondition" : "Subscription_End", "acceptanceDateC" : null } ] }, { Although, the lastChangeType is 'remove', the effectiveEndDate and effectiveStartDate are not right. "effectiveStartDate" : "2020-06-24", "effectiveEndDate" : "2020-06-24", It should be "2020-04-24", which is the contract effective end date of the removal Reason: User is using the below API call. https://www.zuora.com/developer/api-reference/#operation/GET_SubscriptionsByAccount This call retrieves all subscriptions associated with the specified account. Zuora only returns the latest version of the subscriptions. Subscription data is returned in reverse chronological order based on updatedDate . In the above-given example : Add Product Amendment version is fetched + latest date (06.24.2020) is returned in the API call.

Aberna · ‎05-02-2020

Problem: In ZOQL export on RatePlanChargeTier Object there is no starting and Units populated. Solution: If you are using Overage charge model in your subscription then there will not be any starting and Ending Units. There will not be any Starting and Ending units while we create the Product Rate plan for Overage charge model. If you have used any of the below charge models then there will be startng unit and Ending unit. Volume, Tiered, Tiered with Overage. Workaround: Use IncludedUnits as Ending Unit and Starting unit as 0 to achieve the desired result. Eg ZOQL query: select Id, StartingUnit, IncludedUnits as EndingUnit from RatePlanChargeTier where RatePlanCharge.ChargeModel='Overage Pricing' and Subscription.Status='Active' and IncludedUnits is not null

Aberna · ‎05-02-2020

Question: Is it possible to gather subscription's pricing for selected accounts when a subscription has an amendment with a future date?The price that we receive is the one for the future date amendment instead of the current one. Solution: In order to achieve this, make use of the previous subscription ID field in the subscription object. This has to be extracted in three steps as shown above 1. Use Export task to extract all the subscriptions, make sure to include previous subscription id. Condition: Status = 'Active' 2. Iterate over the extracted export. 3. Use query task based on the previous subscription ID and extract the required fields. Id= '{{Data.Subscription.PreviousSubscriptionId}}' This will fetch the details of the previous subscription version.

Aberna · ‎03-31-2020

Question: To pull invoice data and then update (data from the custom field) to the most recent version of a subscription and not on the subscription which is mapped to the invoice. Solution: In order to achieve this, you have to include one more Retrieve task between the iterate (after Export of Invoices) and the update as shown below. 1. Retrieve task Select the subscription ID and in conditions give the below condition. Status='Active' Please give a different payload name as highlighted in the 2nd screenshot to avoid confusion. 2.For the Update task: Select the Data.sub1 in the update task as shown below. On doing the above the current version of the subscription will be updated rather than the subscription version which is mapped to the invoice.

Aberna · ‎01-30-2020

Question: The CSV file generated by the 'Export End-Customer Subscription Details' activity has the default Zuora column names like 'Account.PlumeCustomerID__c'. We will have to send this export CSV as email attachment. Is there any way to change the column names to something like 'Customer ID' before sending the email? Solution: Use Data query instead of Export in the workflow. Data Query allows you to use alias name while extraction.

Aberna · ‎01-30-2020

Question: Invoice being posted when it shouldn't be. Reason: When there is a Draft invoice that is not posted, when a BR runs next this Invoice will be picked up in it and the settings in the second BR will be taken into consideration. Below is the history of what has happened on those invoices. 1.BR-00021305 executed on 09/25/2019 with Auto post set to No, making the generated Invoice -INV01266078 be in Draft status. 2. As this invoice was in Draft status and before it was posted, when the BR BR-00021979 which has Auto-post set to Yes, picked up the Invoice INV01266078 and Auto posted it. Though both the BR's are run by 2 different users this scenario will take place. In such cases you would find 2 BR's associated to this invoice as shown below.

Aberna · ‎11-26-2019

Question : For a subscription( A-S01414961) that the Zuora TCV is showing an amount higher than what's been fully billed on the subscription. Attached below is a TCV and TCB export for the mentioned subscription. Everything has been billed on the subscription, so I would expect TCV and TCB to match (TCV is higher by roughly $8k). Do we know why this is? Answer: By design TCV and TCB values might not be the same, the same could be found in the below article. https://knowledgecenter.zuora.com/BC_Subscription_Management/Orders/AA_Overview_of_Orders/Key_Metrics_for_Orders#Order_Tcv How TCB and TCV are calculated? Charge # C-01484722 Version 2 Total charge Value= 10.07*17545 MRR value =176678.15/12=14723.179166667 Below is how the system calculates TCV The charge is trigger on 2/21/2019, its start date is 02/21/2016 and end date is 01/01/2020 1. interval months: 10 months. 2. Partial Date = Start Date + Interval Months = 12/21/2019 3. Interval Date = End Date - Partial Date = 01/01/2020 - 12/21/2019 = 11 days 4. Base Days = (Start Date + Interval Months + one month) - Partial Date = (21/02/2019 +10+1)-12/01/2020 = (21/01/2020-21/12/2019)=31 days 5. TCV = MRR x ( interval Months + (Interval Date / Base Days)) = MRR * (10 + 11/31) TCV=14723.179166667 *(10+(11/31))=152456.145564516 Below is how the system calculates TCB Total_amount = Price_per_month * (Number_of_full_months +(Prorated_days/Actual_number_of_days_of_the_prorated_month) ) TCB=MRR *(10+(8/28)) =14723.179166667*(10+(8/28)) =151438.41

Aberna · ‎09-28-2019

Question : In the Knowledge center article , proration for January is calculated as January proration: 17 days * $100/31 days = $54.74 but 17*100/31 = 54.83 how is this value arrived at? https://knowledgecenter.zuora.com/CC_Finance/D_Finance_Settings/Manage_Revenue_Rules/Components_and_Configuration_Options Solution: Rounding Rule of the revenue schedule has to be checked first. Here the rounding is considered to be "Round Trailing". Use case: Service period: January 15 to April 14 of the same year Invoice item amount: $300 Proration is calculated as follows: Number of prorated days: 17 + 14 = 31 days (January and April) January proration: 17 days * $100/31 days = $54.74 April proration: 14 days * $100/31 days = $45.26 January calculation: One prorated day: 100/31= 3.22580645. Round to two decimal places = 3.22 remaining value: 0.00580645 Calculation for 17 Days: 3.22*17 = 54.74 , Rounding value for 17 Days: 0.00580645*17 = 0.09870965 April Calculation: One prorated day for April: 100/31= 3.22580645 Round to two decimal places = 3.22 , remaining value: 0.00580645 Calculation for 14 days: 3.22*14 = 45.08, Rounding value for 14 days: 0.00580645*14 = 0.0812903 Remaining rounding values from January and April then get added to April's amount: 45.08 + 0.09870965 + 0.0812903 = 45.26.

Aberna · ‎09-02-2019

This video shows how to create Accounting Period using API loader in bulk.

Aberna · ‎08-31-2019

Question: In my workflow I want to query two accounts (using Query activities) and I want both account objects to be accessible to me throughout the workflow. However, after the 2nd query runs it overwrites the first account object. How to achieve the above? Solution: There is an option in Workflow called "Payload" which can be used in Query, Using which we could avoid overwriting the account object. Please find below steps to achieve the same. 1. In the Search for the account for the same email id give Payload Alternative Placement (which could be any name) 2. In the Iterate Through All Accounts select the alternate name given in the above step 3. In Update the Account Number, use the alternate name for Updating as shown below. On doing the above steps , we are capturing the second account number in the Payload field thus avoiding the Overwriting.

Aberna · ‎08-05-2019

This tutorial will walk you through the steps in sending email notifications from Workflow app.

Aberna · ‎08-05-2019

This tutorial will walk you through the steps in creating an Amendment using workflow app.

Aberna · ‎08-05-2019

This tutorial will walk you through the steps in creating an Amendment using API loader functionality available as part of Developer Tools.

Aberna · ‎07-24-2019

Question :Requirement is to schedule a workflow which will extend the term by 1 more year for all termed subscriptions which have reached their term end date. However, there is no 'Terms and Conditions' option in the Amendment activity Answer: Terms and Conditions Amendment can be created in Workflow using CRUD functionality workflow provides. Step 1: On start create a CRUD function - > Create function. 2. Object should be Amendment as shown below, Give all the mandatory fields that are required for creating an Amendment. Which are the fields that are Mandatory /Optional can be found in below KC article. https://knowledgecenter.zuora.com/DC_Developers/G_SOAP_API/E1_SOAP_API_Object_Reference/Amendment

Aberna · ‎06-30-2019

In the above issue there were two products 1st product Rate plan with contract effective date as 11/28/2017 2nd Product Rate plan with contract effective date as 11/17/2018 In order to cancel an subscription for an orders enabled tenant follow the steps in given order. 1.Perform Remove product amendment for the product which has contract effective date as 11/17/2019. 2.Create an cancellation amendment for the Product which has contract effective date as 11/28/2017. On performing the steps given in the above order there will not be any invoices or credits created for the subscription.

Aberna · ‎06-30-2019

Question : There is a subscription in our environment (A-S00006521) with two products. Both products are Evergreen and are recurring. The first product has a Contract Effective/Service Activation Date of 11/28/2017, while the second product has a Contract Effective/Service Activation Date of 11/17/2018. We would like to cancel both subscriptions without generating any invoices or credits.

Aberna · ‎01-22-2019

There is a T9 feature " Override Accounting Code When Creating Invoice Item Adjustment via SOAP API" this needs to be enabled for the tenant to ensure Accounting code gets updated.

Aberna · ‎01-22-2019

I have created a Zuora connect workflow job that is write-off invoices of cancelled customers. In the Recognized Revenue Account field, I have entered "Bad Debt" and can see that the Soap call passes that account along in the create InvoiceItemAdjustment request. However, the recognized revenue accounting code is not being updated and is set to the default on the invoice item. What am I doing wrong?

Aberna · ‎01-22-2019

This can be achieved through Workflow app by following the below steps. 1.Create Custom Field in Product Rate plan charge. Billing Settings->Manage Custom Fields->Product Rate Plan Charge Fields->Add new Field 2.Launch the workflow app in your tenant and design as per the below layout. Prerequisite Before starting clear workflow cache for the new custom field created as part of the Product rate plan charge. Create Workflow Click on +Add->+Blank Workflow Provide Workflow Name & Description and create. Step 1: Export: 2.Iterate 3.Update 4.Email Notification Configure the email and Run schedule, Based on which the workflow will be triggered and email will be sent to the mail id established. This is how the final Layout will look like

Aberna · ‎01-22-2019

Our Enterprise Data team needs to know when a new Product Rate Plan Charge or PRPC Tier is created or updated in our Zuora catalog and I am trying to determine the best way to set up a notification to alert them. Ideas so far: Problem : 1) Set up a recurring report to send to distribution list when PRPC Created Date = TODAY. Issue: I would only want this report to be sent if there are actually records that meet this criteria and would not want to send a blank report. This does not seem to be possible, I found a Community Post (ABILITY TO SEND SCHEDULED REPORT BY MAIL ONLY IF THESE ARE NOT EMPTY) where another user had the same issue. 2) Set up a custom notification to email mentioned team when a new PRPC is created Issue: PRPC does not appear to be an available object to set up a custom notification for. Any thoughts on how we can achieve this? Thanks.

Aberna · ‎12-26-2018

Approach : Verify the currency configuration for the tenat. No of Decimal Places Rounding Mode Billing Settings->Customize Currencies In Zuora, Tax is calculated for each line individually. Based on the currency configuration the Tax amount is rounded off and totalled. Due to this there will be a tax rounding difference in the invoice total. More information on Rounding and precision https://knowledgecenter.zuora.com/CB_Billing/TB_Rounding_and_Precision

Happy Business Starts Here