zuora

How do I synchronize custom fields to Salesforce from Zuora without code?

How do I synchronize custom fields to Salesforce from Zuora without code?

This article explains how to synchronize custom fields created in the Zuora application to Salesforce. 

Synchronize a Custom Field

Zuora 360 supports fields of String, Date, and Picklist types in the Product Catalog sync and the Accounts and Related Objects sync. 

Custom fields are synchronized when the Zuora objects synced to Salesforce. See Sync Objects Mappings for the list of Zuora objects synchronized to Salesforce. 

To synchronize a custom field:

  • In the Zuora application, navigate to Settings > Billing > Manage Custom Fields, and define the custom field as described in Manage Custom Fields.
  • Define the corresponding field in Salesforce with the same API name. You must create the field in Salesforce before you can sync Zuora custom field data. You can synchronize custom fields up to 255 characters long. For the picklist type custom fields, each picklist option can be up to 255 characters long.
    • For example: Create a subscription custom field in Salesforce by going to Setup > App Setup > Create > Objects > Subscription > New Custom Fields & Relationships. Create the same custom field as you created in Zuora using the same field attributes, such as picklist, values, API Name.
  • Add the custom field on the Salesforce related list.
    • For example, if you are adding a subscription custom field, go to Setup > App Setup > Customize > Accounts > Page Layouts > Account Z-Force 360 Layout v## (latest version) > Edit the Related List for Subscriptions and add the custom field you created in the prior step.
  • The sync process will automatically sync the custom fields to Salesforce. Your Zuora 360 sync will execute according to your sync settings in Zuora. See Synchronize Data from Zuora about setting sync options. In the Field Name field, you can enter a value, for example, MyCompanySKU, and Salesforce will insert the required __c custom field suffix automatically.
  • After the sync is completed, refresh the Salesforce account page. The custom fields will now show the value that came from Zuora.

 

Zuora NetSuite Integration - An Overview

Overview

The Zuora NetSuite Integration (aka Connector) is an optional solution that leverages the core capabilities of both the Zuora and NetSuite applications. Zuora manages complex subscriptions and NetSuite is a hosted General Ledger (GL) System.

Features

Zuora NetSuite Connector combines Zuora's subscription billing capabilities with NetSuite's ERP/Financials solution with bi-directional integration across every core application module to seamlessly combine the two applications.

This solution is a pre-defined, out-of-the-box integration that synchronizes transactions between the two applications. Zuora provides NetSuite Connector customers with an integration console in the Zuora Billing user interface which is used to set up the integration, control and monitor the synchronization of data, and view any error or success logs from the synchronization.

Integrating Zuora with NetSuite allows you to use Zuora's applications to:

  • Manage complex pricing and packaging models
  • Align charges with existing subscriptions
  • Consolidate billing
  • Streamline renewal patterns

Advanced Pricing Configuration

Configure any type of subscription pricing, packages and bundles (including one-time, recurring, usage and metering charges, volume tier pricing, and overage pricing) to link Zuora's Product Catalog and NetSuite's Item. For example, simple or complex subscription pricing can be configured in Zuora, such as a cellular phone plan or a data plan with usage, and synchronized to NetSuite's product catalog (e.g. items in the same hierarchical structure).

Customer Account Mirroring

Synchronize Customer Accounts, Billing Accounts, and any customer account hierarchies to provide a single view of all customers whether the data is in Zuora or NetSuite. For example, an address change in Zuora is synchronized with the corresponding account address in NetSuite (and synchronized from NetSuite to Zuora).

Bi-Directional Payment Operations

Manage the Invoice to Cash process in either Zuora or NetSuite with the two-way integration of Zuora Payment Operations with NetSuite's Accounts Receivable module. For example, a customer is issued a refund in Zuora when a subscription is cancelled and the refund is applied to the appropriate payment in NetSuite.

Revenue Recognition Integration

Manage revenue recognition by mapping Zuora's subscription details, including revenue recognition codes, trigger conditions, revenue start dates and revenue end dates to NetSuite's revenue recognition templates and Advanced Revenue Management Module.

