What is an ISRC

Introduction

The International Standard Recording Code, or ISRC, is the global identifier assigned to individual sound recordings and music video recordings. Every commercially distributed recording that enters the digital supply chain is expected to carry one. Without it, platforms cannot reliably track usage, distributors cannot reconcile reports accurately, and royalty systems struggle to match performances to the correct master owner.

An ISRC does not identify a song, a release, or a product. It identifies a specific recording. If the same composition is recorded multiple times, each recording receives its own ISRC. If the same master is distributed worldwide across different platforms and formats, it retains the same ISRC throughout its lifecycle.

As distribution systems have become automated and data-driven, the ISRC has moved from being a cataloging convenience to a structural requirement. Digital service providers, collective management organizations, distributors, neighboring rights administrators, and reporting systems rely on the ISRC as the primary anchor for recording-level data.

Understanding how ISRCs are structured, assigned, embedded, and maintained is essential for preventing duplication, mismatched reports, and delayed payments. The code itself is simple. The operational consequences of using it incorrectly are not.

Learning Objectives

By the end of this guide, you should be able to:

• Define the International Standard Recording Code and explain its function within the global recording supply chain
• Distinguish between ISRC, ISWC, and UPC, and understand how each identifier applies to a different layer of music rights and distribution
• Interpret the structural components of an ISRC and apply the correct assignment rules
• Determine when a new ISRC is required for edits, remasters, alternate mixes, or derivative versions
• Obtain a registrant prefix or assign ISRCs through an authorized distributor
• Embed ISRCs properly in audio files and delivery standards such as DDEX ERN and RIN
• Identify metadata errors that lead to duplicate recordings, unmatched usage reports, or delayed royalties

Table of Contents

Overview

The ISRC is a standardized identifier governed by ISO 3901 and administered globally through the framework established by the International Federation of the Phonographic Industry. Its purpose is consistency across jurisdictions, systems, and reporting environments. A recording assigned an ISRC in one country must be recognizable in another without reinterpretation or conversion.

Unlike commercial barcodes or internal catalog numbers, the ISRC is designed to remain attached to a recording for its entire lifespan. Ownership may change, distribution partners may change, and platforms may change, but the identifier remains stable. Reassignment or duplication disrupts reporting systems and can fragment historical usage data.

Modern distribution infrastructure assumes the presence of an ISRC at multiple stages: mastering, ingestion by distributors, delivery to digital service providers, and reporting back from those platforms. The code is referenced in royalty statements, neighboring rights claims, broadcast logs, and digital exchange standards.

Errors typically arise not from the absence of an identifier, but from misuse. Reassigning a new ISRC to an existing master during catalog migration, failing to issue a new ISRC for a materially different version, or inconsistently embedding the code across delivery formats can result in duplicate entries and mismatched reporting.

The sections that follow examine how the ISRC system was established, how codes are structured and assigned, and how they operate within current metadata and royalty workflows.

Origins and Standardization

The International Standard Recording Code was introduced in 1986 as an international solution to a growing identification problem within the recorded music industry. As global distribution expanded and recordings began circulating across borders, labels and distributors relied on internal catalog numbers that were inconsistent and not interoperable. A standardized identifier was required to support cross-border reporting and automation.

The ISRC was formalized under ISO 3901, published by the International Organization for Standardization. The current edition, ISO 3901:2019, reflects updates aligned with digital distribution practices and metadata exchange requirements. The standard defines the structure of the code and the responsibilities of registrants but does not regulate how recordings are commercially exploited.

Global administration is coordinated by the International Federation of the Phonographic Industry, which appoints national and regional ISRC agencies. These agencies issue registrant prefixes to recording owners within their jurisdictions. In the United States, prefix management is handled by the RIAA, operating as the U.S. ISRC Agency.

The system was originally designed for physical distribution environments, including CD manufacturing and broadcast logging. Its relevance increased significantly with the growth of digital delivery in the 2000s. Automated reporting, electronic release messaging, and neighboring rights claims now rely on ISRCs as the primary recording-level identifier.

The standard does not require central approval for each code issued. Once a registrant prefix is granted, the recording owner assigns designation numbers according to ISO rules. This decentralized structure enables scalability while preserving global uniqueness.

Governance and Administration

