ISWC vs. ISRC: Works, Recordings and Royalty Matching

Understand what ISWC and ISRC identify, how works connect to recordings, and why a correct identifier is not proof of ownership, royalty entitlement or payment.

An ISWC identifies a musical work. An ISRC identifies a recording. They answer different questions about what can sound like the same song, and neither code, by itself, says who must be paid or how much.

For a royalty team, the useful distinction is not which identifier is more important. It is which asset a report refers to, how that asset connects to the other side of the catalog, and which rights information supports the calculation.

ISWC: the identifier for the composition

The International Standard Musical Work Code identifies a composition independently of a particular recording. Its structure is the letter T, nine identifying digits and a check digit: 11 characters before optional display separators. The ISWC agency's explanation also makes clear that the code does not contain ownership shares.

ISWCs support work identification in registrations, licensing records, usage reports and royalty administration. They are not a substitute for the writer, publisher, territory and agreement information held alongside them. A change of publisher or royalty arrangement does not, by itself, create a different work identifier. CISAC's agency guidance explicitly separates identification from copyright and distribution agreements.

A new performance of an unchanged composition is different from a new version of the work. CISAC's work-eligibility guidance calls for separate ISWCs for arrangements, lyric adaptations and translations, with the relationship to the original recorded in the metadata. Do not assume every cover changes the composition, or that every adaptation leaves it unchanged.

ISRC: the identifier for the recording

The International Standard Recording Code identifies a sound recording or music video recording, rather than the underlying composition. It contains 12 alphanumeric characters. IFPI's current structure guidance describes a five-character prefix, a two-digit year of reference and a five-digit designation. The year records assignment of the code, not necessarily the year the music was recorded.

A separately recorded cover or live performance needs its own recording identity. Remastering is more nuanced: IFPI says an existing ISRC is generally appropriate where the remaster remains fundamentally the same recording; significant new creative input can justify a new code. “Remaster” in the title is not, on its own, an assignment rule. See the IFPI FAQ.

Ownership changes are different again. IFPI's ownership guidance says to retain the recording's ISRC when rights change hands. Store the updated ownership information separately; do not read the current owner or royalty entitlement out of the code.

One composition, many recordings—and important exceptions

Consider a fictional, unchanged composition recorded three times: an original studio performance, a new live performance and a new cover by another artist. The recordings are distinct, but they can all refer to the same work. This is an illustration of identity, not a claim about a real song's registrations or earnings.

The reverse relationship cannot be ruled out. DDEX defines a work-resource link as a connection from a recording or video resource to one or more musical works. A data model should therefore not reject every multiple-work association as an error.

That does not mean every receiving organization accepts the same registration structure. For example, The MLC's medley guidance treats the medley as a separate composite work requiring its own registration. It also warns that a medley recording cannot simply be matched to your individual composition when it contains other compositions you do not control. Check the recipient's rules instead of forcing every case into a single catalog relationship.

These distinctions identify the records to check. They do not establish permission to use a composition or recording.

A streaming example: separate records, not automatic payments

Suppose the fictional cover is streamed on Spotify. The recording side concerns that cover recording; the publishing side concerns the composition it uses. The cover artist's recording identity does not replace the original work's identity.

Spotify describes separate recording and publishing royalties, paid through the relevant licensors, publishers and collection organizations. What ultimately reaches an artist or writer depends on the applicable agreements. The example does not imply two immediate bank payments for every play, a fixed per-stream rate, or a direct payment to every producer.

A matching problem on the work side may need a different investigation from an incorrect recording reference. Neither a correct ISRC nor a correct ISWC proves that the associated shares, contract calculation or payment are correct. When reviewing an amount, keep the identifier check separate from the balance and settlement checks described in our royalty statement guide.

What if the ISWC or recording-to-work link is missing?

Missing metadata deserves attention, but “no ISWC means there is no possible route to payment” is too absolute. The MLC's individual registration instructions require only the work title at the Work Details step, then collect writers, publishers and shares in later steps. They also allow recording information to be added to assist matching. An ISWC is not the only information in that process.

Its Matching Tool guidance describes searches using recording titles or ISRCs, with writer and artist criteria, followed by a proposed match to a work. This is a specific U.S. blanket-license workflow, not a promise that every society can resolve every missing code or that a proposed match guarantees payment.

The practical response is to check the work registration, supplied recording data and recipient's matching status. Do not invent an ISWC or create a duplicate registration just to fill an empty field.

A practical identifier review for label teams

Use the following as an operating checklist, not as a universal registration policy:

• Keep work and recording records distinct. Store confirmed relationships between them, including the source of each relationship.
• Check whether an existing code already identifies the asset before requesting another one.
• Verify the actual version. Similar titles are not enough to establish that two recordings are the same.
• Keep rights shares, territories and effective dates separate from identifier fields.
• Give unknown or disputed relationships a review status instead of treating them as confirmed.
• Follow the registration and correction process of each organization receiving the data.

This article addresses work-versus-recording identity. It does not prescribe a complete publishing administration system or determine a disputed ownership claim.

What Qlero documents—and what to confirm

Qlero's external IDs and aliases guide describes recording-side sales matching. Aliases provide additional identifiers that can match incoming sales to a track or release; an External ID is for reference and export, not sales matching. Editing these fields requires Repertoire write access.

The invalid-lines guide explains how an unmatched incoming recording identifier can be linked to existing repertoire. That action saves an alias immediately and can affect later imports. Confirm the recording before linking it, then revalidate and review any remaining invalid reasons. The documented permissions for Sales Files and Repertoire & Agreements also apply.

Those workflows do not establish automatic verification of an ISRC-to-ISWC relationship across publishing databases. If that is part of your requirements, ask Qlero to demonstrate the exact work-recording relationship, source data and supported workflow before relying on it. This is a documentation-based description, not a hands-on test or a claim that Qlero assigns ISWCs.

Frequently asked questions

Does a song need both an ISWC and an ISRC?

A composition and its recording are separate assets. Where both exist, the identifiers serve complementary purposes. The code for one does not identify the other; check the relevant registration and reporting requirements.

Does a cover version get a new ISWC?

A new recording of an unchanged work can use the existing work identity while receiving its own ISRC. An arrangement, translation or adaptation needs a separate work-level assessment under the ISWC rules.

Which identifier matters more for streaming royalties?

Start with the record you are investigating: the recording, the work, or the link between them. Neither code establishes the contractual share or proves a payment was made.

Who assigns the codes?

ISWC allocation is managed through its registration system and agencies. For ISRC, the recording rights owner can assign codes under the scheme, or use a properly appointed ISRC Manager. Confirm the assignment route with the relevant agency or provider.

Is a missing ISWC proof that royalties cannot be matched?

No. Other metadata and recipient-specific matching processes may help. Supply accurate identifiers where available and investigate the actual registration or matching status rather than assuming success or failure.

Can one recording refer to more than one work?

Yes. DDEX's model allows that relationship. Composite works such as medleys also have recipient-specific registration rules, so several related work references are not automatically evidence of a mistake.

Keep identity, rights and payment separate

The useful catalog is not just a list of codes. It records what each code identifies, why two records are linked, and which rights and agreements govern the accounting. That separation makes an identifier discrepancy easier to investigate without mistaking a successful match for a correct royalty payment.

Book a Qlero demo to discuss your recording identifiers, sales files and any work-linking requirements. Confirm the supported workflow against your own requirements before choosing a setup.