6.2 RevenueReport

The RevenueReport enables a music licensing company to communicate revenue data in respect of sound recordings, music videos and/or audio-visual resources containing music for which the music licensing company has received a rights claim from a rights controller or administrator.

The RevenueReport shall comprise the following Records:

1. 1 Header Record of type RHEA.01 created in accordance with Clause 7.1;

2. 1-2 Revenue Summary Record of type RS01.01 created in accordance with Clause 7.4. This Record shall provide summary information about the detailed revenue data in the Revenue Details Records (RD01.01, RD02.01, RD03.01):

   1. 1-n Allocated Party Summary Records of type RS02.01 created in accordance with Clause 7.5 shall follow each RS01.01 Record. The Allocated Party Summary Records shall each be pointed to by at least one of the RD01.01, RD02.01 or RD03.01 Records;

3. At least one of:

   1. 1-n Sound Recording Revenue Details Record of type RD01.01 created in accordance with Clause 7.6 which shall point to exactly one Allocated Party Summary Record; and/or

   2. 1-n Audio-visual Resource Revenue Details Record of type RD02.01 created in accordance with Clause 7.7 which shall point to exactly one Allocated Party Summary Record; and/or

   3. 1-n Other Revenue Details Record of type RD03.01 created in accordance with Clause 7.8 which shall point to exactly one Allocated Party Summary Record; and

4. 1 Footer Record of type RFOO created in accordance with Clause 7.2.

In the circumstances where a message sender wishes to send a RevenueReport message to report zero revenues, it shall completely omit any RD01.01, RD02.01 or RD03.01 Records.

The header Record only permits a single DistributionDate, therefore a RevenueReport message can only relate to revenue being passed on in a single distribution.

The table below provides an overview of the order and cardinality of the Records to be used in this message.

Table 2 – RevenueReport structure