ISRC governance is structured to maintain global uniqueness while allowing decentralized assignment. The standard itself is defined under ISO 3901, but operational oversight is coordinated by the International Federation of the Phonographic Industry. IFPI appoints national and regional ISRC agencies responsible for issuing registrant prefixes within their territories.

A registrant prefix authorizes a recording owner to generate ISRCs directly. The prefix identifies the registrant, not the distributor or platform. Once issued, it remains associated with that rights holder and can be used across releases and years, subject to ISO rules governing structure and uniqueness.

In territories without a national agency, IFPI may issue prefixes directly. In the United States, the designated ISRC agency operates under the Recording Industry Association of America, which manages prefix issuance and guidance for U.S.-based registrants.

Assignment authority operates on a trust-based model. After receiving a prefix, the registrant assigns designation codes internally. No external approval is required for each new recording. This structure enables labels, production companies, and independent artists to manage identifiers at scale without central bottlenecks.

Distributors also play a role. Many digital distributors assign ISRCs automatically when delivering recordings to digital service providers. In these cases, the distributor acts as the registrant. The code remains attached to the recording even if the artist later changes distribution partners. Reassignment of a new ISRC to an unchanged master disrupts continuity across reporting systems.

Governance ensures that each ISRC is globally unique. Administration ensures that the assignment follows defined structural rules. Responsibility for correct use remains with the registrant.

ISRC Code Structure and Syntax

An ISRC consists of 12 characters divided into four elements. The format is standardized under ISO 3901 and follows this structure:

CC-XXX-YY-NNNNN

Each segment carries a specific meaning.

Country Code (CC) - The first two letters identify the country of the ISRC agency that issued the registrant prefix. This does not necessarily indicate where the recording was created or released. It reflects the territory of prefix issuance.

Registrant Code (XXX) - This three-character alphanumeric code identifies the rights holder or entity authorized to assign ISRCs. It is issued by a national agency and remains constant for that registrant.

Year of Reference (YY) - The two-digit year reflects when the ISRC was assigned, not when the recording was made or released. The year component does not update if the recording is reissued in a later year.

Designation Code (NNNNN) - The final five digits form a unique serial number assigned by the registrant. The designation number must not be reused within the same year for the same prefix.

An ISRC is not embedded with release information, genre, or ownership splits. It is a structural identifier only. The code does not expire and does not change when ownership transfers.

Formatting conventions may include hyphens for readability, but hyphens are not stored in metadata systems. The canonical representation is a continuous 12-character string.

Assignment Rules and Version Control

ISRC assignment is governed by the principle that each distinct recording must have its own unique code. A new ISRC is required when the audio content is materially different in a way that affects the listening experience.

A new ISRC must be assigned in the following cases:

• A new studio recording or alternate take
• A remix or re-edit that alters structure or mix
• A remaster that produces a perceptible audio difference
• A live recording
• Instrumental or a cappella versions
• Clean or explicit edits with audio differences
• Spatial audio or Dolby Atmos mixes that constitute a distinct mix
• A music video recording, even if the audio matches the master

A new ISRC is not required when:

• The same master is distributed across additional platforms or territories
• The recording appears on compilations, deluxe editions, or box sets
• Distribution partners change without altering the audio
• Metadata corrections are made that do not affect the recording itself

The year of reference within the ISRC reflects when the code is assigned, not when the recording was first released. Reissuing an older recording does not justify assigning a new ISRC unless the audio itself has changed.

Version control errors are common during catalog migrations. Assigning a new ISRC to an unchanged master fragments usage history and can create duplicate entries across digital service providers. Conversely, failing to assign a new ISRC to a materially altered version can merge reporting for distinct recordings.

Correct assignment depends on assessing whether a listener would reasonably perceive the recording as different. The ISRC identifies the recording itself, not its commercial packaging or marketing context.

ISRC vs ISWC vs UPC

The ISRC operates alongside other identifiers that apply to different layers of music rights and distribution. Confusion arises when these codes are treated as interchangeable. They are not. Each identifier applies to a separate asset within the music value chain.

The differences are most clearly understood in comparison.

Identifier Comparison

Key distinctions:

• Multiple ISRCs can correspond to one ISWC if the same composition has several recordings.
• A single UPC can contain multiple ISRCs because a release typically includes multiple recordings.
• The ISRC does not identify ownership shares or songwriting splits.
• The ISWC does not identify recordings.
• The UPC does not track performances or streams at the recording level.

