An ISRC code is the unique identifier attached to every commercial recording — and without one, your track cannot be tracked, matched, or paid correctly across streaming platforms, broadcast, and neighbouring rights collection. Here is everything independent artists need to know.
What is an ISRC code?
ISRC stands for International Standard Recording Code. It is a twelve-character alphanumeric identifier assigned to a specific recording — not a song, but the actual master take. The format is: two-letter country code, three-character registrant code, two-digit year, and five-digit designation number. For example: GB-CGM-26-00001. Every commercially released recording should carry one. The ISRC travels with the recording wherever it goes — embedded in audio files, listed on distribution upload forms, and referenced in royalty reporting systems. It is the primary mechanism by which streaming platforms, broadcasters, and collecting societies match a playback event back to the rights holder who should be paid.
Why every track needs one
The ISRC is not a nice-to-have. It is the plumbing that makes royalty payment possible at scale. When a listener streams your track on Spotify, the platform logs a playback event against the ISRC associated with that file. That log feeds into Spotify's royalty calculation system, which then reports usage to your distributor. SoundExchange — the US neighbouring rights organisation — uses ISRCs to match digital radio plays to recordings and route payment to the rights holder. PPL in the UK uses ISRCs to track broadcast usage on UK radio and television. Without a correctly assigned ISRC, the matching process fails, and the royalty is either held in suspense or permanently unmatched. For back-catalogue releases — tracks uploaded years ago without an ISRC — the losses compound with every stream that goes unpaid.
Who issues ISRC codes in the UK?
In the United Kingdom, PPL (Phonographic Performance Limited) is the national ISRC agency. PPL manages the UK registrant code block and can issue new registrant codes to labels and artists who want to self-administer their ISRCs. If you are a PPL member, you can request a registrant code and manage your own ISRC allocation. If you release through a distributor, most major distributors — DistroKid, TuneCore, CD Baby, Amuse — will generate and assign an ISRC for you at the point of upload. The ISRC they assign is registered to their registrant code, not yours. That is fine in practice, but it is worth recording which ISRC was assigned to which track in your own catalog log so you can cross-reference it against royalty statements later.
How to get an ISRC code
There are three routes to obtaining an ISRC for your recording:
- Via your distributor — the simplest option for most independent artists. When you upload a track to DistroKid, TuneCore, CD Baby, or a similar service, an ISRC is generated automatically if you do not supply your own. Keep a record of it from your distribution dashboard.
- Directly from PPL — if you are a PPL member with your own registrant code, you can generate ISRCs within your own block and self-administer your catalog. This is the better option for artists managing more than twenty releases, or for anyone running a label.
- Via a label services company — companies like Code Group Music can assign ISRCs and maintain a catalog registry on your behalf as part of a broader metadata administration service. This ensures your codes are correctly recorded and cross-referenced against your royalty accounts.
Common ISRC mistakes to avoid
The most frequent ISRC error is reuse: assigning the same ISRC to a different version of a track, or failing to generate new ISRCs for remasters, remixes, and alternate edits. Each distinct recording must carry its own unique ISRC. A remaster — even a subtle one — is a different recording. A radio edit is a different recording. A feat. version with an additional artist is a different recording. Reusing an ISRC conflates two recordings in the matching system, which can cause royalties to be attributed to the wrong version or the wrong rights holder. The second most common mistake is failing to register ISRCs for back-catalogue tracks that were released before the artist understood the system. These tracks continue generating streams and broadcasts without a matching code, meaning the royalties have nowhere to go.
If you are unsure whether your catalog has ISRCs assigned, or whether those ISRCs have been correctly registered with PPL and your distribution chain, a Catalog Assessment is the right starting point. Code Group Music reviews your full release history, cross-references codes against PPL records, and identifies any recordings that are missing identifiers or have been assigned incorrectly. Start your free assessment at codegroupmusic.co.uk/#catalog-assessment.
Published