Music Metadata: Identifiers, Formats and Rights Data

Understand ISRC, ISWC, UPC, IPI and ISNI, distinguish DDEX from CWR, and check catalog metadata without confusing identifiers with rights or payment.

Royalty metadata needs to answer different questions: which recording was used, which musical work it contains, which parties are involved, and which rights and agreements apply. An identifier helps name an entity. It does not answer all those questions on its own.

This guide maps five identifier systems and the formats used to exchange their surrounding data. The practical aim is to make catalog records easier to check—not to promise that adding a code will release money or repair every downstream system.

Why metadata matters beyond discovery

Keep identification, registration and payment separate when investigating an unmatched report. A correct recording code does not establish who controls the composition, what share a contract assigns, or whether a payment has reached a bank account.

The MLC illustrates why the distinction matters. Its individual-registration process includes separate work, writer, publisher/share and optional recording steps. Recording information can help automated matching; the final submission screen still shows a Submitted status, not proof of acceptance or payment. See The MLC's registration guide.

That is a specific workflow, not evidence that every missing code causes the same outcome. Avoid diagnosing an unexplained balance as “black box” money without checking the responsible organisation's records and the relevant usage period.

The core identifiers behind royalty metadata

ISRC: a recording, not its owner

The International Standard Recording Code identifies a sound recording or music video recording. IFPI says an existing ISRC stays with an unchanged recording even when ownership changes. A remaster generally retains it unless significant new creative input makes a new assignment appropriate. See IFPI's ISRC FAQ.

Do not create a new identifier merely because a recording moves to another owner. Equally, do not treat an identifier carried into a spreadsheet as proof that the associated ownership claim is correct.

ISWC: the musical work

The International Standard Musical Work Code identifies a composition, not a recording. It does not encode copyright ownership shares. Keep the work's identity distinct from the recording used and the parties claiming rights. The ISWC authority's explanation makes those limits explicit.

For a fuller explanation, see ISWC versus ISRC. Do not assume that every recording-to-work relationship can be resolved by copying one code into another field.

UPC/EAN: the release product

IFPI distinguishes a recording's ISRC from the UPC/EAN identifiers commonly used for physical and digital music products. A release identifier and a recording identifier answer different catalog questions, even when the release contains just one track.

In data exchanges, preserve the identifier's format. DDEX treats barcode identifiers as fixed-length strings, so leading zeroes matter. A spreadsheet's numeric conversion is not an editorial correction.

IPI and ISNI: parties and public identities

IPI identifies interested people and legal entities across categories of artistic works; it is not limited to music. SUISA administers the system under CISAC and BIEM guidelines. See CISAC's IPI overview.

ISNI identifies public identities across creative fields. Its scope is disambiguation and links between information systems, not a complete rights or financial record. See ISO 27729:2024's public abstract.

Use the scheme the recipient requests. IPI and ISNI are not interchangeable, and neither number by itself establishes a royalty share.

Identifiers at a glance

This is a field-selection guide, not a table of ownership or payment rules.

The definitions above come from IFPI, the ISWC authority, CISAC and ISO. A value that passes a format check still needs to refer to the intended entity.

DDEX and CWR: different exchanges for different jobs

DDEX publishes several message standards, not one universal file used by every participant:

• Electronic Release Notification (ERN) communicates release/resource metadata and the terms under which releases can be made available, usually from a label or distributor to a DSP.
• Digital Sales Reporting (DSR) communicates sales and usage metadata, usually from a DSP to a rights owner. Its profiles address different business circumstances.

Common Works Registration (CWR) belongs to CISAC's formats, not DDEX's. It exchanges musical-work registration information between publishers and societies and supports registration-status communication. See CISAC's format descriptions.

A release delivery, a sales report and a work registration are not the same transaction. Confirm the recipient's supported version, profile and requirements instead of assuming “DDEX compatible” means that all incoming files have identical structures. For the reporting side, see our DDEX DSR guide.

Four metadata problems worth investigating

These are diagnostic checks, not a ranking of the industry's most frequent failures.