Digital reporting systems rely on all three identifiers operating together. A streaming report may reference the ISRC for the recording, while royalty allocation for composition rights relies on the ISWC. Retail accounting references the UPC for release-level aggregation.

These identifiers operate in parallel rather than in hierarchy. Misalignment between them can lead to mismatched reporting, especially when recordings are reissued, bundled, or re-delivered through new distribution channels.

Obtaining an ISRC and Managing a Registrant Prefix

ISRCs can be assigned in two primary ways: directly by a rights holder who holds a registrant prefix, or indirectly through a distributor acting as the registrant.

Obtaining a Registrant Prefix

Recording owners may apply for a registrant prefix through their national ISRC agency. In the United States, prefix issuance is administered by ththe RC Agency under the global framework coordinated by IFPI.

A registrant prefix is issued once and remains valid indefinitely. After issuance, the rights holder assigns designation numbers internally for each new recording. There is no requirement to seek approval for individual ISRCs once a prefix is granted.

Responsibilities of a prefix holder include:

• Ensuring uniqueness of designation numbers within each year
• Assigning new ISRCs only when assignment rules require it
• Maintaining internal records linking ISRCs to recordings
• Preserving continuity during ownership transfers or catalog migrations

Distributor-Assigned ISRCs

Many digital distributors assign ISRCs automatically at the time of delivery. In this model, the distributor holds the registrant prefix and generates the code on behalf of the artist or label.

Important operational considerations:

• The ISRC remains attached to the recording even if distribution partners change.
• Replacing a distributor does not require assigning a new ISRC if the master is unchanged.
• If a distributor assigns the ISRC, the artist does not control the registrant prefix component of the code.

Ownership Transfers

An ISRC does not change when recording ownership changes. The identifier is permanent and continues to represent the same master recording regardless of who controls it. New ownership is reflected in contractual and metadata systems, not by issuing a new ISRC.

Managing a registrant prefix internally provides greater control over long-term catalog consistency. Using distributor-assigned ISRCs simplifies short-term delivery but may limit control over future catalog migrations.

Embedding and Propagation in Metadata Workflows

Assigning an ISRC is only effective if the code travels consistently with the recording through mastering, distribution, and reporting systems. An ISRC stored only in an internal spreadsheet does not ensure accurate tracking. It must be embedded in files and included in delivery messages used by distributors and digital service providers.

File-Level Embedding

Common audio formats support storage of the ISRC in metadata fields:

• MP3 (ID3 tag): Stored in the TSRC frame
• WAV/BWF: Stored in designated RIFF or BWF metadata fields
• FLAC/Vorbis: Stored in the ISRC tag

Embedding at the file level allows downstream systems to extract the identifier during ingestion. This is particularly relevant when recordings are exchanged outside formal distributor pipelines, such as direct label deliveries or archival transfers.

Delivery Standards

Within digital supply chains, ISRCs are transmitted via structured metadata standards, most commonly those developed by DDEX.

Two relevant message types include:

• Electronic Release Notification (ERN): Used by labels and distributors to deliver releases to digital service providers. The ISRC is a required field in ERN messages for commercial recordings.
• Recording Information Notification (RIN): Used primarily during studio and production workflows to capture recording-level credits and identifiers before release.

Accurate propagation requires that the ISRC:

• Matches the code embedded in the audio file
• Matches the code submitted in ERN or other delivery messages
• Remains consistent across territories and distribution partners

Common Propagation Errors

• Delivering a recording with one ISRC in the file and a different ISRC in the release message
• Reassigning a new ISRC during re-delivery to a new distributor
• Omitting the ISRC in a metadata update or catalog migration
• Allowing aggregators to auto-generate new ISRCs for previously released masters

Propagation consistency is as important as assignment accuracy. Once distributed, digital service providers use the ISRC as the primary recording-level reference in usage reports, royalty calculations, and catalog indexing.

ISRC in Usage Reporting and Royalty Systems

Digital service providers report recording-level usage using ISRCs as the primary identifier. Streams, downloads, and certain performance reports reference the ISRC rather than a release barcode or internal catalog number. Royalty accounting systems rely on that reference point to match usage data to the correct master owner.

Within streaming environments, ISRCs appear in:

