Skip to main content

Implementation guide

Zuora

Implementation guide

  1. Last updated
  2. Save as PDF

 

Steps to do after OTR enablement

After enabling the Order to Revenue feature, you must check and, if necessary, perform the following tasks on your Billing tenant:

  1. Ensure your user role has the Manage OTR Settings permission enabled. For more information, see Billing Roles.
  2. Configure field mapping for custom fields. For more information, see Manage revenue fields mapping.
  3. Configure the mapping from your Billing tenant, entity, or organization to your revenue organization. One-to-one mapping, multi-entity to one mapping, and multi-org to one mapping are supported. For more information, see Manage Revenue organization mapping.
  4. Configure the following settings in Finance > Manage Currency Conversion. For more information, see Manage currency conversion and Currency Conversion Fields Added to the Export.
    • Home currency
    • Reporting currency
    • Exchange rate for foreign currency conversion

      If you use custom exchange rates, you must upload them to Zuora. Otherwise, billing transactions cannot be generated.

  5. Configure the interface settings for how you want to generate booking and billing transactions for discounts and pending subscriptions. For more information, see Configure interface settings.
  6. Configure the revenue recognition policy, so that when setting up a product rate plan charge, you can configure necessary revenue recognition fields. For more information, see Configure revenue recognition policy.
  7. Perform data backfill to update data in the Billing tenant with required revenue-related fields, including the following field types. For more information, see Perform data backfill.
    • Accounting codes
    • Exclusion fields and allocation flags
    • Product attributes
    • Custom fields
  8. Perform data migration to generate booking, billing, and revenue recognition events transactions for historical data in your Billing tenant. For more information, see Perform data migration.
  9. Use the following Data Query templates to validate the accuracy of the booking transactions and billing transactions generated in the preceding step:
    • Booking Transaction Validation
    • Billing Transaction Validation for Rate Plan Charge
    • Billing Transaction Validation for OLI
    • Billing Transaction Validation for Standalone Billing Document

OTR enablement and segment-split changes

When you renew a subscription to generate a new term, the segment-split by term behavior changes because of OTR enablement. Let’s understand how the segment-split by term behavior changes before and after you enable OTR.

Before you enable OTR, when a subscription is renewed to generate a new term, the charge will be extended to the same Segment for existing billing customers. The TCV is calculated for the two terms at $200 in this case.

After you enable OTR, when a subscription is renewed to generate a new term, the charge will  be split to a different segment. As there will be two sales order lines from a revenue recognition perspective, the CCV will be calculated for each charge segment. In this scenario, it is split into two charge segments: 

  • Charge segment 1 $100, and 

  • Charge segment 2 $100

The behavior impacts the following:

  • The recurring charges

  • The usage charges

  • Auto renew, renew to evergreen, renew order action

                                                    segmentsplit_new.png