DDEX ERN 4.3 Explained: What Independent Labels Need to Know About the Latest Standard

What DDEX is

DDEX (Digital Data Exchange) is a standards-setting body whose members include major streaming platforms (Spotify, Apple, Amazon, YouTube), major distributors, and rights management organisations. DDEX's purpose is to create and maintain technical standards for the electronic communication of music business information. The most widely used DDEX standard is ERN — Electronic Release Notification — which defines the data format used when a distributor delivers music metadata to a DSP. When DistroKid sends your release to Spotify, or when a major label's distribution arm sends an album to Apple Music, the delivery is formatted according to ERN.

What ERN defines

ERN is an XML-based message format that specifies exactly which fields must be present in a music delivery and how they must be structured. A complete ERN delivery for a single track includes:

• Recording information: ISRC, recording title, duration, language, explicit content status, audio file format specification.
• Artist information: primary artist name, featured artist names, and their identifiers (IPI, IPN, ISNI where available).
• Composition information: ISWC, songwriter names and their IPI numbers, publisher names and IPI numbers, territory-specific ownership splits.
• Release information: UPC, release title, release date, label name, release type (album, EP, single).
• Artwork: image file specification, dimensions, colour space.
• Territory and availability: which territories the release should be available in, and any territory-specific restrictions.
• Pricing and deal terms: release type, streaming tier eligibility, pricing category.

What changed in ERN 4.3

ERN 4.3 is an evolution of ERN 4.1 (the previous widely-used version) with several significant additions relevant to independent labels:

• Improved handling of user-generated content (UGC): ERN 4.3 includes clearer specifications for how rights holders communicate their preferences for UGC platforms, particularly YouTube and TikTok. This affects how your content policy travels with the delivery.
• Enhanced contributor metadata: ERN 4.3 adds more granular fields for contributor roles — distinguishing between types of producer, featuring roles, and session contributors — enabling more accurate attribution on DSP artist pages and in royalty matching.
• Improved ISNI field support: ERN 4.3 formalises the inclusion of ISNI identifiers for both artists and publishers in the delivery, enabling better cross-database matching.
• Streamlined territory rights model: the rights message structure has been simplified in ERN 4.3 to reduce the complexity of communicating territory-specific availability and rights.
• Better support for classical and spoken word: ERN 4.3 improves handling of work parts (movements, acts, scenes), relevant for classical or multi-part release formats.

Why independent labels should care about ERN compliance

Independent labels rarely build or consume ERN messages directly — that is the distributor's job. But ERN compliance matters to independent labels for a specific reason: the quality of your distributor's ERN implementation determines the quality of your metadata on DSPs. A distributor with a poorly implemented ERN pipeline may silently drop optional fields (including ISWC codes and songwriter credits), format required fields incorrectly (causing rejections or truncation), or deliver stale data without triggering a metadata update on the platform. The result is releases with missing credits, incorrect songwriting attribution, or ISRC mismatches — all of which affect royalty collection downstream.

How to assess your distributor's ERN compliance

You cannot directly inspect your distributor's ERN messages, but you can evaluate the downstream evidence of compliance quality:

• Check your DSP pages: are all songwriter credits visible on Spotify and Apple Music? Are featured artist names correctly formatted? Is the release type (album vs single) displayed correctly?
• Check your PPL registration: does your recording appear in the PPL database with the ISRC your distributor issued? If the ISRC in PPL does not match what is on the DSP, there is a delivery inconsistency.
• Check your PRS statement: does your PRS distribution include streaming royalties that match your streaming volume? A pattern of unmatched streaming income despite correct PRS work registration can indicate ISWC data was not transmitted in the distributor's ERN delivery.
• Ask directly: request from your distributor their DDEX certification status and which version of ERN they use for DSP deliveries. A DDEX-certified distributor operating on ERN 4.3 is the current best practice.

The other DDEX message types

ERN is the most widely encountered DDEX standard but not the only one. Independent labels with more complex operations may encounter:

• MEAD (Music Encoding and Delivery): for audio delivery specifications.
• DSR (Digital Sales Reporting): the format DSPs use to report usage data back to rights holders and distributors.
• BWARM (Bulk Works And Rights Management): for large-scale catalog rights registration.
• PIE (Price Information Exchange): for communicating pricing and deal terms between distributors and DSPs.
• CRB (Claims, Rights and Boundaries): for rights conflict resolution.

Code Group Music distributes music using DDEX ERN 4.3 compliant delivery pipelines and audits release metadata for completeness before submission — including ISWC codes, songwriter credits, and ISNI data. If you have existing releases with metadata gaps, a catalog assessment will identify where corrections are needed. Start at codegroupmusic.co.uk/#catalog-assessment.

Frequently Asked Questions