CMO
Collective Management Organization — an entity authorized to grant licenses and collect royalties on behalf of multiple rights holders. CMOs operate under national law and typically cover specific right types (performance, mechanical, or both). Examples include GEMA, SACEM, PRS, and SOCAN.
Articles about CMO
Collective Management Organizations (CMOs) Explained: Roles, Payments, and Global Differences
Understanding how a collective management organization operates is essential for anyone designing royalty workflows or reconciling cross-border revenue. This briefing maps the operational roles of societies and the end-to-end payment flows from licensee to rights holder, highlights metadata and matching failure modes that cause leakage, and compares how key territories - the United States, the United Kingdom, and continental Europe - differ in mandate and scope.
Maximizing Pay Sources: 5 Essential Differences Between PROs and CMOs
Music publishing can be complex and confusing, especially when understanding the different pay sources available to songwriters and music publishers. Two of the most essential pay sources in the music industry are PROs (Performing Rights Organizations) and CMOs (Collective Management Organizations).
Top 5 Essential Benefits of Joining a PRO/CMO: Unlock Your Music Royalties Now!
Joining a PRO/CMO can be a game-changer for music artists, songwriters, publishers, and collection societies. These entities play a crucial role in tracking and collecting performance and mechanical royalties, ensuring that creators receive their due compensation for using their musical works.
Demystifying the Process: A Step-by-Step Guide to Affiliating with a PRO/CMO
Introduction Affiliating with a Performing Rights Organization (PRO) or Collective Management Organization (CMO) can seem daunting. However, navigating with the correct information and guidance becomes much more accessible.
publishing royalties vs mechanical royalties
Publishing Royalties vs Mechanical Royalties If you released a piece of music on Spotify or Apple Music, there is a strong chance you are owed multiple types of music royalties from different collecting societies. The music industry splits how royalties are paid by how the music is used.
Music Rights Clearance: The Complete Process for Licensing Permissions
Music rights clearance is the operational work that turns a creative cue into lawful use—and it routinely breaks projects without a repeatable process. This guide gives a step-by-step, reference-style workflow to identify required rights, map ownership, execute licenses, and document compliance for common scenarios including sync, samples, covers, reissues and digital uses.
Neighboring Rights Explained: Who Gets Paid and How Collections Work Internationally
Neighboring rights are a persistent blind spot for many music businesses; they sit alongside copyright, attach to performers and phonogram producers, and generate cross-border payments that frequently go unclaimed. Neighboring rights explained: this article lays out who is entitled under different laws and CMOs, how reporting and reciprocal agreements move money internationally, and where metadata failures create black box pools.
Music Metadata Standards: Essential Information for Rights Management and Royalty Payments
Missing or incorrect metadata is the single biggest operational cause of unpaid royalties, and music metadata standards are the practical rules that prevent those losses by defining identifiers, fields, and delivery flows. This article unpacks the identifiers and formats you actually need to manage rights and payments — ISRC, ISWC, GRid, IPI, UPC, DDEX ERN and RIN, in-file tags and society feeds — and shows how to validate, map, and remediate metadata in real ingestion and reconciliation pipelines.
Sync Licensing Royalties: A Complete Guide to Synchronization Rights and Payments
Sync placements generate multiple, overlapping revenue streams and frequent confusion about who gets paid, when, and through which society or channel. Treat this as sync licensing royalties explained for implementers: it breaks down one-off sync fees versus master licenses, public performance and mechanical flows, cue-sheet requirements, and the metadata and identifiers your systems must track.