Skip to main content
Royalty Reporting
Guide · 8 min read

Common royalty audit findings (and how to avoid them)

A royalty audit finding is a discrepancy a licensor's audit firm identifies between what a licensee reported and what the agreement required — and findings are the norm, not the exception. Published royalty-audit studies report that 80–90% of licensees misreport royalties in some form, with underpayments averaging 10–25% of what was owed. Almost none of it is fraud. It is process: stale rates, deduction overreach, attribution gaps, and spreadsheet drift compounding quietly until an audit prices them all at once. This guide covers the six findings that dominate apparel-licensing audits and the process design that prevents each.

Why findings are the norm

Royalty reporting is self-reporting: the licensee computes what it owes and the licensor periodically verifies. Audit clauses exist because the verification gap is real — and the published numbers say the gap is wide. Studies from royalty-audit practices consistently report that 80–90% of audited licensees misreported in some form, with underpayments running 10–25% on average.

The economics make findings expensive beyond the back-payment itself. Most agreements charge interest on underpayments, and most shift the audit's cost to the licensee when the underpayment exceeds a threshold — commonly 3–5% of royalties owed for the audited period. A finding that crosses the threshold turns a verification exercise the licensor paid for into an invoice the licensee pays.

The pattern across every finding below: none requires bad faith, all compound monthly until discovered, and all are preventable with structure rather than vigilance.

Finding 1 — the wrong rate (stale-master drift)

The most quietly expensive finding: a rate change from an amendment, renewal, or scheduled step-up that never propagated to the calculation workbook. Every unit since the effective date mis-rated, every statement since technically wrong, exposure compounding monthly. Auditors find it fast because checking applied rates against executed contract documents is the first procedure in any royalty audit program.

Prevention is structural, not procedural: rates need to live in one versioned, effective-dated source that calculations read from automatically — not in lookup tabs copied between period workbooks. When the rate card is structured data, an amendment is one update with an effective date; when it is a spreadsheet tab, it is a manual propagation task that will eventually be missed.

Finding 2 — deduction overreach

Licensees routinely net costs out of the royalty base that the agreement never authorized: markdown subsidies, co-op advertising, warehousing, bundling discounts allocated against licensed product. Each feels commercially reasonable — which is why it survives internal review and fails external audit. The agreement's allowed-deduction list, not commercial intuition, defines the royalty base.

Auditors test deductions by recomputing the base from gross and challenging every netting line against the contract language. Prevention: every deduction line maps to a specific clause, carries period-level support, and anything not explicitly allowed is not deducted. Where the contract language is genuinely ambiguous, raise it with the licensor before relying on it — a documented interpretation beats a discovered one.

Finding 3 — unapproved product, channel, or territory

Licensors verify more than math. Audit programs check that reported units trace to approved products made by approved factories, sold in granted channels and territories. A SKU that skipped product approval, an off-price channel the agreement excludes, or DTC orders shipped into a territory licensed to someone else all surface as findings — sometimes priced at the full sale, not the royalty.

In apparel portfolios this is frequently a master-data failure rather than a rights failure: the rights exist, but the product master cannot demonstrate which SKUs map to which approvals and which territories. Prevention is carrying license scope — approved product, channel rights, territory — as structured attributes on the SKU from setup, so out-of-scope sales are blocked or flagged at the transaction, not reconstructed at audit.

Finding 4 — cooperative-mark misses

A product carrying two rights holders' marks owes two royalties, and audits regularly find units reported to one licensor and not the other — typically because the SKU was attributed to a single license at setup. League-plus-players-association product is the canonical apparel case.

The exposure runs in both directions: the unpaid rights holder is owed back-royalties with interest, and the audit that finds it is usually that rights holder's. Prevention mirrors finding 3: attribution must support multiple licenses per SKU as first-class data, with every calculation fanning out to every agreement the unit touches.

Findings 5 and 6 — MG, advance, and true-up attribution

Minimum-guarantee and advance findings cluster around interaction mistakes: treating an advance as satisfying the MG when the contract holds them as separate obligations, missing a shortfall settlement, or letting cumulative recoupment math drift across period workbooks until the balance is simply wrong.

True-up findings are attribution mistakes: returns and corrections lumped into the period they were discovered instead of attributed to the original-sale period. The total royalty may even be right, but the per-period history is corrupted — MG satisfaction by year becomes unverifiable, and auditors write up what they cannot verify.

Both share one prevention: per-period attribution preserved at the calculation level, with prior statements immutable and adjustments carrying explicit tie-back to the periods they amend. That is an architecture property, not a diligence property — spreadsheets do not preserve attribution under pressure, period after period, across staff turnover.

Making the audit boring

The goal of audit preparation is not winning arguments; it is having nothing arguable. That means: rates applied from versioned effective-dated rate cards, deductions mapped to clauses with support, license scope enforced at the SKU, every unit's calculation reproducible, and every adjustment attributed to its originating period — continuously, as the work happens, not assembled in the three weeks after a notice arrives.

This is the operating premise of Royalty Reporting: an immutable audit trail at every calculation, versioned rate cards, structured license scope, and per-period attribution as defaults rather than disciplines. Licensees running that structure answer audit requests with document production. The published 80–90% error rate describes the workflows licensors audit most profitably — the way out is not auditing yourself harder, it is removing the structure that produces the findings.

Want to see how this works in the platform?

Walk through royalty calculation, statement generation, advance recoupment, and audit trail in a 30-minute demo.