Creating a Royalty Run
Overview
Creating a new royalty run in Revelator Pro allows users to allocate revenue across royalty statements for their payees. This feature is essential for ensuring accurate and comprehensive revenue distribution based on detailed statements and data from digital service providers (DSPs).
Creating a new royalty run in Revelator Pro allows users to allocate revenue across royalty statements for their payees. This feature is essential for ensuring accurate and comprehensive revenue distribution based on detailed statements and data from digital service providers (DSPs). You may create a royalty run if errors were corrected or adjustments made to previous accounting periods. If a payment error occurred in a previous accounting period but has not been corrected, creating a new royalty run will not be helpful until the issue is resolved. You must include at least one pre-existing report to create a royalty run.
Who Is It For?
Label Managers: Automate and streamline the revenue allocation process.
Financial Administrators: Manage revenue distribution with precision.
Rights Holders: Ensure accurate and complete revenue allocation.
Real-World Scenario #1: Creating a Monthly Royalty Run
A financial administrator creates a new royalty run for March 2025 to consolidate revenue from multiple DSPs and allocate the income to rights holders.
Real-World Scenario #2: Adjusting FX Rates for International Revenue
A label manager sets FX rates manually to ensure accurate conversion from USD to various currencies during royalty calculations.
Key Benefits
Efficient Revenue Allocation: Automates the distribution process.
Custom FX Rates: Supports manual input of foreign exchange rates.
Unprocessed Revenue Handling: Automatically detects unprocessed revenue reports.
Preview and Confirmation: Review before processing to ensure accuracy.
Error Resolution: Facilitates error correction and revenue adjustments for previous accounting periods.
Prerequisites
Corrected Errors and Adjustments: Verify that any errors from previous accounting periods have been corrected. Creating a new royalty run without addressing these errors may lead to inaccurate revenue allocation.
Pre-Existing Reports: At least one pre-existing revenue report must be available to include in the royalty run.
Approved Reports: Make sure that all reports you intend to include have been approved or are ready for approval.
FX Rates Prepared: If your revenue involves foreign currencies, ensure that the necessary FX rates are prepared or manually inputted where required.
Access Permissions: You must have the necessary permissions to create and approve royalty runs within the platform.
How It Works: Step by Step Guides
Entering Royalty Run Details
Fill in the Statement Month by selecting the year and month from the dropdown.
Enter a Statement Name (e.g., "2025 March Royalties").
Optionally, add Royalty Run Notes for internal reference.
Toggle Additional FX Rates to input custom currency exchange rates (e.g., USD to AUD, BRL, CAD, EUR, GBP, HUF, ILS).
Selecting Unprocessed Revenue Reports
View the list of Unprocessed Revenue Reports.
Use tabs to filter reports by Approved, To Approve, Unmatched, and Need FX.
Select reports to include in the run by checking the box next to each report.
If necessary, resolve any Unmatched or Need FX issues before proceeding.
Frequently Asked Questions
Why can’t I create a royalty run? Ensure that all required fields (statement month and name) are filled in and that any unprocessed revenue issues (like FX rate requirements) are resolved.
How do I set custom FX rates? Toggle the Additional FX Rates switch and enter the desired exchange rate for each currency.
What if some reports are not processed due to FX issues? Go to the Need FX tab and add the required exchange rate before proceeding.
Additional Resources
[Royalty Runs Overview Guide]
[FX Rate Management Documentation]
[Unprocessed Revenue Troubleshooting Guide]
Next Steps and Future Releases
Automated FX rate updates from trusted sources.
Enhanced filtering for unprocessed reports.
Last updated