Subscription Metrics

Drive key business decisions by using Zuora's subscription metrics, such as Contracted Monthly Recurring Revenue, Total Contract Value, Renewal Rate and Churn.

NetSuite customers can leverage NetSuite's cloud ERP/Financials solution in mixed cloud application environments, including using the Zuora CPQ solution which seamlessly connects Salesforce CRM and Zuora's subscription commerce platform.

Deciding to Use NetSuite Connector

Use NetSuite Connector to solve the following business problems:

  • You have are using NetSuite for one line of your business, but you want to leverage Zuora for subscriptions
  • You have customized NetSuite for subscriptions, but you have reached the limit of the NetSuite customization
  • You are using QuickBooks and want to upgrade your accounting system.
  • You want to have all transactions in your general ledger for a full reporting view in NetSuite.
  • You want NetSuite to handle your revenue recognition.

The New Zuora Orders Feature

We've received quite a few questions about the new Zuora Orders feature over the past several months. In summary, Zuora has evolved with their customers and the orders feature is an extension that allows greater system flexibility and supports more complex use cases than standard subscriptions feature. In other words, it allows Zuora a means to build out more functions and features that support complex business cases.

This article describes the objects used to support Orders. The objects provide essential information needed to create and maintain orders in Zuora.

The following diagram summarizes the Orders objects and their relationships. For the summary of all Zuora key objects, refer to Zuora Business Object Model.

Orders

Represents an agreement between a merchant and a customer, which creates or changes one or more Subscriptions. An Order is owned by a single Billing Account.

Corresponding data source: Order

Order Actions

Order actions represent the actions that can be performed on subscriptions, such as creating subscriptions and making changes to subscriptions.

An order can contain multiple order actions, acting against one or more subscriptions.

The following types of order actions are supported:

  • Create Subscription 
  • Terms And Conditions
  • Renewal
  • Cancellation
  • Owner Transfer
  • Add Product
  • Update Product
  • Remove Product

The following types of order actions are not currently supported:

  • Suspend a subscription
  • Resume a subscription
  • Update a subscription to change the subscription term end date before the renewal term start date

Order actions operate at the subscription level or at the rate plan level.

One rate plan level order action affects one rate plan. Rate plan level order action types include New Product, Remove Product, and Update Product.

One subscription level order action affects one or more rate plans. Subscription level order action types include Renewal, Cancellation, Terms and Conditions.

Corresponding data source: Order Action

Order MRR

Indicates how a given Order Action has changed discounted MRR for each charge. Metrics are tied to each Order Action, which are then linked to Orders.

Corresponding data source: Order Mrr

Order TCB

Indicates how a given Order Action has changed Total Contacted Billing (TCB) for each charge. Metrics are tied to each Order Action, which are then linked to Orders.

Corresponding data source: Order Tcb

Order TCV

Indicates how a given Order Action has changed Total Contact Value (TCV) for each charge. Metrics are tied to each Order Action, which are then linked to Orders.

Corresponding data source: Order Tcv

Order Quantity

Indicates how a given Order Action has changed quantity for each charge.Metrics are tied to each Order Action, which are then linked to Orders.

Corresponding data source: Order Quantity

Walmart’s problem isn’t Amazon — it’s a lack of interest in who its customers are

This story was written by Zuora CEO and Founder Tien Tzuo for VentureBeat.

This week investors held a collective freakout over the fact that Walmart’s online sales grew at just 23 percent over the fourth quarter of 2017, down from 50 percent the previous quarter. They tanked Walmart’s stock by 10 percent, its biggest one-day decline in several decades.

While I also happen to be bearish on Walmart, I think its investors are missing the bigger picture here. E-commerce accounts for less than four percent of Walmart’s business. This is a company with much bigger problems.

Unlike the rest of Wall Street, I do not agree that Walmart’s problems begin and end with Amazon. The Walmart-versus-Amazon battle is typically framed as a clash between an ascendant e-commerce business and a dying retail industry, but that’s nonsense.

