ISRC, ISWC, and IPI: A Music Metadata Guide to Protect Credits and Royalties

When a track is finally mastered, the data work is only beginning. Inconsistent writer names, missing producer roles, confused recording versions, or identifiers scattered across different files can make credits harder to trace and corrections painfully slow.

Metadata is not mere administration. It is the identity layer connecting a recording, its underlying composition, creators, releases, distributors, streaming services, and rights organisations. Clean metadata does not guarantee payment by itself, but it helps participants across the music supply chain match usage to the correct work, recording, and rightsholder.

This guide separates ISRC, ISWC, IPI, and release identifiers, then turns those concepts into a workflow independent artists, bands, small labels, studios, and managers can use before and after release day.

Start with Two Different Assets: The Work and the Recording

A song has at least two layers that should be separated from the beginning:

• The musical work or composition: the melody, harmony, lyrics, and structure created by songwriters or composers.
• The sound recording or master: a particular recorded performance of that work.

One composition can have many recordings: studio, live, acoustic, remix, or cover versions. A digital release can also contain several recordings. Confusion begins when the title is treated as the only identity, even though the same title may point to entirely different assets.

ISRC: The Identifier for a Specific Recording

The International Standard Recording Code (ISRC) identifies sound recordings and music videos—not compositions, release products, or performers. According to the International ISRC Registration Authority, an assigned ISRC remains a fixed reference when that recording is used across services, territories, or licensing arrangements.

In other words, the ISRC belongs to a specific recording. A live performance and a studio master are not the same recording. Do not create a new code simply because you change distributors or re-release the identical master; when a change creates a new recording, check the official assignment rules. Record the decision in your internal catalogue so two team members cannot assign different codes to the same asset.

ISWC: The Identifier for a Musical Work

The International Standard Musical Work Code (ISWC) is a unique, permanent reference for a musical work. It does not identify a recording. The ISWC Registration Authority explains that an ISWC connects a work with descriptive data such as its title and creators.

Artists do not self-issue an ISWC. It is allocated through an authorised Registration Agency, commonly as part of work registration with an affiliated collective management or rights management organisation. Writer splits, registered names, and creator roles should therefore be confirmed before registration.

IPI: The Identifier for an Interested Party

Interested Party Information (IPI) uniquely identifies a person or legal entity with an interest in a work, such as a composer, arranger, or publisher. CISAC explains that the IPI system supports documentation, distribution, and accounting among rights societies.

In simple terms: ISRC answers “which recording?”, ISWC answers “which work?”, and IPI helps answer “which party?”. They complement one another, but none replaces the others.

What About UPC or EAN?

A UPC or EAN typically identifies a release product or package, such as a single or album—not the composition and not a creator’s personal identity. In a distribution workflow, one album may carry one product code while each track has its own ISRC.

Credit Metadata to Agree Before Upload

Create one master metadata sheet as the source of truth. At minimum, include:

• the official work title and the release display title;
• main and featured artist names with consistent spelling and capitalisation;
• legal or registered names for songwriters and composers;
• each contributor’s role: performer, producer, engineer, mixer, mastering engineer, arranger, and other relevant roles;
• agreed writing splits and evidence of that agreement;
• the master owner or controller and their administration contact;
• the ISRC for every recording, the ISWC when allocated, and relevant IPI identifiers;
• release product code, label, release date, territory, language, genre, and explicit status;
• relationships between versions: original, radio edit, instrumental, live, remix, or remaster.

Do not pack featured artists, producers, years, or promotional phrases into the title when your distributor provides structured role fields. Structured metadata travels more reliably than information buried inside display text.

Why Distributor Data Controls Platform Credits

Platforms receive metadata through the digital supply chain. Spotify for Artists, for example, says displayed credits come from metadata sent by a label or distributor. If credits are missing or wrong, the update must come through that sender.

At industry level, DDEX provides data-exchange standards such as Electronic Release Notification (ERN), commonly used by labels or distributors to deliver release and recording information to digital services. Independent artists do not need to operate DDEX themselves, but they should understand that data entered into a distributor form may travel through many downstream systems.

A Practical Metadata Workflow: Session to Release Audit

1. Capture credits during production

The studio or project manager records who did what, on which date, and for which file version. Use names that align with rights administration records, not only nicknames.

2. Lock splits and ownership

Confirm writing splits and master ownership in writing. Metadata does not replace a contract or split sheet.

3. Create internal IDs before external IDs

Give each project and file version an internal number. This prevents “final”, “final-2”, and “actual-final” from becoming your catalogue system.

4. Validate before delivery

Have at least two people check spelling, roles, artist order, identifiers, audio files, artwork, and dates. Compare the distributor form against the master sheet—not memory.

5. Preserve delivery evidence

Archive form exports, confirmation emails, split sheets, contracts, master file names or checksums, and release-detail screenshots. Apply access controls appropriate to each role.

6. Audit after publication

Check the destination artist page, title, featured artists, credits, explicit flag, artwork, date, and links. Log issues by platform, then submit corrections through the distributor using the same source data.

The Artist Website as a Public Verification Layer

A website does not replace work registration, a distributor, or a rights organisation. It can, however, become a consistent public reference for discography, artist naming, release dates, selected credits, official listening links, an Electronic Press Kit, licensing contacts, and usage policies.

Create one permanent page for each release. Populate it from the master sheet and update it when corrections occur. Keep the complete catalogue in an access-controlled internal system; not every contract, split, or administrative identifier belongs on a public page.

The Most Expensive Metadata Mistakes to Correct

• treating an ISRC as the identifier for a song or composition;
• changing a creator’s name spelling from one release to the next;
• delivering the same master with different ISRCs without a valid reason;
• postponing split confirmation until usage has already accumulated;
• keeping all credits in one band member’s personal notes;
• changing distributors without preserving old identifiers and catalogue metadata;
• treating correct metadata as a substitute for rights registration or agreements.

FAQ

Does an ISRC prove ownership of a master?

No. An ISRC identifies a recording; it is not an ownership certificate or a replacement for a contract.

Does one song have only one ISRC?

One specific recording has one ISRC. The same composition can have multiple ISRCs when recorded in different versions.

Can an artist create an ISWC?

No. ISWCs are allocated by authorised Registration Agencies through the work-registration process.

Can I directly edit incorrect Spotify credits?

Corrections normally need to be resent by the label or distributor that delivered the metadata to Spotify.

Does complete metadata guarantee every royalty payment?

No. Payment also depends on registration, agreements, usage reporting, territory rules, and each organisation’s processes. Consistent metadata strengthens matching and makes problems easier to investigate.

Conclusion

Good metadata is career infrastructure. Separate the work from the recording, use each identifier for its intended purpose, agree credits before upload, and audit the result after publication. The earlier this system exists, the easier it becomes to grow a catalogue without losing its context.

Wirasena Digital helps artists, bands, labels, and studios build discography websites, release pages, EPKs, content catalogues, and digital data workflows aligned with their distribution process. If your catalogue is becoming hard to trace, start with one master metadata sheet and one digital home your team can maintain.