Candidate Standard

Skip to end of metadata
Go to start of metadata

This section of the DDEX Knowledge Base contains Version 1.0 of Part 2 (Record Type Definitions) of the Claim Detail Message Suite Standard

 

 

1 Introduction

This standard was developed by the member organisations of the Digital Data Exchange, LLC (DDEX) and provides a format for a response to a sales/usage report received by an owner/administrator of Musical Works (usually the "Licensor") which sets out the claim (“right share”) each owner/administrator is making in respect of the Musical Works identified in the sales/usage report and all the calculation details behind the individual and aggregate royalty claim being made by each owner/administrator in such detail that the original sender (usually the "Licensee") of the sales/usage report can be confident in accepting the associated invoice for payment. 

This standard defines the the Record Types used by the various Profiles of the Claim Detail Message Suite Standard.

Any organisation wishing to implement this (or any other DDEX standard) is required to apply for an Implementation Licence. The terms of the licence and an application form can be found on https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers.


Essential Reading

Download/Print standard (PDF)

This standard is Part 2 of a multi-part standard. The other parts (incl. samples) are available here.

Samples for the CDM Standard can be found here.

CDM is a "Candidate Standard", which is a formal standard approved by DDEX for which DDEX has not had any information about live implementations. Once DDEX has received such input, it is expected that CDM will be promoted to "DDEX Standard".

2 Scope

 2.1 Introduction
The message design defined in this standard provides a mechanism for Licensors (typically Music Rights Societies, Audio-visual Rights Societies, and/or Music Publishers) to make rights claims on Musical Works and send these to Licensees (typically Digital Service Providers).  The message design defined in this standard also provides a mechanism for Licensors to accompany, if appropriate, such claims with invoice details. The message design defined in this standard also provides a mechanism for Licensees to provide information on discrepancies they have detected in such rights claims or invoice details.

Such data is provided, in accordance with the overall architecture defined in Part 1, in a series of Records. The order of these Records is defined in the relevant Profile (as documented in a separate Parts of this standard) whereas the syntax and semantics of each Record is defined in this Part 2.

 2.2 Organisation of the Standard
This standard has five clauses. Clauses 1–4 provide an introduction, scope, a set of core terms and abbreviations before Clause 5 defines the Record Types used in the Profiles of the Claim Detail Message Suite Standard.

3 Normative References

 3 Normative References
The following normative documents contain provisions, which through reference in this text constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest version applies.
  • DDEX Data Dictionary Standard. Latest Version.
  • DDEX. Claim Detail Message Suite Standard – Part 1: Architecture.

4 Terms and Abbreviations

 4 Terms and Abbreviations
The terms and abbreviations used  in Part 1 of the Claim Detail Message Suite Standard also apply to this Standard.

5 Record Type Definitions

5.1 Header and Footer Records

 5.1.1 CDMH — Header Record for Claim Detail Messages and Claim Detail Discrepancy Notifications
This is the Header Record for the Claim Detail Messages and Claim Detail Discrepancy Notifications created in accordance with this standard. Each file containing a Claim Detail Message or Claim Detail Discrepancy Notification shall have exactly one such Header Record. It shall be the first Record in each file.
Cell Name   Field DefinitionData TypeM/O/C? [1] Example
1

RecordType

 

The Type of the Record; always to contain “CDMH”.

Fixed string

M

CDMH

2

MessageVersion

The Version of the Message. This shall be in the form CDM/xxx/yyy/zzz with:

  • xxx being the version number of the referenced Part 1 (Architecture) of the Claim Detail Message Suite Standard;
  • yyy being the version number of the referenced Part 2 (Allowed Value Sets) of the Digital Sales Report Message Suite Standard; and
  • zzz being the version number of the referenced Part 2 (Record Type Definitions) of the Claim Detail Message Suite Standard.

CDM/1.1.2/5.0/1.0 would therefore signal that the Claim Detail Message or Claim Detail Discrepancy Notification was created in accordance with the Architecture in version 1.1.2 of the Claim Detail Message Suite Standard, with the allowed values from version 5.0 of Part 2 of the Digital Sales Report Message Suite Standard and with the Record Type Definitions provided in version 1.0 of the Claim Detail Message Suite Standard.

Fixed string

M

CDM/1.2/5.0/4.2

3

MessageId

A string used to uniquely identify the Message. The MessageId shall be, in combination with the Message Sender's Id, globally unique. Thus, a Message Sender shall never re-use a MessageId.

String

M

1234567890

4

MessageCreatedDateTime

The date and time on which the Message was created. The only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD.

ISO datetime

M

2014-12-14T10:05:00Z

5Profile

The Identifier of the Profile used for the Message in accordance with the relevant Profile of the Claim Detail Message Suite Standard.

For Claim Detail Messages and Corrections to Claim Detail Message the value for this Cell is defined in the relevant Profile.

For retractions, this Cell shall contain the string CDMRetraction.

String

M

BasicCDMPostUsage

6ProfileVersion

The Identifier of the Version of the Profile used for the Message in accordance with the relevant Profile of the Claim Detail Message Suite Standard.

String

M

1.0
7

RelatedCDM

 

The MessageId of the Claim Detail Message that is retracted by this message or for which discrepancies are reported.

This Cell must be provided if a message is either a retraction to a previous Claim Detail Message or if the message at hand is a Discrepancy Notification.

String

 

C1234567890
8SalesReportId  

The MessageId of the DSR (or equivalent) Message that the Claim Detail Message or Claim Detail Discrepancy Notification is in respect of.

The SalesReportId shall be provided when the sales/usage report the Claim Detail Message or Claim Detail Discrepancy Notification is in respect of response to carries a message identifier (e.g. DDEX DSR). In that case, this Cell shall contain the MessageId of that DSR (or equivalent) Message.

In the case of a pre-usage choreography, this Cell may contain the Message ID of a message formatted in accordance with the Part 10 of the Digital Sales Reporting Message Suite Standard, i.e the Masterlist Profile, to which the Claim Detail Message or claim Detail Discrepancy Notification is in respect of.

String

C

0987654321
9

StartDate

The StartDate of the reporting Period covered by the Message (in ISO 8601:2004 format).

In most cases, this Cell shall contain the UsageStartDate from the DSR (or equivalent) Message that the Claim Detail Message is in response to.

This is a string with the syntax YYYY[-MM[-DD]].

ISO date

C

2014-12-01

10

EndDate

The EndDate of the reporting Period covered by the Message (in ISO 8601:2004 format).

In most cases, this Cell shall contain the UsageEndDate from the DSR (or equivalent) Message that the Claim Detail Message is in response to.

This is a string with the syntax YYYY[-MM[-DD]].

ISO date

C

2014-12-01

11

SenderPartyId

The DDEX PartyId (DPID) of the Message Sender.

DDEX Party ID

M

PADPIDA2008120501W

12

SenderName

The Full Name of the Message Sender.

String

M

GEMA

13

ServiceDescription

The service name (e.g. a service tier) that the Claim Detail Message or Claim Detail Discrepancy Notification relates to. The ServiceDescription may not contain space characters or underscores.

The ServiceDescription is intended to be a human-readable expression of the totality of the services the Claim Detail Message or Claim Detail Discrepancy Notification is in respect of. Where the Claim Detail Message or Claim Detail Discrepancy Notification is in respect of a DSR (or equivalent) Message that contained sales/usage data covering one sales context this should be the same as the string used in the file name and in the single Summary Record contained in the DSR (or equivalent) Message.

For Claim Detail Message or Claim Detail Discrepancy Notification covering multiple sale contexts, the ServiceDescription in the Header should be the same as on the file name and represent a human-readable summary of the sales contexts provided in the Summary Records.

In most cases, this Cell shall contain the ServiceDescription from the DSR (or equivalent) Message that the Claim Detail Message is in response to.

String

C

PremiumService

14

RecipientPartyId

The DDEX PartyId (DPID) of the Message Recipient. This element is mandatory when the Claim Detail Message or Claim Detail Discrepancy Notification is sent to one Message Recipient.

In most cases, this Cell shall contain the SenderPartyId from the DSR (or equivalent) Message that the Claim Detail Message is in response to.

DDEX Party ID

O

PADPIDA2007081601G

15

RecipientName

The Full Name of the Message Recipient. This element is mandatory when the Claim Detail Message or Claim Detail Discrepancy Notification is sent to one MessageRecipient.

In most cases, this Cell shall contain the SenderName from the DSR (or equivalent) Message that the Claim Detail Message is in response to.

String

O

YouTube

16ClaimingRound

The cardinal number of the claiming round.

ClaimingRound needs to be provided when Licensee and Licensor have agreed that claims are provided in multiple "rounds".

IntegerC1

 



[1] Mandatory – Optional – Conditional

 5.1.2 SRFO – Footer Record for Claim Detail Messages and Claim Detail Discrepancy Notifications
