DDEX Explained: Why Metadata Standards Matter for Your Royalties

What DDEX is

DDEX (Digital Data Exchange) is a standards-setting body that develops and maintains the data communication standards used by the music industry to exchange information about recordings, compositions, and rights holders. Founded in 2006 with input from major labels, DSPs, and collection societies, DDEX has become the backbone of how music metadata moves between distributors, streaming platforms, and rights management databases. When your distributor sends your release to Spotify or Apple Music, the file it sends — containing your track details, rights information, ISRC codes, contributor credits, and composition data — is structured according to DDEX standards. If that file is malformed or contains incorrect data, the platform either rejects it or imports it with errors. Both outcomes affect your royalties.

Why metadata standards exist

The music industry processes billions of individual streaming events every month across hundreds of platforms in dozens of territories. Each of those events triggers a royalty calculation that must be attributed to the correct rights holders — the master recording owner, the composer, the lyricist, the performers, and the producer. Without a common standard for how this attribution data is structured and communicated, matching a stream to a rights holder becomes guesswork. DDEX solves this by defining exactly what fields must be present, in what format, with what validation rules, for a music delivery to be considered complete and attributable. Non-compliance with DDEX standards is not a minor formatting issue — it is a structural barrier to correct royalty attribution.

The key DDEX standards independent artists should know

DDEX maintains several standards for different use cases. The ones relevant to independent artists are:

• ERN (Electronic Release Notification): the standard for communicating release and track information from distributors to DSPs. ERN defines the structure for communicating ISRC codes, track metadata, contributor credits, and rights information. Most digital distribution uses ERN 4.x currently.
• MEAD (Music Encoding and Distribution): an older standard still in use by some platforms. Inconsistencies between MEAD and ERN data from the same distributor are a common source of mismatch errors.
• DSR (Digital Sales Report): the standard that governs how DSPs report usage data back to distributors. If your distributor does not receive DSR-compliant usage reports, your royalty statement will have gaps or unexplained aggregations.
• RIN (Recording Information Notification): a newer standard for communicating studio production data including performer credits and producer information, relevant for neighbouring rights collection via PPL.
• MWN (Musical Work Notification): the standard for communicating composition ownership data to publishers and collection societies. Incorrect MWN data is a common cause of PRS non-matching.

How DDEX non-compliance causes royalty errors

DDEX non-compliance is rarely an artist's direct error — it is more commonly a distributor or aggregator problem. But its effects flow downstream to the artist. Common failure modes:

• Missing or malformed ISRC: the ISRC code is the primary identifier linking a streaming event to a specific recording. If the ISRC in the DDEX delivery is missing, incorrectly formatted, or different from the ISRC registered with PPL, the stream cannot be attributed and the royalty goes unmatched.
• Incorrect contributor credits: if performer credits in the DDEX delivery do not match the credits registered with PPL for neighbouring rights, PPL cannot match the broadcast or stream to the performer and neighbouring rights royalties go uncollected.
• Missing ISWC: the ISWC (International Standard Work Code) links a streaming event to a composition for publishing royalty purposes. If the ISWC is missing from the DDEX delivery, PRS and overseas collection societies may be unable to match the performance to the registered work.
• Character encoding errors: non-standard characters in artist names or track titles (particularly accents, Cyrillic, Arabic, or Chinese characters) can corrupt fields during DDEX ingestion, causing the track to be stored under a different identifier than expected.
• Rights territory mismatches: if the DDEX delivery specifies different rights territories than the society registrations on file, platforms may block delivery in certain territories or attribute royalties to the wrong party.

How to check if your metadata is DDEX-compliant

Most independent artists cannot directly access the DDEX files sent by their distributor. But there are proxy checks that reveal whether DDEX compliance is likely to be an issue: verify your release on multiple DSPs and confirm that artist name, track title, ISRC, and contributor credits are identical and correctly formatted across all platforms. Discrepancies between platforms are almost always the result of a malformed or inconsistent DDEX delivery. Log into your PRS online account and confirm that all your released works appear with correct ISWC codes, composer splits, and titles. Check your PPL account and confirm your recordings appear with correct ISRC codes and performer credits. Any discrepancy between your DDEX delivery data and your society registration data is a potential royalty gap.

Why distributors vary in DDEX compliance

Not all distribution services achieve the same level of DDEX compliance, and the variation is not always disclosed. Consumer-grade aggregators (the ones charging £20/year for unlimited distribution) often process high volumes of submissions with minimal metadata validation, relying on automated rejection for the most obvious errors but passing through incomplete or malformed data that meets their minimum standards. Professional distribution services and label services providers conduct manual metadata checks before submission, validate ISRC and ISWC codes against society databases, and monitor for post-delivery discrepancies across platforms. The difference in royalty collection accuracy between a compliant submission and a non-compliant one is real and cumulative — errors that persist across an entire catalog over multiple years represent significant uncollected income.

What to do if you suspect a DDEX error

If you identify discrepancies between your DSP pages and your society registrations, the correct course of action is: first, obtain the ISRC and ISWC codes for all affected works and verify them against your registration records. Second, contact your distributor in writing requesting confirmation of the DDEX delivery data for the specific releases — what was sent, in what version, and whether any platform rejections or warnings were received. Third, contact PRS and PPL with the specific track details to check for any unmatched or disputed registrations on their databases. Fourth, if errors are confirmed, request a metadata correction delivery from your distributor. Corrections can be submitted but take time to propagate across all platforms — typically 5–15 business days. Document all of this in writing.

Code Group Music's metadata administration service includes DDEX compliance checking for all new releases and catalog audits for existing catalogs. We verify ISRC and ISWC codes against society databases before submission and monitor for post-delivery discrepancies. Start with a free catalog assessment.