Performance obligations processing

Knowledge Center > Zuora RevPro > Policy-related configuration > Performance obligations processing

Performance obligations processing

After the transaction lines are grouped into the revenue contract based on the RC grouping templates, the transaction lines within one revenue contract must be grouped into promises that are made to customers. These promises are referred to as performance obligations (POB) by ASC 606. Revenue can be recognized as or when the performance obligation is satisfied.

In RevPro, performance obligations are defined by POB templates and POB assignment rules. A performance obligation template determines the revenue recognition pattern (trigger and timing) for each distinct performance obligation and might also define cost treatment, variable consideration assignment, and any performance obligation dependencies if applicable.

Revenue release event

When you create a POB template, you must specify the revenue release event for the performance obligation. The revenue associated with a performance obligation can be released in one of the following ways:

  • Upon Event
    For example, upon shipment by quantity.
  • Upon Booking
    This event occurs when the sales order is processed during the RevPro data collection process.
  • Upon Billing
    This event occurs when the invoice is processed during the RevPro data collection process.
  • Upon Manual Release
    For example, a revenue user manually performs the release of revenue for the performance obligation.
  • Upon Expiry
    For example, after 30 days from the sales order book date.
  • Upon Satisfying a POB Dependency
    For example, when a parent POB within the same revenue contract is satisfied.

Predefined release events are provided for you to select when you create a POB template. You can also create your own revenue events in Setups > Application > Event Setup based on your business needs. Both the predefined and user-defined revenue events can be displayed when you create a POB template. For more information about release event setup, see Event Setup.

Ratable method

To perform revenue recognition, a ratable method must be specified for each performance
obligation within a revenue contract. A ratable method describes how RevPro will schedule
revenue based on the triggered release events and how RevPro interacts with the start
and end dates that come in with the sales order transaction line.

For example, when a revenue action such as Upon Delivery By Qty triggers a release of revenue on a performance obligation, the ratable method that is assigned to the POB template determines whether
the revenue of a performance obligation is scheduled for immediate recognition or whether the
revenue is scheduled over a duration of time such as contract ratable. The Contract Ratable method indicates that the release of revenue is based on the revenue start date and end date of the sales order. When you create a POB template in RevPro, you must select one ratable method.

POB assignment order

RevPro identifies the correct performance obligation template to assign to the transaction lines within a revenue contract by attempting all available POB assignment rules in the following order:

  1. Advanced Rule

  2. Assignment - By Attributes

  3. Assignment - By Item/SKU#

If RevPro does not find a rule to assign a performance obligation template, RevPro assigns the Auto POB template by default.

Related articles

For RevPro to automatically group transaction lines into POBs within a revenue contract, complete the following tasks:

  1. Create POB template. For information, see Create POB template.

  2. Define POB assignment rules. For information, see Define POB assignment rules.

Last modified

Tags

This page has no custom tags.

Classifications

(not set)