What is DSR? Digital Sales Reporting, the Royalty Standard Explained

DSR means Digital Sales Reporting. It is the DDEX message format that every DSP uses to send streaming, download, and ad-revenue data back to a distributor each month.

If ERN is the letter that delivers a release to a DSP, DSR is the letter that comes back saying “here is what your release earned.” It is the underlying truth behind every statement you see in your distributor dashboard.

What is DSR?

DSR is a DDEX-standardised reporting format. The current generation is DSR 4.x, and most major DSPs ship a flat-file variant: a large CSV or TSV (sometimes XML) sent monthly to each distributor or label content provider.

A DSR file contains, line by line, every monetisable event in the reporting period:

  • The ISRC of the track that played.
  • The country where the play happened.
  • The user tier (free vs premium, family, student, etc.).
  • The number of streams, downloads, or other usages.
  • The gross revenue attributable to those events before splits.
  • The DSP’s reporting currency.
  • The reporting period (usually a calendar month).

One DSR file from Spotify in a busy month for a mid-sized distributor can be tens of millions of lines.

Why does DSR exist?

Same reason as ERN. Before DSR, every DSP shipped royalty reports in its own format. A distributor with twelve DSP relationships maintained twelve different parsers, and a label with multiple distributors could not compare across them.

DSR collapses the formats. Distributors build one parser. Labels and artists get apples-to-apples data. The royalty industry’s transparency story, such as it is, starts with DSR.

How does DSR work in practice?

The monthly cycle:

  1. The DSP closes its books on the month (usually with a 30 to 60 day lag).
  2. It generates a DSR file per content provider, listing every reportable event that quarter or month.
  3. The file is dropped on an SFTP server the distributor monitors.
  4. The distributor’s royalty engine ingests, validates, and matches each line to an ISRC in its catalog.
  5. For each matched line, splits are applied per the artist’s splits sheet.
  6. The resulting amounts land in artist dashboards, usually 60 to 90 days after the play happened.

This is why your January streams typically appear in your April statement. The delay is not the distributor stalling. It is the DSR cycle.

What this means for global indie artists and labels

Three working rules.

1. The DSR is the source of truth for any payout dispute. If you believe Spotify underpaid you in Q3, the document you need is the raw DSR for that period. A serious distributor can produce it. If they refuse, that is a red flag about the entire operation.

2. DSP per-stream rates only exist after you have the DSR. Average per-stream rates are calculated by dividing the DSR’s revenue lines by its stream lines, country by country. Anyone quoting “Spotify pays X per stream” without referencing actual DSR data is guessing.

3. Regional payout currency matters more than the headline number. Boomplay DSRs come in USD but settle through local payment rails. JioSaavn DSRs come in INR. Anghami DSRs split between USD and local Arab currencies. The number on the statement is only useful once you know the FX conversion and any banking fees attached.

Common DSR mistakes and gotchas

  • Unmatched ISRCs. If your release was re-issued with a new ISRC by a new distributor, plays counted against the old ISRC may never reach you. The DSR line existed, but the parser could not match it. This is the most common cause of “missing royalties.”
  • Period boundary confusion. A play on the night of 31 January in Tokyo may land in the February DSR depending on the DSP’s timezone handling. Disputes that cross month boundaries are extra hard.
  • Currency conversion drift. Distributors typically convert DSR revenue to a settlement currency (often USD) using a monthly average FX rate. If you compare a Nigerian artist’s statement in USD to their bank deposit in NGN, the gap is usually FX and bank fees, not the distributor short-changing you.
  • Late or skipped DSRs. Some smaller regional DSPs ship DSRs quarterly or even semi-annually rather than monthly. Your earnings on those platforms appear in lumpy blocks.
  • Refunds and chargebacks. A negative line in this month’s DSR may be reversing a play counted in a previous month. Net royalties on a single track can go negative for a month.
  • Sub-distributor double-counting. If a label is in a white-label arrangement with a parent distributor, the same DSR line can theoretically be processed twice. A good royalty engine deduplicates by ISRC plus reporting period plus DSP.

How InterSpace Distribution handles this

InterSpace Distribution parses DSR files from every connected DSP and applies splits at the line level, with monthly artist statements that map back to the source files. Raw DSR data is available on request for any artist or label client who wants to audit a specific period. The same engine handles African, MENA, South Asian, and Southeast Asian DSRs that majors-focused distributors deprioritise or skip entirely.