Introduction to Revenue Runs

Knowledge Center > Zuora RevPro > Zuora RevPro Integration Overview > DRAFT: Revenue Runs > Introduction to Revenue Runs

Introduction to Revenue Runs

Revenue runs are used to automate the process of gathering data from Zuora Central, processing the data based on specified templates, and sending the transformed data to RevPro for revenue recognition on an ongoing basis. 

By using revenue runs, you can accomplish the following tasks:

  • Identify which records within the Zuora Central platform should be sent to Zuora RevPro on an ongoing basis.
  • Trigger the action of sending data to RevPro.
  • Track the progress of whether the Zuora RevPro Integration services have successfully transferred the applicable transactions to RevPro.
  • Manage errors and exceptions during the whole process.   

In order to meet your order-to-cash requirements of Zuora subscriptions and the revenue recognition requirements of RevPro, the following key sets of data need to be transferred from Zuora Central to RevPro: 

  • Orders
  • Invoices
  • Invoice Item Adjustments
  • Credit Memos
  • Usage

The Orders and the Invoice Settlement features are in Limited Availability. If you wish to have access to these features, submit a request at Zuora Global Support.

View Revenue Runs

You can view the revenue runs by navigating to icon-menu.png > Revenue Run under the Date Interface section in the Zuora RevPro UI. By default, the revenue run creation section is displayed.

Revenue Run_2.png

You can click the icon_revenuerun.png button to see the full list of revenue runs.

Full_revenue run.png

View an Individual Revenue Run

Click right_arrow.png to expand an individual revenue run and view the associated revenue run jobs.

Revenue Run Job details.png

Click a transaction type in the column Revenue Run Job Name and the Exceptions and Errors page that includes all exceptions and errors in this particular job is displayed.

Revenue Run Status

After a revenue run is executed, the status of the revenue run will be one of the following statuses:

  • Processing: While all the transactions within a revenue run are being processed, the overall revenue run is in the Processing status.
  • Submitted: The revenue run request has been successfully submitted to Zuora Central Data Pipeline services.
  • Completed: When all the transactions within a revenue run have completed processing in Zuora Central and the data is ready for downloading, the overall revenue run will be in the Completed status. 
  • PRESTAGE_SUCCESSFUL: The data has been successfully loaded into the RevPro Prestage tables.
  • PRESTAGE_ERROR: An error is encountered while loading the data into the RevPro Prestage tables. This error occurs typically due to the mismatch of the data and the number of columns.
  • Error: A batch-level error occurred while submitting a revenue run to the Data Pipeline service. This error is typically due to an invalid token or network issues.

Transaction Status

The transactions in a revenue run batch have one of the following statuses:

  • Processing: When you click create revenue run, the status of transactions included in that revenue run will be updated to Processing.
  • Completed - Success: If a transaction has successfully passed the data collection process to RevPro, then it will be tagged as “Completed - Success”
  • Completed - Failure: If a transaction encounters an error during the data collection process in RevPro and fails to proceed to the next collection, the status will be updated to Completed-Failure.

 

 

Last modified

Tags

This page has no custom tags.

Classifications

(not set)