Candidate Standard

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Current »

This section of the DDEX Knowledge Base contains Version 1.0 of Part 4 (Notification of Record Discrepancies) 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 Profile to communicate discrepancies that a Licensee has detected, or believes to have detected a Record Discrepancy (as described in Clause 2.1) in a Claim Detail Message (or similar) it has received from a Licensor.

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 1 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 defined in this Part provides a mechanism for Licensees who have received Claim Detail Messages (or an equivalent message) to respond with a Claim Detail Record Discrepancy Notification should they determine that the Claim Detail Messages contain "discrepancies", i.e. issues that the recipient of the Claim Detail Messages has determined may impact the calculation of the royalties. While the resolution of such discrepancies is out of scope, Licensees are expected to use the Claim Detail Record 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 a Claim Detail Record Discrepancy Notification, if it detects:

  • Structural errors in the message such as missing mandatory Record Types or Cells;
  • Use of allowed values not supported by the Claim Detail Message Suite Standard;
  • Missing Record Types or Cells that are technically optional or conditional but that are agreed to be present by the Licensor and Licensee in their bilateral agreement(s);
  • Data in Cells that lead to discrepancies in royalty calculations between the information provided in the Claim Detail Message received by the Licensee and its own calculations; and/or
  • Any other discrepancies of this nature that are agreed between Licensor and Licensee.

Claim Detail Record Discrepancy Notifications 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.

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 Profile for the Notification of Line Item Discrepancies

 5 Profile for the Notification of Claim Detail Record Discrepancies
This standard defines the choreography for reporting Claim Detail Record Discrepancies depicted below. 

 

Unless specifically agreed otherwise between the Licensee and the Licensor, a Licensee may only send one Claim Detail Record Discrepancy Notification for each Claim Detail Message (or equivalent) received; for the purpose of this, Corrections are considered new Claim Detail Messages. 

Items in Claim Detail Message(s) received that are not subject to any discrepancy may be progressed in accordance with relevant licence agreements.

A Claim Detail Record Discrepancy Notification created in accordance with this Profile comprises:

  1. One Header Record CDMH;
  2. 1-n Summary Record CDS1;
  3. One or more Discrepancy Records CDD1;
  4. One Footer Record SRFO.

Details about these Record Types are provided in Part 2 of this Standard.

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 RecordDiscrepancy 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:

  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.

  • No labels