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 Name | Field Definition | Data Type | M/O/C? | Example | |
---|---|---|---|---|---|
1 | RecordType | The Type of the Record; always to contain “ | Fixed string | M | CDD1 |
2 | ClaimDiscrepancyId | Proprietary identifier of the claim discrepancy, allocated by the Licensee. Taken together with the MessageId this shall be globally and perpetually unique. | String | M | 43DF |
3 | ClaimId | 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 | String | M | 34 |
5 | DiscrepancyType | The type of the discrepancy. | AVS | M | SalesDataIncorrect |
6 | DiscrepantRecordType | 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 | String | M | CD01 |
7 | DiscrepancyDescription | 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. | String | M | Number is inconsistent with sales report. |
8 | DiscrepantCellName | The name of the Cell where the discrepancy was found. If the nineteenth Cell in a | String | M | Usages |
9 | DiscrepantRecordId | The Record in which a discrepancy has been detected. The identifier used will vary between Record Types For:
If the above information is not available or unique, this Cell is to be left empty. | String | C | 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 | Integer | C | 2345 |
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 |
12 | ValueFound | 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. | String | C | 105 |
13 | ValueExpected | 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. | String | C | 110
|
14 | RoyaltyImpactInCurrencyOfInvoicing
| The sum of all A 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 | Decimal | C | 123.43 |