Music Distribution Royalty Reports: How Revenue, Revenue Share, and Payouts Work

For a distributor, the revenue report is the moment of truth. Everything before it — uploading, approving, delivering — is operational. The report is where the money shows up, and where mistakes become expensive. Here is how the process works end to end.

Reporting months are not payment months

Stores report earnings after the fact. Revenue for streams in one month usually arrives in a report weeks or months later, labelled with the month it belongs to. Good distribution software keeps track of this reporting month for every row so that analytics show the month the revenue was earned, not the month the file was uploaded.

How a report becomes artist balances

• The distributor uploads the store's report file (CSV or XLSX).
• Each row is matched to a release using its ISRC — the code that identifies a recording.
• Revenue is calculated per artist account after applying that account's revenue share.
• The result is added to the artist's available balance and appears in their analytics.

Why exact ISRC matching matters

Matching depends entirely on the ISRC in the report matching the ISRC in your catalog. A typo, a stray hyphen, or a reused code means revenue lands in the wrong account or in none at all. This is why distribution software should generate and validate ISRC and UPC codes at upload time, and flag duplicates before a release ever goes live.

Revenue share

Revenue share is the percentage of store revenue that goes to the artist; the distributor keeps the rest. It is usually set per account, so a long-term partner can have a different rate from a new artist. The key requirement is that the rate is visible to the admin, applied consistently, and reflected in the balance the artist sees.

Payout requests

Artists request a payout from their available balance, usually with a minimum threshold, and the admin approves or rejects it. A clean payout flow shows the artist the request status, shows the admin the bank details and amount in one queue, and records a reason when a request is rejected.

When these pieces — report upload, ISRC matching, revenue share, payout queue — live in one system, a month-end close becomes a routine task instead of a spreadsheet project.