This is the Footer Record for Claim Detail Messages and Claim Detail Discrepancy Notifications created in accordance with this standard. Each Message shall have exactly one such Footer Record. It shall be the last Record in the Claim Detail Message or Claim Detail Discrepancy Notification.
Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “SRFO”.

Fixed string

M

SRFO

2

NumberOfLinesInReport

Number of data lines communicated in the report or message, including Header and Footer Records, empty Records and commented-out Records in accordance with the relevant clauses of the flat-file architecture.

Integer

M

1234

3NumberOfSummaryRecordsNumber of Records in accordance with the relevant profile.IntegerM20

 

Note: the structure of the Footer Record for Claim Detail Messages and Claim Detail Discrepancy Notifications is the same as used for the Single Record Block Variants for the Digital Sales Reporting Message Suite Standard.

5.2 Summary Record Types

 5.2.1 CS01 — Basic Summary Record for Post-Usage Claim Detail Messages
This is the Summary Record for Claim Detail Messages created in accordance with this standard.

 

Cell Name  Field DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CS01”.

Fixed string

M

CS01

2

SummaryRecordId

 

The Identifier (specific to the Message) of the Summary Record. This Identifier shall also appear in the Invoice Detail Records to indicate to which Summary Record the information in each Invoice Detail Record relates. 

StringM34
3InvoiceReference

A reference to the formal invoice document that is sent based on the information contained in the Claim Detail Message.

In some cases, the formal invoice does not exist when the Claim Detail Message is sent. In such cases, the InvoiceReference shall remain empty.

StringODL/09/2018-5
4RightsControllerName

The name of the Rights Controller for all rights being claimed in for the Sales Context in this Claim Detail Message.

The Rights Controller may also be the Licensor. However, some Licensors may represent several Rights Controllers. It is vital therefore in such circumstances that that distinction is understood and reflected in any message formatted in accorance with this Standard.

StringMMyCo
5

RightsContollerPartyId

The PartyId of the Rights Controller

PartyIDMDPIDA12345SDF::6547996
6DistributionChannel

The Licensee that generated the DSR (or equivalent) Message on which the information contained in the Claim Detail Messages is based.

DistributionChannel needs to be provided if the DSR (or equivalent) Message generated by the Licensee contained sales/usage information relating to multiple distribution channels so that this can be differentiated in the Claim Detail Message.

In most cases, this Cell shall contain the DistributionChannel from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

StringCMyCo
7DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DistributionChannelDPID shall be provided when essential to the commercial relationship being reported on.

In most cases, this Cell shall contain the DistributionChannelDPID from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

DPIDCDPIDA12345SDF
8

StartOfClaimPeriod