Selling products to strangers doesn’t cut it anymore. To succeed in retail today you need to start with the customer, not the product. You need to flip the script. Let me explain.

Nearly every American spent money at a Walmart last year. The vast majority of us live within 20 minutes of a Walmart store. The company has almost 5,000 retail locations, over two million employees, and over 140 million customers.

But let me ask you a simple question: What was the last thing you bought at Walmart? Walmart certainly can’t tell you. Got any receipts handy? Once you walk past the cash register at Walmart, you’re gone.

Walmart is still essentially a product company. It has decades of institutional experience with supply chains, transport logistics, and inventory management. It knows how to buy and sell products. That worked fine for a long time. It doesn’t anymore.

In the old product model. You built a product, put it into as many channels as possible, and hoped there were customers waiting at the end of those channels. In the new service-based model. You start with the customer, understand their wants and needs, and then wrap your service around that customer via relevant channels. No more pushing units to strangers.

Now let me ask you another question: What was the first thing you bought on Amazon? It’s sitting right there in your order history. Go ahead, open up a new browser tab and look it up. I bought “The Seven Habits of Highly Effective People” and “Inside the Tornado: Marketing Strategies from Silicon Valley’s Cutting Edge” on January 11, 1997.

Amazon is beating Walmart because it knows its customers. That’s the reason. Plain and simple. So does this mean e-commerce is bound for glory, and retail is doomed to failure? Will it be all retail apocalypse and zombie malls from here on out? Of course not.

Right now, there are at least a dozen new companies in the midst of opening hundreds of new retail stores. And why are they doing this? Because the stores they currently have are making money hand over fist.

You’ve probably heard some of the names: Allbirds, Casper, Birchbox, Boll & Branch. According to real-estate data company CoStar Group, these online-first stores have increased their retail space tenfold over the last five years. Warby Parker is averaging $3,000 per square foot of retail space, which is almost as good as Tiffany’s (!).

Why is this happening? Well, one reason is that it’s really hard to operate as a standalone e-commerce vendor. Almost two thirds of all online sales are owned by just 15 giant e-commerce marketplaces. RetailNext CEO Alexei Agratchev recently told me:

“As an ecommerce vendor, you have really high variable costs around shipping and returns. On the other hand, Amazon is an amazing logistical machine, and they’re not even running at a profit most of the time. … And the other question is, how do you really differentiate yourself online? Anything you do on your website, a competitor can steal pretty easily. But you can actually create really cool experiences in stores.”

As a result, retail is changing in all sorts of interesting ways. Take a look at b8ta, a new personal technology chain. It has hip, minimalist stores that let you try out the latest gadgets. What’s even more interesting is that b8ta doesn’t make any money from product sales. Product manufacturers pay a subscription fee for access to its customer base.

And as for those malls? Well, the ones that are doing well are doing really well. As old retailers are replaced by new online-first stores that are doing two to three times more business, the malls benefit from the increased foot traffic and attract better brands. Everyone wins.

Again, it’s never been just about e-commerce versus retail. It’s always been about flipping the script — starting with the customer as opposed to the product sale, and wrapping both your e-commerce and your retail channels around that customer experience.

Walmart is a product company that still views its e-commerce efforts as a distinct channel, a separate line of business. That’s not too surprising, considering the vast majority of its e-commerce business has been bought, not built: Jet.Com, Bonobos, ShoeBuy.Com, Moosejaw.Com, etc.

Walmart tried to buy its way in. But it doesn’t seem to be working out. The leopard can’t change its spots.

How do I recognize revenue with Z-Suite and without NetSuite ARM?

Overview

Zuora powers the revenue recognition used for the Z-Suite integration to NetSuite.

Many of the hardest challenges for revenue recognition are managed by Zuora, including the proration and calculation of the revenue recognition start and end dates.

Zuora has robust functionality where you can define a Revenue Recognition Code per Charge in the Zuora Product Catalog.  Each Charge can also have a separate revenue recognition trigger date that can trigger revenue such as a recurring charge to start when the Service is activated.

