None of these look like mistakes at the time
Ask a label or publisher to describe a mistake they've made tracking royalties, and most will struggle to name one — not because they haven't made any, but because the ones that matter most don't announce themselves. Each individual statement still looks roughly right. Nothing throws an error.
That's exactly what makes the ten below worth listing explicitly. Each one produces something that looks fine on the surface — right up until someone lines up a distributor statement, a PRO statement and a sub-publisher statement for the same recording and finds a gap no one can immediately explain.
None of the ten below are hypothetical edge cases dreamed up for effect — each is a pattern that recurs across catalogs of very different sizes and distribution setups, the ordinary, unremarkable ways a royalty statement quietly drifts out of sync with what another statement, or the recording itself, says it should be.
1 · An ISRC typo at the point of release
A single transposed digit in an ISRC, entered once at the point of release and copied into every subsequent distribution and registration, quietly breaks the link between that recording and every statement that's supposed to report on it using the correct code.
The recording still earns — streams still happen, sales still occur — but any source matching strictly by ISRC either fails to find it at all, or worse, matches it against a different, unrelated recording that happens to share the mistyped code.
The tell: a track showing real streaming activity on one source but reporting nothing on another source that should also be paying on it.
2 · A composition with no registered ISWC
Many independent releases never formally register an ISWC for the underlying composition — a step that's easy to skip when a release is self-distributed and the recording-side ISRC already feels like it's doing the identifying work. PRO and sub-publisher statements, which key almost entirely to ISWC rather than ISRC, have nothing to match against.
Performance royalties on that composition still accumulate somewhere in the collection pipeline — they simply never make it back to the correct songwriter or publisher, because there's no registered identifier connecting the two.
The tell: a track with real distributor-reported streams but no corresponding performance-royalty statement from a domestic PRO after a reasonable reporting window.
3 · A remaster assigned a brand-new ISRC
A remaster, an anniversary reissue, or a region-specific release variant is often registered with an entirely new ISRC, even though a catalog owner considers it, functionally, the same recording and the same earning stream as the original. Statements referencing the old and new ISRC separately make the track's combined income look artificially split across two smaller totals.
Neither total is wrong on its own — the income genuinely was reported against two different codes — but reading either one in isolation understates what the recording actually earned as a whole.
The tell: two ISRCs with near-identical titles and artists, each reporting a fraction of the volume the release's overall popularity would suggest.
4 · Reporting lag mistaken for missing income
A distributor statement for a given quarter is usually available within weeks. A domestic PRO statement for the same quarter often takes several months longer. A foreign sub-publisher or collection society's share can take over a year. Treating the fastest statement as the full picture for that quarter systematically understates a catalog's real income — not because anything is missing, but because it hasn't arrived yet.
This is, by a wide margin, the most common cause on this list, precisely because it requires no error at all — just an incomplete view mistaken for a complete one.
The tell: a quarter's reconciled total that quietly grows every time it's revisited months later, without any new statement correcting an error.
5 · A sub-publisher's commission read as underpayment
A sub-publisher administering a catalog in a foreign territory deducts a commission — often 10% to 25% — before remitting the rest. A statement showing a net figure well below the gross income a catalog owner expected from that territory can look like an underpayment, when it's actually the contracted commission being applied exactly as agreed.
The confusion is easiest to avoid by reading gross and net figures as two separate lines on every sub-publisher statement, rather than comparing the net figure directly against an expectation formed from a different, commission-free source.
The tell: a territory's net royalty consistently landing at a fixed percentage below its gross figure, matching a known commission rate rather than fluctuating like a genuine error would.
6 · Currency conversion applied at a different rate per source
A catalog earning internationally accumulates royalty lines converted at whatever rate applied on the date each specific statement was issued — not one consistent rate applied uniformly across a year. A Japanese distributor statement and a UK PRO statement converting the same underlying currency months apart will rarely agree to the cent, even when both are entirely correct.
Re-converting every figure to a single assumed rate after the fact, in an attempt to make the numbers match more cleanly, actually introduces a discrepancy that was never really there in the first place.
The tell: a small, inconsistent variance between two statements' converted totals that tracks with normal exchange-rate movement over the gap between their issue dates.
7 · Black-box royalties distributed to someone else
When a PRO or foreign collection society collects performance income but can't match it to a specific rights holder — usually because of exactly the metadata problems described in causes one and two — that unmatched pool eventually gets distributed by market share among everyone else, rather than held indefinitely waiting for a claim.
Once that distribution period closes, the money is, in most jurisdictions, permanently gone to the catalog that actually earned it. This is the single most expensive cause on this list precisely because it doesn't just delay income — it can eliminate it.
The tell: a recording with strong streaming activity in a specific territory but consistently low or absent performance-royalty statements from that territory's collection society.
8 · A featured-artist credit spelled differently
A track credited as “Artist A featuring Artist B” on one statement, “Artist A” alone on another, and with a stage-name variant or initials on a third, can look like three different recordings to a matching process that relies on the artist field rather than a code.
Where a track's ISRC is consistent across statements, this cause never actually breaks anything — but for the sub-publisher and older PRO statements that carry no code at all and rely purely on title and artist text, an inconsistent credit is enough to produce a false split.
The tell: the same track appearing to earn from a source under two slightly different artist-name spellings, with no code available to confirm they're the same recording.
9 · Recoupment producing a net-zero payout
A statement covering a period during which an artist or writer is still working off an advance can show real, fully earned royalties alongside a net payable of zero — the earnings are being applied entirely against the outstanding balance rather than paid out. Read at the net-payable line alone, that looks exactly like a period with no income at all.
The earned figure and the recoupment deduction are two different facts, and conflating them — treating a fully recouped statement as if nothing happened that quarter — hides real information about how close an advance is to clearing.
The tell: a statement with a zero or near-zero net payable but a nonzero gross-earned figure, alongside a known outstanding advance balance.
10 · A compilation's shared UPC misattributing income
A various-artists compilation shares one UPC across tracks from many different rights holders. A statement or a naive matching process that groups income by UPC alone, without also checking the track-level ISRC, can attribute a compilation's combined income to the wrong contributor, or blend several contributors' shares into one undifferentiated total.
This cause is specific to catalogs with tracks that appear on licensed compilations or various-artists releases — a rare case for a catalog that only releases its own standalone albums and singles, but a recurring one for a catalog with sync placements or licensed compilation appearances.
The tell: a compilation appearance reporting income that doesn't correspond to the specific track's own known streaming or sales volume.
Why none of these trigger an alarm
Every one of these ten shares a structural feature: none produces a statement that looks obviously broken. A statement with a typo'd ISRC still has a valid-looking code, just the wrong one. A statement affected by reporting lag still contains real, accurate figures — just not all of them yet. A recoupment-affected statement is entirely correct on its own terms.
What each cause actually breaks is the relationship between statements — the fact that two documents, both individually accurate, should agree with each other once matched correctly, and quietly don't. That's a much harder kind of error to notice than a statement that's simply wrong on its face, because checking any single statement in isolation reveals nothing.
The pattern behind all ten
Look closely and eight of the ten trace back to one of two root causes: a metadata problem (identifiers one, two, three, eight and ten) or a timing problem (four, seven in part). The remaining two — sub-publisher commission and recoupment — are contractual facts that get misread as errors because the gross figure, not the contracted net figure, is what a catalog owner instinctively expects to see.
That concentration matters practically: fixing metadata registration once, at the point of release, and reading every statement's gross and net figures separately rather than only the bottom line, prevents the large majority of this list before it ever has a chance to compound.
A twenty-minute check that catches most of it
Pick one recording with real streaming activity. Pull its distributor statement, its most recent PRO statement, and — if applicable — its mechanical collection statement for the same period. Confirm the ISRC and ISWC match across all three documents exactly, character for character. Confirm the PRO statement has actually arrived for a period consistent with that source's normal reporting lag, not the distributor's faster one. Confirm any sub-publisher figure is being read at its net line, checked against the correct commission rate, not compared directly to the gross.
Twenty minutes, one recording, and most catalogs find at least one of these ten already present somewhere in their reporting — usually cause four, sometimes cause one or two.
The mistake that compounds all the others
There's an eleventh pattern underneath the ten, worth naming separately: none of this knowledge survives a handoff unless it's written down. A royalty administrator who's learned which sources run slow, which sub-publishers deduct what commission, which older releases still need an ISWC registered — all of that context leaves with them unless it's documented somewhere the next person can find it.
Catalogs with high turnover in whoever handles royalty administration are, in practice, the ones most exposed to every cause on this list, simply because the informal knowledge that used to compensate for gaps in the underlying metadata keeps resetting to zero.
A composite case, built from several real ones
No single catalog hits all ten in one year, but the pattern below — assembled from cases that recur across many catalogs rather than any one in particular — shows how a few of these compound into something bigger than any of them look on their own.
An independent label with a roster of six artists had reconciled royalty statements loosely for as long as anyone could remember — a glance at each distributor payout, no cross-source matching. At year-end, total royalty income looked meaningfully lower than the streaming and sales data would suggest, with no obvious single explanation.
Working backward through the year's statements turned up three separate, unrelated causes. Two older tracks had never had an ISWC registered, meaning a full year of domestic PRO income for those compositions had never been collected at all — cause two, and the largest single contributor to the gap. A remaster of the label's best-known single, reissued with a new ISRC for a streaming re-promotion, had been tracked as an entirely separate, much smaller-earning recording — cause three. And a foreign sub-publisher's statements had been compared directly against gross expectations every quarter without anyone checking the contracted commission rate, generating months of unnecessary internal concern over an “underpayment” that was, in fact, correct — cause five.
None of the three would have been remarkable on its own, caught within the quarter it happened. Stacked across a full year of loose reconciliation, they added up to a royalty gap the label noticed and had no immediate explanation for — exactly the scenario a cross-source, identifier-based reconciliation is built to prevent.
| Cause found | Share of the gap |
|---|---|
| Two tracks with no registered ISWC (a full year of uncollected PRO income) | ~5 points |
| Remaster tracked as a separate recording under a new ISRC | ~2 points |
| Sub-publisher commission investigated repeatedly as underpayment (wasted time, no revenue impact) | ~0 points |
| Total royalty gap explained | ~7 of 8 points |
Why these compound instead of canceling out
A reasonable instinct is to assume small errors in both directions roughly cancel — a mismatch one way balanced by another the other way, netting out to something close to correct. In practice, that's not how most of these ten behave.
Most of them are one-directional. A missing ISWC only ever means missed performance income, never extra. Black-box redistribution only ever moves money away from the catalog that earned it, never toward it. A reporting lag only ever makes a quarter look smaller than it eventually turns out to be, never larger.
Because the errors skew in a consistent direction relative to whichever cause produces them, they accumulate rather than average out, which is exactly why a gap that looks small after one quarter can look substantial after a full year of the same unchecked pattern repeating across a whole catalog.
That one-directional bias is the strongest argument for reconciling every statement as it arrives rather than sampling occasionally: it caps how much any single unchecked cause can accumulate before someone notices.
Each cause, and its one fix
Ten causes can feel like ten separate things to remember. In practice, each one has a single, specific habit that prevents it — worth having as a quick reference rather than re-deriving from the full description each time.
| Cause | The one fix |
|---|---|
| 1 · ISRC typo at release | Verify the ISRC against the official registration on the very first statement that reports it |
| 2 · No registered ISWC | Register an ISWC for every composition before or immediately after release, not after the first missing statement |
| 3 · Remaster with a new ISRC | Deliberately link a reissue's new ISRC back to the original recording in your own catalog records |
| 4 · Reporting lag mistaken for a gap | Revisit each quarter's total as slower sources arrive, rather than treating the first pass as final |
| 5 · Sub-publisher commission confusion | Read gross and net as two separate lines, checked against the actual contracted commission rate |
| 6 · Currency variance | Expect a small conversion variance between sources and stop re-investigating it |
| 7 · Black-box redistribution | Register metadata correctly with every relevant collection society before a distribution period closes |
| 8 · Featured-artist spelling | Match by ISRC first; only fall back to artist-name comparison when no code is present |
| 9 · Recoupment read as no income | Track gross earned and recoupment deduction as two separate figures on every statement |
| 10 · Compilation UPC misattribution | Match compilation appearances by track-level ISRC, not by the release's shared UPC alone |
None of these ten fixes require new tools or a change in how the catalog operates day to day. Each is a single habit, applied consistently — which is the same underlying principle as the pattern discussed above, just made concrete enough to actually act on the next time any of these ten situations comes up.
Print this table, or keep it pinned somewhere visible during royalty reconciliation, and most of the ten stop being mistakes waiting to happen and start being a five-second check each cycle.
Who actually catches these, in practice
In operations with more than one person touching royalty administration — a label manager and a royalty accountant, or an artist reviewing quarterly with a business manager — these ten causes get caught noticeably more often than in a solo-run catalog handling both releases and royalty reconciliation with no one double-checking the work.
That's not a comment on any individual catalog owner's competence. It's simply that a second person looking at the same statement asks different questions, notices different things look odd, and isn't blind to the same assumptions the first person has already made without realizing it.
Catalogs without the luxury of a second reviewer aren't without options — a short, explicit checklist like the one in this article substitutes reasonably well for a second pair of eyes, precisely because it forces the same questions a second reviewer would ask, even when there isn't one available.
If you're new to reconciling royalty statements, start here
A catalog reconciling royalty statements for the first time doesn't need to memorize all ten causes before doing anything useful. Three checks, done on the next set of statements, catch a disproportionate share of what's likely to have already gone quietly wrong.
Pick your five most-streamed tracks and confirm each one has a registered ISRC and ISWC that matches across every statement you have for it.
Check whether a PRO statement has ever arrived for your catalog at all — its absence entirely is more common, and more consequential, than a delayed one.
For any sub-publisher relationship, confirm you know the exact contracted commission rate before comparing a net figure to anything.
None of these three require deep familiarity with any specific source's reporting history — they're checks anyone can run against current statements within a few minutes, well before the rest of the reconciliation learning curve has been climbed.
A fourth, less mechanical step matters just as much: ask directly whether royalty statements have ever been reconciled across sources at all, or only glanced at individually as they arrive. The answer shapes how much of this article's ten points are worth worrying about immediately versus over the coming reporting cycles.
Does catalog size make this worse, or better?
Intuitively, a larger catalog with more releases and more writers would seem to have more room for these causes to hide. In practice the relationship is more complicated than that, and cuts both ways depending on which cause is in question.
Larger catalogs are more exposed to causes two, seven and ten — unregistered ISWCs, black-box redistribution and compilation misattribution — because a bigger back catalog is more likely to include older releases from before consistent registration practices were established, and more likely to have tracks licensed onto compilations.
Smaller catalogs and self-releasing artists are more exposed to causes four and nine — reporting lag and recoupment confusion — for the opposite reason: with fewer tracks and fewer statements to cross-check, a single misread quarter is a much larger share of that catalog's total reported income than the same miss at a larger operation with dozens of releases smoothing out the noise.
The practical conclusion is the same either way: no catalog size is naturally immune to this list, just exposed to a different subset of it.
Knowing which end of that spectrum your own catalog sits on is worth a moment's honest thought — it points directly at which two or three of the ten deserve the closest attention first, rather than treating all ten as equally likely.
| Catalog size | Most exposed to |
|---|---|
| Self-releasing artist, single distributor | 4 · Reporting lag, 9 · Recoupment confusion |
| Small independent label (a handful of artists) | 5 · Sub-publisher commission, 8 · Credit spelling |
| Larger catalog or publisher (older back catalog) | 2 · Unregistered ISWC, 7 · Black-box redistribution, 10 · Compilation misattribution |
What this doesn't fix
Naming these ten causes doesn't decide whether a royalty rate was actually correct, doesn't file a black-box claim on your behalf, and doesn't tell you when a gap is worth pursuing with a society versus writing off. Those remain decisions for whoever owns the catalog's royalty administration, made with accurate information — which is the one thing this list is actually trying to protect.
The step-by-step method for reconciling statements across sources without falling into any of these ten is in how to reconcile music royalty statements.