The start of the period for which Right Share Claims are being made (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

The period between StartOfClaimPeriod and EndOfClaimPeriod is usually the same period as indicated in the CDMH Record. When a sales/usage report covers longer periods such as a quarter, the period between StartOfClaimPeriod and EndOfClaimPeriod can be used to identify sub-periods for claiming and/or invoicing.

StartOfClaimPeriod and EndOfClaimPeriod reflect the reporting period range agreed between Licensee and Licensor and may be the aggregation of several sales/usage periods reported in a DSR (or equivalent) message.

StartOfClaimPeriod must be provided if the Licensor is responding to a DSR (or equivalent) Message that provides separate sub periods. Otherwise the period is specified in the CDMH record. Otherwise the period is specified in the CDMH record. 

ISO date

C

2014-11-14

9

EndOfClaimPeriod

The end of the period for which Right Share Claims are being made (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

The period between StartOfClaimPeriod and EndOfClaimPeriod is usually the same period as indicated in the CDMH Record. When a sales/usage report covers longer periods such as a quarter, the period between StartOfClaimPeriod and EndOfClaimPeriod can be used to identify sub-periods for claiming and/or invoicing.

StartOfClaimPeriod and EndOfClaimPeriod reflect the reporting period range agreed between Licensee and Licensor and may be the aggregation of several sales/usage periods reported in a DSR (or equivalent) message.

EndOfClaimPeriod must be provided if the Licensor is responding to a DSR (or equivalent) Message that provides separate sub periods. Otherwise the period is specified in the CDMH record. Otherwise the period is specified in the CDMH record. 

ISO date

C

2021-11-13

10CommercialModel

The Type of CommercialModel of the SalesTransaction for which the claim is made or the invoice details are provided. The CommercialModel defines how a Consumer has gained access to a Service or Release/Resource whether for payment or otherwise.

In most cases, this Cell shall contain the CommercialModel from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMPayAsYouGoModel
11UseType

The nature of a Service as used by a Consumer for which the claim is made or the invoice details are provided.

In most cases, this Cell shall contain the UseType from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMPermanentDownload
12Territory

The Territory for which the claim is made or the invoice details are provided.

In most cases, this Cell shall contain the Territory from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMDE
13ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place for which the claim is made or the invoice details are provided. The ServiceDescription may not contain space characters or underscores.

The ServiceDescription shall be provided if the Licensee that generated the DSR (or equivalent) Message offers multiple services that need to be differentiated in the Claim Detail Message and should be the same as reported in the DSR (or equivalent) Message that gave rise to the Claim Detail Message.

In most cases, this Cell shall contain the ServiceDescription from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

StringCPremiumService
14

CurrencyOfReporting

The currency used in the DSR (or equivalent) Message to report sales/usages, to which the Blocks referencing this Summary Record are responding to, in the Claim Detail Message.

CurrencyOfReporting shall be provided unless the CurrencyOfReporting is the same as the CurrencyOfInvoicing.  

AVSCCAD
15CurrencyOfInvoicing

The currency in which the invoice information contained in the Claim Detail Message is being provided.

CurrencyOfInvoicing shall be provided when the Claim Detail Message Blocks linked to this Summary record contains invoice information.

AVSCCHF
16ExchangeRate

The Exchange rate used to convert from the CurrencyOfReporting into the CurrencyOfInvoicing.

The ExchangeRate shall be provided if the CurrencyOfReporting and the CurrencyOfInvoicing differ. 

Decimal C 12.34
17

ExchangeRateSource

The source of the ExchangeRate.

The ExchangeRateSource shall be provided if an ExchangeRate is provided.

StringChttp://currencyexchange.net
18DateOfCurrencyExchange

The date and time on which the ExchangeRate was determined. The only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

If an EndDateOfCurrencyExchange is also provided, the DateOfCurrencyExchange provides the start date and time of the period over which the exchange rate was averaged.

The DateOfCurrencyExchange  shall be provided if an ExchangeRate is provided.

ISO datetime

C

2014-12-14T10:05:00Z

19EndDateOfCurrencyExchange

The end date and time of the period over which the exchange rate was averaged. The only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

The EndDateOfCurrencyExchange may only be provided if a DateOfCurrencyExchange is provided. 

ISO datetime

C

2014-12-14T10:05:00Z

20RightsTypeSplitMechanical

The percentage of the MechanicalRight that is applicable to the Musical Works linked to this Summary Record for the Sales Context for the Licensor, Territory and Period.

RightsTypeSplitMechanical shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

The sum of RightsTypeSplitMechanical and RightsTypeSplitPerforming must be 100 (i.e. 100%).

Decimal

M

75
21RightsTypeSplitPerforming

The percentage of the PerformingRight that is claimed in the Musical Works linked to this Summary Record for the Licensor, Territory and Period.

RightsTypeSplitPerforming shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

The sum of RightsTypeSplitMechanical and RightsTypeSplitPerforming must be 100 (i.e. 100%).

Decimal

M

25
22

TotalMarketShare


The market share of the Rights Controller compared to all sales/usages in the same Sales Context (as defined in Part 1 of the Digital Sales Report Message Suite Standard). The MarketShare shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

Decimal

O

 

60

23

TotalClaimedAmount

The amount due for this Sales/Usage Context.

If a CS01 Record is followed by multiple CS02 Records, the TotalClaimedAmount in CS01 is the sum of all TotalClaimedAmount Cells from the following CS02 Records.

This is the aggregate of the ClaimedAmount from the CD01 or ClaimedAmountDelta in CD02.
DecimalM125.00
 5.2.2 CS02 — Basic Financial Record for Post Usage Claim Detail Messages
This is the Financial Summary Record for Claim Detail Messages created in accordance with this standard. It can be used to provide additional information to the information provided in a Summary Record of type CS01.

 

Cell Name  Field DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CS02”.

Fixed string

M

CS02

2

SubSummaryRecordId

 

The Identifier (specific to the Message) of the Sub Summary Record. This Identifier shall also appear in the Invoice Detail Records to indicate to which Sub Summary Record the information in each Invoice Detail Record relates. 
StringM34
3ParentSummaryRecordIdThe Identifier (specific to the Message) of the Parent Summary Record of type CS01.StringM43
4NetRevenue

Net Revenue of the Licensee generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources in the InCurrencyOfReporting.

NetRevenue shall be provided when applicable in the relevant business relationship.

DecimalO100961.16
5

TotalUsages

The number of Usages of the Release or Resource provided to Consumers in the Sales Context defined in this Record as reported in the DSR (or equivalent) Message.

DecimalO145.2313
6ContentCategory

A string categorising the content that has been used or distributed as agreed between Licensor and Licensee. 

ContentCategory needs to be provided if the DSR (or equivalent) Message reported a ContentCategory for the relevant Work(s).

StringCMusic
7MarketShareMechanical

The market share by Content Category of the Rights Controller compared to all sales/usages in the same Sales Context (as defined in Part 1 of the Digital Sales Report Message Suite Standard) for the Mechanical Right. The MarketShareMechanical shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

Decimal

O

 

60

8MarketSharePerforming

The market share by Content Category of the Rights Controller compared to all sales/usages in the same Sales Context (as defined in Part 1 of the Digital Sales Report Message Suite Standard) for the Performing Right. The MarketSharePerforming shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

Decimal

O

 

60

9

CombinedMarketShare

The market share by Content Category of the Rights Controller compared to all sales/usages in the same Sales Context (as defined in Part 1 of the Digital Sales Report Message Suite Standard). The MarketShare shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

Decimal

O

 

60

10

ClaimedUsagesMechanical


The total number of usages claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record for the Mechanical Right (after applying the right share percentage).

DecimalO145.2313
11ClaimedUsagesPerforming

The total number of usages claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record for the Performing Right (after applying the right share percentage).

DecimalO145.2313
12TotalClaimedUsages

The total number of usages claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record. TotalClaimedUsages is the sum of ClaimedUsagesMechanical and ClaimedUsagesPerforming.

DecimalO145.2313
13ActivityRatio

A ratio between the TotalClaimedUsages and the TotalUsages expresses as a decimal fraction of TotalClaimedUsages/TotalUsages

DecimalO0.654
14

ClaimedAmountMechanical

The total amount of royalty claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record for the Mechanical Right (after applying the right share percentage) in the CurrencyOfInvoicing.

DecimalO23.15
15

ClaimedAmountPerforming

The total amount of royalty claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record for the Performing Right (after applying the right share percentage) in the CurrencyOfInvoicing.

DecimalO43.60
16

TotalClaimedAmount

The total amount of revenue claimed by the Rights Controller for all Musical Works in the Sales Context defined in this Record (after applying the right share percentage) in the CurrencyOfInvoicing.

TotalClaimedAmount is the sum of ClaimedAmountMechanical and ClaimedAmountPerforming.

DecimalO389.75
17AggregatedRevenue
InCurrencyOfReporting

Sum of all the GeneratedRevenueExcSalesTax InCurrencyOfReporting in CDxx records. 

DecimalO3456.23
18

AggregatedRevenue
InCurrencyOfInvoicing

Sum of all the GeneratedRevenueExcSalesTax-InCurrencyOfInvoicing in CDxx records. 

DecimalO6543.54
19

TariffParameterType

All applicable types of tariff parameters that have been agreed between the Licensor and Licensee are to be used for royalty calculations. Types might include minimum amount or rate payable.

Multiple stringCMinimumAmount|
MaximumAmount
20

TariffParameterValue

 

The value or values of such parameters.

There must be the same number of TariffParameterValue values as there are entries in the TariffParameterType cell.

Multiple decimalC100|1000

 

 

 5.2.3 CS03 — Basic Summary Record for Pre-Usage Claim Detail Messages
This is the Summary Record for Pre-Usage Claim Detail Messages created in accordance with this standard.
Cell Name  Field DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CS03”.

Fixed string

M

CS03

2

SummaryRecordId

 

The Identifier (specific to the Message) of the Summary Record. This Identifier shall also appear in the Invoice Detail Records to indicate to which Summary Record the information in each Invoice Detail Record relates. 

StringM34
3RightsControllerName

The name of the Rights Controller for all rights being claimed in for the Sales Context in this Claim Detail Message.

The Rights Controller may also be the Licensor. However, some Licensors may represent several Rights Controllers. It is vital therefore in such circumstances that that distinction is understood and reflected in any message formatted in accorance with this Standard.

StringMMyCo
4

RightsContollerPartyId

The PartyId of the Rights Controller

PartyIDMDPIDA12345SDF::6547996
5DistributionChannel

The Licensee that generated the DSR (or equivalent) Message on which the information contained in the Claim Detail Messages is based.

DistributionChannel needs to be provided if the DSR (or equivalent) Message generated by the Licensee contained sales/usage information relating to multiple distribution channels so that this can be differentiated in the Claim Detail Message.

In most cases, this Cell shall contain the DistributionChannel from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

StringCMyCo
6DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DistributionChannelDPID shall be provided when essential to the commercial relationship being reported on.

In most cases, this Cell shall contain the DistributionChannelDPID from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

DPIDCDPIDA12345SDF
7

StartOfClaimPeriod

The start of the period for which Right Share Claims are being made (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

The period between StartOfClaimPeriod and EndOfClaimPeriod is usually the same period as indicated in the CDMH Record. When a sales/usage report covers longer periods such as a quarter, the period between StartOfClaimPeriod and EndOfClaimPeriod can be used to identify sub-periods for claiming and/or invoicing.

StartOfClaimPeriod and EndOfClaimPeriod reflect the reporting period range agreed between Licensee and Licensor and may be the aggregation of several sales/usage periods reported in a DSR (or equivalent) message.

StartOfClaimPeriod must be provided if the Licensor is responding to a DSR (or equivalent) Message that provides separate sub periods. Otherwise the period is specified in the CDMH record. Otherwise the period is specified in the CDMH record. 

ISO date

C

2014-11-14

8

EndOfClaimPeriod

The end of the period for which Right Share Claims are being made (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

The period between StartOfClaimPeriod and EndOfClaimPeriod is usually the same period as indicated in the CDMH Record. When a sales/usage report covers longer periods such as a quarter, the period between StartOfClaimPeriod and EndOfClaimPeriod can be used to identify sub-periods for claiming and/or invoicing.

StartOfClaimPeriod and EndOfClaimPeriod reflect the reporting period range agreed between Licensee and Licensor and may be the aggregation of several sales/usage periods reported in a DSR (or equivalent) message.

EndOfClaimPeriod must be provided if the Licensor is responding to a DSR (or equivalent) Message that provides separate sub periods. Otherwise the period is specified in the CDMH record. Otherwise the period is specified in the CDMH record. 

ISO date

C

2021-11-13

9CommercialModel

The Type of CommercialModel of the SalesTransaction for which the claim is made or the invoice details are provided. The CommercialModel defines how a Consumer has gained access to a Service or Release/Resource whether for payment or otherwise.

In most cases, this Cell shall contain the CommercialModel from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMPayAsYouGoModel
10UseType

The nature of a Service as used by a Consumer for which the claim is made or the invoice details are provided.

In most cases, this Cell shall contain the UseType from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMPermanentDownload
11Territory

The Territory for which the claim is made or the invoice details are provided.

In most cases, this Cell shall contain the Territory from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

AVSMDE
12ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place for which the claim is made or the invoice details are provided. The ServiceDescription may not contain space characters or underscores.

The ServiceDescription shall be provided if the Licensee that generated the DSR (or equivalent) Message offers multiple services that need to be differentiated in the Claim Detail Message and should be the same as reported in the DSR (or equivalent) Message that gave rise to the Claim Detail Message.

In most cases, this Cell shall contain the ServiceDescription from the relevant Summary Record of the DSR (or equivalent) Message that the Claim Detail Message is in response to.

StringCPremiumService
13ContentCategory

A string categorising the content that has been used or distributed as agreed between Licensor and Licensee. 

ContentCategory needs to be provided if the DSR (or equivalent) Message reported a ContentCategory for the relevant Work(s).

StringCMusic
14RightsTypeSplitMechanical

The percentage of the MechanicalRight that is applicable to the Musical Works linked to this Summary Record for the Sales Context for the Licensor, Territory and Period.

RightsTypeSplitMechanical shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

The sum of RightsTypeSplitMechanical and RightsTypeSplitPerforming must be 100 (i.e. 100%).

Decimal

M

75
15RightsTypeSplitPerforming

The percentage of the PerformingRight that is claimed in the Musical Works linked to this Summary Record for the Licensor, Territory and Period.

RightsTypeSplitPerforming shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

The sum of RightsTypeSplitMechanical and RightsTypeSplitPerforming must be 100 (i.e. 100%).

Decimal

M

25

 

 

 5.2.4 CDS1 – Summary Record for Claim Detail Discrepancy Notifications
This Record provides information about a set of discrepancies that a Licensee has detected in a received Claim Detail Message.

Each Summary Record for Claim Detail Discrepancy Notifications provides summary information for all detailed records that have the same DiscrepancyDescription. Therefore, each Summary Record for Claim Detail Discrepancy Notifications summarises discrepancies for a common (i) CommercialModel, (ii) UseType, (iii) Territory, (iv) ServiceDescription and (v) DiscrepancyDescription.

 

Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CDS1”.

Fixed string

M

CDS1

2

SummaryRecordId

 

The Identifier (specific to the Message) of the Summary Record. This Identifier shall also appear in the Detail Records to indicate to which Summary Record the information in each Discrepancy Record relates. 

StringM34
3DiscrepancyDescription

Free-form description summarising the type of discrepancies reported in the detailed records pointing to this Summary Record.

Each Discrepancy Summary Record CDS1 usually provides information for one type of Record Discrepancies. However, it is possible to collate multiple Discrepancy types into one CDS1 Record, In that case, the DiscrepancyDescription describes, in effect, a family of DescriptionTypes.

StringMMathematical inconsistencies
4NumberOfDiscrepanciesNumber of discrepancies reported in the detailed records pointing to this Summary Record.IntegerM12
5

CurrencyOfInvoicing

The currency used for invoicing the items that are the subject of the discrepancie(s) being reported in the detailed records pointing to this Summary Record.

AVSCCAD
6EstimatedRoyaltyImpactAn estimate of the impact to the royalties that are affected by the discrepancie(s) reported in the detailed records pointing to this Summary Record. This allows the recipient to prioritise the discrepancie(s).DecimalM345.123
7CommercialModel

The Type of CommercialModel of the SalesTransaction for which the original claim was made for which the discrepancie(s) are being reported.

AVSOPayAsYouGoModel
8UseType

The nature of a Service as used by a Consumer for which the original claim was made and for which the discrepancie(s) are being reported.

AVSOPermanentDownload
9Territory

The Territory for which the claim was made and for which the discrepancie(s) are being reported.

AVSODE
10ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place for which the claim is made and for which the discrepancie(s) are being reported. 

The ServiceDescription may not contain space characters or underscores.

StringOPremiumService

5.3 Detailed Record Types

 5.3.1 CD01 — Basic Claim Detail Record with Financial Information
This Record provides claim and, potentially, invoice information for a Musical Work that has been used in a specific Sales Context. The Record also describes the Musical Work and the Resource into which the Work has been recorded.

Note that the Cells that describe the Resource or Work are primarily provided for humans to investigate the issues – they are not for automated processing.

Cell Name  Field DefinitionData TypeM/O/C?[1]Example
1

RecordType

The Type of the Record; always to contain “CD01”.

Fixed string

M

CD01

2ClaimId

ProprietaryIdentifier of the Claim, allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

Note: The ClaimID Cell is used to link CXxx Records, if used, to a CD01 Record.

String

C

2345

3

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Record provides details for.

String

M

34

4

DspResourceId

The ProprietaryIdentifier of the Resource provided by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

String

M

12345678

5

ISRC

The ISRC (International Standard Recording Code as defined in ISO 3901) for the SoundRecording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.

ISRC is mandatory when available to the MessageSender.

String

C

USS1Z1412345

6

ResourceTitle

The Title of the SoundRecording as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Bohemian Rhapsody

7DisplayArtistName

The DisplayArtistName that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Queen
8DisplayArtistPartyId

The PartyId of the DisplayArtist as reported by the Licensee if it was reported by the Licensee in the the DSR (or equivalent) Message, to which the Claim Detail Message is a response.

If the DisplayArtistPartyId that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

To be provided when available and when contractually mandated.

PartyIDCISNI::0000000081266409
9

LicensorWorkId

The ProprietaryIdentifier of the Musical Work assigned to the Musical Work by the Licensor

Where this is an unmatched work there needs to be a unique ID generated. This could be the same ID for all unmatched works.

String

M

0974854321/76432-9

10

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

ISWC is mandatory when available to the Licensor and should be represented without dashes.

String

C

T0030749586

11WorkTitle

The ReferenceTitle of the Musical Work

String

M

Bohemian Rhapsody

12AlternativeTitles

Other titles by which the Musical Work is known to the Licensor.

Multiple StringsO 
13

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource as known by the Licensor. The ComposerAuthor Cell in this Record shall be used to communicate all known writers to aid identifying the Musical Work. The ComposerAuthor Cell in the CXxx Record shall be used to communicate the writers on whose behalf a claim is being made.

ComposerAuthor shall be provided based on contractual agreements between the Licensor and the Licensee.

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly.

Multiple String

C

Johann Sebastian Bach

14 ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s).

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. A maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)OISNI::0000000081266409
15

ClaimBasis

The basis for the Rights Claim made by the Licensor.

AVS

MDirect
16ShareClaimedMechanical

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight.

The ShareClaimedMechanical shall be provided as a Decimal between 0 and 100.

DecimalM

33.33

17ShareClaimedPerforming

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the PerformingRight.

The ShareClaimedPerforming shall be provided as a Decimal between 0 and 100.

DecimalM25
18BlendedShareClaimed
ForMechAndPerf

The blended percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight and the PerformingRight.

If, for example a Licensor uses a right share split of 75% for mechanical and 25% for performance, and the Licensor is claiming 50% for the mechanical right and 25% for the performing right, the BlendedShareClaimedForMechAndPerf be (50% x 75%) + (25% x 25%) = 43.75%. The splits used are provided in the Summary Record referenced via the SummaryRecordId.

The BlendedShareClaimedForMechAndPerf shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM3.75
19SalesTransactionId

ProprietaryIdentifier of the Sales Transaction as used in the DSR (or equivalent) Message to which the Claim Detail Message is a response, to identify the individual SalesTransaction composite/record for which the invoice details on a claim is made.

This cell must be communicated if the DSR (or equivalent) Message to which the Claim Detail Message is a response has a SalesTransactionId (or equivalent).

String

C

13463
20

Usages

The number of Usages of the Release or Resource provided to Consumers, including any sales adjustments that are used to calculate the value of the invoice.

Decimal

M

1000.1

21PercentageOfResource
InRelease

A percentage indicating how much of the traded Release is represented by the Resource for which the Basic Post-Usage Claim Details is being made by the Licensor.

The PercentageOfResourceInRelease shall be provided as a Decimal between 0 and 100.

PercentageOfResourceInRelease shall be provided if it has an impact on the royalty calculations. It shall not be used for when providing invoice information for streamed Resources.

Decimal

C

16.25
22

GeneratedRevenue
ExcSalesTax
InCurrencyOfReporting

The revenue generated by the use of all Resources/Releases (as opposed to one single use) in the currency of reporting. If the traded item was a Release, the value shall be pro-rated across the Resources that make up the Release.

Whether the GeneratedRevenueExcSalesTaxInCurrencyOfReporting needs to be reported will depend on the Sales Context. It shall be left empty if no revenue can be directly attributed to the relevant Resource.

The conversion between the GeneratedRevenueExcSalesTaxInCurrencyOfReporting and GeneratedRevenueExcSalesTaxInCurrencyOfInvoicing shall be done in accordance of the information provided in the relevant Summary Record.

Decimal

C

10.07
23

GeneratedRevenue
ExcSalesTax
InCurrencyOfInvoicing

 

The revenue generated by the use of all Resources/Releases (as opposed to one single use) in the currency of invoicing. If the traded item was a Release, the value shall be pro-rated across the Resources that make up the Release.

Whether the GeneratedRevenueExcSalesTaxInCurrencyOfInvloicing needs to be reported will depend on the Sales Context. It shall be left empty if no revenue can be directly attributed to the relevant Resource.

The conversion between the GeneratedRevenueExcSalesTaxInCurrencyOfReporting and GeneratedRevenueExcSalesTaxInCurrencyOfInvoicing shall be done in accordance of the information provided in the relevant Summary Record.

Decimal

C

7.53
24

ClaimedAmount
Mechanical

 

The amount due to the Rights Controller for the MechanicalRight portion for all reported usages in the relevant Sales Context after applying the claim percentage as per RightTypeSplitMechanical communicated in CS01 in the CurrencyOfInvoicing.

Decimal

M

250.51

25ClaimedAmount
Performing

The amount due to the Rights Controller for the PerformingRight portion for a all reported usages in the relevant Sales Context after applying the claim percentage as per RightTypeSplitPerforming communicated in CS01 in the CurrencyOfInvoicing.

Decimal

M

250.51

26

TariffParameterType

The type of tariff parameter that has been used for royalty calculation documented in this Record. The type might include minimum amount or rate payable and must be agreed between sender and recipient.

String

 

O

Minimum|Maximum

27TariffParameterValue

The value of the tariff parameter. 

If the TariffParameterValue is a penny value, then the currency to be used must be clear from the TariffParameterType (either through the use of an appropriate TariffParameterType string or through the provisions of the contract between Licensor and Licensee).

Decimals

C

52.24|72.66

28

ClaimedAmount

 

The amount due to the Rights Controller for all rights for all usages in the relevant Sales Context.

The ClaimedAmount should equal the sum of ClaimedAmountMechanical and ClaimedAmountPerforming.

Decimal

M

751.53

 5.3.2 CD02 — Basic Record for Correcting Claim Detail Records with Financial Information
This Record provides information about a correction to a previously made Claim for a Share for a specific RightsType in a specific Musical Work for a specific Sales Context and/or to invoice details based on such a Claim (whether the Claim is corrected to not). This record shall only be used if, in the view of the Licensor, there is a financial impact for a Rights Controller.

This Record is based on CD01. The Cells from CD01 that can be corrected in CD02 are triplicated in that, for instance, Cell 16 (ShareClaimedMechanical) appears in CD02 as 16a, 16b and 16c which can communicate the value as originally communicated (ShareClaimedMechanicalOriginal), the corrected value (ShareClaimedMechanicalCorrected) and the difference between the two values (ShareClaimedMechanicalDelta).

The cardinalities listed in the M/O/C column only apply to the first of these three Cells. The other two Cells shall only be communicated for those Cells that need correcting and shall be omitted for Cells that do not need correcting.

If the CD01 Cell in question is a multiple value Cell, and one of these values needs correcting, the Licensor shall re-send all other values in addition to the correction in the same order as communicated previously.

 

Cell Name  Field DefinitionData TypeM/O/C?[1]Example
1

RecordType

The Type of the Record; always to contain “CD02”.

Fixed string

M

CD02

2ClaimId

ProprietaryIdentifier of the Claim, allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

The ClaimId will have to be changed when the report is re-generated or the claim is corrected.

Note: The ClaimID Cell is used to link CXxx Records, if used, to a CD02 Record.

String

C

2345

3

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Record provides details for.

String

M

34

4

CorrectedClaimID

The ClaimId of the claim that is corrected in this Record.

StringM1234
5CorrectedClaimMessageIdThe MessageId of the Claim Detail Message (or equivalent) containing the claim that is corrected in this Record.StringM0987
6

DspResourceId

The ProprietaryIdentifier of the Resource provided by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

String

M

12345678

7

ISRC

The ISRC (International Standard Recording Code as defined in ISO 3901) for the SoundRecording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.

ISRC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where Licensors genuinely do not have this information, DDEX has decided to mark this Cell as “Conditional”.

String

C

USS1Z1412345

8

ResourceTitle

The Title of the SoundRecording as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Bohemian Rhapsody

9DisplayArtistName

The DisplayArtistName that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Queen
10DisplayArtistPartyId

The PartyId of the DisplayArtist as reported by the Licensee if it was reported by the Licensee in the the DSR (or equivalent) Message, to which the Claim Detail Message is a response.

If the DisplayArtistPartyId that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

To be provided when available and when contractually mandated.

PartyIDCISNI::0000000081266409
11

LicensorWorkId

The ProprietaryIdentifier of the Musical Work assigned to the Musical Work by the Licensor

Where this is an unmatched work there needs to be a unique ID generated. This could be the same ID for all unmatched works.

String

M

0974854321/76432-9

12

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

ISWC is mandatory when available to the Licensor and should be represented without dashes.

String

C

T0030749586

13WorkTitle

The ReferenceTitle of the Musical Work

String

M

Bohemian Rhapsody

14AlternativeTitles

Other titles by which the Musical Work is known to the Licensor.

Multiple StringsO 
15

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource as known by the Licensor. The ComposerAuthor Cell in this Record shall be used to communicate all known writers to aid identifying the Musical Work. The ComposerAuthor Cell in the CXxx Record may be used to communicate the writers on whose behalf a claim is being made.

ComposerAuthor shall be provided based on contractual agreements between the Licensor and the Licensee.

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly.

Multiple String

C

Johann Sebastian Bach

16 ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s).

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. A maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)OISNI::0000000081266409
17