• DSP usage reports delivered to labels and distributors
• Revenue statements that allocate income per recording
• Catalog management systems used to reconcile territory-level reporting

For U.S. non-interactive digital performances, usage reports submitted to SoundExchange include ISRCs to identify the specific sound recording performed. Matching occurs at the recording level, not at the release level. If the ISRC is missing or incorrect, the performance may be held as unmatched.

In neighboring rights systems outside the United States, ISRCs are similarly used to identify recordings for performance royalty distribution. Collective management organizations rely on standardized identifiers to match broadcast logs and digital reports to registered recordings.

Reporting workflows typically follow this sequence:

1. Recording is assigned an ISRC and embedded in metadata.
2. Distributor delivers release information to DSPs with the ISRC included.
3. DSP logs usage events and associates them with the ISRC.
4. Usage reports reference the ISRC in royalty statements.
5. Labels, artists, or collecting societies reconcile income based on the ISRC.

When ISRCs are duplicated, reassigned, or inconsistently embedded, usage history may fragment across multiple identifiers. That fragmentation can lead to parallel catalog entries and reporting discrepancies.

ISRCs function as the anchor point for recording-level accounting. Royalty systems interpret activity through that code rather than through title matching alone.

Catalog Migrations, Remasters, and Edge Cases

ISRC errors most frequently occur during catalog transitions rather than at initial release. Distributor changes, remastering projects, and format updates introduce risk when assignment rules are misunderstood or inconsistently applied.

Distributor Changes

When moving a catalog from one distributor to another, the original ISRC must remain attached to the recording if the audio has not changed. Assigning a new ISRC to an unchanged master creates a second recording entry in digital service provider systems. Historical usage remains tied to the original code, while future usage may attach to the new one, resulting in split reporting.

Correct migration practice includes:

• Delivering the original ISRC in all re-ingestion files
• Confirming that DSP systems recognize the recording as a continuation rather than a new asset
• Avoiding automatic reassignment by the new distributor

Remasters and Audio Modifications

A new ISRC is required when a remaster produces a perceptible difference in audio. Minor level adjustments or file format conversions that do not alter the listening experience do not require a new ISRC.

Examples requiring a new ISRC:

• A remaster with noticeable tonal or dynamic changes
• A spatial audio or Dolby Atmos mix that constitutes a new mix
• A revised edit altering structure or duration

Examples not requiring a new ISRC:

• Re-encoding the same master from WAV to FLAC
• Lossless format conversion without audio change
• Repackaging the same recording in a new release configuration

AI-Assisted and Derivative Recordings

If AI tools are used to create a new recording derived from an existing one, a new ISRC is required when the result constitutes a distinct recording. An AI-assisted restoration that materially alters the sound is treated similarly to a remaster and evaluated under the same perceptibility principle.

Music Video Recordings

Music video recordings require their own ISRC even if the audio track is identical to the sound recording. The identifier applies to the audiovisual recording as a separate asset.

Ownership Transfers

Ownership changes do not justify a new ISRC. The identifier remains fixed to the recording. Rights ownership updates must be handled through contractual documentation and metadata systems rather than by issuing a replacement code.

Catalog integrity depends on the consistent application of assignment rules during transitions. Once fragmented, usage history cannot be merged across ISRCs without manual reconciliation in platform systems.

Practical Implications for Rights Holders

ISRC management affects revenue continuity, reporting accuracy, and catalog integrity. Errors often surface only after distribution, when correcting them becomes more complex.

Key operational considerations include:

• Control of Assignment - Holding a registrant prefix allows direct management of ISRC continuity across distributors and reissues. Relying on distributor-assigned ISRCs reduces administrative burden but can complicate migrations if historical codes are not preserved.
• Catalog Auditing - Periodic review of released recordings helps identify duplicate ISRCs, missing codes, or inconsistencies between file metadata and distributor records. Audits are particularly important before changing distribution partners.
• Remaster Planning - When planning remasters or alternate mixes, assignment decisions should be made before delivery. Determining whether a new ISRC is required avoids post-release conflicts.
• Data Consistency Across Systems - The ISRC embedded in the audio file should match the ISRC delivered through metadata messages and the ISRC displayed in DSP back-end dashboards. Discrepancies can prevent accurate matching in royalty systems.
• International Reporting - Neighboring rights claims outside the United States rely on ISRC accuracy. Incorrect or duplicated codes may affect broadcast and performance collections in foreign territories.
• Archival and Long-Term Management - Maintaining an internal registry linking ISRCs to master files, recording dates, and ownership history supports future licensing, audits, and catalog sales.

