How to prepare a royalty statement for your licensor
A royalty statement is the periodic remittance document a licensee submits to a licensor, reporting the period's licensed sales, the royalty calculation, and the amount due. Most published guidance on royalty statements is written for licensors checking statements they receive; this guide is the licensee side — the team actually preparing the document. It walks the six steps from contract clause to archived submission, in the order that avoids rework.
Before anything: read the reporting clause
Every licensing agreement contains a reporting clause specifying what the licensee must report, at what cadence (monthly or quarterly are typical in apparel), in what format, by what due date, and with what level of detail — per SKU, per product category, per territory, per channel. Statements get rejected for missing contractually required detail far more often than for math errors.
Pull the clause for each licensor and turn it into a per-licensor reporting requirements sheet: due date, cadence, required line items, required granularity, submission method (portal, email, specific workbook format), and any certification language an officer has to sign. A 12-licensor portfolio will have 12 meaningfully different answers. This sheet is the spec for everything below.
Step 1 — Assemble sales data with licensor attribution
Gather the period's sales for every channel — DTC ecommerce, wholesale, marketplaces, retail — with each row attributed to the licensor (or licensors, for cooperative marks) whose product it represents. Attribution is the step that breaks: a sales export missing the licensor field, a new SKU set up without license mapping, a channel feed that lags the period close.
The discipline that prevents downstream rework: attribute at the SKU level in the product master, once, when the SKU is created — not per period in the reporting workbook. If a SKU's attribution is decided at reporting time, it will be decided inconsistently across periods, and inconsistent attribution is precisely what audit sampling is designed to catch.
Returns belong in this step too, attributed to their original-sale period. A return posting this period against a sale from three periods ago is a true-up against that prior period, not a reduction of this period's gross.
Step 2 — Compute net sales
Apply only the deductions the agreement explicitly allows — typically returns, specified trade allowances, freight, and sales tax. Each licensor's allowed-deduction list differs, and the same deduction can be allowed under one agreement and prohibited under another in the same portfolio.
Keep each deduction as its own labeled line with period-level support behind it. Licensors and their audit firms scrutinize deductions harder than any other statement element, because deduction overreach is the most common and most defensible-sounding way statements understate royalties. A deductions block that ties to support is the difference between an audit question and an audit finding.
Step 3 — Apply the rate card
Apply each licensor's current effective rates — per product category, channel, and territory as the agreement defines them — to the period's net sales. Before calculating, verify the rate card reflects every executed amendment. A rate change negotiated mid-term that never propagated to the calculation workbook (stale-master drift) silently corrupts every statement from the amendment's effective date forward.
For cooperative marks, run the calculation once per rights holder: the same net sales base feeds each agreement's rate independently, producing separate royalty amounts for separate statements. Nothing nets between them.
Step 4 — Apply advance recoupment and MG position
If an advance is outstanding, the period's earned royalty amortizes against the balance before cash is due. The statement still reports the full earned royalty, the recoupment applied, the remaining advance balance, and the resulting net due — even when net due is zero. Reporting nothing during recoupment periods is a common first-year licensee mistake and reads to the licensor as a missed statement.
Track the minimum guarantee position alongside: cumulative earned royalties for the MG period against the guarantee. The statement format may not require the MG position every period, but projecting it monthly means a shortfall is a budgeted settlement payment rather than a year-end surprise.
Step 5 — Format per the licensor's template
Each licensor expects its own statement layout — its line-item structure, its category groupings, its file format, its portal. CLC-style collegiate statements, league statements, and golf-property statements share almost no formatting. Submitting a correct calculation in the wrong format earns a rejection and a resubmission cycle that eats the close calendar.
Maintain one statement template per licensor, versioned, matched to the current reporting requirements sheet from the pre-step. When a licensor revises its template — which happens routinely — version the change rather than editing in place, so prior periods remain reproducible in the format they were actually submitted in.
Step 6 — Tie out, submit, archive
Before submission, tie the statement out three ways: statement totals to the calculation workbook, calculation inputs to the source sales data, and the period's figures to the prior period for reasonableness (volume shifts, rate changes, deduction percentage drift). Anomalies caught here cost minutes; the same anomalies caught by the licensor cost credibility.
Then archive the statement exactly as submitted — the file itself, not a reconstruction — together with the sales data, rate card version, and calculation behind it. Licensor audits routinely reach back two to three years, and the audit-defense standard is reproducing the original statement and its full derivation on request. An archive that can do that turns an audit into document production; one that cannot turns it into a forensic rebuild.
The most common statement rejections
Four defects account for most licensor pushback: missing required granularity (the clause says per-SKU, the statement says per-category); unauthorized deductions netted into the royalty base; missing recoupment detail during advance periods; and format drift — a statement template that accumulated edits until it no longer matches what the licensor's system ingests.
All four are process defects, not math defects, which is why they recur period after period in spreadsheet workflows. Royalty Reporting generates statements from the same structured calculation data per licensor template — granularity, deduction rules, recoupment detail, and format come from the agreement's structured terms, so the statement matches the clause because both derive from the same source.