ClaimBasis

The basis for the Rights Claim made by the Licensor.

AVS

MDirect
18aShareClaimed
MechanicalOriginal

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight.

The ShareClaimedMechanicalCorrected shall be provided as a Decimal between 0 and 100.

DecimalM133.33  
18bShareClaimed
MechanicalCorrected
18cShareClaimed
MechanicalDelta
19aShareClaimed
PerformingOriginal

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the PerformingRight.

The ShareClaimedPerformingCorrected shall be provided as a Decimal between 0 and 100.

DecimalM25
19bShareClaimed
PerformingCorrected
19cShareClaimed
PerformingDelta
20aBlendedShareClaimed
ForMechAndPerfOriginal

The blended percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight and the PerformingRight.

If, for example a Licensor uses a right share split of 75% for mechanical and 25% for performance, and the Licensor is claiming 50% for the mechanical right and 25% for the performing right, the BlendedShareClaimedForMechAndPerf be (50% x 75%) + (25% x 25%) = 43.75%. The splits used are provided in the Summary Record referenced via the SummaryRecordId.

The BlendedShareClaimedForMechAndPerf shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM3.75
20bBlendedShareClaimed
ForMechAndPerfCorrected
20cBlendedShareClaimed
ForMechAndPerfDelta
21SalesTransactionId

