Localization and rights note
Use this article as an operational checklist, not as legal advice.
- Confirm local collection society rules, payout access, tax paperwork, and dispute routes in the country where the right is exploited.
- Route high-value transfers, disputes, samples, manager authority, or exclusivity through qualified counsel.
Document assumptions, keep rights evidence, and verify the local rule before release, claim, or deal signature.
Localization note
Legal, tax, privacy, rights, royalty, and contract guidance changes by jurisdiction. Treat this article as an editorial starting point, not legal or accounting advice.
For English readers, separate United States, United Kingdom, Canada, Australia, and global-audience assumptions. Do not treat a US workflow as universal.
Quick Answer
Royalty metadata is payment infrastructure. Wrong ISRCs, misspelled writer names, missing IPI/CAE numbers, conflicting publisher shares, duplicate titles, and bad territory data can block matching even when the song is generating real usage.
Errors that stop matching
| Error | Likely consequence | Fix |
|---|---|---|
| Wrong or reused ISRC | Master income and neighboring-right claims may attach to the wrong recording. | Assign one ISRC per recording version and keep a release log. |
| Writer name mismatch | PRO or publisher systems may create duplicate identities. | Use legal name, stage name, IPI/CAE, and publisher exactly as registered. |
| Split totals not 100 percent | Registrations can reject or conflict. | Confirm writer and publisher shares before upload. |
| Missing ISWC or duplicate work | Composition income can sit unmatched. | Register once, track alternate titles, and resolve conflicts with the society/admin. |
| Territory data ignored | Income may not route correctly across local societies. | Map society, publisher, and administrator coverage by territory. |
Pre-release metadata audit
- Freeze credits
Confirm writers, producers, performers, publishers, labels, and administrators before distribution. - Match identifiers
Link ISRC, UPC, ISWC when assigned, IPI/CAE, publisher IDs, and society membership data. - Check localized names
For Brazil, Russia, China, Japan/Korea, Turkey, Indonesia, Spanish-region, and Arabic-region releases, verify local naming, scripts, society fields, and payment access. - Save correction history
Keep screenshots and support tickets for metadata edits, rejected registrations, and claim disputes.
Jurisdiction notes
United States: separate copyright registration, PRO affiliation, MLC-style mechanical collection, SoundExchange-style neighboring-right collection, DMCA takedown workflow, and state contract rules. Registration can matter for litigation posture, but this article is not legal advice.
EU/EEA and UK: copyright is generally automatic, but collection, moral rights, neighboring rights, private-copying rules, and cross-border licensing are handled through local law and societies. Do not copy a US-only registration or DMCA workflow into Europe without review.
Brazil: public performance collection commonly runs through ECAD-linked society workflows; keep Portuguese metadata, society affiliation, and local tax/payment paperwork aligned before expecting payouts.
Russia, China, Japan/Korea, Turkey, and Indonesia: platform access, local societies, banking rails, censorship/content rules, and enforcement routes can differ sharply. Verify availability and local administration before promising a takedown, payout, or license clearance timeline.
Spanish and Arabic audiences: localize by country or region. Spain is not Latin America, and Arabic markets differ across GCC, Egypt, North Africa, and the Levant for societies, payments, venue licensing, and platform access.
Statement audit
- Distributor vs publisher: master income and composition income may report different periods and territories.
- Neighboring rights: performer and master-owner metadata may be separate from distributor credits.
- Sync: cue sheets must match registered work titles and writer data.
Turn rights assumptions into a written checklist before the next release or deal.
Browse Free DownloadsFrequently Asked Questions
- Is this legal advice?
- No. It is a conservative operating checklist for producers and independent teams. Use local legal counsel for contract language, disputes, tax questions, sample clearance, or rights transfers.
- What should I save for every release?
- Save dated project files, bounced masters, split notes, approvals, license receipts, ISRC/UPC data, registrations, distributor reports, and claim correspondence.
- Can metadata be fixed after release?
- Often yes, but corrections can take weeks or months to propagate and may not recover every missed match automatically. Fixing metadata before release is cheaper.