Skip to main content

Royalties Withheld from Your Statement

Support avatar
Written by Support
Updated yesterday

If Kingsmen Studio (via our distribution platform) identifies any post-distribution rights infringement or DSP Terms of Use violations, we will:

  1. Notify you and identify the specific asset(s) flagged.

  2. Indicate the exact type of violation involved.

  3. Withhold all royalties related to the issue until you provide sufficient evidence that no violation occurred.

Below are the violation types currently tracked, what’s expected of you, and how withholding is applied:


1. Artist Imposture

Misleading or deceptive presentation of the artist—such as altered names—or impersonation tactics.

  • Action Required: Provide proof of identity/ownership (e.g., ID, social verification, original content). If unable to do so within 3 business days, the release must be taken down. Failing to remove infringing material within 5 days may result in a $10 fine per release.

  • Withholding Impact: Royalties are withheld until you conclusively demonstrate legitimate ownership.


2. Questionable Ownership

Metadata may appear clear, but ownership rights are in doubt.

  • Action Required: Submit documentation verifying rights.

  • Withholding Impact: Royalties are pending confirmation of ownership.


3. Sound Recording Matches Metadata (Recording Fraud)

Mismatch between audio and metadata (e.g., title or artist is incorrect).

  • Action Required: Confirm accuracy of both audio and metadata.

  • Withholding Impact: Royalties remain on hold until accuracy is verified.


4. Missing Licenses for Remixes, Samples, or Derivatives

Using protected content (e.g., remixes, mashups, speed edits) without proper licenses.

  • Action Required: Provide valid licensing documentation within 3 business days.

  • Withholding Impact: Royalties withheld until licensing is confirmed.


5. Artificial Streaming (Fraudulent Activity)

Irregular streaming patterns or bot-driven plays.

  • Action Required: Either pause/review the release or provide logs showing legitimate streaming activity.

  • Withholding Impact: Only royalties from affected DSPs are withheld—unless clear malicious behavior is confirmed.


6. UGC Platform Incompatibility (e.g., TikTok, YouTube)

Content not compliant with User-Generated Content platform policies.

  • Action Required: Prove eligibility or remove the release from those platforms.

  • Withholding Impact: Royalties withheld from affected UGC DSPs only.


7. YouTube Content ID Policy Violation (Parasitic Content)

Using popular third-party content just to gain performance metrics—a behavior YouTube flags.

  • Action Required: Remove the content from Content ID until compliance and originality are assured.

  • Withholding Impact: Royalties derived through Content ID are withheld.


8. Fraudulent or Non-Compliant Accounts

Accounts consistently violating rights or platform policies.

  • Action Required: Provide valid account ownership documentation or consider termination.

  • Withholding Impact: All royalties from that account are withheld until cleared.


Summary Table

Violation Type

Required Action

Withholding Applies To

Artist Imposture

ID verification or removal of content

Full royalties for that content

Questionable Ownership

Prove ownership

Full royalties

Recording Fraud

Verify audio matches metadata

Full royalties

Missing Remix/Sample Licensing

Provide license documentation

Full royalties

Artificial Streaming

Validate legitimate streaming

Only affected DSP royalties

UGC Platform Incompatibility

Confirm compliance or remove release

Only UGC DSP royalties

YouTube Content ID Violation

Remove from Content ID

Only Content ID royalties

Fraudulent Account Behavior

Verify identity or cease account

All account royalties


What to Do If You Disagree

If you believe a violation was flagged in error:

  1. Submit an appeal—include documentation or justification.

  2. During the review, the original release remains withheld.

  3. On successful appeal, royalties are released promptly.

Did this answer your question?