ProprietaryIdentifier of the Sales Transaction as used in the DSR (or equivalent) Message to which the Claim Detail Message is a response, to identify the individual SalesTransaction composite/record for which the invoice details on a claim is made.

This cell must be communicated if the DSR (or equivalent) Message to which the Claim Detail Message is a response has a SalesTransactionId (or equivalent).

String

C

13463
22

Usages

The number of Usages of the Release or Resource provided to Consumers, including any sales adjustments that are used to calculate the value of the invoice.

Decimal

M

1000.1

23PercentageOfResource
InRelease

A percentage indicating how much of the traded Release is represented by the Resource for which the Basic Record for Correcting Post-Usage Claim is being made by the Licensor.

The PercentageOfResourceInRelease shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

PercentageOfResourceInRelease shall be provided if it has an impact on the royalty calculations. It shall not be used for when providing invoice information for streamed Resources.

Decimal

C

16.25
24

GeneratedRevenue
ExcSalesTax
InCurrencyOfReporting

The revenue generated by the use of all Resources/Releases (as opposed to one single use) in the currency of reporting. If the traded item was a Release, the value shall be pro-rated across the Resources that make up the Release.

Whether the GeneratedRevenueExcSalesTaxInCurrencyOfReporting needs to be reported will depend on the Sales Context. It shall be left empty if no revenue can be directly attributed to the relevant Resource.

The conversion between the GeneratedRevenueExcSalesTaxInCurrencyOfReporting and GeneratedRevenueExcSalesTaxInCurrencyOfInvoicing shall be done in accordance of the information provided in the relevant Summary Record.

Decimal

C

10.07
25

GeneratedRevenue
ExcSalesTax
InCurrencyOfReporting



The revenue generated by the use of all Resources/Releases (as opposed to one single use) in the currency of invoicing. If the traded item was a Release, the value shall be pro-rated across the Resources that make up the Release.

Whether the GeneratedRevenueExcSalesTaxInCurrencyOfInvloicing needs to be reported will depend on the Sales Context. It shall be left empty if no revenue can be directly attributed to the relevant Resource.

The conversion between the GeneratedRevenueExcSalesTaxInCurrencyOfReporting and GeneratedRevenueExcSalesTaxInCurrencyOfInvoicing shall be done in accordance of the information provided in the relevant Summary Record.

 

Decimal

C

7.53
26a

ClaimedAmount
MechanicalOriginal

 

The amount due to the Rights Controller for the MechanicalRight portion for all reported usages in the relevant Sales Context after applying the claim percentage as per RightTypeSplitMechanical communicated in CS01.

 

Decimal

M

250.51

26bClaimedAmount
MechanicalCorrected
    
26cClaimedAmount
MechanicalDelta
    
27aClaimedAmount
PerformingOriginal

The amount due to the Rights Controller for the PerformingRight portion for a all reported usages in the relevant Sales Context after applying the claim percentage as per RightTypeSplitPerforming communicated in CS01.

 

Decimal

M

250.51

27bClaimedAmount
PerformingCorrected
    
27cClaimedAmount
PerformingDelta
    
28a

TariffParameterType
Original

The type of tariff parameter that has been used for royalty calculation documented in this Record. The type might include minimum amount or rate payable and must be agreed between sender and recipient.

String

 

O

Minimum

28bTariffParameterType
Corrected
29aTariffParameterValue
Original

The value of the tariff parameter. 

TariffParameterValueOriginal and TariffParameterValueCorrected must be provided if a parameter type is being provided. TariffParameterValueDelta must be provided only if the parameter type is not changed.

Decimals

C

52.24

 

29bTariffParameterValue
Corrected
29cTariffParameterValue
Delta
30a

ClaimedAmount
Original 

The amount due to the Rights Controller for all rights for all usages in the relevant Sales Context.

The ClaimedAmount should equal the sum of ClaimedAmountMechanical and ClaimedAmountPerforming.

 

Decimal

M

751.53

