Spotify plans to charge Premium subscribers an added monthly fee to create remixes and covers, with payments going to original rights holders. For an independent label, the commercial question is how a subscriber payment becomes a payment for a particular recording or song.
The fee and the royalty are different numbers
An added monthly fee sets a price for access to a tool. It does not, by itself, tell a rights holder what one use of their catalogue earns. A subscriber might pay once in a month and create several outputs, or create none. To turn that payment into a catalogue royalty, the service needs a rule for identifying uses and allocating money among the rights attached to them.
That distinction matters when assessing Spotify’s proposed payments to original rights holders. A label cannot value the proposal from the subscriber price alone. It needs to know which event triggers a payment: creating an output, saving it, sharing it, or listening to it. Those events can produce different usage counts. The contract and statement need to use the same event definition, or the label will have no reliable way to reconcile the payment.
The word “original” also needs an operational meaning. A cover points back to an existing song; a remix points back to existing material used in a new output. Before accepting a payment designation, a rights holder should establish which catalogue item the service identified and which party it recorded as entitled to collect. That is a practical rights check, not a prediction about the feature’s eventual terms.
Keep the product fee separate from rate setting
The National Music Publishers’ Association (NMPA) and Nashville Songwriters Association International (NSAI) renewed their request for documents from the Mechanical Licensing Collective’s (MLC) royalty lawsuit against Spotify in the Phono V rate proceeding. That development concerns the information used in a rate process. The planned remix and cover feature concerns a new paid product and promised payments to original rights holders. A label reviewing the product should keep those questions separate in its accounts.
The subscriber’s added fee is a receipt at the product level. A royalty rate determines what a defined use owes under a defined set of terms. An allocation rule determines which work or recording receives a share of a pool. A payment record shows what was actually sent. None of those entries can substitute for another. If a statement shows only total receipts from the feature, it cannot explain a catalogue payment. If it shows only a catalogue payment, it cannot show whether every eligible use was counted.
This separation gives independent rights holders a useful negotiating test. Ask the service to identify the usage event, the applicable payment rule and the field that links each payable event to a catalogue identifier. Then check whether the statement provides those fields. The point is to make the promised payment traceable from use to recipient, whatever price the service ultimately charges subscribers.
Identification errors can change the recipient
YouTube restored a performance of a Bulgarian folk song after Media Nov Records withdrew its copyright complaint. That case illustrates a basic control problem for any system that identifies protected material and acts on a claim: the initial claimant may later withdraw. For an AI remix or cover payment, the corresponding accounting question is what happens to money assigned through an incorrect match.
A catalogue team should be able to challenge an identification without losing the transaction history. If a match changes, the service needs a way to connect the corrected work or recording to the original usage event and adjust the recipient’s account. Otherwise, a later correction may fix a visible claim while leaving the payment record attached to the wrong party.
The same issue runs in the other direction. A rights holder who cannot see which source material a tool identified cannot tell whether an eligible use was missed. For that reason, a useful statement should carry the output’s usage reference, the source catalogue reference, the rights holder recorded for payment and any subsequent correction. These are requests for an audit trail, not assumptions about how Spotify’s planned tool will work.
Set a catalogue rule before the feature launches
An independent label can prepare a short, product-specific review for each recording it controls. The useful checks are concrete:
- Confirm the label’s recording identifier and the party authorised to receive its payment.
- Record the song information associated with the recording so a cover or remix can be checked against the right source.
- Ask which user action creates a payable use and how multiple uses under one monthly subscription are counted.
- Require statements that connect each payment to a usage event and catalogue item.
- Set a correction route for disputed matches and payments assigned to the wrong recipient.
The decision is whether the label can reconcile a payment for each eligible use of its catalogue. Spotify’s plan pairs an added subscriber fee with payments to original rights holders, but those two entries meet only through identification, allocation and reporting. Put those three mechanisms in the review before treating the fee as catalogue revenue.