Self-Report to SoundExchange with a Low-Cost Enrichment Layer

Streaming a station in the United States means paying sound-recording royalties, and paying them means filing a SoundExchange Report of Use— a periodic data file listing every recording you played. Some webcaster hosts fold ISRC assignment and report filing into their subscription at a premium. That is a legitimate convenience. But it is not the only option: you can self-report, and the gap you actually have to close is smaller than it looks.

The build-vs-buy choice

A bundled reporting product does two things for you: it attaches an identifier to each recording and it hands the finished report to SoundExchange. Both are useful, and for some operators the convenience is worth the premium. This article is for the other operators — the ones who already run their own automation, already have the play counts, and would rather self-report and pay only for the small piece they are missing.

Neither path is “correct.” The question is simply whether you want to buy a whole reporting workflow, or fill a two-field gap in the report you can already assemble yourself.

What self-reporting actually requires

Strip a Report of Use down to its fields and most of it is data your automation already produces: the track title, the featured artist, the number of performances, and the name of your service or station. (For a full field-by-field walkthrough, see what a Report of Use requires.) The genuine gap is the recording identifier: the ISRC on each line — or, when the ISRC is unavailable, the album name and the marketing label together, which is SoundExchange's accepted fallback.

In other words, you are not missing a reporting system. You are missing one or two columns. Everything else, you own.

Filling just the gap

SonoVault turns an artist and a title into the ISRC, the album, and the marketing label for that recording. That is exactly — and only — the data a play log tends to lack, so you can close the gap without buying a full bundled product to do it. There are two routes, depending on whether you want to touch code:

• No code. Paste or upload your list of played tracks into the free Bulk Lookup tool, choose the ISRC and Label columns, and download the enriched result as CSV. The RadioBoss enrichment guide walks the whole flow end to end.
• As a pipeline.Resolve each unique track through the API and attach the ISRC and label programmatically — see the automation-log-to-Report-of-Use pipeline for the dedupe-then-resolve pattern.

It is worth knowing that SoundExchange itself offers free tools that backfill ISRCs after the fact — its ISRC Search and Report of Use Augmentation services will return your submitted report with ISRCs added and flag lines that may be missing required information. Those are a fair safety net. SonoVault's difference is that it enriches your data before you file, so the report leaves your hands complete.

A rough cost sketch

The reason self-reporting stays cheap is that the enrichment job is small and bounded. A station plays the same records over and over, so the number of unique recordings in a reporting period is far smaller than the number of plays. Dedupe your log down to distinct tracks, resolve each one once, cache the result, and then re-attach the ISRC and label to every play by that track.

We are deliberately not quoting a figure here, and definitely not one pitched against any named product — your volume, your catalogue, and how much of it already carries ISRCs all move the number. The point is structural: filling two columns on a deduplicated track list is a modest, predictable job, not a recurring platform fee.

What SonoVault does and doesn't do

Used that way, self-reporting is not the daunting part of running a station — it is a spreadsheet you already mostly have, with two columns filled in. Start with the Report of Use field guide, then enrich your log with the free Bulk Lookup tool.