ISWC Codes Explained: The Global ID for Your Songs

The ISWC — International Standard Musical Work Code — is the global ID for a composition. One song, one ISWC, regardless of who recorded it, who covered it, or how many times it's been re-released. Every PRO and every collection society in the world uses ISWCs to match royalty payments to compositions, and the MLC won't reliably pay you US streaming mechanicals without one. If you write songs and you don't know your ISWCs, your royalty pipeline has a gap.

Short answer: An ISWC is the permanent global ID for a composition, issued free by your PRO when you register a song. Look it up in your PRO portal and paste it into every other registration — MLC matching gets unreliable without it.

What an ISWC is

An ISWC is a 10-character identifier issued by national agencies under the umbrella of CISAC, the Confédération Internationale des Sociétés d'Auteurs et Compositeurs. CISAC maintains a global registry of compositions; every PRO and collection society in the network can look up any ISWC and see who wrote what.

The format is fixed:

T-123.456.789-0

• T — fixed prefix, indicates this is an ISWC (T = "tune")
• 123.456.789 — a nine-digit unique number assigned to the composition
• -0 — a single-digit check digit, used to validate the code

The dots and dashes are part of the format. Some systems accept a stripped version (T1234567890); others require the formatted version. Most PRO portals output the formatted version.

ISWCs are unique globally and permanent. Once a composition is assigned an ISWC, that's its ID forever. If two PROs each issue an ISWC for the same composition (which happens with co-writes across societies), CISAC merges them — one composition ends up with one canonical ISWC, with the duplicates retired.

How an ISWC differs from an ISRC

The other code that gets confused with the ISWC constantly is the ISRC, the International Standard Recording Code. They sound similar and they're part of the same family of music identifiers, but they identify completely different things.

Same Spotify play, two codes in motion. The ISRC tells the streaming service which recording is playing. The ISWC tells the publishing collection societies which composition the streaming service is paying mechanicals on. We have a longer breakdown at /blog/iswc-vs-isrc.

The codes are not interchangeable. Pasting an ISRC where an ISWC belongs is one of the most common reasons MLC matching fails for indie writers.

How to get an ISWC

ISWCs are issued by PROs, not by the MLC, not by your distributor, and not by any music ID registrar directly. The path to an ISWC always runs through a PRO.

In the US:

• ASCAP issues ISWCs for works in their repertoire, when you register a song with them
• BMI issues ISWCs for works in their repertoire, when you register a song with them
• SESAC issues ISWCs for works in their repertoire, when you register a song with them

Internationally, the same model: the PRO in your home territory (PRS in the UK, GEMA in Germany, SACEM in France, JASRAC in Japan, etc.) is the issuing agency for compositions registered with them.

Steps:

1. Join a PRO. If you're not already a member, apply with ASCAP, BMI, or SESAC (or your home PRO if you're outside the US). Membership is free at ASCAP and BMI; SESAC is invitation-only. See /guides/ascap and /guides/bmi.
2. Register the song. Submit a work registration with the PRO — title, writers, IPIs, splits. The PRO assigns an ISWC during the registration process.
3. Look up the ISWC. Crucially: the PRO does not always email you the ISWC. You have to log into their portal and look it up.
   • ASCAP: log into ASCAP ACE Repertory and search by title or IPI. The work detail page shows the ISWC.
   • BMI: BMI Repertoire Search (Songview), find your work, the ISWC is in the metadata.
   • SESAC: log into the member portal and check your work registrations.
4. Record it everywhere. Add the ISWC to your MLC registration, your sub-publisher submissions, your sync metadata sheets, your distributor's composition fields if available, and your own catalog spreadsheet. Once you have the number, it's good forever.

ISWCs are free. There's no per-ISWC fee from any PRO. The cost is the time spent registering each song properly.

Why the MLC needs your ISWC

The MLC matches every streaming service play report to a registered work in their database. The play report from Spotify (or Apple Music, or Amazon Music) contains:

• The ISRC of the recording that played
• The number of plays in the reporting period
• The revenue allocation

The MLC then has to figure out which composition corresponds to that recording, so they can pay the right writer and publisher. They do that by matching:

