Track rights before money arrives
Royalty tracking starts with identifiers and contracts, not statements.
Create one source of truth for recordings, compositions, contributors, splits, ISRCs, UPCs, distributors, society registrations, contract terms, and statement imports.
Separate income streams
Do not merge distributor, PRO, mechanical, neighboring-rights, sync, and direct-license money into one vague line.
Separate streams let you notice missing registrations, recoupment errors, territory gaps, and tracks that earn in one system but not another.
Localization note
Royalty systems are market-specific.
This is an operational checklist for producers and artists, not legal advice. Use it to prepare questions, documents, and metadata before a qualified local professional or platform support team reviews the final decision. United States, EU/EEA, United Kingdom, Brazil, Russia, China, Japan/Korea, Turkey/Indonesia, Spanish-language, and Arabic-language markets require local society, payout, tax, and platform checks.
Tracking table structure
| Table | Purpose | Minimum fields |
|---|---|---|
| Works | Composition ownership | Title, writers, shares, PRO, IPI, publisher, ISWC if available |
| Recordings | Master tracking | ISRC, artist, version, master owner, distributor, release date |
| Contracts | Rights and payment terms | Party, asset, term, territory, fee, royalty, recoupment, claims |
| Statements | Income audit | Source, period, territory, track, amount, currency, deductions |
| Claims | Platform disputes | Notice, claimant, URL, deadline, evidence, outcome |
Setup steps
- Create identifiers first: Assign or import ISRCs, UPCs, work IDs, and contributor IDs before release.
- Link every statement row: Connect each payment line to a recording, work, contract, and territory.
- Normalize currencies and periods: Store original currency and exchange reference separately from reporting currency.
- Review quarterly: Check missing territories, unmatched tracks, negative adjustments, and late society registrations.
Learning path
Related answer hubs
Keep production downloads separate from rights accounting, and archive every royalty source file.
Browse Free DownloadsRoyalty tracking FAQ
- Is this legal advice?
- No. It is a conservative operational checklist for preparing documents and questions before legal, tax, society, distributor, or platform review.
- Can one English template work worldwide?
- Usually no. English source copy can describe the workflow, but United States, EU/EEA, United Kingdom, Brazil, Russia, China, Japan/Korea, Turkey/Indonesia, Spanish-language, and Arabic-language markets need localization.
- What should I save before releasing?
- Keep the contract, split sheet, licenses, metadata export, payment record, approval messages, and platform screenshots in a dated project folder.
- Can a spreadsheet be enough?
- Yes for a small catalog if it is consistent, backed up, and linked to source documents.
- What is the most common tracking mistake?
- Mixing master income and publishing income, then losing the ability to audit missing money.