{"id":24395,"date":"2026-10-28T22:36:12","date_gmt":"2026-10-28T22:36:12","guid":{"rendered":"https:\/\/interspacemusic.com\/blog\/why-streaming-growth-and-royalty-claims-need-separate-catalogue-models\/"},"modified":"2026-10-28T22:36:12","modified_gmt":"2026-10-28T22:36:12","slug":"why-streaming-growth-and-royalty-claims-need-separate-catalogue-models","status":"publish","type":"post","link":"https:\/\/interspacemusic.com\/blog\/why-streaming-growth-and-royalty-claims-need-separate-catalogue-models\/","title":{"rendered":"Why Streaming Growth and Royalty Claims Need Separate Catalogue Models"},"content":{"rendered":"

Deezer raised its 2026 revenue and profitability forecasts after Direct revenue growth lifted its third-quarter results<\/a>. That is a useful market signal, but it is not a new royalty forecast for an independent catalogue. A label deciding how much to spend against future streaming income needs to keep platform growth, disputed payments and cash received in separate lines.<\/p>\n

What a platform forecast measures<\/h2>\n

Deezer\u2019s revised outlook contains two distinct measures: revenue and profitability<\/a>. Revenue describes money entering the business. Profitability concerns what remains after the costs accounted for in that measure. Neither figure states what a particular catalogue earned. Even the reported driver, growth in Deezer\u2019s Direct revenue<\/a>, identifies a part of the company\u2019s business rather than a payment rate for a recording.<\/p>\n

That distinction matters when a label builds a release or acquisition budget. A higher company forecast can support a decision to examine a market more closely. It cannot, by itself, support a higher expected payment per stream, a larger advance against one catalogue or an increase in promotional spending. The label needs its own statements to make those changes: the money credited to its catalogue, the period in which it was earned and the amount that reached its account.<\/p>\n

Start with the catalogue\u2019s actual receipts as the baseline. If a platform announces growth, record that announcement as a reason to review later statements. Change the forecast only when those statements show a change the label can measure. This keeps a company-level result from becoming an unsupported catalogue-level assumption.<\/p>\n

A claim is not a payment<\/h2>\n

The other side of the model is money under dispute. Spotify\u2019s potential liability in The Mechanical Licensing Collective\u2019s audiobook bundling lawsuit rose to roughly $619 million<\/a>. The number describes potential liability in a lawsuit. It does not describe an amount paid to rightsholders, and it cannot be divided into a dependable forecast for an individual catalogue.<\/p>\n

For a catalogue owner, the practical question is whether a disputed amount has appeared in its accounts. Keep a claim in a separate scenario until a statement records a payment attributable to the catalogue. That rule prevents a large aggregate figure from entering a working budget as though it were an approved receivable. It also makes the eventual result easier to assess: compare the payment shown on the statement with the amount previously assumed, rather than trying to reconcile it with the headline claim.<\/p>\n

The distinction runs in both directions. A US federal judge permanently dismissed RBX\u2019s $600 million lawsuit alleging that bot-driven Spotify streams reduced royalties for other rightsholders<\/a>. The $600 million claim is not a measure of what any one label lost. Following the dismissal, it is not a source of expected recovery for that claim either. A label should still judge its own income from its statements, rather than treating the size or outcome of another party\u2019s lawsuit as a substitute for catalogue data.<\/p>\n

Put each number in the right line<\/h2>\n

A workable forecast separates three questions that can otherwise collapse into one optimistic revenue estimate:<\/p>\n