Help - Mechanical Royalty Runs

The "Mechanical Royalty Runs" page lists mechanical royalty runs that have been completed for publisher reporting. This historical listing of runs includes the ability to access details for each run from this page.

High level information concerning each run is provided within this view:

# of Statements

- The number of statements that are available in a specific royalty run. By selecting the number in this column the user is taken to the list of statements that are included in the royalty run.

Payor

- The name of the payor for whom the statements were generated. Note that royalty runs are Payor specific. All statements contained in a royalty run are associated with the same Payor.

Start Date

- The start date of the royalty run period. This is informational only and is used to help differentiate royalty runs.

End Date

- The end date of the royalty run period. This is informational only and is used to help differentiate royalty runs.

Run Date

- The date that the royalty run was generated.

Status

- The status of the royalty run. The following statuses are available for a royalty run:

• Completed – The royalty run successfully completed with no errors.
  • A completed run can be deleted if corrections to data have been made and another run is required. When deleted, the run will be removed from the system.
  • A completed run can be invalidated. The run will remain in the system, but cannot be committed. Note: Changes to mechanical related data within the system can only be made if there are no "Completed" runs.
  • A completed run can be committed.
• Committed – The royalty run was committed. All associated calculations and data are confirmed and set within the application.
  • Committed royalty runs cannot be deleted.
  • Payments can be made against a committed royalty run.
• Closed – If a subsequent royalty run is committed, the previous run is automatically closed. "Closed" is the final state for a royalty run.
• Error – Notes that the associated royalty run has an error and statements could not be fully generated.
• Invalid – Notes that the associated royalty run has been invalidated. Statements can be viewed, but the run can only be deleted and is no longer available for being committed as data has changed since it was initially created.

Action

- By selecting the action task within this column, the specific action will be taken against a specific royalty run.

• Two actions that can be taken against a mechanical royalty run by users:
  • Invalidate – Invalidates a specific royalty run. The run is kept within the system, but is not allowed to be committed. This allows a user to make changes to mechanical variables while referencing the invalidated run.
  • Edit Payments – Provides an interface to add payment information for royalty runs that have been committed. Payments can only be edited for a committed run. Once a subsequent run is committed, the current committed run is moved to a closed state and payments can no longer be edited.
• Contact Client Services to have the following additional actions taken against a specific royalty run. Available actions include:
  • Create New Royalty Run – Kicks off a new mechanical royalty run within the system.
  • Delete – Deletes a specific royalty run from the system. Only completed, error, or invalidated runs can be deleted.
  • Commit – Confirms and locks all associated data within the application for the specific royalty run.