1. Unclear contributor-name relationships. Different names do not automatically mean different people. SUISA explains that multiple IPI Name Numbers can be linked through one Base Number. Confirm the relationship before merging or replacing records. See SUISA's IPI explanation.
2. Missing identifiers. Check the actual registration or delivery route. The MLC does not require ISWC entry in its individual Work Details step, and its recording step is optional. That does not make the whole registration title-only, nor establish every other recipient's requirements.
3. Identifier mismatches between systems. Compare the scheme, value and associated recording or work. DDEX says ISRC hyphens used for display are not included in messages, while barcode leading zeroes must remain. Do not apply one blanket “strip formatting” rule to every identifier.
4. Records left unreviewed after a catalog change. List the affected destinations and confirmations you need. A local correction is not evidence that an external registration or previously issued statement changed.

DDEX's identifier communication guidance supplies the formatting examples. It does not establish which mismatch caused a particular missing payment.

Five practical habits for metadata accuracy

The following are recommended controls, not a universal standard or measured savings claim.

1. Collect confirmed identifiers early. Search existing records and follow the assignment authority's rules. Record an unresolved field honestly instead of inventing a value to complete a release checklist.
2. Check names together with identifiers. Keep credited names and verified name relationships distinguishable. Do not force every pseudonym into one public name.
3. Validate by scheme and destination. Preserve the original supplied value alongside any normalised representation. Check leading zeroes, check characters and the recipient's specification.
4. Track corrections to completion. Keep the source, proposed change, responsible organisation and confirmation. Recheck the affected record rather than assuming propagation.
5. Review metadata as the catalog changes. Prioritise new repertoire, acquisitions, distributor changes and reported exceptions. Choose a review cadence that fits the risk; “once a year” is not an industry-wide rule.

How technology can help—and what Qlero documents

A useful software evaluation is to ask how the system exposes mismatches, preserves references and lets a reviewer confirm a correction. Do not assume that software removes all reconciliation work.

Qlero's track and release guide documents separate records: tracks require a name, artist and company-unique ISRC; releases require a name, artist and a barcode or catalog number. Creating repertoire requires Repertoire write access.

Its External ID and aliases guide distinguishes a reference field from sales-matching aliases. External ID is not used for sales matching. Aliases require Repertoire write access, must be unique within their type and take effect after saving in the documented manual workflow.

Those pages support specific internal catalog and sales-matching claims. They do not establish automatic validation against every identifier registry, CWR submission, upstream catalog correction or reconstruction of historical statements. A documentation limit is not proof that a feature is absent: ask for the particular workflow to be demonstrated. A match or saved reference is not evidence of money movement.

Frequently asked questions

Can a recording have multiple ISRCs?

Do not deliberately assign another code to an unchanged recording. IFPI generally permits the same code for a remaster without significant new creative input; materially changed recordings need the applicable assignment rules checked. Investigate suspected duplicate assignments instead of treating every remaster label as proof a new code is needed.

Is DDEX a metadata standard or a file format?

DDEX publishes a family of standards for particular exchanges, including ERN and DSR. Specify the standard, version and profile you mean. CWR is a separate CISAC format, not another DDEX message.

Why might a correctly assigned ISRC still appear in an unmatched report?

The code alone does not diagnose the problem. Compare the reported value and referenced recording with your catalog, then inspect the receiving workflow's validation and matching results. Avoid assuming that formatting is always the cause or that a local match resolves a publishing claim.

Does metadata accuracy matter more for one royalty type?

Different workflows need different information. Recording identity, musical-work registration and the relevant rights data should not be collapsed into a single checklist. Start with the report or registration you are investigating and the recipient's requirements.

Which identifier should a team fix first?

Prioritise a known error blocking the actual workflow, its affected records and the evidence available. There is no universal rule that ISRC or party identifiers always matter more than ISWC or product identifiers. Do not guess an uncertain identifier just to clear a warning.

How often should catalog metadata be reviewed?

Use a risk-based routine and review affected records after significant changes or reported problems. This is an operational recommendation, not a mandatory annual interval or a guarantee that earlier records are correct.

Keep identifiers, rights and payment evidence separate

The aim is a traceable connection between the right entity, the right data exchange and the evidence supporting a rights claim. Standard identifiers make those records easier to discuss; they do not replace agreements, recipient confirmations or payment evidence.

Book a Qlero walkthrough to discuss the catalog and sales-matching checks your team needs to verify.