Direct answer: An ISRC identifies a particular sound recording. It is not a copyright registration, ownership certificate, composition identifier, or sample clearance. Assign or receive codes through the appropriate recording owner or distributor process, keep each code tied to the correct version, and reconcile the code with approved metadata before delivery.
What an ISRC identifies
ISRC stands for International Standard Recording Code. It is a code attached to a sound recording so the recording can be distinguished in metadata and reporting systems. Think of it as a label for a particular recorded asset, not a label for the entire creative project. A song may have one composition and several recordings: an original master, live take, instrumental, clean edit, or remix. The recording record is where the code belongs.
IFPI’s official guidance is the primary source for using ISRC. Read current instructions rather than relying on a remembered prefix or an old distributor workflow. Keep the code with the audio file, master name, version, recording owner, and approved delivery metadata. A code is most useful when a later reviewer can tell exactly which file it identifies and why that file is the authorized release version.
What an ISRC does not prove
An ISRC is not a copyright registration, ownership certificate, contract, split sheet, trademark registration, or sample license. Having a code does not prove that a person owns the master, that all performers consented, or that the underlying composition was cleared. Conversely, not yet having a code does not answer whether a creator has rights. Keep the identifier task separate from the rights review while linking both records.
Do not use the code as a shortcut in a dispute. If two people disagree about a master, assigning a number cannot decide the issue. Record the disagreement, identify the authorized decision maker, and obtain professional advice where necessary. The code should be entered only after the team has selected the recording it intends to distribute and has a truthful basis for the related ownership and credit fields.
Versions and recordings
Version control is the practical heart of ISRC work. Use explicit labels for original mix, radio edit, instrumental, live version, remix, remaster, and alternate language version. Compare audio, not just file names. Record the creation date, producer or editor, final approval, and relationship to the composition. A small change in loudness may not mean the same thing as a new creative recording, while a new vocal or remix usually deserves careful review under current guidance.
Never copy a code from a similar track because the title and artist match. Do not create duplicate records for the same approved master merely because it is delivered through two channels unless the governing process instructs you to do so. If the status is unclear, put the version in review and consult IFPI or the relevant distributor. A conservative pause is better than a catalog with codes attached to the wrong audio.
Assignment and custody
The recording owner or the authorized release party typically manages the identifier workflow through an approved route. The exact process can vary by territory, distributor, and account arrangement, so use current official guidance. Keep a custody note stating who requested or received the code, when, through what system, and for which master. If a label, distributor, or collaborator supplies a code, preserve the confirmation and verify the code against the audio they reference.
When rights or distribution arrangements change, retain the original code history and update the owner, label, or account metadata only according to the applicable process. A transfer of administration is not necessarily a new recording. A new code is not a substitute for documenting an assignment or license. Ask the responsible rights professional or service about the correct correction path rather than withdrawing a code casually.
Metadata reconciliation
Create one approved metadata row for each recording. Include ISRC, title, version, primary artist, featured artists, contributors, recording owner, release date, label, audio file name, and status. Add composition writers and publishers in the appropriate separate fields. Compare the row with the master, artwork, lyric information, video description, and distributor form. Mark each field as confirmed, pending, or not applicable.
Names need deliberate handling. A professional artist name, legal name, writer name, and account name may differ, but the choice should be intentional and consistent with agreements and platform requirements. Preserve punctuation and accents where supported. Keep a change log for corrections. The music copyright basics guide explains why the composition and recording cannot be treated as one asset, while the music metadata checklist broadens the delivery review.
The CODE lifecycle framework
Use CODE: Confirm the recording; Organize the version history; Document custody and rights evidence; Enter the code only in the approved delivery packet. Confirm means listening to the exact master. Organize means making version names unambiguous. Document means linking the identifier to the authorized recording owner and contributors. Enter means copying the approved value into a form under creator control.
Run CODE when the master is locked, when a distributor provides or requests an identifier, and when a catalog correction is needed. At the first gate, resolve the audio. At the second, reconcile the value and metadata. At the third, preserve the correction history and check every live destination that needs updating. This framework helps prevent clerical errors; it does not determine legal ownership or guarantee platform reporting.
Collaborators, labels, and ownership records
Multiple people may touch a recording without having the same rights or responsibilities. The performer may have a credit, the producer may have a contract, a label may control delivery, and a distributor may administer an account. Record each relationship separately from the ISRC. Link contracts, contributor approvals, split sheets, and release instructions to the master record. If a collaborator sends an identifier without identifying the associated audio, request clarification before using it.
For an AI-assisted project, preserve the human-authorship and tool records as well as the ISRC. For a sampled project, preserve the clearance packet. For a co-written project, preserve the split. The identifier travels with the recording, but it does not absorb the evidence for those other layers. Read the AI music copyright principles, split sheet guide, and sample clearance workflow for those distinct questions.
ISRC decision table
| Scenario | Record first | Identifier action |
|---|---|---|
| Final original studio master | Approved audio, recording owner, version, credits, delivery status. | Follow current authorized assignment process and link code to that file. |
| Instrumental or clean edit | Audio comparison, edit description, release purpose, metadata. | Check current guidance rather than copying the original code. |
| Remix or materially changed recording | Remixer agreement, source master, new audio, approval. | Determine treatment under current IFPI or distributor guidance. |
| Code supplied for an unknown file | Confirmation, source, owner, exact audio, version history. | Hold entry until the code-to-recording match is verified. |
Distributor and platform fields
Distributors collect identifiers alongside title, artist, artwork, credits, and release details. Their upload instructions can be useful operational references, but the form does not decide the rights behind a code. Enter only values that match the approved release packet. Save the submitted fields and confirmation. When claiming Spotify or Apple Music artist access, follow the official account guidance and keep profile administration separate from the recording identifier ledger.
Platform ingestion can expose a mismatch: the wrong audio may appear under a code, a title may be abbreviated, or an artist identity may be merged. Treat that as a catalog correction task. Gather the code, exact audio, distributor order, dates, screenshots, and ownership contacts. Do not create a new identity or duplicate release merely to hide a clerical error; follow the relevant support process and document who approved the correction.
Correcting a mismatch
First stop new copies of the incorrect metadata. Compare the file sent, the file intended, the code, and the confirmation. Classify the problem: wrong code on the right audio, right code on the wrong audio, duplicate delivery, wrong artist name, or a genuinely new version. Then contact the party that controls the affected catalog entry with a concise evidence packet. Keep the original records; correction does not mean erasing history.
After a correction, recheck every destination that received the bad field and update internal records. Notify collaborators when public credit or reporting may be affected. Do not promise that a platform will correct an item by a particular date unless it has said so. Artello can record the request, evidence, owner, and status, but it cannot autonomously contact a service or submit changes on your behalf.
ISRC checklist
- Identify the exact sound recording and version before entering a code.
- Keep composition, master ownership, and identifier records distinct but linked.
- Use IFPI and current distributor instructions as primary operational references.
- Record who supplied or assigned the code and the confirmation date.
- Never copy a code from a similar title without an audio match.
- Reconcile code, audio, title, artists, credits, and release status.
- Preserve corrections and investigate every code-to-file mismatch.
- Keep the creator or authorized release owner in control of submission.
For the surrounding rights workflow, read music copyright basics, the split sheet guide, and sample clearance. Artello offers records and guidance, not identifiers, legal clearance, or autonomous distribution.
Build a catalog record that survives handoffs
An identifier is most reliable when it lives in a catalog record with context. Include the exact audio file, a listening reference, title, version label, primary and featured artists, recording owner, release status, code source, assigned date, and the person who approved the entry. Add links to contributor agreements, sample permissions, and composition records without confusing those documents with the code itself. A catalog record should answer both “what is this code?” and “who authorized this release?”
Use one source of truth for the approved row, then export the fields needed by a distributor or platform. Avoid letting several spreadsheets become competing catalogs. If a collaborator maintains a separate list, compare it at handoff and record any differences. A small discrepancy in punctuation may be harmless in one destination and confusing in another, so classify rather than dismiss it.
Catalog maintenance continues after launch. Add takedown, replacement, remix, reissue, and correction events to the history. Do not delete a prior code record merely because a release is no longer active; explain its status and preserve the audio relationship. When an authorized owner changes, record the effective date and the responsible service or label process. Keep public claims modest: the catalog shows what your team recorded, not an independent adjudication of every right.
Schedule a human review before a reissue or compilation. Compare the incoming audio with existing masters, check whether the release is a new recording or a reuse, and inspect credits and ownership evidence. Then follow current IFPI or distributor instructions. This process prevents a familiar title from hiding a different recording and gives the creator a clear audit trail when a platform asks for clarification.
Questions creators ask
What does an ISRC identify?
An ISRC identifies a sound recording, such as a particular master or recording version. It does not identify the underlying composition and does not by itself prove ownership or clearance.
Does a new mix need a new ISRC?
The answer depends on whether the version is a new recording for the relevant system and guidance. Compare the actual recording and current IFPI or distributor instructions; do not change codes just to solve a metadata disagreement.
Can Artello assign an ISRC?
Artello provides workflow guidance and records but does not claim to issue identifiers or autonomously submit releases. Follow the current IFPI and distributor process and keep the creator in control.
Citations and further reading
These official sources support the factual descriptions in this guide. They are starting points for your own review, not a substitute for advice about a particular work or dispute.
Keep the decision with the creator
Artello can help you organize workflow guidance and records so that your decisions, files, credits, and follow-ups stay visible. It does not generate legal clearance, decide ownership, or autonomously submit releases or permissions. Create a creator-controlled workspace when you are ready, or review pricing and workspace options before choosing a plan.
This article is general information, not legal advice. Rules can differ by country, contract, and fact pattern. When a release involves uncertainty, ask a qualified attorney or rights professional to review the actual materials.