Examples

To ensure that an RCSUM conveys the correct and complete message, all required information outlined above must be provided. Only when ErrorType and ErrorSeverity are used together can the full business context be understood, enabling an accurate determination of the resulting RegistrationStatus and providing rights holders with clear expectations regarding royalty payouts.

The table below illustrates example scenarios demonstrating how different combinations of error type and severity map to registration outcomes and their associated implications for royalty distribution.

ErrorType

Example Context

ErrorSeverity

Resulting RegistrationStatus

MissingValueError

ISRC missing (mandatory identifier)

Critical

RegistrationRejected — no royalties payable

MissingValueError

Optional “language” field missing

Warning

ResourceRegisteredInvalid — accepted but flagged; no payout impact

FormatSyntaxError

Invalid date format in ReleaseDate

Critical

RegistrationRejected — processing blocked until corrected

LogicSemanticError

Unauthorised submitter ID

Critical

RegistrationRejected — no royalties payable

LogicSemanticError

Placeholder value (“TBD”) provided in Genre

Warning

ResourceRegisteredInvalid — accepted with warning