ISRC code

A song can exist in many recordings: an original studio performance, a live version, a new interpretation and a remix. An ISRC identifies a particular recording within that landscape, not the abstract song shared by those versions. This distinction helps businesses exchange information about exactly which recorded performance was delivered, used or reported instead of relying only on a title and artist name.

The identifier can support catalog matching and usage reporting, but it is not a complete rights record. The people controlling a recording can change without changing the recording itself. Likewise, two recordings of the same composition can have different recording owners and different ISRCs. To understand the underlying musical work, consult the relevant composition information and publishing arrangements separately.

An ISRC contains twelve alphanumeric characters, often displayed in grouped form for readability. Its components comprise a country code, a registrant code, a year of reference and a designation code. The groups help create a unique identifier within the assignment system. They should not be interpreted as a compact biography of the recording or a public certificate describing its legal status.

The code does not encode a track title, ownership percentage, songwriter list or release-level product identity.

Codes may be assigned through an authorized registrant arrangement or supplied by a distributor or another authorized provider. The available route depends on the relevant ISRC framework and provider services. Before requesting a new identifier, check whether the exact recording already has one. Assigning another code merely because an artist changes service providers can create unnecessary ambiguity in catalog and reporting records.

Maintain a recording register that connects each code to the approved audio, artist, title, version description and assignment details. Also retain contributor and rights documentation separately. This register helps the release team distinguish an instrumental from a vocal version or a live performance from a studio master. It should be accessible to whoever coordinates distribution, without making one provider the only keeper of essential information.

An unchanged recording generally retains its ISRC when it appears on another release or moves between distributors. A new performance, remix or materially different recording version generally needs its own identifier. Changes to release artwork, ownership or the surrounding collection do not by themselves create a new recording. The relevant question is what happened to the recorded content, not whether the campaign feels new.

Borderline cases need closer attention. A technical conversion is different from an edit that changes the recording, and the word remastered alone does not settle every case. Consult current ISRC guidance and the responsible assignment provider when uncertain. Document the decision with the source file and version notes so a future team does not have to reconstruct why two similar files share or differ in identification.

Imagine a Dubai artist preparing a studio single, an instrumental version and a separately recorded live performance in Abu Dhabi. The release coordinator treats them as distinct recordings and checks the appropriate identifier for each. The shared song title does not make them one recording. The register uses clear version labels and links each approved audio file to its assigned code before delivery.

Later, the unchanged studio master appears on a collection through another distributor. The team supplies its existing ISRC rather than requesting a new one solely for the new release. They separately preserve the composition credits and recording permissions. Nothing about the code is presented as UAE copyright registration, proof of local ownership or evidence that every contributor has approved every possible commercial use.

An ISRC can help match reported activity to a recording, but it does not collect money by itself. Payment depends on accurate reporting, applicable rights, registrations where relevant and the agreements governing collection. If income appears missing, investigate the reporting period, metadata and collection route rather than assuming that possession of the code automatically triggers every payment connected with the music.

The code is also different from a release-level product identifier and from an identifier for a musical work. Keeping those categories separate prevents errors in contracts, catalog spreadsheets and royalties discussions. If ownership is disputed, examine the actual agreements and evidence with appropriate professional advice. The fact that someone supplied or assigned an ISRC does not, by itself, resolve that dispute.