ISRC discipline reduces fragmentation across reporting environments and limits the need for corrective data reconciliation after release.

Frequently Asked Questions

Does every song need an ISRC? Every commercially distributed sound recording or music video recording requires an ISRC. The composition itself does not. Multiple recordings of the same song each require separate ISRCs.

Can two recordings share the same ISRC? No. An ISRC must uniquely identify one specific recording. Reusing an ISRC for a different recording violates ISO rules and creates reporting conflicts.

Does re-releasing a song require a new ISRC? Not if the audio has not changed. The same master recording retains its original ISRC across territories, distributors, and release formats.

If I remaster a track, do I need a new ISRC? If the remaster produces a perceptible audio difference, a new ISRC should be assigned. Minor format conversions without audio change do not require a new code.

Does changing distributors require a new ISRC? No. The original ISRC must remain attached to the recording. Assigning a new ISRC during migration creates duplicate entries in DSP systems.

Who owns the ISRC? The ISRC is permanently associated with the recording. The registrant prefix holder assigns it, but ownership of the recording can transfer without changing the ISRC.

Can a distributor assign ISRCs for me? Yes. Many distributors generate ISRCs automatically. However, the distributor’s registrant prefix will appear in the code.

Are ISRCs required for neighboring rights collections? Yes. Neighboring rights administrators and digital reporting systems rely on ISRCs to match performance data to the correct recording.

Key Takeaways

• The ISRC is the global identifier for individual sound recordings and music video recordings, standardized under ISO 3901.
• Each materially distinct recording requires its own ISRC; unchanged masters retain their original code across releases and territories.
• The year element reflects the year of assignment, not necessarily recording or release year.
• A registrant prefix authorizes a rights holder or distributor to generate ISRCs without central approval for each recording.
• ISRCs must be embedded consistently in audio files and metadata deliveries to prevent duplicate catalog entries and reporting errors.
• Distributor changes do not justify assigning a new ISRC to an unchanged master.
• Royalty reporting systems, including DSP statements and neighboring rights distributions, rely on ISRCs as the primary recording-level reference.

Practical Resources

ISRC Catalog Audit & Continuity Template

This template supports internal catalog integrity, distributor migrations, remaster projects, and royalty audits. It centralizes recording-level data and prevents duplicate ISRC assignment.

Recommended Internal Tracking Fields

Maintaining this registry prevents:

• Accidental reassignment during distributor changes
• Duplicate DSP entries
• Fragmented usage history
• Neighboring rights mismatches

This registry should be updated before:

• Any catalog migration
• Any remaster campaign
• Any distributor change
• Any catalog acquisition

ISRC Metadata Failure Scenarios

Most ISRC problems arise after release. The following table outlines common failures and their operational consequences.

These failures are typically preventable at the assignment or migration stage. Correction after release often requires manual intervention across DSP systems.

References

International Organization for Standardization. (2019). ISO 3901:2019 – Information and documentation — International Standard Recording Code (ISRC). https://www.iso.org/standard/74883.html

International ISRC Agency (IFPI). (n.d.). About the ISRC system. https://isrc.ifpi.org/en/

U.S. ISRC Agency (RIAA). (n.d.). How to obtain an ISRC registrant code. https://usisrc.org/how-it-works/

DDEX. (n.d.). Electronic Release Notification (ERN) message suite. https://ddex.net/standards/electronic-release-notification-message-suite/

DDEX. (n.d.). Recording Information Notification (RIN) standard. https://ddex.net/standards/recording-information-notification/

SoundExchange. (n.d.). ISRC search database. https://isrc.soundexchange.com/

ExifTool. (n.d.). RIFF metadata tags (WAV/BWF). https://exiftool.org/TagNames/RIFF.html

CISAC. (n.d.). ISWC — International Standard Musical Work Code. https://members.cisac.org/CisacPortal/documentLink.do?sw=off&id=18367

GS1. (n.d.). What is a UPC? https://www.gs1us.org/upcs-barcodes-prefixes/guide-to-upcs