Z-Suite has extremely powerful revenue recognition capabilities and powers all the information NetSuite needs to build the revenue schedule.

This article explains how you can recognize revenue using Zuora Z-Suite.

Solution

In the Zuora Product Rate Plan Charge, you can define the Revenue Recognition Code, which equates to the name of a Revenue Recognition Template in NetSuite.

You can also define the type of Revenue Template you are using in NetSuite:

  • Standard templates: These templates take the invoice item amount and recognize it over the revenue recognition start and end date.
  • Variable templates: These templates are used for percent complete revenue recognition when you use NetSuite Projects.

Z-Suite supports both standard and variable Revenue Recognition Templates. And since these are on every charge, you can have one charge in a rate plan use a Variable Template and another use a Standard.

Variable Revenue Recognition

Variable Revenue Recognition is primarily used for milestone-based revenue recognition for projects, such as a fixed-price project.

When using Variable Template, the NetSuite Project Code entered on the Zuora Subscription is used as the project. If this field is not populated, the invoice will not be synchronized to NetSuite - so the recommended best practice is to create the project in NetSuite first, which will give you the needed project code.

When Variable is selected as the NetSuite Revenue Recognition Template Type and the NetSuite project is populated on the Zuora Subscription, the invoice will be synchronized to NetSuite using the Revenue Recognition Template and in NetSuite, the Revenue for the Invoice Item amount will be placed on hold.

In NetSuite, you can track the project, enter milestones and take the revenue off hold and recognize it.

Standard Revenue Recognition

Standard Revenue Recognition uses the start and end dates entered on the Product Rate Plan Charge.

You can define the Revenue Start and End Dates when you define your product catalog and automatically populate these dates based on what is entered on each subscription (Contract Effective, Service Activation, Customer Acceptance). 

For the NetSuite Revenue Recognition Start Date, you can select either the Charge Period Start or the Rev Rec Trigger Date.  This means you can use the standard start date from the charge or use one of the delayed dates that you define as your revenue recognition trigger. This is standard Zuora functionality as described in How do the invoice and revenue recognition triggers work in Zuora?.

For the NetSuite Revenue Recognition End Date, you can select Charge Period End or the Subscription End Date. The Subscription End Date is often used when you want to recognize a one time charge over the subscription term.

Examples

If you want to recognize each invoice item using the charge service period, which is common for straightforward recurring revenue, such as quarterly or annual billing, you would set the following:

  • NetSuite Revenue Recognition Start Date=Charge Period Start
  • NetSuite Revenue Recognition End Date=Charge Period End

If you want to use delayed revenue recognition where you invoice on contract effective and trigger revenue on either the Service Activation or the Customer Acceptance, you would set the following:

  • NetSuite Revenue Recognition Start Date=Rev Rec Trigger Date
  • NetSuite Revenue Recognition End Date=Charge Period End
  • Revenue Recognition Trigger=either Service Activation Date or Customer Acceptance Date

Z-Suite will automatically create the invoice in NetSuite on Contract Effective Date and will put revenue on hold in NetSuite if the Service Activation or the Customer Acceptance is not known.  When these dates are entered, Z-Suite will automatically take the revenue off hold in NetSuite.  Pretty cool stuff!

If you want to recognize a charge, such as a one time, using the subscription end date when you have to recognize a one time or professional services fee over the life of the subscription and not the service period, you would set the following:

  • NetSuite Revenue Recognition Start Date=Rev Rec Trigger Date or Charge Period Start
  • NetSuite Revenue Recognition End Date=Subscription End Date
  • Revenue Recognition Trigger=either Service Activation Date or Customer Acceptance Date depending

Z-Suite will use the subscription end date as the revenue recognition end date and you can use this feature with delayed Rev Rec as well.

So, there it is. Z-Suite has extremely powerful revenue recognition capabilities and powers all the information NetSuite needs to build the revenue schedule.