30bClaimedAmount
Corrected
30cClaimedAmount
Delta
 5.3.3 CD03 — Basic Claim Detail Record without Financial Information
This Record provides claim information for a Musical Work that is planned to be used in a specific Sales Context. The Record also describes the Musical Work and the Resource into which the Work has been recorded.

Note that the Cells that describe the Resource or Work are primarily provided for humans to investigate the issues – they are not for automated processing.

 

Cell Name  Field DefinitionData TypeM/O/C?[1]Example
1

RecordType

The Type of the Record; always to contain “CD03”.

Fixed string

M

CD03

2

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Record provides details for.

String

M

34

3ClaimId

ProprietaryIdentifier of the Claim, allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

The ClaimId will have to be changed when the report is re-generated or the claim is corrected.

Note: The ClaimID Cell is used to link CXxx Records, if used, to a CD03 Record.

String

C

2345

4

DspResourceId

The ProprietaryIdentifier of the Resource provided by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

String

M

12345678

5

ISRC

The ISRC (International Standard Recording Code as defined in ISO 3901) for the SoundRecording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.

ISRC is mandatory when available to the MessageSender.

String

C

USS1Z1412345

6

ResourceTitle

The Title of the SoundRecording as reported by the Licensee if it was reported by the Licensee in the the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Bohemian Rhapsody

7DisplayArtistName

The DisplayArtistName that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Queen
8DisplayArtistPartyId

The PartyId of the DisplayArtist as reported by the Licensee if it was reported by the Licensee in the DSR (or equivalent) Message, to which the Claim Detail Message is a response.

If the DisplayArtistPartyId that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

To be provided when available and when contractually mandated.

PartyIDCISNI::0000000081266409
9

LicensorWorkId

The ProprietaryIdentifier of the Musical Work assigned to the Musical Work by the Licensor

Where this is an unmatched work there needs to be a unique ID generated. This could be the same ID for all unmatched works.

String

M

0974854321/76432-9

10

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

ISWC is mandatory when available to the Licensor.

String

C

T0030749586

11WorkTitle

The ReferenceTitle of the Musical Work

String

M

Bohemian Rhapsody

12AlternativeTitles

Other titles by which the Musical Work is known to the Licensor.

Multiple StringsO 
13

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource as known by the Licensor. The ComposerAuthor Cell in this Record shall be used to communicate all known writers to aid identifying the Musical Work. The ComposerAuthor Cell in the CXxx Record shall be used to communicate the writers on whose behalf a claim is being made.

ComposerAuthor shall be provided based on contractual agreements between the Licensor and the Licensee.

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly.

Multiple String

C

Johann Sebastian Bach

14 ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s).

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. A maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)OISNI::0000000081266409
15

ClaimBasis

The basis for the Rights Claim made by the Licensor.

AVS

MDirect
16ShareClaimedMechanical

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight.

The ShareClaimedMechanical shall be provided as a Decimal between 0 and 100.

DecimalM

33.33

17ShareClaimedPerforming

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the PerformingRight.

The ShareClaimedPerforming shall be provided as a Decimal between 0 and 100.

DecimalM25
18BlendedShareClaimed
ForMechAndPerf

The blended percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight and the PerformingRight.

If, for example a Licensor uses a right share split of 75% for mechanical and 25% for performance, and the Licensor is claiming 50% for the mechanical right and 25% for the performing right, the BlendedShareClaimedForMechAndPerf be (50% x 75%) + (25% x 25%) = 43.75%. The splits used are provided in the Summary Record referenced via the SummaryRecordId.

The BlendedShareClaimedForMechAndPerf shall be provided as a Decimal  between 0 and 100. 

DecimalM3.75
19PercentageOfResource
InRelease

A percentage indicating how much of the traded Release is represented by the Resource for which the Basic Pre-Usage Claim Detail is being made by the Licensor.

The PercentageOfResourceInRelease shall be provided as a Decimal between 0 and 100.

PercentageOfResourceInRelease shall be provided if it has an impact on the royalty calculations. It shall not be used for when providing invoice information for streamed Resources.

 

Decimal

C

16.25
 5.3.4 CD04 — Basic Record for Correcting Claim Detail Records without Financial Information
This Record provides information about a correction to a previously made Claim for a Share for a specific RightsType in a specific Musical Work. 

This Record is based on CD03. The Cells from CD03 that can be corrected in CD04 are triplicated in that, for instance, Cell 16 (ShareClaimedMechanical) appears in CD02 as 16a, 16b and 16c which can communicate the value as originally communicated (ShareClaimedMechanicalOriginal), the corrected value (ShareClaimedMechanicalCorrected) and the difference between the two values (ShareClaimedMechanicalDelta).

The cardinalities listed in the M/O/C column only apply to the first of these three Cells. The other two Cells shall only be communicated for those Cells that need correcting and shall be omitted for Cells that do not need correcting.

If the CD03 Cell in question is a multiple value Cell, and one of these values needs correcting, the Message Sender shall re-send all other values in addition to the correction in the same order as communicated previously.

 

Cell Name  Field DefinitionData TypeM/O/C? [1] Example
1

RecordType

The Type of the Record; always to contain “CD04”.

Fixed string

M

CD04

2

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Record provides details for.

String

M

34

3ClaimId

ProprietaryIdentifier of the Claim, allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

The ClaimId will have to be changed when the report is re-generated or the claim is corrected.

Note: The ClaimID Cell is used to link CXxx Records, if used, to a CD01 Record.

String

C

2345

4

CorrectedClaimID

The ClaimId of the claim that us corrected in this Record.

StringM1234
5CorrectedClaimMessageIdThe MessageId of the Claim Detail Message (or equivalent) containing the claim that is corrected in this Record.StringM0987
6

DspResourceId

The ProprietaryIdentifier of the Resource provided by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

String

M

12345678

7

ISRC

The ISRC (International Standard Recording Code as defined in ISO 3901) for the SoundRecording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.

ISRC is mandatory when available to the MessageSender. This field is important for Message Recipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where Licensors genuinely do not have this information, DDEX has decided to mark this Cell as “Conditional”.

String

C

USS1Z1412345

8

ResourceTitle

The Title of the SoundRecording as reported by the Licensee if it was reported by the Licensee in the the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Bohemian Rhapsody

9DisplayArtistName

The DisplayArtistName that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

This should be the same as reported in the DSR (or equivalent) Message.

To be provided when available and when contractually mandated.

String

C

Queen
10DisplayArtistPartyId

The PartyId of the DisplayArtist as reported by the Licensee if it was reported by the Licensee in the DSR (or equivalent) Message, to which the Claim Detail Message is a response.

If the DisplayArtistPartyId that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee in the original DSR (or equivalent) Message, to which the Claim Detail Message is a response.

To be provided when available and when contractually mandated.

PartyIDCISNI::0000000081266409
11

LicensorWorkId

The ProprietaryIdentifier of the Musical Work assigned to the Musical Work by the Licensor

Where this is unmatched work there needs to be a unique ID generated. This could be the same ID for all unmatched works.

String

M

0974854321/76432-9

12

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

ISWC is mandatory when available to the Licensor and should be represented without dashes.

String

C

T0030749586

13WorkTitle

The ReferenceTitle of the Musical Work

String

M

Bohemian Rhapsody

14AlternativeTitles

Other titles by which the Musical Work is known to the Licensor.

Multiple StringsO 
15

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource as known by the Licensor. The ComposerAuthor Cell in this Record shall be used to communicate all known writers to aid identifying the Musical Work. The ComposerAuthor Cell in the CXxx Record may be used to communicate the writers on whose behalf a claim is being made.

ComposerAuthor shall be provided based on contractual agreements between the Licensor and the Licensee.

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly.

Multiple String

C

Johann Sebastian Bach

16 ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s).

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. A maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)OISNI::0000000081266409
17

ClaimBasis

The basis for the Rights Claim made by the Licensor.

AVS

MDirect
18aShareClaimed
MechanicalOriginal

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight.

The ShareClaimedMechanical shall be provided as a Decimal between 0 and 100.

DecimalM

33.33

18bShareClaimed
MechanicalCorrected
18cShareClaimed
MechanicalDelta
19aShareClaimed
PerformingOriginal

The unblended (i.e. not rights-split-weighted) percentage that is claimed by the Licensor for the relevant Sales Context for the PerformingRight.

The ShareClaimedPerforming shall be provided as a Decimal between 0 and 100.

DecimalM25
19bShareClaimed
PerformingCorrected
19cShareClaimed
PerformingDelta
20aBlendedShareClaimed
ForMechAndPerfOriginal

The blended percentage that is claimed by the Licensor for the relevant Sales Context for the MechanicalRight and the PerformingRight.

If, for example a Licensor uses a right share split of 75% for mechanical and 25% for performance, and the Licensor is claiming 50% for the mechanical right and 25% for the performing right, the BlendedShareClaimedForMechAndPerf be (50% x 75%) + (25% x 25%) = 43.75%. The splits used are provided in the Summary Record referenced via the SummaryRecordId.

