Welcome to Zuora Product Documentation

Explore our rich library of product information

Use cases of mapping order actions or amendments

The common use cases of how order actions or amendments in Zuora Billing are mapped to sales order actions in Zuora Revenue

Billing - Revenue Integration includes support for various use cases. The following table demonstrates how order actions or amendments are mapped to Zuora Revenue sales order actions:

Zuora Order Action/amendment

Termed subscription: Segment/charge behavior

Evergreen subscription: Segment/charge behavior

Zuora Revenue SO action

New Subscription

  • New Charge ID

  • New Segment

  • New Charge ID

  • New Segment with no End Date

New SO Line

New Product

  • New Charge ID

  • New Segment

  • New Charge ID

  • New Segment with no End Date

New SO Line

Amendment/Order Action - Price Change

  • Original Charge ID

  • Existing Charge Segment with an End Date

  • Original Charge ID

  • Existing Charge Segment with an End Date

Update Existing SO Line

  • New Charge Segment with an End Date

  • New Charge Version

  • New Charge Segment with no End Date

  • New Charge Version

New SO Line

Amendment/Order Action - Quantity Change

  • Original Charge ID

  • Existing Charge Segment with an End Date

  • Original Charge ID

  • Existing Charge Segment with an End Date

Update Existing SO Line

  • New Charge Segment with an End Date

  • New Charge Version

  • New Charge Segment with no End Date

  • New Charge Version

New SO Line

Renewal

  • Original Charge ID

  • New Charge Segment with an End Date

  • Original Charge ID

  • New Charge Segment with no End Date

New SO Line

Remove Product

  • Original Charge ID

  • Bring forward Segment End Date

  • Original Charge ID

  • Create Segment End Date

Update SO Line

Cancel

  • Original Charge ID

  • Bring forward Segment End Date

  • Original Charge ID

  • Create Segment End Date

Update SO Line

Terms and Conditions

  • Original Charge ID

  • Extend or bring forward Segment End Date

  • Original Charge ID

  • Extend or bring forward Segment End Date

Update SO Line

Suspend

  • Original Charge ID

  • Bring forward Segment End Date

  • Original Charge ID

  • Bring forward Segment End Date

Update SO Line

Resume

  • Original Charge ID

  • New Segment

  • Original Charge ID

  • New Segment

New SO Line

Owner Transfer

None

None

None

When creating a new subscription or amending an existing subscription in Zuora Billing, the number of the created SO lines depends on the discount type of rate plan charges:

  • For regular rate plan charges without discount, including one-time charges and recurring charges, each charge is mapped to one sales order (SO) line in Zuora Revenue.
  • For fixed amount discount charges, a charge is treated in Zuora Revenue as a new and stand-alone SO line that will not be allocated, regardless of how it is applied. This is done through extracting the Fixed Amount Discount amount from the Rate Plan Charge Tier data source from Zuora Billing.
  • For percentage discount charges, a charge can be mapped to multiple SO lines in Zuora Revenue depending on the number of transactions it is applied to. It ensures Zuora Revenue can correctly allocate the revenue against the charges that have been discounted.

See Charge Models for more information on rate plan charge models.

For more information on use cases of mapping order actions or amendments, refer to these articles: