Music Royalty Audit: How to Reconcile Distributor, Publishing, and Neighboring Rights Statements

Music royalties rarely arrive as one number that can be accepted at face value. A single recording may generate revenue through a digital distributor, publishing administrator, collective management organization, sync licensing, YouTube, and a neighboring-rights administrator. Each party may use different periods, currencies, terminology, levels of detail, and payment schedules.

The useful question is therefore not simply, “How much did this song earn?” It is whether all uses were reported, whether the recording and composition were connected to the correct rightsholders, whether splits followed the relevant agreements, and whether every difference has evidence and a next action.

Why streaming numbers are not a final royalty statement

Platform dashboards are useful for audience analysis, but they are not always the same as payment statements. Spotify explains that it pays rightsholders—such as labels, distributors, publishers, performance rights organizations, or collecting societies—who then pay artists and songwriters according to their agreements. Spotify also does not use one fixed per-stream rate.

A stream count alone cannot determine what should have been paid. Listener territory, account type, usage period, rights ownership, contractual deductions, tax, currency conversion, and reporting lag may all affect the final statement.

Royalties also follow two distinct assets:

• The sound recording or master: connected to the master owner, recording artist, label, distributor, and certain neighboring rights.
• The musical work or composition: connected to songwriters, composers, publishers, performance rights, and mechanical rights.

One person may be the singer, songwriter, producer, and master owner. Payment systems can still process those roles through separate channels. A reliable audit separates the rights before adding the money.

What is a music royalty audit?

An operational royalty audit reconciles catalog data, agreements, usage records, statements, and payments to find exceptions that require action. It does not assume that every difference is an underpayment. A gap may be caused by reporting lag, currency, a payment threshold, a distributor migration, unmatched data, a claim conflict, or an internal bookkeeping error.

A useful audit answers four questions:

1. Are the complete catalog and all entitled parties registered?
2. Have all expected statement sources delivered their files?
3. Can each revenue line be mapped to the correct recording or composition?
4. Can net revenue be explained by gross revenue, deductions, splits, tax, and cash received?

Step 1: build a master royalty ledger

Begin with a single catalog ledger that acts as the reference source. Do not use an audio filename or a distributor spreadsheet title as the primary key because spelling and version labels can change.

Minimum fields for each recording

• a stable internal ID and ISRC where available;
• official title, version, primary artist, featured artist, and release date;
• master owner, ownership percentage, territory, and rights period;
• active label and distributor with start or end dates;
• the underlying work, songwriters, publisher or administrator, and splits;
• source documents: split sheets, contracts, letters of direction, invoices, and registration evidence;
• payment account, currency, and expected statement schedule.

Model “recordings” and “works” separately, then connect them. One work can have multiple recordings; a medley can contain multiple works. This separation prevents master revenue from being mixed with publishing revenue.

Step 2: inventory every revenue path

List every source that should issue a statement, not only sources that have already paid. For an independent artist, this may include a distributor, publishing administrator, collective management organization, neighboring-rights administrator, YouTube or UGC administrator, sync agent, direct sales system, and label agreements.

Indonesia offers a timely example. In 2026, LMKN said its distribution process includes usage-data verification, validation, distribution reconciliation, and matching membership data with economic rights. LMKN has also announced unclaimed royalties, making identity and membership checks a practical priority rather than optional paperwork.

For each source, record:

• covered rights and territories;
• reporting frequency and expected lag;
• available file formats;
• payment threshold;
• currency and payment method;
• support contact and dispute deadline.

Step 3: preserve raw statements

Download complete statements on a fixed schedule. Store original files in a read-only folder with a consistent naming pattern, such as source_period_export-date_currency. Do not overwrite an older export even when a platform provides the same period again; adjustments may have been added.

The Mechanical Licensing Collective, for example, offers work-summary statements as well as royalty-detail files that can expose recording-level data from DSP usage reports. That difference in granularity determines which audit tests are possible.

Keep the PDF statement, CSV or TSV export, remittance advice, invoice, and bank evidence. A statement explains the calculation; a transfer proves the cash movement. The two must reconcile.

Step 4: normalize every source into one schema

Each provider labels columns differently. Build a normalized table while preserving the raw data. Practical columns include:

• statement source, payee, and statement number;
• usage period, statement period, and payment date;
• platform, territory, and usage type;
• ISRC, recording title, artist, work ID, and work title;
• usage units when supplied;
• gross revenue, deductions, tax, net royalty, and currency;
• exchange rate with its date and source;
• contract ID, applied split, and destination account;
• matching status and exception reason.

Do not turn missing fields into zero. “Not supplied” is different from “zero value.” Use explicit states such as not supplied, not applicable, or pending match.

Step 5: run seven reconciliation tests

1. Completeness test

Compare the expected statement calendar with received files. A missing statement is an exception even before you know whether it contains money.

2. Identity test

