Royalty audit defense checklist
Most apparel licensees with major-licensor agreements will face a royalty audit at some point. CLC, Fanatics College, NFL Properties, MLB Properties, and event licensors all routinely audit licensees on a 1–3 year cycle. The audit team requests historical royalty calculations, supporting sales data, applied deductions, advance amortization, and statement versions. A clean audit defense depends on what the licensee can produce — fast and consistently.
What licensor audit firms actually ask for
Royalty audit firms — typically engaged by the licensor, often the same firms repeatedly used for that licensor — request a standard package: every royalty calculation for the audit period at the school/team/product-category level, every statement version sent to the licensor, the rate-card history showing what rate applied to what period, and supporting sales data reconciled to the calculations.
They also ask about specific deductions — which deductions were applied, what contractual basis, and whether they exceeded any agreed caps. And they ask about advance recoupment — the amortization history showing how advances were applied against earned royalties.
The three most common audit findings
First — stale-master drift. A rate changed mid-term, the change updated one workbook but not another, and the licensee reported at the old rate for some period. Audit firms catch this by reconciling the rate-card version history against the actual rates applied in calculations.
Second — disallowed deductions. The licensing agreement specifies what deductions are permitted; deductions outside that list (or exceeding caps within it) are pulled back. Audit firms catch this by reviewing the deduction history against contract terms.
Third — missed cooperative-mark splits. A product that should have reported royalties to multiple licensors only reported to one. Audit firms catch this through SKU-level analysis showing mark types that triggered cooperative rights.
What the licensee's finance team should produce
Recompute history at the calculation level. For every period, the audit needs to see what was originally reported, every recompute, and the current state. If the audit covers 2 years and the licensee can only produce current-state data, the audit team will assume worst-case for the original reports.
Original statement versions per period. The audit team wants to compare what was reported to the licensor at the time against the current data. If statements have been rebuilt or rewritten, this comparison breaks down.
Rate-card version history per agreement. Every rate that applied in the audit window, with effective dates. This is the defense against stale-master drift allegations.
Per-period sales reconciliation. The audit firm will sample SKUs and verify they reconcile from POS or ecommerce data through to the royalty calculation. Gaps here trigger expanded scope.
Why spreadsheet workflows fail audits more often
Spreadsheet workflows fail audit defense not because the math is wrong, but because the audit trail is fragmented. Statement versions are saved-as-of-then in a SharePoint folder that doesn't always survive personnel turnover. Recompute history lives in tracked changes that someone may have accepted-all. Rate-card version history is typically not preserved at all — current-state-only.
Structured-data royalty platforms preserve all of this automatically. The same underlying data that drove the calculation at the time drives the audit-response export now. The defense is structurally easier — not because the calculation is more accurate, but because the documentation is intact.