This section of the DDEX Knowledge Base contains Version 1.0 of Part 5 (Notification of Over-Claim Discrepancies) of the Claim Detail Message Suite Standard
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 Profile to communicate discrepancies that a Licensee has detected, or believes to have detected, that there is an Over-claim Discrepancy (as described in Clause 2.1) in a Claim Detail Message (or similar) it has received from a Licensor.
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".
The message defined in this Part provides a mechanism for Licensees who have received such Claim Detail Messages (or an equivalent message) to respond with an Over-claim Discrepancy Notification should they determine that the Claim Detail Messages contain "over-claim discrepancies", i.e. issues that the recipient of the Claim Detail Messages has determined indicate that two or more Licensors have made claims in respect of a single Musical Work that exceed 100% of the total allowed Claim. While the resolution of such discrepancies is out of scope, Licensees are expected to use the Over-claim Discrepancy Notification to signal such discrepancies to Licensors and subsequently work with those organisations to resolve them.
A Licensee that has received a Claim Detail Message (or equivalent message), including a message containing corrections, can respond to it with an Over-claim Discrepancy Notification, if it detects over-claims between Claim Detail Messages from multiple Licensors.
The Over-claim Discrepancy Notification may also be sent by triggers independent of the receipt of a Claim Detail Message (or equivalent message).
2.2 Organisation of the Standard
This Part of the Claim Detail Message Suite Standard comprises five clauses. Clauses 1–4 provide an introduction, scope and a list of core terms and abbreviations. Clause 5 then defines the Profile for communicating discrepancies.
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. Claim Detail Message Suite Standard - Part 1: Architecture.
DDEX. Claim Detail Message Suite Standard - Part 2: Record Type Definitions.
DDEX. Digital Sales Reporting Message Suite Standard - Part 2: Allowed Value Sets.
5 Profile for the Notification of Over-claim Discrepancies
5 Profile for the Notification of Over-Claim Discrepancies
This standard defines the choreography for reporting Over-Claim Discrepancies depicted below.
Items in Claim Detail Message(s) received that are not subject to any discrepancy may be progressed in accordance with relevant licence agreements.
An Over-Claim Discrepancy Notification created in accordance with this Profile comprises:
One Header Record CDMH;
1-n Summary Record CDS1;
One or more Over-Claim Discrepancy Records CDD2
each CDD2 must be followed by 2-n CDD3 Records that provide details regarding the rights claims provided to the Licensor from, potentially, all Licensors that contribute to the over-claim;
One Footer Record SRFO.
Details about these Record Types are provided in Part 2 of this Standard.
If a Licensee receives Claim Detail Messages from one Licensor that, on its own, contains an over-claim, the Licensee should use the Profile for Reporting Line Item Discrepancies as defined in Part 4 of this Standard as there is a high likelihood of an underlying data issue (rather than an over-claim).
To indicate that a Claim Detail Discrepancy Notification is created in accordance with Profile, the Profile Cell in the Header Record shall be set to OverClaimDiscrepancy and the ProfileVersion Cell to 1.0.
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:
The suitability or fitness of the standards for any particular purpose;
The merchantability of the standards;
The accuracy, completeness, relevance or validity of the standards; or
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.