Skip to main content

Overview of event processing

Zuora

Overview of event processing

  1. Last updated
  2. Save as PDF

In Zuora Revenue, the following types of POB releasing methods are supported:

  • Booking
  • Billing
  • Events
  • Manual

In the Events method, events are triggered for revenue release, cost release, and also for holding the revenue or cost. For events processing in Zuora Revenue, you must first create the event types based on your business needs, and then associate the event with the appropriate POB templates or revenue holds. After the setups are completed, you can upload event data to Zuora Revenue and then start the event process for Zuora Revenue to process the uploaded events.

This feature is not applicable for Billing - Revenue Integration since Zuora Billing and Zuora Revenue have different policies and requirements.

Supported event types

The following types of events can be created in Zuora Revenue:

  • Budgeted Cost
    Use this event to release revenue based on the percentage of completed budgeted cost.

  • Budgeted Hours
    Use this event to release revenue based on the percentage of completed budgeted hours.

  • Cost
    Associate this event type with a POB template to release cost.

  • Hold
    Associate this event type with the holds or approvals to release the revenue hold or to transfer revenue that is placed on an RC, POB or line.

  • Revenue
    Associate this event type with a POB template to release revenue.

Events processing using Nova 

As part of the tech upgrade, the functionality of Event Processing was enhanced. The following changes were made to Event Processing:

  • Earlier, if an exception or error occurred, the system stopped events processing and triggered the process again, irrespective of the stage in which it failed. With this upgrade, the system handles the exceptions in the following stages:
  1. Process events
  2. create actions
  3. Process actions
  4. Post-release process

If an exception or error occurs, the system triggers event processing only at the stage where it failed. For example, if an RC with 5 POBs fails when processing the 5th POB, the system will trigger the process again only for the 5th POB. 

  • Earlier, the process type was not considered based on the value populated in the percentage or amount column; the events processing was processed. With this upgrade, the process type takes precedence; validation restricts the data from getting processed with a proper error message. 
  • Earlier, If the line was negative, the event was amount-based, and the value processed using events processing was positive. The system processed the value by moving it to the stage, but an accounting entry was not created. With this upgrade, the system displays the following error messages in such scenarios:
    • INVALID_PERCENT_EVENT("Release amount or release quantity is uploaded for percent based event")
    • INVALID_AMOUNT_EVENT("Release percent or release quantity is uploaded for amount based event")
    • INVALID_QUANTITY_EVENT("Release percent or release amount is uploaded for quantity based event")

Related tasks

The following tasks are required for Zuora Revenue to take appropriate actions against revenue or cost based on the uploaded events:

  1. Create the event type that you are going to upload in Zuora Revenue. See Event setup.
  2. Depending on the event type that you create, different steps are required:
  3. Upload the event data based on an event upload template. See Event upload.
  4. Start the event process in Zuora Revenue. See Release event.