Royalty statement to Excel

Why royalty statements are harder to reconcile than invoices

None of these four are a sign that any single royalty statement is badly built — they're the normal shape of a royalty pipeline that involves a recording rights side and a publishing rights side, domestic and foreign collection, and a reporting cycle that was never designed around a label's or publisher's own need to reconcile it all in one place.

What this doesn't do, stated up front

What's left is narrow, and it's exactly the part that eats a reporting period: turning a stack of differently structured statements into one place where a track's total income across every source is visible and checked.

What gets read

Not every statement carries every field — a sub-publisher statement rarely prints an ISRC, and a distributor statement rarely prints an ISWC. Reading each statement for what it actually contains, rather than expecting a fixed template every source should have used, is what makes matching across them possible at all.

flowparse.io

Distributors, PROs, sub-publishers and mechanical societies

A catalog earning from more than one kind of source discovers quickly that the differences aren't just cosmetic formatting — each statement type reports a genuinely different slice of income, on its own schedule, keyed to its own identifier.

None of that is a reason to give up on one consistent process — it's the reason each source gets read on its own terms rather than forced into a template built for a different kind of statement, and rolled into one place only after that.

How a track finds itself across statements

Matching checks a fixed hierarchy, strongest signal first, because no single identifier is reliably present on every statement type a catalog is likely to encounter.

A line that matches on ISRC or ISWC is treated with high confidence. A line that only matches by title and artist — the case for many sub-publisher statements — is matched with a flag, since a title alone can genuinely collide across a large catalog or a common song name.

flowparse.io

One recording, three statements, reconciled

A single track, one calendar quarter, reported by a distributor almost immediately and by two other sources months later.

Looked at from the distributor statement alone, this track earned $412 that quarter. The full picture — $604 — only exists once the mechanical and performance statements are matched to the same ISRC and ISWC and added in, seven months after the quarter actually closed. A catalog that stops reconciling once the fastest statement arrives is routinely underestimating its own income by a third or more, not because anything is wrong, but because it never waited for the slower sources to catch up.

flowparse.io

How it works

flowparse.io

Black-box royalties and metadata mismatches

“Black-box” royalties are a well-documented, industry-wide problem: money collected by a PRO or a foreign collection society that can't be matched to a specific rights holder, usually because the recording's metadata — a missing ISWC, a title spelled differently than the registration, a writer's name in a different order — didn't line up with what the society has on file. That unmatched pool eventually gets distributed by market share among everyone else, rather than paid to the catalog that actually earned it.

This doesn't claim black-box money back on its own — that requires registering correct metadata with the relevant society directly. What it does is make the gap visible: a recording that shows real activity on a distributor statement but never appears on the corresponding PRO or mechanical statement for the same period is exactly the pattern worth checking against that society's registration records, rather than a discrepancy that quietly disappears into an unreconciled total.

flowparse.io

Why the same quarter arrives at different times

A distributor statement for a given quarter is usually available within weeks — the platform already has the streaming data and pays out on a fixed, short cycle. A domestic PRO statement for the same quarter typically takes several months longer, because performance data has to be reported, matched and processed before a payment run. A foreign sub-publisher or a foreign collection society's share can take the longest of all — sometimes over a year — because that income first has to be collected domestically abroad, reported to the home society or sub-publisher, converted, and only then remitted.

None of these delays is unusual or a sign of a problem with any single source. What it does mean is that a reconciliation run the month after quarter close will always be reading an incomplete picture for that quarter — accurate for what's arrived, structurally missing whatever hasn't. Revisiting a prior quarter as later statements arrive, rather than treating the first pass as final, is what catches the difference between a genuinely complete number and one that just looks complete because the slow statements hadn't landed yet.

Currency conversion across territories

A catalog earning internationally accumulates royalty lines in a dozen currencies, each converted at whatever rate applied on the date that specific statement was issued — not a single rate applied consistently across the year. A Japanese distributor statement converts yen to dollars at one rate; a UK PRO statement converts pounds at a different rate, months later.

Figures are read exactly as each statement reports them, in the currency and at the conversion the statement itself used, rather than re-converted to a single assumed rate. That preserves what the statement actually said — which matters when a specific line is later checked against the exact deposit it produced, since re-converting after the fact would introduce a discrepancy that was never really there.

How catalog size changes the reconciliation