• ISRC → linked composition record (when the writer registered ISRCs against their work)
• Title + writer name + ISWC → composition record (when the writer registered with full metadata)
• Fuzzy matching on title alone (last resort, unreliable)

Having the ISWC on file is what makes the matching reliable. Without it, the MLC falls back to fuzzy-matching, which works sometimes and fails often. Failed matches send the royalty into the unmatched pool until somebody claims it.

This is why "register with the MLC" alone isn't enough. You have to register with the MLC with the ISWC populated, which means going to your PRO portal, copying the ISWC, and pasting it into the MLC submission. The MLC field accepts it; your PRO won't fill it in for you.

For more on the MLC registration mechanics: /guides/mlc.

ISWCs and international royalties

International publishing collection runs through PROs and CMOs (collective management organizations) in each country. Reciprocal agreements pass royalties between societies, but the matching is done on ISWC in almost every case. PRS in the UK, GEMA in Germany, SACEM in France, JASRAC in Japan — they all key off the ISWC when figuring out which writer to pay.

If your composition has an ISWC issued by ASCAP and your song streams in Germany, GEMA looks up the ISWC, finds the composition record, sees that the writer is registered through ASCAP, and routes the payment back to ASCAP through the reciprocal agreement. ASCAP pays you.

Without an ISWC, the foreign society's match fails. The royalty either goes to the unmatched pool in their territory or gets distributed to other writers proportionally. Either way, you don't see it.

This is the cleanest answer to "why do international royalties leak so much for indie writers": missing or incorrect ISWCs at the source. Sub-publishing relationships help fill the gap (an admin's sub-publisher pushes registrations into foreign societies directly, bypassing the reciprocal-agreement matching), but ISWCs are the foundation. Get them right at the PRO level and the whole international pipeline works better.

For more on sync licensing and how publishing income flows internationally: /guides/sync-licensing.

Common problems indie writers hit

Patterns we see when auditing a new artist's catalog:

"I have a PRO account but I don't know my ISWCs"

Most common. Writer joined ASCAP or BMI years ago, registered a few songs, never bothered to look up the ISWCs, now needs them for MLC registration and can't find them. The fix is to log into ACE Repertory or Songview and search by writer name — every registered work shows its ISWC in the work detail.

"I never registered the song with my PRO at all"

Means there's no ISWC yet. PROs don't auto-issue ISWCs based on streaming activity; the writer has to actively register the work. Fix: log into your PRO portal, file a new work registration with title + writers + splits, and an ISWC gets assigned.

"My PRO and the MLC have different ISWCs for the same song"

Usually means a co-writer is at a different PRO and their PRO issued a separate ISWC. CISAC merges duplicates over time, but the merge can lag. The MLC's usually fine accepting either one — what they need is the link to a real composition record. If both ISWCs are accepted by the MLC for the same song, that's evidence the merge hasn't finished yet.

"I see an ISWC on Songview but my MLC registration says blank"

Means the ISWC was issued but never copied into the MLC submission. The MLC doesn't auto-pull from PRO data — the writer has to populate the field. Fix: edit the MLC work registration and add it.

"My distributor pasted an ISRC where the ISWC should be"

Less common but happens. ISRC is twelve characters in the format US-ABC-26-12345; ISWC is ten characters in the format T-123.456.789-0. Mistaking one for the other on a registration form usually causes the form to reject (the format check fails) but sometimes systems accept and fail downstream. Audit by length and prefix.

Where Davincii fits in

For our roster, the ISWC pass is one of the first things we do during onboarding:

1. Pull every song from the artist's catalog (Spotify discography, distributor reports, manual additions)
2. Look up the corresponding ISWC at the artist's PRO — ASCAP ACE for ASCAP writers, Songview for BMI writers
3. Where an ISWC is missing because the song was never registered with the PRO, register it through our publisher account
4. Populate the ISWC into the MLC registration, the sub-publisher submissions, and the artist's catalog file

This step alone often surfaces money. Songs that streamed for years without an ISWC populated at the MLC get matched once the ISWC is added, and back-payments flow through the unmatched-pool claim process.

For pricing: /pricing. Application: /signup. The full picture of how publishing admin works under the hood is at /guides/publishing-administration-for-independent-songwriters, and the difference between ISWC and ISRC has its own writeup at /blog/iswc-vs-isrc.