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.

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

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.

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

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.

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]].

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.

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.

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. 

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.

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.

The PartyId of the Rights Controller

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. 

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. 

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.  

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%).

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%).

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%.

O

60

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.

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.

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%.

O

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%.

O

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%.

O

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).

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).

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.

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

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.

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.

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.

Sum of all the GeneratedRevenueExcSalesTax InCurrencyOfReporting in CDxx records. 

Sum of all the GeneratedRevenueExcSalesTax-InCurrencyOfInvoicing in CDxx records. 

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.

The value or values of such parameters.

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

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. 

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.

The PartyId of the Rights Controller

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. 

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. 

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%).

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%).

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. 

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.

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

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.

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

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.

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.

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.

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.

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.

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.

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.

The basis for the Rights Claim made by the Licensor.

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.

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%.

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).

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.

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.

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.

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.

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.

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.

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

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).

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.

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

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.

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

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”.

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.

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.

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.

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.

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.

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.

The basis for the Rights Claim made by the Licensor.

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.

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%.

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).

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

The basis for the Rights Claim made by the Licensor.

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.

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. 

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.

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

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

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.

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”.

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.

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.

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.

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.

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.

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.

The basis for the Rights Claim made by the Licensor.

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.

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. 

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.

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

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

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

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.

2014-12-14T10:05:00Z

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.

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.

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 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 ComposerAuthorSocietyAffiliationPartyId can be provided for each ComposerAuthorSocietyAffiliation.

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 PartyID(s)

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

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.

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 CommercialModel, UseType, Territory and ServiceDescription for the discrepancy reported in this Record.

The type of the discrepancy.

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).

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.

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.

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.

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.

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.

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.

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 CommercialModel, UseType, Territory and ServiceDescription for the discrepancy reported in this Record.

The type of the discrepancy, always Overclaim. 

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.

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.

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.

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.

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%.

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%.

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.

A 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.

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.

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

The PartyId of the RightsController.

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

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.

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.