RegistrationStatus

As work progresses toward the next iteration of the RDR Standard (RDR-N 2.0), it is recognised that additional enhancements will be required for the RCSUM message in the future. Until those changes are introduced, it is strongly recommended that the RegistrationStatus below be applied consistently, with the element treated as mandatory as a business rule and generally be limited to the following outcomes:

• RegistrationRejected: A State in which the registration of a Resource has been rejected due to errors.
  This value should be used when a Critical error has been reported. This state indicates that no royalty payout will occur unless a new and corrected DeclarationOfSoundRecordingRightsClaimMessage is submitted.

• ResourceRegisteredValid: The message is a valid MLC message and the MessageSender was able to register the claim based on the claim data provided in the message. However, not all of the fields noted as to be included in the core profile are available to the MessageSender. The bilateral agreement between MessageSender and MessageRecipient defines what such a registration entails and whether the MessageSender will be able to pay out any revenue generated based on that claim.
  This value should be used when the claim can be registered and any errors present are informational only. Although the data is acceptable for processing and payout, it remains advisable to update internal systems.

• ResourceRegisteredInvalid: A State in which a resource has been registered as being invalid due to errors, and is not payable.
  ResourceRegisteredInvalid is important particularly for music licensing companies and joint societies that follow specific data-quality or contributor-validation rules. RDx supports this value to accommodate the differing policies across societies — especially with respect to performer and contributor data — allowing claims to be processed even when certain non-blocking issues require follow-up. Local business rules will determine whether, and to what extent, royalties can be paid in such cases.

• The value PendingReview (indicating acknowledgment of repertoire receipt prior to evaluation of registration and claim status) is considered unhelpful within the decision flow, as it does not provide rights holders—typically producers—with clear information about why a registration is paused or when royalty payments may be expected. For this reason, PendingReview should be avoided until further notice.

These values should also be interpreted in conjunction with ErrorType and ErrorSeverity that together determine the appropriate RegistrationStatus: