June 2, 2026

Royalty Audit Procedures: Find Unpaid Royalties

Most advice on royalty audit procedures is stuck in the CD era. It treats an audit like a rare legal ambush. That's outdated.

For modern artists, songwriters, managers, and indie labels, a significant concern isn't whether a statement contains an erroneous formula. Rather, the difficulty stems from money moving through distributors, DSP reports, PROs, CMOs, publishers, neighboring rights systems, and accounting exports that don't naturally line up. A clean-looking royalty statement can still be wrong because the data chain behind it is incomplete.

That changes how smart teams should think about audits. They shouldn't start with panic. They should start with triage, documentation, and a hard look at which deals are worth testing first. Then they should trace the money from source systems back to the contract. That's where unpaid royalties usually show up.

Errors are normal not exceptional
A statement can be neat and still be wrong

Start with the audit clause
Pick targets instead of auditing everything
Build a clean audit file

Standardize the mess first
Follow one song through the system
What to test when the numbers feel off

Lead with evidence not emotion
A practical escalation path

Trusting summaries instead of source data
Letting fuzzy contract language slide
Treating small discrepancies like they do not matter

Use reviews for small issues and audits for bigger ones
Continuous monitoring is the real upgrade

Why Your Royalty Statements Are Probably Wrong

Artists get told to trust the statement unless something looks wildly broken. Bad advice. In music, a royalty statement is often the last stop in a long relay of exports, mappings, deductions, split calculations, and metadata joins. If one upstream input is wrong, the final PDF can still look polished.

A royalty audit isn't a declaration of war. It's a business control. That's not opinion dressed up as drama. In a webinar summary published by TAA Abstract, auditor Juli Saitz described a five-phase audit process and said most audits produce findings, with an average underreporting range of 15% to 20% according to TAA Abstract's summary of royalty audit phases.

An infographic titled Why Your Royalty Statements Are Probably Wrong, highlighting audit statistics for music artists.

Errors are normal not exceptional

The popular fantasy is that accounting teams catch everything and contracts remove ambiguity. They don't. Royalty reporting breaks when teams classify products incorrectly, miss bundled uses, apply exclusions loosely, or interpret escalation language differently from the rights holder.

That matters even more in music because one release can generate several kinds of income at once. A track might earn from streaming, downloads, neighboring rights, public performance, mechanicals, direct licenses, and YouTube claims. Those flows don't arrive in one neat bucket.

Practical rule: If the income path is fragmented, the statement needs verification.

A healthy mindset is simple. Trust the relationship, but verify the math. Good partners shouldn't be offended by competent oversight.

A statement can be neat and still be wrong

The biggest mistake artists make is judging accuracy by formatting. If the columns add up and the branding looks official, they assume the statement is right. That's not how payment accuracy works.

A clean statement can still hide problems like:

Missing source revenue: money collected somewhere else never made it into the payor's report.
Wrong royalty-bearing status: a use got classified as non-payable when the contract says otherwise.
Bad territory handling: one region got routed through a different system with different assumptions.
Split mismatches: the recording side and publishing side reflect different ownership data.

A manager looking at a strong catalog with weak cash flow shouldn't start with conspiracy theories. The better move is to treat the statement like a summary, not a fact. Summaries are where mistakes get hidden because nobody checks the source layers underneath.

Before You Audit Get Your House in Order

A sloppy audit request gets ignored, delayed, or narrowed. A prepared one gets taken seriously. Before anyone asks for backup data, the rights team needs to know what the contract allows, which payor matters most, and what documents already exist on the artist side.

Start with the audit clause

The contract is the gatekeeper. Every deal should be reviewed for the language that controls audit rights, notice requirements, timing, and lookback limits. If the agreement has amendments, side letters, or rate memos, those belong in the same folder. Half the confusion in royalty disputes comes from people relying on the main contract and forgetting the later paper that changed the economics.

A clean prep file should include:

The signed agreement: not the draft, not the email summary.
All amendments and extensions: especially anything that changed rates, deductions, or territory.
Royalty statements by period: with payment dates attached where possible.
Support files already received: spreadsheets, sales summaries, foreign sub-publisher reports, distributor exports.
A release list: every master, composition, version, remix, and alternate title.

