ISRC Codes: Format, Assignment and Royalty Matching
By Qlero Team

Learn the ISRC format, who assigns codes and when a remaster should retain one. Check catalog mistakes without confusing identity, rights and payment.
An ISRC identifies a particular sound recording or music video recording. For a label, the important questions are when to assign it, when to keep it, and whether the recording behind an incoming code is the one your catalog describes.
An incorrect identifier can create a matching problem. A correct identifier does not, by itself, establish ownership, contractual shares or payment. This guide focuses on ISRC assignment and preventable catalog mistakes, rather than a complete reconciliation of distributor reports.
What an ISRC identifies
The International Standard Recording Code belongs to the recording, not its composition or the release containing it. IFPI's scope guidance distinguishes sound and music video recordings from works, products and artwork.
An unchanged recording can appear on a single and later on an album without acquiring a new recording identity. The release identifier is a separate question. For the work-level distinction, see ISWC versus ISRC.
A rights transfer also does not replace the ISRC. IFPI's ownership guidance says the identifier stays with the recording when ownership changes. Keep current rights and agreement information alongside it; neither the prefix nor the rest of the code proves who is entitled to a royalty.
The three parts of an ISRC
IFPI describes a 12-character value, divided into three elements:
| Element | Length | What to check |
|---|---|---|
| Prefix | 5 characters | Two letters followed by three alphanumeric characters; use the prefix allocated through the ISRC system. |
| Year of reference | 2 digits | The assignment year, not necessarily the recording or release year. |
| Designation | 5 digits | A value within the registrant's allocated range, not repeated for that prefix in the same year. |
For example, US-ABC-26-00047 displays the value USABC2600047: 5 + 2 + 5 = 12 characters. This is a hypothetical formatting example, not a verified assignment or a code to use for your recording.
Do not infer a recording's current country or owner from its prefix. A well-formed string is only a syntax check, not confirmation that it was assigned to the intended audio.
Who assigns ISRCs?
The assignment route should be deliberate:
- A recording owner can obtain a prefix through the relevant agency and maintain its own assignments. IFPI's prefix guidance stresses record keeping and compliance with the rules.
- A properly appointed ISRC Manager can assign codes on behalf of owners or exclusive licensees under the relevant arrangement. A distributor doing this does not thereby acquire ownership of the recording.
- IFPI also offers an online assignment service. It takes recording metadata and checks its dataset for an existing code. That lookup is not a guarantee that every prior assignment worldwide will be found.
The U.S. ISRC Agency is operated by the RIAA. For another territory, use IFPI's agency route rather than assuming the U.S. process applies.
Before delegating assignment, ask who will supply the code, how you will receive the recording metadata, and how existing codes are preserved on a later transfer. Those are recommended handover questions, not evidence that one assignment route produces better royalty results.
When a recording needs a new code
IFPI's assignment guidance calls for a new ISRC for a new or materially changed recording. Examples include a different mix or edit, or a historical restoration involving creative input. A previously uncoded recording can also receive an ISRC retrospectively; its assignment year need not be its original release year.
A remaster is not automatically a new recording for this purpose. The IFPI FAQ on remastering says an ordinary remaster generally retains the existing code, unless significant new creative input warrants a new one. Assess the actual change, not just the word “remastered” in a title.
Likewise, changing the distribution partner, release packaging, file format or bitrate does not, by itself, justify a replacement code for the same recording.
Example: a single, then a deluxe edition
Suppose a label releases a single using USRC12345678. Six months later, a deluxe edition contains a version described as a remaster. The code here is another hypothetical example, not a verified registration.
The assignment decision has two different branches:
- If it is an ordinary remaster that remains fundamentally the same recording, retaining the ISRC is generally appropriate. The deluxe edition's packaging does not alone change that conclusion.
- If the new version materially changes the recording, apply the new-recording rules and record the distinct version under its appropriate ISRC.
Now assume the deluxe project also has different producer credits or royalty terms. Those facts need their own metadata and agreement review; they are not, on their own, proof that the audio requires a new ISRC.
As a separate illustration, a local report that groups only by ISRC could combine rows you need to distinguish for accounting. Inspect the available release, version and reporting fields before drawing conclusions. This is an assumed local grouping problem, not a claim that every DSP merges the income or that the history is irrecoverable. Neither a new code nor a successful match automatically applies the correct contract.
Six ISRC mistakes to check
Use these as review prompts, not as a measured ranking of the industry's most common errors:
- One code attached to distinct recordings. Compare the actual versions and assignment records; similar names are not enough.
- A missing code in a required field. Check whether the source omitted it or the import read the wrong column. Do not invent an identifier to clear an error.
- A second code assigned during a transfer. Ask the parties to establish the existing assignment before treating both codes as interchangeable.
- A blanket “new version, new code” rule. A remix and an ordinary remaster are not the same assignment decision. Nor does a new album package necessarily create new recordings.
- ISWC entered where ISRC belongs. The composition's code cannot stand in for the recording's code.
- Formatting that changes the value. Keep the complete identifier, including zeroes. Normalize display separators only according to the receiving system's rules; a formatting repair must not silently become a different assignment.
Six controls for your catalog
These are suggested operating controls, not a promise that a checklist eliminates matching failures:
- Keep an assignment register linking each ISRC to its recording, version, assignment source and supporting metadata.
- Choose who controls assignment. An own-prefix workflow requires reliable record keeping; using a manager does not remove the need to retain the resulting data.
- Review required identifiers before delivery and before importing royalty reports. Treat an unknown value as an exception to investigate.
- Record why a changed version retained or received a code. Keep that decision separate from credits and contractual shares.
- Compare the codes supplied by a new distributor with the existing register before accepting replacements.
- Preserve source values and document normalization. Make it possible to trace a cleaned value back to the report that supplied it.
This assignment register complements, rather than replaces, a review of report scope, duplicate income and contractual calculations.
What Qlero's documentation supports
Qlero's track creation guide requires a track name, artist and ISRC. It specifies an ISRC without dashes and uniqueness within the company. Creating repertoire requires Repertoire write access. That company-level check is not proof of a valid international assignment or ownership.
Its aliases guide describes additional identifiers used to match incoming sales to repertoire. External ID is for reference and export, not sales matching. Editing aliases requires the relevant Repertoire access and an explicit save; only link codes after confirming that they identify the same recording.
Qlero's invalid-lines guide distinguishes an unmatched ISRC from missing dates, amounts, exchange rates and other problems. Linking in the mapping manager saves an alias immediately and can affect later files from any source in the company. Sales Files and Repertoire & Agreements permissions apply. Review remaining invalid reasons after revalidation.
That repair is not a statement rewrite. The revalidation guidance says revalidation can repair invalid rows linked to a published or closed period while leaving its statements unchanged.
These are documentation-based descriptions, not independent product tests. They do not establish that Qlero assigns ISRCs, repairs an upstream registry, verifies rights or moves money. Confirm any such requirement separately; an undocumented workflow should not be assumed either available or absent.
Frequently asked questions
Does every recording need its own ISRC?
Each distinct recording should have its own identity under the ISRC rules. Do not assign a second code merely because the same recording appears on another release. Whether a changed version is distinct requires the assessment described above.
Can I reuse an ISRC when re-releasing a track?
Keep the existing code for the same recording. Reusing that value on another release is different from assigning it to a different recording, which is not allowed.
What is the difference between an ISRC and a UPC?
An ISRC identifies the recording; a UPC identifies a product such as an album or single. They answer different questions and should not be substituted for one another.
How does a label get an ISRC?
Use the appropriate agency/prefix route, a properly appointed manager, or an applicable online assignment service. First establish whether the recording already has a code, and retain the assignment details.
What happens when a royalty report's ISRC does not match?
Investigate the source value, the actual recording and the receiving system's exception reason. An unmatched identifier is not enough to conclude that income is permanently lost. In Qlero, fixing a match may still leave another validation or contract issue.
Does changing distributor require new ISRCs?
Not for the same unchanged recordings. Supply the existing identifiers and confirm the provider's transfer process; do not let a change of service become an unexplained reassignment.
Make the assignment decision traceable
A useful ISRC register records what was identified and why a code was assigned or retained. Keep that evidence separate from release packaging, ownership and royalty terms, then investigate discrepancies without treating a successful identifier match as a payment guarantee.
Book a Qlero demo to discuss your repertoire and representative royalty files, and ask to see how the documented matching workflow handles your specific exceptions.