DRAFT: Introduction to Revenue Runs

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

DRAFT: 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
  • Debit 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 Data Interface > Revenue Run in the Zuora RevPro home page. The revenue run configuration section is displayed in the upper pane and the created revenue run jobs are displayed in the lower pane.

Click the icon_revenuerun.png button to view the full list of revenue run jobs.

Full_revenue run.png

View an Individual Revenue Run

Click right_arrow.png in the row of a revenue run to view all associated revenue run jobs.

Revenue Run Job details.png

Click a transaction type in the column Revenue Run Job Name. The “Exceptions and Errors” page that includes all exceptions and errors in this job will be displayed. The following tabs display different error types in the "Exception and Errors" page, which facilitates troubleshooting during the revenue run:

  • API/Upload Errors: The errors that occur during the file uploading or partial file uploading process in the revenue run.
  • PreStage Errors: The errors captured during the data transformation process.
  • Staging Errors: The errors captured in the RevPro Line Staging table.

Revenue Run Status

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

  • BATCH_CREATED: The revenue run job batch has been created successfully.
  • 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 Zuora RevPro Integration service. This error is typically due to an invalid token or network issues.

 

Last modified

Tags

This page has no custom tags.

Classifications

(not set)