For recording catalogs, metadata discipline matters more than most artists think. ISRCs, UPCs, alternate titles, and contributor names have to match across systems or revenue gets split into ghost fragments. Teams that haven't cleaned up release identifiers should fix that first. A practical place to tighten the basics is this guide to barcodes for music releases, because audit work gets ugly fast when release IDs are inconsistent.

An infographic titled Before You Audit outlining six key steps for preparing to conduct a royalty audit.

Pick targets instead of auditing everything

Most public content explains how to run an audit after the target is chosen. The better question is which agreements deserve attention first.

The University of California's proposed audit identification approach starts with ongoing monitoring and uses a dollar threshold, such as $5M, to flag candidates, as shown in the University of California audit identification materials. Music teams can steal that logic even if their catalogs are smaller. The point isn't the exact threshold. The point is triage.

A smart target list usually ranks deals by these signals:

Deal signal	Why it matters	Example
High revenue	Bigger upside if there's leakage	A label deal tied to the strongest streaming releases
Complex payment terms	More room for interpretation errors	Net receipts language, cross-collateralization, escalations
Multiple collection layers	More chances for gaps	Distributor to label to artist, or publisher to sub-publisher to writer
Sudden statement changes	Often points to process changes or missing data	Catalog is stable but reported income drops without a clear reason
Weak backup support	Harder to verify summary lines	Statements arrive without territory detail or source schedules

The first audit target usually isn't the most suspicious partner. It's the agreement with the largest combination of revenue, complexity, and missing visibility.

Build a clean audit file

Before a formal request goes out, the artist's team should prepare a one-page summary for each deal under review. Nothing fancy. Just the practical stuff.

Include:

Counterparty name
Contract period
Products or works covered
Royalty types involved
Periods that look questionable
Specific concerns
Requested records

A non-combative request works better than a theatrical one. The tone should sound like finance, not litigation. Something as simple as “The team is reviewing reporting completeness and would like supporting detail for these periods and works” usually lands better than accusations.

The Deep Dive Matching Data and Finding Gaps

Royalty audit procedures transition from theory to detective work. The team has the contract. It has the statements. Now it needs to answer the only question that matters. Does the money reported match the money that should have been reported?

A professional accountant performs data matching between physical documents and spreadsheets on two computer monitors.

Modern music audits are hard because the source data lives in separate worlds. Metacomet notes that a major challenge is reconciling royalty data from fragmented systems like distributors, PROs or CMOs, and DSP statements, and that the biggest risk is often incomplete visibility across the data chain, as discussed in Metacomet's royalty auditing overview.

Standardize the mess first

The raw exports almost never match each other. One file uses track title. Another uses ISRC. Another groups by territory. Another shows net revenue after fees. Another lists only payable units. If the team starts comparing those files line by line without standardizing them, it'll chase ghosts.

A workable process looks like this:

Normalize identifiers: map every row to the same release and track IDs where possible.
Align periods: convert statements to the same reporting month or quarter.
Separate revenue types: don't mix master income with publishing income during testing.
Tag territories and counterparties: missing country or partner fields create fake variances.
Track deductions separately: never bury them inside gross comparisons.

A practical example helps. Suppose one song appears on Spotify, Apple Music, YouTube, and a few regional DSPs through a distributor, while public performance and mechanical income flow through separate collection channels. The artist statement may show one line for “digital streaming receipts.” That line is too compressed to audit on its own. The team needs the underlying schedules.

One useful prep step is learning how payors present summaries versus source detail in their financial exports. This breakdown of how to read earnings reports gives a clean way to separate top-line statements from actual audit evidence.

Follow one song through the system

The easiest way to catch leakage is to trace one commercially meaningful song from origin to payment.

Start with a song that checks three boxes:

It generated meaningful activity
It has known ownership data
It appeared across multiple platforms or territories

Then test it in sequence.