A single-artist catalog with a dozen released tracks and one distributor produces a reconciliation that's straightforward mostly because there's little room for a mismatch to hide — a missing statement or an unmatched line is obvious against a short list. A label or publisher administering several hundred tracks across dozens of writers faces the same underlying task at a scale where a single missing statement, or one recording's metadata mismatch, is easy to lose inside a large total that otherwise looks reasonable.

Reading every line individually rather than checking only the aggregate is what keeps a large catalog's reconciliation from silently absorbing exactly the kind of small, per-track gap that a total-only glance would never surface — the difference matters more, not less, as a catalog grows.

Advances, recoupment and negative balances

A label or publisher statement often carries a recoupment balance — an advance paid to an artist or writer, deducted from royalties as they're earned until the advance is fully recovered. A statement during that recoupment period can show real earned royalties alongside a net payable of zero, or even a negative running balance, which looks like a missing payment if the recoupment context isn't read alongside the earnings themselves.

Reading the earned-royalty figure and the recoupment deduction as their own separate lines — rather than only the net payable — keeps a fully recouped statement from being mistaken for a period with no real activity, and makes it possible to track exactly when an advance will clear based on actual earnings rather than a projection.

What happens to what doesn't match

A line that doesn't match anything on another statement isn't discarded or folded into a catalog-wide total — it's kept as its own visible group, with the title, identifier and amount as reported, so it can be checked directly rather than disappearing into a reconciled figure that quietly absorbed a gap.

In practice, an unmatched line turns out to be one of a small number of things: a statement from a different period than expected, a recording genuinely not yet reported by a slower source, or a metadata mismatch worth investigating with the society or sub-publisher directly. Each has a specific, quick next step once it's visible instead of buried.

Who this is for

This isn't a connected-account sync

Worth being precise about the boundary. This doesn't connect to your DistroKid, TuneCore, ASCAP, BMI or publisher administration account — there's no login, no OAuth, no ongoing sync. You download the statement yourself, the same way you already download it to check by hand, and upload it here.

For catalogs that also need the underlying bank deposits matched to what a distributor reported it paid out, that's the other half of the picture — the same document-reading approach applied to a bank statement, matched against the royalty statement's own reported total.

flowparse.io

Moving from a spreadsheet built by hand

Most catalogs that reach for this have already built a spreadsheet — retyping figures from each statement, tab by tab, into one running total. It works, in the sense that it produces a number, but it's slow enough that it usually only happens once a quarter, and a transcription error or a missed statement rarely gets caught until much later, if at all.

The transition doesn't require throwing that spreadsheet away on day one. A reasonable first step is running the automatic matching alongside the existing spreadsheet for one reporting period, comparing the two, and building confidence in where they agree and where the automatic result catches a line the manual process missed.

What tends to convince a skeptical royalty team isn't a claim about accuracy — it's seeing their own catalog's statements produce a matched total that surfaces a missing PRO statement or a metadata gap they hadn't actually checked before, in a fraction of the time the manual version took.

How often to reconcile

Reconciling as each statement arrives, rather than waiting for a full quarter's worth of every source, catches a missing or mismatched line while the specific period is still fresh enough to investigate quickly. Waiting for every source to arrive before looking at any of them means a metadata problem from the fastest statement sits unnoticed for months, right alongside the slowest one.

A practical rhythm for most catalogs is a light pass whenever a distributor statement lands — since that's usually the fastest and most frequent source — and a fuller reconciliation once a quarter, when PRO and sub-publisher statements for that period have had a reasonable chance to catch up.

What accuracy actually looks like

A useful way to think about matching accuracy isn't a single percentage — it's the shape of the distribution across confidence levels. A catalog with clean, consistently registered ISRCs and ISWCs sees most lines match at high confidence, with only a small tail needing review. A catalog with older releases, missing registrations, or several sub-publisher relationships sees a larger medium-confidence tail, which means more review time, not necessarily more errors.

That distinction matters because a larger review queue is easy to misread as the matching working poorly, when it's often an honest reflection of how incomplete the underlying metadata actually is. The alternative — resolving every ambiguous line silently and reporting everything matched — isn't more accurate, it's hiding the uncertainty instead of surfacing it.

In practice, catalogs with well-registered metadata across most releases see somewhere between 80% and 92% of statement lines match at high confidence on a given reconciliation, with the rest split between a quick medium-confidence confirm and a smaller number of genuine gaps worth investigating individually.

Privacy

Full details are on the security page.

Frequently asked questions

Keep reading