The 100% Publisher Share Glitch

Scenario: The ASCAP Administrative Leak

David, an independent songwriter, signs up for ASCAP. He writes a song, registers it under his personal name, and leaves the publisher field completely blank, assuming ASCAP will pay him all royalties.

The Issue The song gets synced in a national television ad campaign, generating $20,000 in public performance royalties. However, when David's ASCAP statement arrives, he only receives $10,000. The remaining $10,000 is held by ASCAP in an unmatched suspense pool.

The Technical Glitch This represents a standard "administrative leak" caused by ASCAP's strict operational rules: 1. Public performance royalties are split 50% to the writer share and 50% to the publisher share. 2. ASCAP will only distribute the writer's share (50%) to David's writer account. 3. Because David did not register an ASCAP publishing company or affiliate with a publishing administrator, the publisher's share (50%) has no registered recipient. 4. If this remains uncorrected for 3 years, the unmatched $10,000 publisher's share is released into the general pool and distributed to major publishers by market share.

The Correction To reclaim the held royalties, David must: 1. Pay $50 to register a single-member publishing entity with ASCAP (e.g., *"David Music Publishing"*). 2. Associate this publishing entity with his ASCAP writer account. 3. Update the song's registration in the ASCAP ACE database to reflect: David (Writer) - 50% / David Music Publishing (Publisher) - 50%. 4. Submit a claim for retroactive matching of the unmatched publisher's share.