Black Box CapitalRoyalty forensics
How it works

Follow the money. Find where it stops.

Every royalty dollar crosses several matching steps before it reaches you. The audit engine reads your statements, rebuilds the chain for each song, and flags each step that should have paid but didn't.

The royalty chain

Select a numbered step
Your catalogrecordings (ISRC) + compositions (ISWC) Distributor → DSPsstreams, downloads, radio, UGC Metadata matchtitle · ISRC · ISWC · IPI · splits6 Distributor paymasters · usually fine The MLCUS mechanicals1 PROUS performance2 SoundExchangeUS non-interactive3 Foreign CMOsperformance + NR4 Content IDYouTube UGC5 Owner's accountwhat actually arrives
Overview

Six places money stops

Each numbered step matches on metadata. A failure at step 6 can starve several collectors at once. Select a step to see the symptom on your statements, the eligibility screen, the typical collection lag, and how the engine detects it.

Masters income through your distributor usually leaks the least. Publishing and neighboring rights leak the most, which is why the report never blends them into one number.

The engine

What happens to your files, step by step.

Parse

PapaParse reads each CSV in your browser. Headers are scored against known layouts (DistroKid, CD Baby, TuneCore-style distributors, PROs, MLC, SoundExchange, YouTube) and the statement type is detected.

Map columns

Title, ISRC, ISWC, period, territory, store, quantity and amount are mapped automatically. You can override any mapping before the audit runs.

Normalize & link

Titles lose "feat.", remaster tags and punctuation; ISRCs are validated. Recordings link to works by ISRC first, then by normalized title, and variants are merged.

Score & screen

Six rules compare what each song earns in one channel with what the others imply. Each hit passes an eligibility screen and gets a dollar estimate, a confidence level and a lag.

Try the normalizer

Why "the same song" isn't, to a database.

Type a title or an ISRC the way it appears on a statement. This is the same function the audit engine uses to merge variants.

Title & ISRC normalizer

Live
Leak rules

Six rules, each with an eligibility screen.

"Identified" means the pattern is on your statements. "Eligible" means it passed the screen and could be collected. We always report both, by income type.

#LeakSymptom on statementsEligibility screenIncome typeTypical lag
1Unregistered or unmatched mechanicalsStreams on the distributor statement, no MLC or administrator income for the workWriter controls the composition share; checked via MLC registered data access, not scrapingPublishing4-6 months
2PRO title or split mismatchUS streams but no domestic performance income, or a co-writer's share missingSplits must be documented; disputed splits are "identified, not eligible"Publishing6-9 months
3No SoundExchangeUS non-interactive plays (radio-style streams, satellite, webcasts), no SoundExchange lineCan't be inferred from distributor statements alone; needs the owner's SoundExchange statement or registration statusNeighboring rights6-9 months
4No foreign or neighboring rightsMaterial ex-US streams, no foreign society incomeSociety membership or sub-publishing; lag disclosed up frontPublishing + NR12-24 months
5No Content IDYouTube or UGC usage, no Content ID revenueExclusive rights in every claimed territory; leased beats, uncleared samples and previously licensed tracks are ineligibleMasters2-4 months
6ISRC/ISWC mismatch or title variantsIncome split across duplicate records, or a recording linked to the wrong workCanonical work record; owner confirms the mergePublishing + masters4-9 months

Sources for the screen: MLC terms of use · MLC data programs · SoundExchange · Revelator · FUGA · iMusician. Lags are planning assumptions from the business plan.

Free audit

Privacy mode

You export CSVs by hand and drop them in. Parsing runs client-side, so your statements never leave the browser. The report shows dollars by leak type and income type, a fitted decay curve and a 10-year projection. The work-by-work fix list is not included.

Engaged

Fix and monitor

Fix and valuation clients sign an opt-in data agreement and a letter of direction. We generate CWR/bulk registration files that a publishing administrator ingests, and a claim-status portal shows each source's progress through its lag.

See it on a real catalog.

The prototype runs on your CSVs, or on a 120-song synthetic catalog with planted leaks.