ISNI and Party Identifiers: Public Names and Catalog Checks

Distinguish public identities from spelling variants, compare ISNI with IPI, and check contributor records without assuming an identifier proves royalty payment.

A contributor can use a legal name, a stage name and several spelling variants without becoming several different people. The catalog question is not simply whether two names look alike. It is whether they represent the same public identity, different public identities of one person, or unrelated parties.

ISNI can help document that distinction. It is not a substitute for a royalty agreement, a society registration or evidence of payment. This guide focuses on contributor identity at setup and during corrections—not on calculating royalty shares.

What ISNI actually identifies

The International Standard Name Identifier identifies public identities across creative fields. ISO 27729:2024 covers parties involved in creating, producing, managing and distributing content. Its public abstract describes disambiguation and links to other systems, not a comprehensive record of a person's rights or finances. See ISO's ISNI scope.

Public identities can belong to people, organizations or groups. Bowker's ISNI FAQ distinguishes separate public identities from spelling, capitalization, transliteration and other variants of the same identity. Those variants do not, by themselves, require separate ISNIs. See Bowker's identifier FAQ.

Think of three separate questions:

• Which public identity does this credit refer to?
• What evidence connects that identity to a person or organization?
• Which agreement or instruction governs the relevant accounting?

Do not let an answer to the first question silently become an answer to the other two.

Worked example: Marcus Reid and Reedwave

Consider a fictional producer, Marcus Reid. Assume he publishes production and songwriting credits as Marcus Reid, and releases performances as Reedwave. These are two deliberately separate public identities of one fictional person, not merely two spellings.

Under those assumptions, separate ISNIs can be appropriate. MVB's registration guidance recommends a separate pseudonym record and says a real-name record can additionally be registered when the person also publishes under that name. It does not make a private legal name an automatic second public identity. See MVB's name and registration guidance.

Now compare “Reedwave” with an accidental “Reed wave” entry. Investigate whether that is a spelling variant before treating it as another identity or applying for another identifier.

For an internal review, keep the confirmed relationship and its supporting evidence alongside the relevant credits. Do not assume that linking names also merges contracts, establishes a tax identity or makes two balances payable to the same account. Those questions need their own records and, where necessary, qualified advice.

The example contains one fictional person and two assumed public identities. It uses no real ISNI, measured loss or promised recovery.

How ISNI differs from IPI

IPI is not limited to music. CISAC describes an interested-party system covering natural people and legal entities across categories of artistic works, administered by SUISA under CISAC and BIEM rules. It supports member societies' information, distribution and accounting processes. See CISAC's IPI overview.

ISNI and IPI therefore identify parties for different information systems; one should not be entered into a field requesting the other. Store the scheme as well as the value. A bare column called “artist number” does not tell a reviewer which system issued it.

Collect each identifier where it is relevant to the contributor's role and the recipient's requirements. Do not require both from every contributor merely to complete an internal checklist.

What Apple Music documents about ISNI delivery

Apple announced support for artist ISNIs in delivery XML on 25 October 2022. That is a dated adoption announcement, not evidence that every platform now requires the field. See Apple's announcement.

The current Apple Music specification says to use the ISNI for the specific contributing identity and supply the artist name when using the ISNI tag. Its track-artist section says a mismatch between the supplied ISNI and Apple identifier or artist name causes delivery to fail.

The specification describes 16 characters, with a final check character that can be a digit or X. Passing a format check is not the same as confirming that the record belongs to the intended contributor.

Apple's credits guidance also allows an existing Apple Artist ID or ISNI when delivering contributor credits. Check the current delivery route and provider requirements. Catalog delivery, credit display and royalty-sales accounting are separate workflows; this is not a test of money reaching an artist.

Four checks when adding a contributor

These are recommended controls, not a claim that every missing identifier causes a payment failure.

1. Capture the credited identity. Record the public name and role relevant to this release or work. Keep spelling variants distinguishable from deliberately separate identities.
2. Record the scheme and evidence. Save the confirmed identifier, its source and the date checked. Mark unresolved identity questions for review instead of filling a required field with a guessed number.
3. Check the destination's requirements. Confirm which fields it accepts and requires. Do not substitute an internal payee code for an ISNI or IPI.
4. Search before creating another record. Compare existing entries and their associated credits. MVB explicitly advises checking for an existing ISNI before registering; a matching name alone is not enough to choose a record.

Four problems worth investigating

• No confirmed identifier. Find out whether one already exists and whether the destination requires it. Missing ISNI does not prove that every system can match only by name.
• Unclear name relationships. Do not merge unrelated people or collapse distinct public identities just because a spreadsheet makes that convenient.
• An identifier added only to a new record. List the older records and destinations that may need review. Adding a value locally is not evidence that historical credits or external databases changed.
• One identifier used as another. Correct the scheme and value together, then inspect the receiving system's response. A successful submission is not proof of correct payment.

Maintain and correct records without assuming automatic repair

Make identity review part of your chosen catalog-maintenance routine, especially when adding new contributors or investigating a reported error. Preserve the old reference, proposed correction, supporting evidence and confirmation so another reviewer can understand what changed.

MVB distinguishes assigned ISNIs from provisional records that have only a PPN because the information was insufficient for ISNI assignment. Finding a record is therefore not necessarily the same as finding an assigned ISNI. Treat a suspected registry error as a correction request, not permission to invent a replacement identifier.

Public linking also needs care: Bowker describes linking separate ISNIs as dependent on the party's authorization. Do not publish a private pseudonym relationship merely because an internal accounting team knows it.

Use five maintenance checks: collect relevant identifiers, confirm name relationships, distinguish schemes, review existing records and search before creating another entry. These are practical recommendations, not quantified savings or a guarantee against future mismatches.

What to verify in Qlero

Qlero's payee glossary documents an optional external payee code and an optional alternate name. Its payee, account and contract guide distinguishes the payee from balances and deal terms.

Those documented fields do not establish dedicated ISNI validation, registry linking or automatic updates to every external registration. That limit in the documentation is not proof that a feature is absent. Ask Qlero to demonstrate the specific identity and accounting workflow you need.

A useful evaluation question is: “Can we trace this public credit to the intended payee and agreement without treating the identifier itself as evidence of entitlement?” Keep any uncertain relationship unresolved until supporting information is available.

Frequently asked questions

Does every music contributor need an ISNI?

Check the receiving platform's current requirements and the contributor's role. Apple's guidance describes using an existing identifier; it does not establish a universal ISNI requirement across the music industry.

Can one person have more than one ISNI?

Yes, where separate public identities are involved. The Marcus Reid/Reedwave scenario assumes that distinction. A spelling variation alone is not the same situation.

Does ISNI replace IPI?

No. Keep identifiers from different systems labelled and use the scheme the recipient requests. Neither number substitutes for the relevant agreement or payment evidence.

Who assigns an ISNI?

The ISNI International Agency administers the system, with registration agencies providing the user-facing route. Check the chosen agency's current application requirements and charges; do not manufacture a number locally.

Should two ISNIs be merged into one catalog record?

First establish what each identifies. Preserve legitimate separate identities; ask the responsible agency to investigate suspected duplicate assignments. Distinguish your internal relationship mapping from an authorized correction to the registry.

Keep identity evidence separate from payment evidence

The goal is a reviewable connection between public names, identifiers and your own records. Correct setup helps make that connection explicit, and existing records can still be investigated and corrected later. Neither early collection nor later cleanup proves that every downstream system has accepted the change.

Book a Qlero walkthrough to discuss how your team keeps contributor references, payees and royalty agreements distinguishable.