# Repertoire and Registration Management for Music Rights Organizations > Give PROs, MROs and the MLC one system to intake, validate and manage repertoire across CWR and DDEX RDR, with acknowledgements and dedup at intake. - Segment: Music Rights Organization - Platform: Noctil Platform - Capabilities: DataFort, ProcessEngine, MatchIQ, OrgLink - Author: Jacob Varghese - Published: 2026-11-03 - Source: https://www.noctil.com/use-cases/repertoire-registration-management-for-music-rights-organizations **In short:** The Noctil Platform gives music rights organizations one system for taking in, validating and managing their repertoire. Musical work registrations arrive in CWR from publishers. Sound recording and performer data arrives in DDEX RDR or DDEX MLC from labels and performers, plus member portal and partner files. DataFort validates each submission against standards and the society's own rules and returns acknowledgements. ProcessEngine runs review, rejection and resubmission workflows. The repertoire, member mandates and exchange with sister societies and industry databases stay versioned and auditable, with an extensible data model for new requirements such as AI attribution and consent. --- _Take in every registration, validate it once, and keep your repertoire right. For PROs, MROs, The MLC and neighbouring rights societies managing musical work and sound recording repertoire, member mandates and exchange with sister societies._ ## The Situation Music rights organizations sit at the centre of the royalty chain. Performing and mechanical rights organizations and The MLC hold the musical work repertoire their members register. Neighbouring rights societies hold the sound recordings, performers and rightsholders they represent. That repertoire is built from a constant stream of registrations, from members, administrators, labels, performers and sister societies abroad. It is the foundation for everything that follows: matching usage, calculating distributions, and paying members accurately. ## The Problem Keeping that repertoire accurate is a daily operational challenge: - **Many intake formats.** Registrations arrive as CWR files from publishers, DDEX RDR or DDEX MLC files from labels and performers, spreadsheets, member portal submissions and partner society exports, each in a different version or variant. - **Society-specific validation.** On top of industry standards, every organization applies its own rules for parties, shares, identifiers and territories. Each submission has to be checked, accepted or rejected, and acknowledged back to the sender. - **Rejections and resubmissions.** Rejected registrations have to be tracked until they are corrected, or the related income stays undistributed. - **Members and mandates.** The rights, territories and periods each member has assigned to the organization change over time and decide what the organization can license and collect. - **Exchange with the wider network.** Repertoire has to be shared with sister societies and industry databases, such as the CISAC ISWC network for musical works and SCAPR's VRDB and IPN for performers, and kept in sync. - **Rigid legacy systems.** Many society systems are hard to extend for new requirements, such as AI attribution and consent, and offer limited version control or audit trails. ## The Solution The Noctil Platform gives music rights organizations one system for intake, validation, repertoire and exchange. 1. **Multi-format intake with DataFort.** DataFort ingests registrations in every common standard and variant and normalizes them into one repertoire: | Repertoire | Typical intake and exchange formats | | --- | --- | | Musical works (PROs, MROs, The MLC) | CWR (Common Works Registration), member portal and partner files | | Sound recordings and performers (neighbouring rights) | DDEX RDR, including the earlier DDEX MLC versions, member portal and partner files | | Exchange with sister societies and databases | CWR, DDEX RDR, and partner-specific formats for networks such as the CISAC ISWC network and SCAPR VRDB | 2. **Validation and acknowledgement.** Every submission is checked against industry standards and the organization's own rules for parties, shares, identifiers and territories. Acknowledgements, such as CWR ACK files, are returned to the sender automatically. 3. **Rejection and resubmission workflows with ProcessEngine.** ProcessEngine tracks every rejected registration until it is corrected, notifies the submitter, and routes edge cases to staff for review. 4. **Members and mandates.** Member agreements are recorded with the rights, territories and periods assigned, so the organization always knows what it can license and collect. 5. **Duplicate prevention at intake.** New registrations are checked against the existing repertoire before they are added, using MatchIQ, so duplicates are caught at the door. 6. **Partner and member portal with OrgLink.** Sister societies, agencies, publishers, labels and administrators get their own connected accounts through OrgLink. They can submit registrations, see acceptance and rejection status, correct errors and review their mandates in one place. Record-level and attribute-level permissions control exactly what each partner can see and change, so partner integration is seamless and secure. 7. **Extensible data model.** Industry-standard attributes are supported out of the box, and the organization can add custom fields as needs change, such as AI attribution and consent flags. 8. **Version control, audit trail and rollback.** Every change to a work, recording, party or share is versioned with who made it and when, and can be rolled back. ## The Result - **One system** for intake, validation, repertoire, mandates and exchange, with partners and members connected through one secure portal - **Every major format accepted**, including CWR, DDEX RDR and DDEX MLC, without separate tools for each - **Lower rejection rates and faster resubmissions**, through clear validation and tracked correction workflows - **Accurate mandates**, so licensing and collection reflect what each member has actually assigned - **A cleaner repertoire**, with duplicates caught at intake - **Full auditability**, with version control and rollback for every change - **Ready for what's next**, with an extensible data model for AI attribution, consent and new industry requirements ## Frequently Asked Questions **How do music rights organizations manage incoming registrations?** The Noctil Platform takes in registrations in CWR, DDEX RDR, DDEX MLC and partner formats, validates them against standards and the organization's own rules, returns acknowledgements, and tracks rejections until they are corrected. **Does Noctil support CWR acknowledgements?** Yes. Acknowledgement files are generated and returned to submitters automatically after validation. **Can Noctil handle both musical works and sound recordings?** Yes. Musical work repertoire for PROs, MROs and The MLC, and sound recording and performer repertoire for neighbouring rights societies, can be managed in the same platform. **How are member mandates managed?** Each member's assigned rights, territories and periods are recorded and kept up to date, so the organization knows exactly what it can license and collect. **Can repertoire be exchanged with sister societies and industry databases?** Yes. DataFort produces CWR, DDEX RDR and partner-specific formats for exchange with sister societies and networks such as the CISAC ISWC network and SCAPR VRDB. **How does this connect to usage matching and deduplication?** A clean, validated repertoire is the foundation for Noctil's MatchIQ usage matching and work, recording and party deduplication. **Can sister societies and partners connect directly?** Yes. Through OrgLink, partners and members get their own connected accounts to submit registrations, track their status and fix rejections. Permissions control what each partner can see and change. **Who is this for?** Performing rights organizations (PROs), mechanical rights organizations (MROs), The MLC, neighbouring rights societies, and other music CMOs.