Statements for Contributor and RightsController revenues
When it comes to reporting revenue in the RevenueDetails message relating to a single distribution, often referred to as a statement (see here) to the recipient of the message, it may need to be sent in multiple files. This is particularly relevant for the communication between music licensing companies where a single distribution includes both RightsController revenues and Contributor revenues, which is specified in the StatementType Cell.
Each record (SRD1) in the RevenueDetails message enables the reporting of revenue and optionally the breakdown of gross revenue for either a RightsController or a Contributor.
If the StatementType is Contributor, the revenue for contribution(s) to a resource and the detailed breakdown of that revenue for each of the contribution(s), including any relevant fees, social deductions, costs etc. is being paid to the allocated party, as specified in the AllocatedPartyFullName Cell (see Clause 7.10 of RDR-R).
For a single distribution, RDR-R enables the sending of one RevenueSummary for each RevenueDetails message or one RevenueSummary for multiple RevenueDetails messages. RDR-R also permits implementers to only send a RevenueDetails message without a RevenueSummary message. In such cases, summary data may need to be sent separately, using some other method of communicaiton.
In the RevenueSummary message the SummaryType, which relates to the StatementType in the RevenueDetails message, identifies whether the revenues in Record SRS1 apply to either a RightsController or a Contributor.
In addition to permitting the sending of separate message files for each StatementType, the RevenueDetails message also requires that each Record within the message communicates revenue information
for a single UseType;
for a single TerritoryOfRevenueGeneration; and
for a single AllocatedPartyContributionRole.
The Record therefore has to be repeated if multiple UseTypes, TerritoryOfRevenueGeneration or AllocatedPartyContributionRoles are to be communicated.
In summary, this translates into the following: