RDR-R explained
RDR-R is the standard which defines the standard messages for the communication of revenues generated from the usage of releases and/or resources. Such standard messages are typically sent by a music licensing company to the rights controllers and/or administrators and/or performers that the music licensing company represents for rights in sound recordings and/or music videos, and/or other audio-visual resources containing music, and other revenues that have not been directly attributed to a resource. This standard may also be used by music licensing companies to report revenues from royalties collected to other music licensing companies as part of their bilateral multi-territory rights licensing agreement with respect to the rights they administer.
The RDR-R version 1.1 offers an additional method for communicating such revenues over version 1.0.
The standard contains specifications for three messages. These are the RevenueReport (already available in 1.0), and a combination of the RevenueSummary (new) and/or RevenueDetails (new) messages. The two latter messages together enable the communication of the same data as the RevenueReport. The RevenueReport is a much simpler format. It is up to implementers to determine whether they use just the RevenueReport or the other two messages in combination. This may vary depending on the operational capabilities of the receiving business partner.
This approach avoids having to send both summary data and the detailed breakdown data of several different revenue streams in one message using a multi-block flat-file format. Rather, the same data can now be sent in one message (the RevenueReport message) and, in circumstances where the amount of data in such a message would be significant, be split into more than one file as specified in RDR-R 1.1. This enables a cost-effective and simplified way of sending and receiving standardised revenue information by territory, usage type, allocated party contribution role for either rights controller or contributor, to, for example, royalty departments and if necessary, a summary message to, for example, the finance department. This enables existing business processes to remain unchanged.
Additonal information can be found in the articles below: