DDEX (Digital Data Exchange) is the standards body that defines how data moves between labels, publishers, distributors, DSPs, and rights societies. Without it, every company in the chain would need custom formats for every partner. With DDEX, organizations can exchange music data efficiently, consistently, and at scale. 

What problem does DDEX actually solve?

Music metadata moves through a long chain: studio, record company, distributor, DSP, publisher, rights society. Each handoff is a chance for data to get lost, duplicated, or mismatched. DDEX standardizes the messages sent at each step, so a release, a claim, or a royalty report means the same thing to every party that touches it.

The Full set of DDEX standards, and what each one does?

Release metadata standards

These standards manage how music release metadata is shared across the digital music ecosystem.

1. ERN (Electronic Release Notification) – Used by record companies and distributors to deliver new music releases, recordings, cover art, and commercial information to DSPs worldwide.

2. MEAD (Media Enrichment And Description) – Provides additional metadata beyond ERN, including lyrics, genres, moods, awards, photos, and alternative titles to enhance music discovery and user experiences.

3. PIE (Party Identification and Enrichment) – Shares rich metadata about people and organizations, such as writers, artists, studio personnel, and record companies.

4. CT (Catalogue Transfers) – Notifies DSPs when a sound recording catalogue is transferred from one record company to another. It supports direct label-to-label catalogue transfers but does not cover transfers involving distributors.

Reporting and claims standards

These standards enable the exchange of music usage, royalty reports, claims, and invoice information between industry partners.

1. DSR (Digital Sales Reporting) – Reports music sales, streaming, and usage data from DSPs and other licensees to rights holders, supporting accurate royalty reporting and payments.

2. CDM (Claim Detail Message Suite) – Allows publishers and rights societies to send royalty claims and invoice details, while enabling licensees to raise discrepancies related to calculations, tariffs, or ownership claims.

Musical work rights standards

These standards support the communication of musical work ownership, licensing, and rights share information.

1. MWN (Musical Works Rights Share Notification) – Allows musical work owners and administrators to communicate ownership shares of a musical work to record companies and other industry participants.

2. MWL (Musical Works Licensing) – Enables record companies and other organizations to request licenses for musical works from their owners or administrators.

3. LoD (Letter of Direction) – Enables new owners or administrators to notify record companies and other organizations about newly acquired rights shares.

4. BWARM (Bulk Communication of Work and Recording Metadata) – Enables the bulk exchange of musical work and recording metadata, including rights shares, between organizations such as Mechanical Licensing Collectives and their partners.

Recording rights and studio-level standards

These standards manage recording rights, revenue reporting, and studio session metadata throughout the recording lifecycle.

1. RDR-N (Recording Data and Rights Notification) – Enables recording owners, performers, and administrators to register and communicate their rights in sound recordings and music videos with music licensing companies.

2. RDR-R (Recording Data and Rights Revenue Reporting) – Allows revenue generated from sound recordings, music videos, and performances to be reported back to their owners or administrators.

3. RDR-C (Recording Data and Rights Choreography) – Defines the workflow for exchanging Recording Data and Rights (RDR) messages between organizations.

4. RIN (Recording Information Notification) – Captures recording session metadata at the source, including performers, instruments, recording details, and production credits.

Why does this matter beyond compliance?

Standards only work if the underlying identifiers are accurate. A perfectly formatted ERN message built on a broken ISRC-to-ISWC match still produces bad data downstream. That’s the layer DDEX doesn’t govern directly, and it’s where automated matching and identifier hygiene become the difference between metadata that flows and metadata that stalls.

Transform Metadata into Any DDEX Standard

Noctil’s Data Transformation Engine enables organizations to transform metadata from any source into any DDEX-compliant format. Through configurable mapping and automated transformation, it ensures metadata is structured correctly for seamless exchange across the music ecosystem.

The takeaway

DDEX gives the industry a shared language. Whether that language produces accurate, paid royalties still depends on the quality of the data feeding into it.