1 Introduction

This document defines the choreography and messages for Part 3 (RDR-R) of the Recording Data and Rights Standard (RDR). It was developed by member organisations of the Digital Data Exchange, LLC (DDEX). Any organisation wishing to implement this (or any other) DDEX standard is required to apply for an Implementation Licence. The terms of the licence can be found here and an application form can be found here.

The messages contained in this part of the RDR standard provide mechanisms for the declaration of revenues generated from the usage of releases and/or resources. These 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 (see Clause 5.1).

This part of the RDR standard provides two mechanisms for the reporting of such revenues which offer the flexibility to communicate the same set of data in two different file structures depending on internal processes and capabilities. The first mechanism is the multi-record RevenueReport. The second mechanism defines two single-record messages, the RevenueSummary message and the RevenueDetails message.

These single-record messages offer a simple and workable solution for making the process of reporting revenues more efficient and accessible to even the smaller entities involved in this sort of revenue and data exchange. To achieve this, pipe delimiters have been removed which enables easier generation and ingestion of messages. The only exception to this is in the optional AudioVisualContributorName and AudioVisualContributorRole Cells in the SRD1 Record which relate to audio-visual resources containing music. Similarly, when using the single-record messages the RevenueDetails message is mandatory in such communications whilst the RevenueSummary message is optional. However, if sent together they enable the communication of all the data that the parties would receive by exchanging a multi-record RevenueReport.