ISRC/ISWC/creator-credit mismatch hotspots blocking African royalty matching
The problem: money can’t match what it can’t recognise
Across Africa-led catalogues, the same pattern keeps showing up in unpaid/underpaid statements: the recording, the work, and the people behind it don’t line up cleanly in the data. When ISRCs, ISWCs and creator identifiers (like IPI) don’t connect, royalties can sit in “unmatched”, “unknown” or “in suspense” buckets longer than they need to.
This audit maps the mismatch hotspots we see most often—and gives rights teams a quality-control (QC) checklist you can run before release to reduce downstream fixes.
Quick refresher: what needs to line up
- ISRC (International Standard Recording Code): identifies the recording.
- ISWC (International Standard Musical Work Code): identifies the composition/work.
- IPI (Interested Party Information): identifies the rightsholder/creator inside the CISAC ecosystem.
If your pipeline can reliably answer: “Which recordings (ISRCs) embody which works (ISWCs), and who owns/wrote what (IPI + splits)?” you’re already ahead.
The top mismatch hotspots (and why they block matching)
Split sheets don’t match the registration submission
- Symptoms: writers listed differently across delivery metadata, admin files, and PRO/CMO registrations.
- Why it breaks: societies/admin systems can’t reconcile shares when names/roles/shares conflict.
Writer identities aren’t standardised (no IPI / wrong IPI / duplicate names)
- Symptoms: “T. Mokoena” vs “Thando Mokoena” vs “Thando Mokoena (SA)” with no unique party ID.
- Why it breaks: matching is identity-first; names aren’t unique. IPI helps disambiguate.
Work titles drift across systems
- Symptoms: alternate spellings, translations, punctuation changes, featured artists appended to titles.
- Why it breaks: many matching rules still rely on fuzzy title + contributor logic; drift increases false negatives.
ISRCs are missing, recycled, or linked to the wrong version
- Symptoms: one ISRC used for multiple edits; remixes/radio edits shipped without clear versioning.
- Why it breaks: usage reports may pay a different recording than the one you think you delivered.
Work-to-recording linkage is missing (ISWC not connected to the ISRC set)
- Symptoms: recordings delivered to DSPs, but the composition registration doesn’t reference the relevant ISRCs (where your systems allow it).
- Why it breaks: recording usage must map back to the underlying work and rightsholders for accurate allocations.
Creator roles are wrong or incomplete
- Symptoms: producers credited as writers (or vice versa) without contractual basis; missing contributors in downstream datasets.
- Why it breaks: role errors become claim errors—especially when publishing, performers’ rights, and sound recording rights are handled in separate lanes.
Territory and society pathways aren’t clear (local CMO vs reciprocal partner)
- Symptoms: works registered in the wrong place first, or duplicated across societies without alignment.
- Why it breaks: conflicting claims slow distributions and trigger manual review.
Why this hits harder locally
African catalogues often travel fast—radio, clubs, TikTok, diaspora playlists, brand work—while admin infrastructure and identifiers get stitched together after the fact. Add cross-border collaborations, multiple languages/spellings, and inconsistent data capture at creation stage, and mismatches become more likely.
The practical win: tighten metadata at source (creation + pre-release) so local registrations can flow cleanly into global systems.
What this audit is (and isn’t)
- Is: a rights-admin QC pass to reduce “unmatched” royalties and slow claims.
- Isn’t: a guarantee of payment speed or outcomes (matching also depends on reporting cycles, society rules, and third-party data quality).
Pre-release metadata QC checklist (run this before you hit “deliver”)
Use this as a release gate. If you fail any “must-have”, stop and fix.
A) Must-have identifiers (release blockers)
- Each track has a unique ISRC (no re-use across edits/versions).
- Each work has a confirmed writer list + split percentages that total 100%.
- Each writer has an IPI (or a documented plan to obtain/confirm it via the relevant society).
- Work registrations include strong identifiers and controlled contributor details (and link to relevant ISRCs where supported).
B) Names, roles, and consistency (high-impact matchers)
- Writer names are consistent across: split sheet → registration → delivery metadata.
- Roles are correct (composer/author/adapter/arranger) and supported by the agreement.
- Publisher/admin fields are consistent (or intentionally blank where unknown).
- Alternate titles/translations are captured as aliases, not as the primary title.
C) Versions and assets (avoids “wrong recording paid” problems)
- Versioning is explicit (radio edit, clean, instrumental, remix) and mapped to the correct ISRC.
- Featured artist and contributor credits are complete and consistent.
D) Society/CMO readiness (reduces conflict + duplicate claims)
- You’ve confirmed the primary local pathway for registration (which society/CMO handles which right in your territory).
- Cross-border co-writes have a clear admin plan (who registers where first; how claims are mirrored).
Quick country examples (starter map, not legal advice)
- South Africa: creators and publishers typically engage with SAMRO for performing rights registration/notifications (membership + “notification of works” style processes), and may also need mechanical licensing pathways depending on deal structures. Keep your work notifications consistent and complete.
- Kenya: MCSK publishes membership requirements (proof of original compositions, ID, referrals, fee). Treat this as a pre-release admin step for writers who aren’t yet registered.
- Nigeria: COSON outlines a membership application process requiring forms and documentation proving ownership of the music being notified; the Nigerian Copyright Commission also operates an online eRegistration system for registering works.
E) Audit trail (so fixes are fast later)
- You can produce: split sheet, contributor contact list, date-stamped metadata export, and proof of submission.
How to run the audit in a rights-admin team (simple workflow)
- Ingest: pull a catalogue snapshot (track list + contributors + ISRCs).
- Normalise: build one “source of truth” sheet for names, roles, splits, identifiers.
- Validate: check IPI/ISWC/ISRC presence and consistency.
- Register + link: submit through the appropriate society/partner format, keeping IDs aligned.
- Monitor: track registration status and resolve conflicts early.
Where DMPA fits (without changing who you are)
DMPA supports rights holders with publishing administration and metadata discipline so works can be identified, claimed, and processed more reliably across the global ecosystem—without acting as a label or distributor.
Sources
- Research note (internal) — Downtown Music Publishing Africa (DMPA).
- CISAC — IPI (Interested Party Information) overview (accessed Feb 2026)
- CISAC — International identifiers (incl. ISWC) (accessed Feb 2026)
- ISWC International Agency — What is an ISWC? (accessed Feb 2026)
- CISAC — Electronic data exchange formats (incl. CWR) (accessed Feb 2026)
- DDEX — Standards overview (accessed Feb 2026)
- SAMRO — Music Creator application info (accessed Feb 2026, South Africa)
- SAMRO — Forms (incl. Notification of Works) (accessed Feb 2026, South Africa)
- MCSK — Membership requirements (accessed Feb 2026, Kenya)
- COSON — How to apply (membership) (accessed Feb 2026, Nigeria)
- Nigerian Copyright Commission — eRegistration system (NCeRS) (accessed Feb 2026, Nigeria)
- CAPASSO — Membership Rules (2024, updated PDF) (accessed Feb 2026, South Africa)
