ErrorType

To improve consistency in how errors are classified and interpreted across RDx and music licensing companies, the allowed value set (AVS) for ErrorType has been reviewed and updated based on practical experience. This update, published in December 2025, ensures greater conformance, clearer communication, and improved overall usability of the RCSUM message.

As part of this harmonisation effort, a number of ErrorTypes have been deprecated and a more precise set of values has been added to be instead. These new values were carefully designed to reflect the actual kinds of errors encountered during validation and to support more standardised error handling without requiring changes to the underlying MLC 1.4 schema.

ErrorType is formally defined as “A classification of errors encountered during data validation, based on their nature and cause. The error type specifies whether an error is due to missing data, invalid format, or logical/semantic inconsistency and provides input into the determination of the associated ErrorSeverity” and the following values are recommended to be used:

  • MissingValueError: An error caused by the absence of a required data element. This requirement may be unconditional (mandatory) or conditional, based on business rules or validation logic. The error signals that the expected value is missing, though its severity may vary depending on the context.

  • FormatSyntaxError: An error caused by data in an invalid format, e.g. with an incorrect type, or including a value not allowed by an AVS. This error indicates that the submitted data does not conform to the expected schema or business rules, preventing proper processing until corrected.

  • LogicSemanticError: An error caused by data that is correct in format but invalid due to logic or business rules, or part of an unauthorised submission. Examples include the use of dummy or placeholder values, submission of data by an unauthorized source, or violations of interdependent business rules that create logical inconsistencies. This error indicates that, although the format is correct, the data is invalid in context and cannot be processed as intended.