The BlendedShareClaimedForMechAndPerf shall be provided as a Decimal  between 0 and 100. 

DecimalM3.75
20bBlendedShareClaimed
ForMechAndPerfCorrected
20cBlendedShareClaimed
ForMechAndPerfDelta
21aPercentageOfResource
InReleaseOriginal

A percentage indicating how much of the traded Release is represented by the Resource for which the Basic Record for Correcting Pre-Usage Claim is being made by the Licensor.

The PercentageOfResourceInRelease shall be provided as a Decimal between 0 and 100.

PercentageOfResourceInRelease shall be provided if it has an impact on the royalty calculations. It shall not be used for when providing invoice information for streamed Resources.

Decimal

C

16.25
21bPercentageOfResource
InReleaseCorrected
21cPercentageOfResource
InReleaseDelta
 5.3.5 CX01 — Auxiliary Information
This Record that can be used to provide further details on the claim and/or invoice details. Including a CX01 Record into a Claim Detail Message is optional and will depend on the commercial relationship between Licensee and Licensor.

If auxiliary information for multiple writers and/or music publishers is to be provided, multiple CX01 Records must be used.

Cell Name  Field DefinitionData TypeM/O/C? [1] Example
1

RecordType

 

The Type of the Record; always to contain “CX01”.

Fixed string

M

CX01

2AuxiliaryRecordId

The Identifier (specific to the Message) of the Auxiliary Record.

Taken together with the SenderPartyId and MessageId this shall be globally and perpetually unique.

StringM124
3ClaimID

The Identifier (specific to the Message) of the CDxx Claim Record that this Auxiliary Record provides additional information for.

StringM0987
4SharePictureDateTime

The date and time that represents the moment when the Rights Share data was, in the view of the Licensor, valid. In many cases this is the same as the SharePictureExtractionDateTime but may, especially for historical data, be different.

The only allowed format is ISO 8601: YYYY-MM-DDThh:mm:ssTZD.

ISO datetimeO2014-12-14T00:00:00Z
5SharePictureExtractionDateTime

The date and time at which the Licensor extracted the Rights Share data from its production systems which are contained in the Claim Detail Message. The only allowed format is ISO 8601: YYYY-MM-DDThh:mm:ssTZD.

ISO datetimeO

2014-12-14T10:05:00Z

6

ComposerAuthor

The Name of a ComposerAuthor of the Musical Work used in creating the Resource for whom the claim is being made.

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly. The ComposerAuthor Cell in this Record shall be used to communicate the writers on whose behalf a claim is being made.

The ComposerAuthor Cell in the CDxx Record shall be used to communicate all known writers to aid identifying the Musical Work.

Multiple String

O

Johann Sebastian Bach

7ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s)

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)



OISNI::0000000081266409

8

ComposerAuthorSocietyAffiliation

The name of a Musical Work rights society to which the relevant ComposerAuthor is affiliated in the territory in the Summary Record as referenced via the SummaryRecordId.

The order of the individual strings in each of the ComposerAuthor, ComposerAuthorPartyId in the CDxx Records, ComposerAuthorSocietyAffiliation and ComposerAuthorSocietyAffiliationPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. A maximum of one ComposerAuthorSocietyAffiliation can be provided for each ComposerAuthor.

Multiple String

C

GEMA
9

ComposerAuthorSocietyAffiliationPartyId

An identifier for the the Musical Work rights society listed above.

The order of the individual string in each of the ComposerAuthor, ComposerAuthorPartyId in the CDxx RecordsComposerAuthorSocietyAffiliation and ComposerAuthorSocietyAffiliationPartyId cells shall be the same so that the Licensee is able to relate names and IDs correctly. 

A maximum of one ComposerAuthorSocietyAffiliationPartyId can be provided for each ComposerAuthorSocietyAffiliation.

Multiple PartyID(s)

CISNI::0000000081266409
10MusicPublisherName

The party that controls the Share claimed in the CD01 or CD03 Record in the territory indicated in the referenced Summary Record at the time of the Sales Transaction provided by the Licensee in the original DSR (or equivalent) Message. This may differ from the Licensor in cases where the Licensor represents the Music Publisher and is not the Rights Controller in its own right.

Multiple StringOSony/ATV
11MusicPublisherPartyIdAn identifier for the Music Publisher in the form namespace::identifier. A MusicPublisherPartyId may only be provided where a MusicPublisherName is provided.

Multiple PartyID(s)

CISNI::0000000081266409
 5.3.6 CDD1 – Record for Claim Detail Record Discrepancies
This Record provides information about discrepancies that only impact one Record (Summary Records notwithstanding), that a Licensee has detected in a received Claim Detail Message.

If such a discrepancy is reported on a detailed Record which has a direct impact on a Summary Record, there is no requirement to also report the consequential discrepancy on the Summary Record.

 

Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CDD1”.

Fixed string

M

CDD1

2ClaimDiscrepancyId

Proprietary identifier of the claim discrepancy, allocated by the Licensee. Taken together with the MessageId this shall be globally and perpetually unique. 

StringM43DF
3ClaimId

ProprietaryIdentifier of the Claim which is being reported on as allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

String

C

2345

4

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Claim Detail Discrepancy Record provides details for.

Each Summary Record referenced through this SummaryRecordId provides the CommercialModelUseTypeTerritory and ServiceDescription for the discrepancy reported in this Record.

String

M

34

5DiscrepancyType

The type of the discrepancy.

AVSMSalesDataIncorrect
6DiscrepantRecordType

The Type of the Record in which a discrepancy has been detected (e.g. for a discrepancy in a Basic Record to describe Resources for which Claims and/or Invoice Details are Provided this should be CD01).

StringMCD01
7DiscrepancyDescription

Description of the discrepancy found. This text, together with the DisrepancyType, is intended to give the Licensor processing the Claim Detail Discrepancy Notification information as to what the Licensee that sent of the Claim Detail Discrepancy Notification objects to.

StringMNumber is inconsistent with sales report.
8DiscrepantCellName

The name of the Cell where the discrepancy was found. If the nineteenth Cell in a CD01 Record is found to be discrepant, this Cell shall contain BlendedShareClaimedForMechAndPerf.

StringM

Usages

9DiscrepantRecordId

The Record in which a discrepancy has been detected. The identifier used will vary between Record Types For:

  • CDMH and SRFO – use MessageId;
  • CS01 and CS02 – use SummaryRecordId; and
  • CD01, CD02, CD03 or CD04 – use ClaimId.
  • CX01 – use AuxiliaryRecordId

If the above information is not available or unique, this Cell is to be left empty.

StringC

4

10

DiscrepantRecordLine

The line number of the Record in which a discrepancy has been detected. Header and Footer Records as well as empty Records in accordance with Clause 6.7 of Part 1 of the Claim Detail Message Suite Standard and commented-out Records in accordance with Clause 6.8 of Part 1 of the Claim Detail Message Suite Standard shall be included when counting.

This is a "last resort" and should only to be used, if no unique DiscrepantRecordId can be provided.

IntegerC2345
11

ActionTaken

The action taken by the Licensee with respect of the claim and/or invoice details. The value for this cell, and whether the Cell should be used in the first place, is subject to the bilateral agreement between the Licensee and the Licensor.

Implementers are advised that DDEX may change this field into an Allowed Value Set once DDEX has obtained information on how it is being used in the marketplace.

String

C

ClaimOrInvoiceAccepted
12ValueFound

The value found in the Claim Detail Message received and which the Licensee that sent the Claim Detail Discrepancy Notification objects to.

This needs to be sent unless the Claim Detail Message message did not contain any value.

StringC105
13ValueExpected

The value that the Licensee that sent the Claim Detail Discrepancy Message would have expected in the relevant Cell.

This needs to be sent if the Licensee that sent the Claim Detail Discrepancy Notification has a value it expected in the discrepant Cell.

StringC

110

 

14

RoyaltyImpactInCurrencyOfInvoicing

 

The sum of all ClaimedAmount Cells in all CD01/CD03 Records and ClaimedAmountDelta in all CD02/CD04 Records that are affected by the discrepancy in the currency of accounting used in the Claim Detail Message unless the message did not contain any value.

A RoyaltyImpactInCurrencyOfInvloicing shall not be reported if the impact is unquantifiable.

The amount reported should be the amount that was provided in the Claim Detail Message by the Licensor for which the discrepancy has been detected.

This is ClaimedAmount in the relevant CD01/CD03 records and ClaimedAmountDelta in CD02/CD04 records.

Decimal

C

123.43
 5.3.7 CDD2 – Record for Over-claim Discrepancies
This Record provides information about a potential over claim that a Licensee has detected as a result of receiving Claim Detail Messages from two or more Licensors. Each CDD2 Record shall be followed by two or more CDD3 Records which provide claim information for all the Licensors whose information in their respective Claim Detail Messages has contributed to the over-claim.

 

Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CDD2”.

