Industry update

SoundExchange and IFPI Made ISRC Assignment Easier for Self-Releasing Artists

SoundExchange and IFPI launched automatic ISRC assignment for individual recordings. If you release music yourself, this is a prompt to document every ISRC before royalties go missing.

Bradley J Simons
Bradley J Simons
Updated July 21, 2026

Short answer

SoundExchange and IFPI announced automatic ISRC assignment on June 2, 2026. The new online capability can assign an International Standard Recording Code to an individual recording through immediate registration, checks SoundExchange's database first to reduce duplicate assignments, and is designed for small labels and self-releasing artists who do not manage large catalogs. Independent artists should keep an ISRC ledger for every recording, confirm distributor-assigned ISRCs before release day, and register recordings with the societies that use ISRCs to match royalties.

SoundExchange and IFPI launched a simpler way to assign ISRCs to individual recordings. Use it as a metadata cleanup prompt. Know which ISRC belongs to every master, never create a duplicate code for the same recording, and keep the code ready for distribution and royalty claims.

Key takeaways

  • SoundExchange and IFPI announced automatic ISRC assignment for individual recordings on June 2, 2026.
  • The system checks SoundExchange's database before assigning a code, which is meant to reduce duplicate ISRCs.
  • It is designed for small labels and self-releasing artists who do not own or manage large catalogs.
  • Artists should keep an ISRC ledger, confirm distributor-assigned codes, and use the same code when registering recordings for royalty collection.

What happened?

SoundExchange and IFPI announced automatic ISRC assignment for individual recordings. An ISRC is the code that identifies a specific recording or music video across delivery, reporting, rights management, and royalty systems. The new capability assigns a code through online registration and checks SoundExchange's database first to avoid giving the same recording multiple codes.

The announcement says the workflow complements the existing national-agency route. In the United States, that route usually means getting an ISRC prefix through the RIAA or letting an appointed manager, such as a distributor, assign codes for the recordings it handles.

ISRC workflow for self-releasing artists
1

Check first

Confirm whether the recording already has an ISRC from a distributor or prior release.

2

Assign once

Use one code for one recording version. Do not create a duplicate for the same master.

3

Store it

Keep the ISRC beside title, artist, version, release date, UPC, and rights owner.

4

Claim royalties

Use that code when registering with SoundExchange and neighboring-rights societies.

Why independent artists should care

Most self-releasing artists meet ISRCs through a distributor form and never build their own ledger. That is fine until you need to move distributors, register neighboring rights, prove which version is which, or clean up a duplicate. The code is boring, but it is one of the identifiers that keeps a recording connected to money.

Where ISRCs get messy
Clean setupProblem setup
One masterOne ISRC follows that exact recording everywhereA new distributor assigns a second ISRC to the same audio
VersionsRadio edit, remix, acoustic, and live versions each have their own codeDifferent recordings share one code because the titles look similar
RoyaltiesSoundExchange and neighboring-rights claims use the same documented codeStatements arrive with codes nobody on the team can map back to a release
The ISRC is not the song. It is the specific recording, and that distinction matters when royalties get matched.
Velveteen

What to do now

Build the ledger before release day

For every master, keep title, artist, version, ISRC, UPC, release date, distributor, rights owner, featured performers, and source session in one sheet. Do this before you switch distributors or upload alternate versions.

Check before assigning

If a distributor already assigned an ISRC, use that code. Do not assign a new one just because you are re-delivering the same recording. New codes are for distinct recordings, not for a new campaign around the same master.

Do not confuse ISRC with publishing metadata

ISRC identifies the recording. It does not replace songwriter splits, publisher names, ISWC, PRO registration, mechanical collection, or neighboring-rights performer claims. You need the code, then you need the rest of the metadata around it.

What is still unclear?

SoundExchange and IFPI did not publish a full cleanup process for existing duplicate ISRCs in the announcement. They also did not say whether distributor-assigned codes that are missing from the public database will be backfilled automatically. For now, the practical work is documentation: know the code before you need to dispute it.

Sources

Frequently asked questions

What is an ISRC?

An ISRC is the International Standard Recording Code that identifies a specific recording or music video across distribution, reporting, and royalty systems.

What changed with SoundExchange and IFPI?

They announced an online capability that can automatically assign an ISRC to an individual recording through immediate registration, with a duplicate check against SoundExchange's database.

Should artists replace distributor-assigned ISRCs?

No. Do not create a second ISRC for a recording that already has one. First confirm what your distributor assigned, then document and use that code consistently.

Why does this matter for royalties?

ISRCs help match recordings to usage, statements, claims, and neighboring-rights collections. A missing or duplicated code can make royalty cleanup harder later.

Related Velveteen guides

Related Velveteen tools

Artist-facing updates

Get music industry updates without the noise

Short notes on platform changes, royalty issues, and release marketing moves that actually affect independent artists.

Improve this page

Was this useful? Send a signal or flag a correction.