Confirm the contract rate. What should the payor owe for this use?
Pull source activity. Distributor exports, DSP statements, society reports, or any direct license support.
Match usage to the statement. Does the song appear under the right title, version, and identifier?
Recalculate the payable amount. Ignore the summary line and do the math from the source.
Log every variance. Missing uses, bad deductions, split errors, territory mismatches.

That process exposes the difference between a statement problem and a data-chain problem. Sometimes the contract math is fine, but the song never got fully registered. Sometimes the registration is fine, but a territory report never flowed into the accounting system. Sometimes the accounting system got the data, but the payor coded the use outside the royalty-bearing bucket.

A short explainer is helpful before getting more technical:

What to test when the numbers feel off

Artists often get distracted by the wrong issue. They argue about rate percentages before proving completeness. Completeness comes first.

Use this checklist when a statement doesn't smell right:

Test	What to ask	Why it matters
Completeness test	Did every expected source file make it into the payable report?	Missing inputs create silent underreporting
Classification test	Was the use coded into the right royalty bucket?	Wrong buckets can suppress payment
Split test	Do ownership shares match current deal terms?	Outdated split data sends money sideways
Territory test	Are foreign earnings routed and translated consistently?	Regional reports often arrive on different schedules
Deduction test	Are reserves, fees, and offsets supported by contract language?	Unsupported deductions shrink payouts fast

Audit the chain, not just the rate. In modern streaming, missing visibility is often the real leak.

One more practical note. If a team is reviewing both sound recording and publishing income, it shouldn't expect the two sides to mirror each other perfectly. They move through different systems. But they should tell a coherent story. If the recording side shows obvious activity and the publishing side looks oddly thin, that gap deserves attention.

Tools can help surface those patterns before a full formal audit. For example, Mogul centralizes catalog and earnings data across distributors, labels, PROs, and other royalty systems, then flags missing registrations, mismatched splits, and possible gaps in royalty flow. That kind of monitoring doesn't replace audit rights. It helps decide where to point them.

Found a Problem How to Escalate and Recover Your Money

Finding a discrepancy doesn't mean sending a furious message at midnight. That move feels satisfying for five minutes and usually makes the process slower.

A better approach is boring, documented, and hard to argue with. A formal workflow typically moves from desk review and records request to detailed testing and confirmation with the auditee before findings are issued, as outlined in this royalty audit workflow breakdown. That structure matters because recovery depends on proof, not volume.

Lead with evidence not emotion

Assume a realistic situation. A manager reviews statements for a catalog single and notices the reported earnings don't line up with source activity from the distributor and collection-side reporting. The team recalculates, flags several line items, and sees that some uses may not have been included correctly.

The first communication shouldn't accuse anyone of theft. It should ask for clarification in a way that corners the facts, not the relationship.

A strong first email usually includes:

The affected periods: so nobody can hide behind “please clarify” replies.
The specific works or releases: title, version, and identifiers if available.
The discrepancy type: missing usage, unsupported deduction, split mismatch, classification issue.
The backup request: source schedules, accounting extracts, and explanation of treatment.

“The numbers don't reconcile. Please walk the team through the source support for these entries.”

That tone works because it sounds like a serious business review. Not a tantrum.

A practical escalation path

If the first round doesn't fix the issue, the team should escalate in layers.

Informal clarification. Start with royalty accounting or business affairs.
Written discrepancy summary. Send a clean memo with exhibits and recalculations.
Formal notice under the contract. Use the audit clause properly.
Specialist support. Bring in a music-focused auditor, royalty analyst, or counsel.
Settlement discussion. Push for payment correction and process fixes.
Dispute proceedings if required. Mediation, arbitration, or litigation only when the economics justify it.

For teams that need help organizing records, correspondence, and supporting schedules before counsel gets involved, it can be useful to Hire Legal assistants to manage document flow and timeline control. That's especially helpful when the issue isn't one bad statement but a stack of periods, amendments, and follow-up requests that need to stay organized.

Artists should also separate unpaid current royalties from money that may be sitting elsewhere because rights weren't claimed correctly. A discrepancy review can overlap with recovery work, but it isn't the same thing. This guide on how to collect unclaimed music royalties is useful when the issue turns out to be missing registrations or uncollected income outside the payor's own statement process.

