Pandora, Spotify, Apple and Amazon can access unredacted Web VI documents for the Phono V proceeding under protective conditions. That order changes what the services can examine in a rate-setting process. It does not tell an independent publisher what its next royalty statement will pay.
What the document order changes
Chief Copyright Royalty Judge Trevor Jefferson granted the four digital service providers (DSPs) access to the Web VI documents for use in Phono V. The immediate effect is procedural: the services can work with records that were previously unavailable to them in unredacted form, subject to the conditions attached to access. A catalogue owner should read the order as a change in the material available to participants, not as a completed change in the price of a play.
That distinction matters because a rate proceeding and a royalty statement operate at different points in the chain. Participants first examine and argue over material in the proceeding. A DSP then applies the applicable payment terms when it accounts for music use. Access to a document belongs to the first step. It does not, by itself, revise the second. If a forecast changes every time evidence enters a proceeding, the forecast starts treating an argument as an outcome.
The protective conditions matter too. The order allows access to unredacted documents with safeguards, which makes the scope of access part of the ruling. It is possible to learn that a participant may inspect material without learning what that material says or how the judge will weigh it. For planning purposes, the useful date is the date a payment rule actually changes, followed by the period of use to which that rule applies.
A claim is a different kind of number
Spotify’s potential liability in The Mechanical Licensing Collective’s (MLC) audiobook bundling lawsuit has reached roughly $619 million. That figure describes exposure in a dispute. It is not a new per-stream rate, a distribution to publishers or a line of earned income for an individual catalogue.
The bundling issue points to a separate mechanism from Phono V. A rate proceeding addresses the terms used to calculate payments. A lawsuit over bundling challenges how a service’s offering is treated under payment rules. Even when both concern streaming royalties, they ask different questions: what rule applies, and whether a particular use was accounted for under it. A large aggregate claim answers neither question for a single work owner. Its size cannot be divided across a catalogue to estimate a recovery.
A second Spotify case shows why the status of a claim must stay attached to its dollar figure. A US federal judge permanently dismissed RBX’s $600 million lawsuit alleging that bot-driven Spotify streams reduced royalties for other rightsholders. The allegation described a possible route by which one set of streams could affect payments to others. The dismissal ended that lawsuit without turning its stated $600 million into royalties for those rightsholders.
The two figures therefore belong in different places from actual receipts. The roughly $619 million in potential MLC suit liability remains a disputed amount. The $600 million sought in RBX’s dismissed action cannot serve as a recovery forecast from that case. Neither tells an artist or label what its own next statement will contain.
Keep three entries in the catalogue model
An independent rightsholder can make this distinction operational by giving each development a different treatment in its working records:
- Current receipts: record the amounts actually shown on royalty statements. Reconcile those amounts to the catalogue and the uses being paid.
- Rate proceedings: track the applicable rule and its effective period. Log the Phono V access order as a procedural event until a payment rule changes.
- Litigation: track the claim, its subject and its status separately. Keep the MLC bundling amount out of expected receipts while it is potential liability, and mark the RBX action as dismissed.
This is a decision rule for budgets as well as bookkeeping. If a label is deciding how much catalogue income can fund an advance, an acquisition or a release, use receipts supported by statements and payment terms. Keep contested amounts in a separate scenario, tied to the specific outcome that would make them payable. That prevents a legal headline from silently raising the income available to spend.
Ask what event moves the money
For every policy or court development, ask what must happen before it reaches a rightsholder’s account. Access to Web VI documents in Phono V allows participants to use evidence in a proceeding; a later payment rule would be the event to watch for a rate change. The MLC’s bundling lawsuit against Spotify concerns a contested liability; its dollar figure does not allocate money to any particular catalogue. The RBX suit’s dismissal shows that an alleged royalty shortfall can also end without recovery through the action that asserted it.
The practical test is simple: identify the rule, the use and the payment record before changing a catalogue forecast. If a development changes only access to evidence or the size of a claim, record that development, but leave booked royalty income where the statements put it.