Match ISRC, title, version, artist, and internal ID. Flag rows matched only by title because remixes, live versions, and unrelated songs with the same name can collide.

3. Ownership and split test

Compare the statement percentage with the agreement effective during the usage period. Do not apply the newest split to an older period without checking effective dates.

4. Period and territory test

Do not confuse usage period with payment date. Confirm that the reporting party actually had a mandate for the territory.

5. Gross-to-net test

Reconstruct gross revenue less fees, recoupment, withholding tax, or other contractually defined deductions. An unexplained deduction belongs in the exception queue.

6. Duplicate test

Search for repeated combinations of source, statement number, period, ISRC, territory, and amount. Duplication often occurs when consolidated and individual files are imported together.

7. Anomaly test

Compare trends by catalog and territory, but do not automatically label a drop as underpayment. Reporting lag, consumption changes, currency, earlier adjustments, or a distributor migration may explain it.

Example: one single, three different exceptions

Imagine a fictional single called “Hujan di Pesisir.” The artist dashboard shows listeners in Indonesia, Malaysia, and Australia. During a quarterly audit, the team finds:

• the distributor statement covers the master in all three territories, but the acoustic version is not connected to the correct ISRC;
• the publishing statement covers only two territories because a work registration remains pending in one territory;
• a neighboring-rights payment reaches the featured artist account, while the master-owner portion has not been claimed in the appropriate account.

None of these cases can be resolved by multiplying streams by an estimated rate. Each requires different evidence: recording metadata, work-registration status, and proof of master ownership.

Build an exception queue, not a colorful spreadsheet

Audit findings must become work with an owner and a deadline. Each exception should contain:

• case ID and priority;
• related recording or work;
• statement source and period;
• issue type: missing statement, unmatched recording, wrong split, duplicate, unexplained deduction, payment mismatch, or claim conflict;
• affected amount when it can be calculated without speculation;
• available evidence and missing evidence;
• party to contact, submission date, ticket number, and next follow-up.

Prioritize cases by risk of rights loss, dispute deadline, material value, and catalog scope. A case with an unknown amount can still be urgent when it affects the entire catalog or rightsholder identity.

A realistic 30-day audit cycle

1. Days 1–5: download statements and payment evidence; lock the raw files.
2. Days 6–10: import, normalize, and validate formats.
3. Days 11–15: match catalog, contracts, territories, and periods.
4. Days 16–20: run completeness, duplicate, split, and gross-to-net tests.
5. Days 21–25: review exceptions with the artist, manager, label, or administrator.
6. Days 26–30: submit evidence-backed disputes, update status, and document decisions.

For a small catalog, a quarterly audit is often more realistic than a full monthly audit. Statement arrival and payment-account changes should still be checked every month.

A dashboard that helps without creating false certainty

An internal dashboard should separate reported, paid, pending, and disputed. Do not present an “expected royalty” as a precise number when it is based only on stream estimates.

More actionable metrics include:

• percentage of catalog successfully matched;
• number of overdue statements;
• cash received but not reconciled;
• open exceptions by age and source;
• recordings missing ownership documents or complete splits;
• average dispute-resolution time.

DDEX provides standards for exchanging recording metadata, rights claims, and revenue reports. Independent artists do not need to implement DDEX themselves, but its principle is valuable at any scale: consistent identities, explicit sources, and machine-readable reporting structures.

Music royalty audit FAQ

Can an audit use an estimated per-stream rate?

Use it only as a rough signal, not as proof of an amount owed. Payment models, territories, contracts, and rights paths differ.

How often should an artist audit royalties?

Check statement arrival monthly and run a full reconciliation at least quarterly. Large catalogs or complex agreements may require a more frequent cycle.

Does a distributor statement include publishing?

Not necessarily. Coverage depends on the service and agreement. Confirm whether mechanical, performance, or publishing administration is included, then identify who handles the remaining rights.

What evidence matters most in a dispute?

Match evidence to the issue: agreements and effective dates, split sheets, proof of master ownership, registration evidence, recording or work IDs, original statements, and a reproducible calculation.

Is an artist analytics dashboard enough?

No. Audience analytics supports marketing, while an audit requires financial statements, rights data, agreements, and payment evidence.

Conclusion: traceable royalties matter more than impressive-looking numbers

A royalty audit is not an exercise in assuming every counterparty is wrong. Its purpose is to create an evidence chain from catalog and rights, to usage, statement, calculation, and payment. When every exception has a status and an owner, artists can repair data leaks without relying on guesses.

Wirasena Digital helps artists, labels, and creative teams design catalog ledgers, document workflows, reconciliation dashboards, and operational portals around their real needs. If your royalty records are scattered across accounts and spreadsheets, we can help turn them into a system that is easier to audit and act on.

Primary sources: Spotify Loud & Clear, The MLC, SoundExchange, DDEX, and LMKN. This article is educational and does not provide legal, tax, or accounting advice.