A solid resolution isn't just a one-time payment. It also includes corrected reporting logic going forward. If the payor fixes a classification rule, updates splits, or starts attaching better support schedules, that may matter almost as much as the recovery itself.

Common Pitfalls That Cost Artists a Fortune

Most lost money doesn't come from one dramatic scam. It comes from lazy process. That's why bad royalty audit procedures usually fail before the audit even starts.

Trusting summaries instead of source data

Moss Adams points to incomplete source data and contract ambiguity as the main technical failure points in royalty audits, and notes that underreporting often appears only after recalculating royalties from the licensee's underlying accounting system extracts, according to Moss Adams on royalty audit risks. That's the core lesson.

Artists lose money when they accept high-level summaries as if they were evidence. A PDF statement is an output. It is not proof that every royalty-bearing event made it into the calculation.

The fix is simple. Ask for raw support. Then tie it back to the accounting records.

Letting fuzzy contract language slide

Undefined terms wreck recovery. “Net receipts.” “Applicable deductions.” “Third-party fees.” “Other income.” Those phrases sound harmless until somebody uses them to shrink the payable base.

When a clause is vague, the payor usually has the operational advantage because it controls the reporting system. That's why teams should mark every ambiguous term before they start recalculating. Otherwise they'll spend hours proving arithmetic and miss the fight, which is interpretation.

A practical rule works well here:

If a deduction appears often, define it.
If a revenue stream is material, name it.
If a sub-licensee or distributor is involved, require reporting detail.

Treating small discrepancies like they do not matter

Tiny errors become expensive because they repeat. A bad split on one release version can spread across every period. A territory mapping mistake can suppress income every time that market reports. A missing writer registration can send publishing money into limbo for far too long.

The dangerous phrase is “it's only a little off.” That's how people ignore patterns.

The other killer is delay. Audit rights and claim windows don't stay open forever. Teams that wait until a relationship sours often discover that the practical ability to challenge older periods is already shrinking. Smart operators review early, preserve records, and act while the paper trail still exists.

Conclusion Make Royalty Audits Part of Your Business

The old model says a royalty audit is a special event. A stressful one. A legal one. Something to do only when the relationship is already damaged.

That model doesn't fit the modern music business. Today, income arrives through too many disconnected systems for passive trust to be enough. The sharper approach is to treat royalty audit procedures as part of routine financial hygiene. Not paranoia. Not drama. Just competent management.

Use reviews for small issues and audits for bigger ones

Not every problem needs a full formal audit. Some issues are better handled through a structured internal review first.

A simple split works well:

Situation	Better move
One-off statement oddity with available backup	Internal review and clarification request
Missing registration or unmatched work issue	Rights cleanup and collection follow-up
Repeated discrepancies across periods	Deeper forensic review
High-value deal with weak transparency	Formal audit under the contract
Contract interpretation dispute with money attached	Auditor and counsel together

That framework keeps teams from overreacting to noise and underreacting to real leakage.

Continuous monitoring is the real upgrade

The strongest shift in the business is away from occasional spreadsheet panic and toward continuous monitoring. That means watching catalogs as new releases go live, checking whether registrations match current ownership data, and comparing incoming earnings across systems instead of waiting years to ask hard questions.

That's especially important for independent teams. They don't have the budget to audit every partner every cycle. They need early warning signals. Missing registrations. Mismatched splits. Territory conflicts. Gaps between expected activity and reported earnings. Those signals help decide whether a lightweight review is enough or whether the deal needs formal escalation.

The artists who keep more of their money usually aren't the loudest. They're the most organized. They know which contracts matter, which data they need, and when to press for source support. They don't confuse politeness with passivity. They run their catalogs like assets.

This point is essential. Good music deserves good accounting. And if the accounting can't stand up to inspection, the statement was never worth trusting in the first place.

Mogul gives artists, managers, and rights teams one place to track catalog, registrations, and earnings across distributors, labels, PROs, and other royalty systems. For teams that want ongoing visibility instead of occasional fire drills, Mogul helps surface missing registrations, mismatched splits, and possible royalty gaps before they turn into bigger payment problems.