Fixed string

M

CDD2

2ClaimDiscrepancyIDProprietary identifier of the overclaim discrepancy, allocated by the Licensee. Taken together with the MessageId this shall be globally and perpetually unique. StringM103
3ClaimId

ProprietaryIdentifier of the Claim that is the subject of the discrepancy as allocated by the Licensor. Taken together with the SenderPartyId and MessageId of the Claim Detail Message this shall be globally and perpetually unique.

String

C

2345

4


SummaryRecordId

The Identifier (specific to the Message) of the Summary Record that this Claim Detail Discrepancy Notification provides details for.

Each Summary Record referenced through this SummaryRecordId provides the CommercialModelUseTypeTerritory and ServiceDescription for the discrepancy reported in this Record.

String

M

34

5DiscrepancyType

The type of the discrepancy, always Overclaim. 

AVSMOverclaim
6ActionTaken

The action taken by the Licensor with respect of the claim and/or invoice details. The value for this cell, and whether the Cell should be used in the first place, is subject to the bilateral agreement between the Licensee and the Licensor.

Implementers are advised that DDEX may change this field into an Allowed Value Set once DDEX has obtained information on how it is being used in the marketplace.

StringC 
7

DspResourceId

The Proprietary Identifier of the Resource provided by the Licensee in the original DSR (or equivalent) Message, that is the subject of the discrepancy.

String

M

1234567
8ResourceTitle

The Title of the Sound Recording as reported by the Licensee if it was reported by the Licensee in the the original DSR (or equivalent) Message, that is the subject of the discrepancy.

If the Title was reported by the Licensor in the the Claim Detail Message, it shall be provided here.

String

C

Bohemian Rhapsody

9DisplayArtistName

The DisplayArtistName that was used by a Licensee when presenting Artist details of the Resource, that is the subject of the discrepancy.

If the DisplayArtistName was reported by the Licensee in the the original DSR (or equivalent) Message, and reported in the Claim Detail Message to which this Claim Detail Discrepancy Notification is a response, it shall be provided here.

StringCQueen
10DisplayArtistPartyId

The Party Id of the DisplayArtist as reported by the Licensee in the the DSR (or equivalent) Message, that is the subject of the discrepancy.

If the DisplayArtistPartyId that was used by a Licensee when presenting Artist details of the Resource to a Consumer and as reported by the Licensee if it was reported by the Licensee, and reported in the Claim Detail Message to which this Claim Detail Discrepancy Notification is a response, it shall be provided here.

PartyIDCISNI::0000000081266409
11SalesTransactionIdThe identifier of the Sales Transaction in a DSR (or equivalent) Message for which the Claim Detail Message provided a claim to which this Claim Detail Discrepancy Notification is a response identifying where the Licensee has detected a discrepancy.StringM1323423
12UsagesThe Number of Usages reported in the original DSR (or equivalent) MessageDecimalM335213.2
13SumShareClaimedMechanical

Sum of all claims for the Mechanical Right for the relevant Sales Context that are the subject of the discrepancy.

The SumShareClaimedMechanical shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM50
14SumShareClaimedPerforming

Sum of all claims for the Performing Right for the relevant Sales Context that are the subject of the discrepancy.

The SumShareClaimedPerforming shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM100
15

SumBlendedShareClaimedForMechAndPerf

Sum of all blended percentages that are claimed for the MechanicalRight and the PerformingRight that are the subject of the discrepancy.

The SumBlendedShareClaimedForMechAndPerf shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM75
16

RoyaltyImpactInCurrencyOfInvoicing

 

The sum of all ClaimedAmount Cells in all CD01 Records and ClaimedAmountDelta in CD02 Records that are affected by the discrepancy in the currency of accounting used in the Claim Detail Message unless message did not contain any value.

RoyaltyImpactInCurrencyOfInvoicing shall not be reported if the impact is unquantifiable.

The amount reported should be the amount that was provided in the Claim Detail Message by the Licensor for which the discrepancy has been detected.

This is ClaimedAmount in the relevant CD01 records and ClaimedAmountDelta in CD02 records.

Decimal

C

123.43

 


 5.3.8 CDD3 – Licensor-specific Record for Over-claim Discrepancies
This Record provides information about each of the Licensor's claims that has contributed to the over-claim summarised in the corresponding CDD2 record.


Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “CDD3”.

Fixed string

M

CDD3

2ClaimDiscrepancyID

The identifier of the over-claim as provided in the parent CDD2 Record.

Taken together with the SenderPartyId this shall be globally and perpetually unique.

StringM103
3RightsControllerName

The name of the Rights Controller whose claim contributes to the discrepancy.

StringMMyCo
4

RightsControllerPartyId

The PartyId of the RightsController.

PartyIDMDPIDA12345SDF::6547996
5ClaimId

ProprietaryIdentifier of the Claim that contributes to the discrepancy, as originally allocated by the Licensor.

StringM76fA
6LicensorWorkId

The ProprietaryIdentifier of the Musical Work that contributes to the discrepancy as  assigned to the Musical Work by the Rights Controller.

String

M

0974854321/76432-9

7

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork that is the subject of the discrepancy. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

ISWC is mandatory when provided by the Licensor in the Claim Detail Message to which this Claim Detail Discrepancy Licensor is a response.

String

C

T0030749586

8ShareClaimedMechanical

Claims for the Mechanical Right that are the subject of the discrepancy.

The ShareClaimedMechanical shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM40
9ShareClaimedPerforming

Claims for the Performing Right that are the subject of the discrepancy.

The ShareClaimedPerforming shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM40
10

BlendedShareClaimedForMechAndPerf

 

Blended claim for the MechanicalRight and the PerformingRight that contribute to the discrepancy.

The BlendedShareClaimedForMechAndPerf shall be provided as a decimal with 0 representing 0% and 100 representing 100%.

DecimalM125
11

WorkTitle

The Title of the Musical Work that is the subject of the discrepancy as known by the Licensor of the original Claim Detail Message to which this Claim Detail Discrepancy Licensor is a response.

WorkTitle is mandatory when provided by the Licensor in the Claim Detail Message to which this Claim Detail Discrepancy Licensor is a response.

String

M

C

Bohemian Rhapsody

12AlternativeWorkTitles

Other titles by which the Musical Work that contributes to the discrepancy is known to the Licensor of the original Claim Detail Message to which this Claim Detail Discrepancy Notification is a response.

AlternativeWorkTitle is mandatory when provided by the Licensor in the Claim Detail Message to which this Claim Detail Discrepancy Licensor is a response.

Multiple Strings

O

C

 
13

ComposerAuthor

The Name of a Writer of the Musical Work that is the subject of the discrepancy as used in creating the Resource as known by the Licensor.

ComposerAuthor shall be provided based on contractual agreements between Licensor and Licensee.

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensor is able to relate names and IDs correctly.

Multiple String

C

Johann Sebastian Bach

14ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s).

The order of the individual strings in each of the ComposerAuthor, and ComposerAuthorPartyId cells shall be the same so that the Licensor is able to relate names and IDs correctly. A maximum of one ComposerAuthorPartyId can be provided for each ComposerAuthor.

Multiple PartyID(s)OISNI::0000000081266409

Evaluation Licence for DDEX Standards

 

 

Subject to your compliance with the terms and conditions of this Agreement, DDEX™ grants you a limited, nonexclusive, non-transferable, non-sublicenseable, royalty-free licence solely to reproduce, distribute within your organisation, and use the DDEX standard specifications (“DDEX Standards”) solely for the purpose of your internal evaluation. You may not make any commercial use of the DDEX Standards under this agreement. No other licences are granted under this agreement.

No representations or warranties (either express or implied) are made or offered by DDEX with regard to the DDEX Standards. In particular, but without limitation, no representations or warranties are made in relation to:

  1. The suitability or fitness of the standards for any particular purpose;
  2. The merchantability of the standards;
  3. The accuracy, completeness, relevance or validity of the standards; or
  4. The non-infringement of any third party intellectual property rights related to the DDEX Standards.

Accordingly, DDEX and/or its members shall not be liable for any direct, indirect, special, consequential or punitive loss or damages howsoever arising out of or in connection with the use of the standards. IN THE EVENT THAT ANY COURT OF COMPETENT JURISDICTION RENDERS JUDGEMENT AGAINST DDEX AND/OR ITS MEMBERS NOTWITHSTANDING THE ABOVE LIMITATION, THE AGGREGATE LIABILITY TO YOU IN CONNECTION WITH THIS AGREEMENT SHALL IN NO EVENT EXCEED THE AMOUNT OF ONE HUNDRED U.S. DOLLARS (US$ 100.00).

Users of the DDEX Standards are cautioned that it is subject to revision. Users are recommended to use the latest versions, which are available at http://www.ddex.net. The use of outdated versions of the standards is not recommended but may be required by agreement between implementers in particular cases.