What is a royalty report? The anatomy of the document a licensee submits to a licensor

A royalty report is a document with one job: to be tested

A license agreement imposes two duties on the licensee. The first is to pay a royalty on the sales of product carrying the licensed marks. The second is to prove, every period, that the royalty paid is the royalty the agreement produced. The royalty report is the instrument of the second duty. It is not the calculation — the calculation happens in the licensee's systems, workbooks or platform — and it is not the payment, which moves through a bank. It is the evidence the licensor is contractually entitled to receive without asking, laid out so the licensor can re-perform the arithmetic, test the scope and compare the period with the ones before it.

That purpose decides the shape. A document built to be tested carries its inputs, not just its outputs: the gross sales behind the net, the deductions behind the gross-to-net step, the rate behind the royalty, the opening balance behind the closing one. Where a licensee's internal management report would show a royalty expense figure and move on, the royalty report shows the derivation, because a derivation is the only thing a reader on the other side of the agreement can check. Every section described in this guide exists to make one step of that derivation visible.

The second thing the purpose decides is who defines the layout. The licensee owns the numbers; the licensor owns the template. The reporting clause of the agreement — and, behind it, the licensor's current template or portal specification — says what the report contains, at what granularity, in what order, by what date and through which channel. A licensee reporting to twelve licensors produces twelve differently shaped documents from one set of sales data, and the shape is not the licensee's to simplify. A report that collapses style-level detail into category totals because the totals are easier to produce is incomplete under a clause that asks for styles, whatever its arithmetic says.

Three neighbouring guides on this site touch the same document from other angles, and it is worth being exact about the boundary. How to read a royalty report is the licensor's side: the three passes a reader runs, the ratios, the red flags and a quarterly report reviewed line by line. How to prepare a royalty statement is the licensee's workflow: the six steps from the reporting clause to an archived submission. What is royalty reporting is the obligation and the period cycle as a whole — base, rate structures, cycle, controls and failure modes. This guide stays with the artefact. It answers what a royalty report is, what is in it, what each field has to tie to, and what a well-built one looks like, so that whichever seat you sit in, the document on the desk is recognisable section by section.

What a royalty report is not

Three other documents borrow the name, and each is a different object. The first is the licensee's own management report on royalties — royalty expense by licensor, by property, by period, against budget. It is built for the licensee's leadership, it nets and aggregates freely, and nothing on it is owed to anyone outside the company. It is a useful document and it is not a royalty report, because it is not organised around any one agreement's terms and no licensor will ever test it.

The second is the licensor's compiled royalty report — the document a licensor's licensing or finance team produces for its own purposes from the reports its licensees submit: royalty income by licensee, by property, by territory, against guarantees. The phrase runs in that direction too, and the guide on how to analyze royalty performance, linked at the end, is written for the reader building that view. It is downstream of the licensee's report, built for a different reader, and shaped by the licensor's portfolio rather than by any single agreement. On this site, royalty report means the licensee's submission unless stated otherwise.

The third is the sales report — the extract from the licensee's order-to-cash system that the royalty report is built from. A sales report is organised by the licensee's own hierarchy, nets by the licensee's own accounting policy, and knows nothing about which styles carry which marks, which deductions an agreement permits, or what the rate card says. It is an input. A licensee that sends a licensor its sales report with a royalty column appended has sent a document that cannot be tested against the agreement, because none of the agreement's structure is in it.

The distinction matters for a practical reason: each of the three is easier to produce than the royalty report, and each is a plausible substitute until someone tests it. The royalty report is the one document in the set whose structure comes from the agreement rather than from the licensee's systems — which is why it has to be prepared, section by section, rather than exported.

Report, statement, remittance advice and invoice: four documents, four jobs

Four documents move between a licensee and a licensor around each reporting period, and they are named loosely enough in practice that the words are worth pinning down before the anatomy. The glossary entries on the royalty report and the royalty statement, linked at the end, define the first two; this section sets all four side by side.

The royalty report is the full periodic submission: the statement that declares what is owed, plus the sales detail and supporting schedules the agreement requires so the licensor can test it, plus the officer's certification. The royalty statement is the summary inside it — gross sales, deductions, net sales, rate, royalty amount, advance and guarantee position, adjustments and net due, in the licensor's format. In conversation the two words name the same submission, and nothing rides on the difference until a portal asks for both files or an auditor asks for the detail behind a total. On this site, royalty report means the licensee's submission and includes the statement.

A remittance advice is a payment document, not a royalty document. It travels with the cash, or arrives from the licensee's accounts payable system when the payment is released, and it tells the licensor's receivables team what the money is for: the agreement, the period, the statement the payment settles, the amount, the currency, the value date, the bank reference, and any withholding tax deducted at source with the certificate that supports it. A remittance advice that does not name the statement it settles is the reason a licensor's ledger shows unapplied cash against a licensee whose report was accepted weeks earlier.

An invoice runs the other way. The royalty itself is self-assessed — the licensee declares and pays it on the strength of its own report — so under a self-assessed structure no invoice precedes the royalty payment at all. Invoices arise for the amounts the report does not self-assess: a minimum guarantee shortfall measured at a contract-year boundary, an advance tranche falling due on a date the agreement names, an audit settlement, interest on a late payment, or a marketing fund minimum. Whether the licensor must also issue a tax invoice for the royalty itself is a question of the tax rules that apply to the parties and of the agreement's own clause, not a question the report answers. The practical point for the preparer is that an invoice from the licensor is a signal that something outside the ordinary period mechanics has matured, and the report for that period should show the position that produced it.

The table below puts the four documents beside each other. Where a licensor's template folds two of them together — a statement page that doubles as the remittance advice, or a portal that generates the invoice from the statement the licensee uploads — the jobs are still distinct, and the fields still have to be present.

Anatomy, part 1: the header, the period and the agreement reference

The header is the smallest section of the report and the one that fails most quietly, because nothing in it is arithmetic. It identifies which agreement the figures belong to, which period they cover, which currency they are stated in, and which version of the report this is. Each of those is a field a reader will test before reading a single sales line, and each has a record on the licensee's side it must match.

The agreement reference is the licensor's identifier for the contract — an agreement number, a license number, a property and licensee code — not the licensee's internal vendor number or the name of the property. A licensee holding two agreements with the same licensor, say apparel and headwear with separate rate cards, needs two references and two reports, because the terms differ and a combined report cannot be tested against either agreement. Where the agreement has been amended, the reference should carry or imply the amendment in force, since the rates and deductions on the body of the report are only correct relative to a dated version of the terms.

The reporting period is the agreement's period, not the licensee's fiscal month or quarter. An apparel licensee closing its books on a 4-5-4 retail calendar and reporting to a licensor that measures calendar quarters has two different period boundaries, and the report has to carry the agreement's. The header states the period start and end dates and the cutoff rule the agreement applies — ship date or invoice date — because the same shipment can fall inside one period under one rule and the next under the other. The glossary entry on the reporting period, linked at the end, covers the cutoff question; for the header, the requirement is that the dates are the contract's and are stated.

The contract year position sits beside the period: which contract year this period falls in, and which period of that year it is. The contract year is the measurement window for the minimum guarantee, for cumulative rate tiers, for gratis and deduction caps measured annually, and for the annual reporting and audit rights — and it runs from the agreement's effective date or a date the agreement names, not from January or from the licensee's fiscal year start. A header that says "Q3" without saying which contract year and which year-start it belongs to cannot be rolled forward or checked against the guarantee.

The contract currency is the currency the royalty is owed in, which the agreement names. Sales may have settled in several currencies; the header states the one the report is denominated in, and the currency section lower down shows how the others were converted into it. A report that is silent on currency is read in whichever currency the reader assumes, which is the licensor's.

Finally the report carries a version and preparation date: the date the report was produced, and whether it is the original submission for the period or a resubmission after a rejection or correction. A resubmission replaces the original as the document of record for the period, which is why the original has to be archived as submitted rather than overwritten — the payment was made against it, and an auditor years later will compare the two. Where a licensor's portal assigns its own submission identifier, that identifier belongs in the licensee's archive next to the file.

Anatomy, part 2: sales detail by SKU, category, territory and channel

The sales detail is the foundation of the report, because every other section derives from it. It lists the period's royalty-bearing sales at the granularity the reporting clause requires — style, style-color or SKU; product category as the agreement defines categories; territory; channel; and, where the licensor asks for it, the customer or retail account — with units and gross invoiced value for each line. Granularity is set by the licensor's template, not by what the licensee finds convenient to export, and a report that aggregates above the required level is incomplete even when its totals are right.

Each dimension on a detail line exists because the agreement prices or restricts on it. The product identifier ties the line to a style the licensor approved, which is how the reader tests that everything sold was inside the grant. The category ties the line to a rate, because category-specific rates are one of the structures licensed-apparel agreements use — headwear, fleece, tees, performance, outerwear and accessories can each carry their own percentage — and a style mapped to the wrong category reports at the wrong rate without any other error. The territory ties the line to the granted geography and, under agreements that price by territory, to a rate. The channel — wholesale, direct-to-consumer, marketplace, off-price, closeout, event — ties the line to a channel rate where one exists and to a channel restriction where one applies, since a closeout channel can be restricted rather than merely rated.

The mark matters too. In pro-sports and collegiate programs a single agreement can price by the mark the product carries — team mark, league mark, event mark, player mark, throwback — so mark type is a required attribute on the style record and, where the template asks for it, on the detail line. A cooperative mark, a style carrying rights from two licensors, appears on two reports with the split the contracts prescribe, and the detail line on each should make the split visible so neither licensor sees a unit it was not told about.

Units are not decoration. Where the agreement carries a per-unit royalty or a per-unit floor, the unit count is the base and cannot be recovered from dollars. Where it does not, units still let the reader compute an average selling price per line and compare it with the prior period and with what the licensor sees at retail — a line whose price per unit has fallen sharply without a channel change is a line worth a query. Units are stated net of returned units only where the template says so; otherwise gross units with returns shown separately, so the two can be reconciled to shipments and credits independently.

Three records on the licensee's side anchor the sales detail. The invoice register for the period, filtered to the licensed styles, is what gross invoiced value must sum to. The product master, with each style's licensor, property, category and mark attribution set when the style was created, is what the identifiers and categories must agree with. And the total sales of licensed product for the period — including the lines excluded as out of scope — is what the report must reconcile to, with every exclusion explained. Under-reporting hides in the sales that never reached the report, and only a reconciliation from total licensed-product sales down to reported royalty-bearing sales exposes a style that shipped without its mark attribution.

Gratis units — samples, seeding, employee product, donations — belong in the sales detail or in their own schedule depending on the template, but they belong somewhere. Agreements address them explicitly: exempt up to a cap expressed as a percentage of units sold or a fixed annual quantity, or reported at a deemed value such as cost or a fraction of wholesale. The report shows the gratis units against the cap and the deemed value where one applies, because a licensee that leaves gratis units off the report entirely has reported fewer units carrying the mark than it shipped, and an auditor comparing shipments to the report will find the gap.

Anatomy, part 3: gross-to-net deductions and their caps

The deductions section is where the report turns gross sales into the royalty base, and it is the section an auditor has most reason to read first, because deduction overreach is the defensible-sounding way a report understates royalty: every line looks like ordinary accounting until the clause is read. The dedicated guide on gross-to-net deductions, linked at the end, works the stack line by line. What the report has to show is simpler to state than to produce: each deduction type on its own line, the amount claimed, the cap as the clause measures it, and the amount allowed.

The deduction types are the agreement's, enumerated in its definition of net sales and nowhere else. An agreement may permit returns and credits, trade and volume discounts, markdown allowances and chargebacks, outbound freight, and sales tax or VAT; it may permit some of those and not others; it may attach conditions — returns only as actual credits issued rather than a reserve, freight only where separately stated on the invoice, allowances only where documented. A deduction type the agreement does not name does not appear on the report, however reasonable it looks on the licensee's own income statement. Where the licensee's accounting view of net revenue includes deductions the agreement excludes, the report shows the difference rather than hiding it: the excluded amounts stay in the base.

Caps are measured as the clause measures them, and the report shows the measurement. A cap expressed as a percentage of gross sales per category per period is tested per category per period, not in aggregate across the report, because an aggregate test lets an over-cap category hide behind an under-cap one. The report shows, for each capped type, the amount claimed, the cap base and percentage, the cap amount, and the amount allowed — so a reader can see $74,000 claimed, a 4% cap on $1,480,000 of gross giving $59,200, and $59,200 allowed, with $14,800 left in the base. The worked example later in this guide uses exactly those figures.

Returns need their own discipline inside the deductions section. A return credited this period against a sale made this period reduces this period's gross-to-net. A return credited this period against a sale made in an earlier period is a prior-period adjustment: it reverses royalty at the earlier period's rate and is shown in the adjustments section, not netted into the current period's returns line. Mixing the two produces a report in which units and dollars stop explaining each other, and a reader comparing the returns ratio with history will see a spike that is really a timing artefact. The guide on apparel returns and royalty true-ups, linked at the end, works the attribution.

The records that anchor this section are the credit memo register for returns, the deduction and chargeback detail by reason code for allowances and discounts, the freight lines on the invoices for freight, and the tax lines for sales tax. Each deduction on the report should reduce to source documents at transaction level; a period-end journal entry is evidence that someone computed a deduction, not evidence of the deduction. An account-level allowance granted to a retail customer across licensed and unlicensed product has to be allocated between the two before any of it reaches the report, and the allocation method has to be stated and consistent from period to period.

Net sales is the result: gross sales less allowed deductions, line by line and in total. Net sales means only what the agreement says it means, so the figure on this report is not the figure on the report to the next licensor for the same shipments, and it is not the net revenue figure in the licensee's general ledger. The guide on tying royalty-reported net sales to the general ledger, linked at the end, builds the bridge between the two; the report's job is to show its own side of that bridge clearly enough that the bridge can be built.

Anatomy, part 4: rate application, including tiered rates

The rate section applies the agreement's rate structure to the base, and the report shows the application rather than just the result: the rate on each line, the base it was applied to, and the royalty it produced, with every structure the agreement uses made visible. The dedicated guide on royalty rates in licensed apparel, linked at the end, covers what moves a rate and the orientation ranges by category; this guide does not restate those bands. What belongs here is the shape the rate takes on the document.

A flat rate is one percentage on every line, and the report shows it once per line. Category, channel, territory and mark-type rates differ by line, so each detail line carries its own rate and the reader can see which rate resolved for which combination. Per-unit terms carry a unit count and a per-unit amount on the line; mixed structures — the greater of a percentage and a per-unit floor — show both computations and the one that governed. A rate is a property of the agreement on a date, so where an amendment changed a rate mid-period the report splits the line at the effective date and shows both rates, rather than applying the current rate to the whole period or the old rate to sales the amendment already repriced.

Tiered rates need the most room on the page, because a tier cannot be tested from a single period's figures. A tiered rate changes as cumulative volume within a measurement period crosses breakpoints the agreement states — on net sales, gross sales or units — and is applied incrementally, each rate only to the volume inside its own band, or retroactively, the rate of the highest band reached to all of the period's volume. The glossary entry on the tiered royalty rate, linked at the end, works both readings. For the report, a tiered rate means four fields the flat-rate report does not need: the cumulative volume entering the period, the breakpoints, the volume allocated to each band this period, and the rate and royalty for each band. Under a retroactive tier, a crossing period also carries a true-up line repricing earlier periods in the measurement window.

The cumulative figure is a rolling balance, and it rolls from the prior report. The volume entering this period must equal the volume the prior report closed on, adjusted for any prior-period returns credited since — a return against an earlier period pulls cumulative volume back and can widen a lower band or reverse a crossing. A report whose opening cumulative figure does not equal the prior report's closing figure has a finding before the reader reaches the arithmetic.

Earned royalty for the period is the sum of the line royalties plus any tier true-up, before anything to do with guarantees or advances. It is shown in full. The record it anchors to on the licensee's side is the rate card in force on each sale date — every version of it, with effective dates — and the calculation detail that resolved each line to its rate. A licensee that cannot produce the rate card version a two-year-old report was computed against cannot defend that report's rate section.

Anatomy, part 5: minimum guarantee and advance recoupment

Two instruments sit on top of earned royalty and change what is paid without changing what is earned. The report shows both positions every period, in full, even when the result is that nothing is payable. The guide on minimum guarantee versus royalty advance, linked at the end, works the three interaction patterns on one set of numbers; here the question is which fields the report carries and what they roll from.

A minimum guarantee is a floor for a measurement period — a quarter, a contract year or the term. The report shows the guarantee amount, the measurement period, cumulative earned royalty for that period to date, and the gap: how much remains to be earned before the floor is cleared, or how far above it the licensee sits. Where the agreement measures the guarantee at the contract-year end, a quarterly report still shows the position, because a shortfall that is visible at the third quarter is a budgeted settlement and one discovered at the licensor's invoice is not. Where a guarantee is paid in advance — the structure in which the two instruments meet — the report shows the prepaid amount and the unrecouped balance exactly as it would an advance, and states that a balance left unrecouped at the measurement boundary is retained by the licensor rather than refunded.

A royalty advance is a prepayment against royalties not yet earned. The report shows the advance paid and its date or tranche schedule, the opening unrecouped balance, the recoupment taken this period, the closing unrecouped balance, and whether the earn-out point has been reached. Recoupment is the lesser of the period's earned royalty and the opening balance; what is left of earned royalty after recoupment is the cash royalty for the period. Reporting zero earned royalty because zero cash is due is the single most damaging simplification a report can make, because it removes the figure the guarantee is measured against and the figure the next period's rolling balance depends on.

The interaction terms are contract terms and the report should state the ones it applied: whether advance payments count toward the guarantee, whether a shortfall is reduced by an unrecouped balance or owed on top of it, whether properties, categories or contract years are cross-collateralized so one basket's excess absorbs another's shortfall. The guide on cross-collateralization, linked at the end, works the multi-property case. A report that applies an interaction rule without stating it is asking the reader to guess which clause it read.

Both positions are rolling balances and anchor to the prior report and to the agreement: the opening balances must equal the prior closing balances, the guarantee and advance amounts must equal the agreement's, and the cumulative earned royalty must equal the sum of earned royalty on every report in the measurement period, adjustments included. On the licensee's books the advance anchors to the prepaid-royalty asset and its amortisation schedule; the guarantee position anchors to the shortfall accrual, where one is being built. The guide on royalty accounting and revenue recognition, linked at the end, covers the balances; the report's job is to show the movement that the balances record.

Anatomy, part 6: adjustments, prior-period true-ups, returns and reserves

The adjustments section is where the report corrects history without rewriting it. Returns credited after their original sale period, corrections found after submission, rate true-ups from amendments with retroactive effect, repricing under a retroactive tier, audit settlements and the reversal of a reserve all land here — as separately attributed lines, each pointing at the period it belongs to, priced at the rate in force in that period, with the reason stated. A closed period is never edited; it is adjusted on the current report, because the original report is the document the payment was made against and the one an auditor will compare.

Each adjustment line carries five things: the period it corrects, the type of adjustment, the gross or unit movement, the rate applied — the original period's rate, not the current one — and the royalty effect, signed. Where an adjustment moves cumulative figures — the tier volume, the guarantee position, the advance balance — the report shows the effect on each, because a return against a prior period under a cumulative tier does not only reverse royalty at the old rate; it also moves the breakpoint for the current period. Netting adjustments into a single signed total destroys the attribution the licensor needs now and the attribution the licensee will need at audit.

Returns reserves are a different object, and the report should not confuse them with returns. A returns reserve is an estimate of future returns booked against current sales in the licensee's own accounts; a return is an actual credit issued. Whether the agreement permits a reserve as a deduction at all is a contract term, and where it does, it names the basis — a percentage of gross, capped, trued up to actuals on a stated schedule. The report then shows the reserve taken, the actuals that have since arrived against earlier reserves, and the true-up between them, so the licensor can see the reserve is a timing device and not a permanent deduction. Where the agreement permits only actual credits, no reserve appears on the report and the licensee carries the estimate on its own books alone.

The records this section anchors to are the credit memos dated in the period and referencing earlier invoices, the amendment that caused a rate true-up with its effective date, the audit settlement agreement, and the prior reports themselves. Each adjustment should be traceable to a document that explains why the earlier period was wrong, and a reader should be able to add the adjustment to the earlier report and reproduce what that report would have said had the information been available then.

Anatomy, part 7: currency

Where sales settle in a currency other than the contract currency, the report carries a currency section, and it answers three questions the guide on multi-currency royalty reporting, linked at the end, treats in depth: which currency the royalty is owed in, which rate converts the sales into it, and on which date that rate is taken. The report states the source currency and source amount of every converted line, the rate source the agreement names, the rate used, the conversion date rule — sale date, period end or payment date — and the converted amount. A report converts exactly once, at a named point, and shows the pre-conversion figure, because a reader cannot test a conversion whose input has been discarded.

Converting twice is the mechanism to design against. A commerce platform that settles in the contract currency has already converted; a royalty workbook that converts the settled figure again at a period-end rate produces a fourth plausible royalty that agrees with none of the other three. The report's currency section is where that error becomes visible, provided it carries the source amount. Withholding tax deducted at source on a cross-border payment belongs on the remittance advice and, where the agreement requires it, on the statement as a reconciling line between the royalty payable and the cash sent — never as a deduction from net sales.

Anatomy, part 8: certification

The report ends with a certification: an officer's statement that the report is complete and accurate, in the wording the agreement or the licensor's template requires, signed and dated. It is the smallest field on the document and the one with the largest consequences, because it converts a set of figures into a representation an individual has put a name to. Where the agreement names the officer's level — a chief financial officer, a controller, an authorised signatory — the signatory has to be that person, and the archive has to show who signed.

The certification is also the control point that separates preparation from approval. The person who assembled the sales detail and ran the calculation should not be the person certifying it; the certifier is attesting to a review, and a review by the preparer is not a review. A certification signed on the strength of a tie-out the certifier did not see is a signature on an assertion, which is why the controls section of this guide treats the pre-certification tie-out as part of the document rather than as a step before it.

The supporting schedules: gratis, fund, per-unit, cooperative marks and sell-off

Beyond the statement and the sales detail, the reporting clause can require schedules that stand on their own because they are computed on their own base or governed by their own clause. Each is a small table with a specific job, and each is missing from a report that was exported rather than prepared. A schedule the agreement names is a required part of the report, whatever the statement total says.

The gratis schedule lists units carrying the mark that generated no sale — samples, seeding, employee product, donations — by style and reason, against the cap the agreement sets and at the deemed value where one applies. It exists because gratis units are units shipped with the mark, and a licensor reconciling shipments to the report needs to see where they went.

The marketing fund schedule shows the contribution an agreement requires on top of royalty — a percentage of net sales, a fixed amount per contract year, or a percentage with an annual minimum — computed on the base its own clause names, which need not be the royalty base, and kept out of the earned royalty the guarantee is measured against unless that clause says otherwise. When it is measured on net sales it inherits every scope and deduction decision in the royalty calculation, so a disallowed deduction understates both at once, and the schedule has to show enough of the base for the reader to see that.

The per-unit schedule carries unit counts and per-unit amounts for lines the agreement prices per piece rather than as a percentage, and for mixed structures shows the percentage computation and the per-unit floor side by side with the one that governed. It exists because a per-unit line cannot be recomputed from dollars, and because unit counts have to reconcile to shipments and returns independently of value.

The cooperative-mark schedule shows every style carrying rights from two licensors, the units and value on each, and the split each contract prescribes, so that each licensor can see the whole unit and its share of it. Without it, each licensor sees a fraction of a style with no indication that a fraction is what it is.

The sell-off schedule appears after a term ends: the inventory certificate fixing the eligible units at termination, the sell-off sales by period against that certificate, the channels used against any tightened restriction, and the units remaining. It carries the final report's weight, because the final statement is tested against the certificate rather than against ongoing production. The guide on sell-off, termination and the final royalty statement, linked at the end, covers the sequence; the schedule is the document the sequence produces.

Territory and channel schedules round the set out where the agreement prices or restricts on them: sales by granted territory, with anything outside the grant shown and explained rather than omitted, and sales by channel against any channel cap or restriction. Each schedule reconciles to the sales detail it was built from — the gratis units to issue records, the fund to the net sales on the statement, the per-unit counts to shipments and credits, the cooperative split to the detail lines, the sell-off units to the certificate — and the statement total is only as defensible as the schedules behind it.

The field table: what every field must tie to in the licensee's books

The table below collects the fields from the eight anatomy sections into one list, in the order they appear on a report, and for each one states what it must tie to in the licensee's books and which term of the agreement governs it. A field is defensible when all three columns can be produced on request — the figure, the record and the clause. A field that ties to nothing is an assertion, not a figure, and a report assembled from assertions can foot perfectly and still be unsupportable.

Use it in two directions. Forward, as a preparation checklist: before a report leaves, every row should have a record behind it. Backward, as an audit map: when a licensor's auditor asks for the support behind a line, the row says which record to produce. The template callout after the worked example links a CSV statement template that covers the statement rows of this table — gross sales, deductions by type, net sales, rate, royalty amount, advance recoupment, the guarantee position and net due — as a working structure, not a licensor-specific layout. Beyond a contract reference, a statement period and category-by-channel sales lines, the header, detail, cap, tier, adjustment, reserve, currency and certification rows above have no column in it and are the licensee's to add.

Footing, cross-footing, rounding and sign conventions

A report is a set of tables, and tables have mechanics that are independent of any agreement. The first reader on the licensor's side will foot and cross-foot the report before judging it, so the report has to be built to pass that pass. Footing means every column sums to its stated total; cross-footing means every row works across — gross less each deduction equals net, net times rate equals royalty, opening balance less recoupment equals closing. A table that foots but does not cross-foot has a rounding or formula problem on some row; a table that cross-foots but does not foot has a missing or duplicated line.

Rounding is where footing failures come from, and the convention has to be stated once and applied everywhere. Royalty is computed per line and rounded per line, so the total is the sum of rounded lines; or it is computed on unrounded lines and rounded once at the total. The two conventions produce totals that differ by cents, and a reader recomputing line by line will find the difference whichever convention the report did not use. The template or the agreement may fix the convention; where neither does, the report states which it applied and applies the same one every period, because a convention that changes between periods produces rolling balances that drift by a few cents a quarter and never reconcile exactly again.

Percentages display as the agreement states them — 10% or 10.00%, not 0.1 — and effective rates derived on the report are shown to two decimal places with the numerator and denominator visible, because a derived rate without its inputs cannot be checked. Currency amounts carry the contract currency symbol or code on every total, and converted amounts sit beside their source amounts.

Signs follow a single rule: amounts that reduce the royalty base or the royalty due are shown as negatives, or in a labelled deductions column, never both. A return shown as a positive in a column headed "Deductions" and a prior-period credit shown as a negative in the adjustments section is an inconsistency a reader has to resolve before reading; a report that uses one convention throughout reads itself. A negative net due — a period in which adjustments exceed earned royalty — is shown as a negative and carried forward or refunded as the agreement provides, not suppressed to zero.

Units of measure are stated: pieces, pairs, sets, dozens where a category trades in them. A category that sells in dozens and reports in pieces, or the reverse, produces a per-unit royalty off by a factor of twelve with every other field correct. None of this is the agreement's content, and all of it decides whether the content can be read.

Who prepares the report, and who receives it

One team signs the report; several teams produce it. Finance — the royalty accountant or the controller's team — assembles the sales detail, runs the calculation, computes the positions and produces the file. The licensing team owns the agreements and is the only group that reliably knows what the current terms say, which makes it the reviewer of scope: are these the licensed categories, channels and territories, and is this the rate card the last amendment left in force. Sales operations owns the path from order to invoice across wholesale, direct-to-consumer and marketplace channels, and is where channel and customer attribution is decided. Merchandising and product own the style records that decide which mark a garment carries and therefore which report it lands on. A break in any one of those four places surfaces as a wrong number on a report somebody else signs, which is why the preparation is cross-functional even when the signature is not.

On the receiving side the picture mirrors it. The licensor's licensing team reads the report for scope and approvals. The licensor's finance team reads it for cash, positions and the match to its own receivable. Where the licensor works through an agent — a collegiate licensing agency acting for schools, or an agency representing a property owner — the agent receives the report, validates it against the contract terms it holds, raises queries, and reports upward to the licensor from its own consolidated view. The guide on how licensing agencies manage royalty reporting across licensees, linked at the end, covers that side of the chain. For the preparer the practical consequence is that the first reader can be an intake process rather than a person — a portal with validation rules, or an agency analyst with a checklist — and the report has to pass that process before any judgment is applied to it.

The manufacturer-licensee is a third seat worth naming. A manufacturer of licensed goods that holds its own agreement reports exactly as a brand licensee does, but with production rather than merchandising as the source of product attribution, and with sell-off and final-statement mechanics that matter more because production straddles term boundaries. The guide on royalty reporting for manufacturers of licensed goods, linked at the end, covers what changes; the document itself is the one described here.

Cadence and due dates by contract year

The reporting clause sets three dates for every period: when the period ends, when the report is due, and when the payment is due — and the three are not always the same day. Due dates are expressed as a stated number of days after the period end, and the period itself is defined against the contract year rather than the calendar or the licensee's fiscal year. A licensee with a portfolio of agreements is therefore running several cadences on several year-starts at once, and the reporting calendar that maps them is itself an operating artefact. The guide on the multi-licensor royalty workflow, linked at the end, builds that calendar; what belongs here is how cadence shapes the document.

Cadence changes the fields the report leans on. A monthly report carries twelve rolling positions a year, so its opening balances are tested twelve times and an error propagates for at most a month before the next report exposes it; it also carries more returns lag, because a return arriving in month three against a sale in month one is a prior-period adjustment on a monthly report and an in-period return on a quarterly one. A quarterly report carries fewer roll points and a cleaner returns picture, but a larger guarantee movement per report and a longer gap between a stale rate taking effect and anyone noticing it. Where an agreement reports semi-annually or annually, the whole contract year's tier and guarantee mechanics concentrate into one or two documents, so the tier allocation and the guarantee measurement happen on the same page as the sales.

The contract year adds its own dates. The guarantee measurement date — the contract-year end — is when a shortfall crystallises and becomes payable, and the report for the final period of the contract year is the one that shows the measurement. A stub first year, where the agreement's effective date and the licensor's preferred year boundary do not coincide, produces a short first measurement period, a prorated guarantee where the agreement provides for one, and a first report whose period is shorter than the cadence; the guide on onboarding a new licensor agreement, linked at the end, covers how to settle the stub in writing before the first period closes. The final period of an agreement, and the sell-off period after it, produce a final report with an inventory certificate and obligations that outlive the term; the guide on sell-off, termination and the final royalty statement, linked at the end, covers that sequence.

Two consequences for the document follow. First, the due date is unaffected by a resubmission unless the clause says otherwise, so a report rejected for format can put a correctly computed royalty late, with whatever late-payment interest the agreement attaches. Second, the period on the report has to be the agreement's period even when the licensee's close calendar makes a different boundary easier — the convenience of a fiscal cutoff is not a term of the agreement.

Formats: licensor templates, portals, CSV and XLSX

The format is the licensor's. A royalty report travels in whichever shape the reporting clause and the current template specify, and the shapes differ enough across a portfolio that formatting is a real step rather than an export. Four shapes cover the ground: a licensor-supplied workbook with locked layouts and formulas the licensee fills; a portal that accepts an upload — CSV or XLSX in a mandated column order — and validates it on intake; a statement document — a PDF, for example — with a separate detail file behind it; and a licensee-produced report in a format the licensor has agreed to accept. Which one applies is a fact about the agreement, and it changes when the licensor revises its template.

A workbook template puts the licensor's structure around the licensee's figures. Its advantage is that the summary arithmetic is the licensor's own, so a statement that foots in the template foots for the reader too; its hazard is that the template carries live formulas over cells the licensee fills, and a licensee that keeps one copy per period and edits forward accumulates drift between what was submitted and what the file now shows. Each period's submission is archived as a frozen file, and the next period starts from the licensor's blank template or a cleared copy, not from last period's filled one.

A portal upload turns the report into data. The portal publishes a specification — column order, the identifiers it recognises, date and number formats, required granularity — and rejects files that do not meet it before anyone reads them. The upside is that a rejection is immediate and specific; the downside is that the specification changes on the portal's schedule, not the licensee's, and a column added to the specification is a rejection on the next upload for every licensee that did not notice. Where a portal computes the royalty itself from the uploaded detail, the licensee still has to compute it independently and reconcile, because the portal's figure is the licensor's figure and the licensee is certifying its own.

CSV and XLSX are the working formats underneath both. A CSV carries one table — detail lines, or a summary — with no formulas and no formatting, which makes it the right vehicle for the sales detail and for any upload; it cannot carry the certification or the layout a statement page needs. An XLSX can carry the whole report in one file — statement, detail, schedules and certification on separate sheets — at the cost of carrying formulas that have to be frozen before archiving. The free CSV template linked after the worked example lays out a monthly multi-licensor statement block — per-licensor sections with the per-agreement rate and calculation, the allowed-deductions block, advance balance and recoupment, the guarantee position with a shortfall indicator, and net due per licensor and consolidated — populated with illustrative example data; it carries none of the tier, cap, adjustment, currency or certification fields described above.

Whatever the shape, two rules hold. The computed figures are rendered into the format, not computed in it: one calculation, held once with its derivation, rendered into as many layouts as the licensee has licensors, so every report reconciles to the same computed figures rather than to separately built workbooks. And every format version is archived with the submission it carried, because a licensor's template from three contract years ago is the template an auditor will compare that year's report against.

Granularity: what per SKU, per style and per category each require

The reporting clause names a level of detail, and the three levels that recur in licensed apparel make different demands on the licensee's data. Per category is the coarsest: sales by the agreement's product categories — headwear, fleece, tees, performance, outerwear, accessories — with units and gross value per category per channel per territory. It can be produced from a product master that carries the agreement's category on each style, and it is the level at which category rates are applied. Its weakness is that it cannot be tested for scope: a category total says nothing about whether every style inside it was approved.

Per style adds the licensee's style identifier and description to each line, so the licensor can match the report to its approval records. It needs the style-level approval list from the licensor and the licensee's own style master to agree on identifiers, which they do only if the identifier the licensee submitted for approval is the one it ships under — a renamed style is an unapproved style on the report until someone maps it back. Per style is the level at which scope becomes testable, and the level at which a cooperative mark becomes visible as a style with two rights attached rather than a unit inside two category totals.

Per SKU — style, color and size — is the finest, and the level some portals and some agreements require. It multiplies lines by colorways and size runs without adding information about rate or scope, and its value is to the reader comparing the report with retail data, where SKUs are what sell. It demands that the SKU identifiers on the report are the ones on the invoices, that retired SKUs are not reissued, and that a size-level split of a return credit is attributed correctly. A per-SKU report that aggregates returns at style level has mixed two granularities and will not cross-foot at either.

Whatever the level, the report cannot be finer than the licensee's data and should not be coarser than the clause. Where the clause asks for a level the licensee's attribution does not yet support — per style where the product master only carries category — the honest report says so and supplies the finer level as soon as the attribution exists, rather than inventing a split. The guide on royalty reporting data requirements, linked at the end, specifies the attribution each level depends on.

One report, several templates: what changes between licensors

A licensee reporting to several licensors renders one calculation into several documents, and the differences between those documents are not cosmetic. The identifiers differ: one licensor keys on its own property codes, another on the licensee's style numbers, a third on a product classification it publishes. The category vocabularies differ: fleece under one agreement is sweatshirts and hoodies under another and cut-and-sew under a third, and the mapping between the licensee's hierarchy and each licensor's categories is contract data that has to be maintained, versioned and defensible like any other term.

The period conventions differ: calendar quarters for one licensor, the licensee's fiscal months accepted by another, a season-aligned contract year for a third, so the same invoice can sit in different periods on different reports. The deduction vocabularies differ even where the economics agree — "allowances" on one template is "markdowns and chargebacks" on another — and the statement block differs in order, in which positions it shows, and in whether the guarantee position appears every period or only at the measurement boundary. Certification wording differs, and so does the signatory level required. Delivery differs: portal, email, a licensor's own workbook, an agent's intake.

The design consequence is the one this guide keeps returning to. Where each licensor's workbook is its own small program, each additional licensor carries close to the full cost of the first, and a change to the underlying sales data has to be made as many times as there are workbooks. Where the calculation is held once in a canonical model and each template is a rendering of it, the differences between licensors become mapping tables — identifier maps, category maps, period maps, label maps — that are maintained as data, and a change in the sales data flows to every report at once. The guide on the multi-licensor royalty workflow, linked at the end, covers the operating calendar; the point here is that the templates differ in ways that make the second approach the only one that scales.

A practical test of a report set: take one invoice line for a cooperative-mark style and find it on every report it should appear on. If it appears on each at the right share, in the right period, under the right category label and the right identifier, the mapping layer is sound. If it appears on one report and not another, or in different periods, the set has a gap that no amount of per-report footing will find.

Resubmissions, corrected reports and the archive

A report is a document of record from the moment it is submitted, and two events can produce a second version of it: a rejection, where the licensor or its portal refuses the file for format or completeness before accepting it, and a correction, where an error is found after acceptance. The two are handled differently on the document, and conflating them is how archives lose the version a payment was made against.

A rejection produces a resubmission for the same period. The resubmission carries the same agreement reference and period, a new preparation date, and a version marker that says it replaces the original; the figures may be identical if the defect was format, or changed if the defect was completeness. The original is kept, marked as rejected, with the rejection notice beside it — not deleted and not overwritten — because the due-date question in the previous section turns on when the first file went in, and because the gap between the two files is itself evidence of what the licensor's template requires.

A correction found after acceptance does not produce a second version of the accepted report at all. The accepted report stands as submitted, and the correction appears on the next report as an attributed adjustment — the period it corrects, the type, the movement, the rate in force in that period, the royalty effect and the reason. Where the correction also changes a rolling balance, the next report's opening figure still equals the accepted report's closing figure, and the adjustment line carries the difference. A licensee that instead reissues the earlier report creates two documents claiming to be the record for one period, and an auditor who finds both will ask which one the payment matched.

The archive is what makes either event survivable. For each agreement and period it holds the report exactly as submitted, in the format submitted; the sales detail and deduction detail behind it at transaction level; the rate card version in force, with its effective dates; the product-to-property mapping as it stood; the calculation that produced the figures, reproducible on request; the pre-certification tie-out record; the certification as signed; the remittance advice and proof of payment; and the licensor's acknowledgement, rejection or queries with the responses. The audit clause sets how far back a licensor can reach, and the archive has to cover at least that window for every agreement — which, across a portfolio with different lookbacks and different contract years, is a per-agreement retention rule rather than a single company policy.

Proof of submission and acknowledgement

A report is submitted when it reaches the licensor through the channel the reporting clause names, and the licensee needs evidence of that moment, because the due date is tested against it. What counts as evidence depends on the channel. A portal issues a submission identifier and a timestamp, and the upload confirmation is the proof; a validation failure before acceptance is a rejection, not a submission, and the clock has not stopped. An emailed report is proved by the sent message with the attachment, its timestamp and the recipient the agreement names — a report sent to a contact who has left the licensor is a report the licensor can say it never received. A licensor's own workbook returned through its intake is proved by the acknowledgement that intake issues.

Acknowledgement is a separate event from acceptance. An acknowledgement says the file arrived; acceptance says the licensor has read it and raises no objection, and the two can be weeks apart or the second may never arrive explicitly. Where the agreement sets a period after which an unqueried report is deemed accepted, the licensee records the date that period ends; where it does not, the report stays open to query until the audit lookback closes, and the archive has to treat it that way.

Both pieces of evidence belong in the archive beside the file: the proof of submission with its timestamp, and the acknowledgement or acceptance with its date, together with every query raised and every response sent. A licensee that can show the report, the moment it went, the moment it was acknowledged and the queries it drew has the complete record of the period; one that has only the file has the figures without the history that makes them a submission rather than a draft.

The controls a good report carries

A royalty report is a representation the licensor is contractually entitled to test over a lookback window the audit clause defines, and what makes it defensible is not the quality of its arithmetic but whether its derivation still exists and can be shown. The CFO's guide to royalty reporting controls, linked at the end, frames the five control objectives and where spreadsheets fail them; the glossary entries on the audit trail, recompute history and statement reconciliation, also linked, define the terms. This section is about the controls a well-built report visibly carries — the ones a reader can see on the document, or request and receive the same day.

The first is the tie to the general ledger. The period's earned royalty ties to the royalty accrual, the net due ties to the royalty payable and then to the payment, the advance movement ties to the prepaid-royalty asset, and the net sales on the report bridge to the ledger's revenue for licensed product through an ordered set of standing difference lines — timing, scope, deductions the agreement excludes, channels the ledger nets differently. The guide on tying royalty-reported net sales to the general ledger, linked at the end, builds the bridge. A report whose net sales cannot be bridged to the ledger is a report whose completeness cannot be shown, and a reconciliation performed only at year-end finds a year of drift at once.

The second is recompute history: the time-ordered record of how the period's calculation changed — original rate, adjustments, true-ups, rate changes — preserved at the calculation level, so that the report as submitted can be reproduced on request years later, and so that any later change to the period is visible as a change rather than as a silently different number. A workbook copied forward with live formulas over prior-period cells has no recompute history; it has a current state. Period locking is the structural form of this control: once reported, a period's figures do not change, and corrections appear as attributed adjustments on later reports.

The third is the audit trail, in both directions: from any line on the report to the sales lines, deductions, rate version and mapping decisions that produced it, and from any sales line of licensed product to the report line it landed on or the recorded reason it was out of scope. The second direction is the completeness test and the one that gets skipped. Versioning sits inside this control: rate cards and amendments, deduction definitions and caps, the product-to-property mapping, category and mark-type assignments, and the statement templates themselves, each with effective dates, so the report can be tested against the terms as they stood on each sale date rather than as they stand today.

Three more controls are visible on a good report rather than behind it. The rolling balances roll — opening equals prior closing on the advance, the guarantee and the tier, with any difference explained by an attributed adjustment. The preparer and the certifier are different people, and the pre-certification tie-out — statement to calculation, calculation to source data, period to prior period for reasonableness — is recorded and dated. And the archive holds the report exactly as submitted, in the format submitted, with the data, rate card version and calculation behind it, so that an audit becomes document production rather than a forensic rebuild.

The errors found in reports, by mechanism

The errors below are described by mechanism — what has to be true in the licensee's process for the error to appear on the report — rather than by frequency, because the frequency figures that circulate for royalty misreporting do not trace to a checkable source, and the mechanism is what a preparer can act on. The guide on common royalty audit findings, linked at the end, covers the six findings royalty auditors write up and the process design that prevents each; the royalty audit defense checklist covers what to have ready when a notice arrives. Every mechanism here shares one property: it produces a plausible number. Nothing errors, the report is accepted and paid, and the discrepancy waits for the audit clause.

A stale rate appears when an amendment, a renewal step-up or a reclassification takes effect on a date and the calculation keeps using the prior value, because the rate lives in a workbook that nobody updated and nothing checks it against the contract file. The report shows the old rate on every line from the effective date forward, and the first period after an effective date is the one that carries the old rate if nothing checked the change. The guide on stale-master drift, linked at the end, is the full treatment.

A habitual deduction stack appears when finance applies one accounting view of net revenue to every licensor, so that every agreement whose enumerated deductions differ from that habit is misreported — some high, some low. On the report it shows as deduction types the agreement does not name, amounts above a cap, or an account-level allowance deducted in full without allocation. A cap measured on the wrong base — in aggregate where the clause says per category, on net where it says gross — is the same mechanism one step down.

Sales that never reached the report appear when a style is set up without its mark attribution, or a retired product code is reissued to a different style, or a channel feed is outside the extraction. The sales reconcile perfectly to a sales system that was never asked about royalties, and the report is internally consistent and incomplete. Only the reconciliation from total licensed-product sales to reported royalty-bearing sales exposes it, which is why that reconciliation is a field on the report in this guide and not a step before it.

Balances that do not roll appear when a prior-period correction is applied by editing the prior period rather than adjusting on the current report, so the current report's opening figures no longer equal the prior report's closing figures as submitted. Zero earned royalty during a recoupment period appears when the preparer confuses what is payable with what is earned. A tier read the wrong way — incremental where the clause says retroactive, or the reverse — appears when the clause's application rule was never written down beside the breakpoints. Currency converted twice, or on the wrong date, appears when the source amount is discarded before the royalty workbook sees it. And unattributed returns appear when a credit is netted into the period it arrived in rather than the period of the original sale, producing a report in which units and dollars stop explaining each other.

None of these is an arithmetic mistake. They are data-model and process failures that the arithmetic then executes faithfully, which is why the controls in the previous section are worth more than any amount of care applied to the calculation itself, and why a report that cannot show its derivation cannot detect its own errors.

Worked example: one report line from gross sales to royalty due

The example that follows works one line of a quarterly report from gross sales to the royalty due, under a tiered rate and with a minimum guarantee that was paid in advance and is being recouped. Every figure — the rates, the breakpoint, the cap, the guarantee and all of the sales figures — is illustrative, chosen so the arithmetic can be followed. They are not benchmarks, not category norms, and not drawn from any licensee, licensor or agreement.

The agreement is a single-category collegiate fleece license, reported quarterly on a contract year that runs 1 July to 30 June. Because it covers one category, the one line below is the whole of the quarter's sales schedule, which keeps the tier arithmetic to a single line. The rate is tiered on cumulative contract-year net sales and applied incrementally: 10% on the first $2,000,000 of net sales in the contract year and 12% on net sales above $2,000,000. Permitted deductions are customer returns as actual credits issued, attributed to the period of the original sale; documented markdown allowances up to 4% of gross sales per category per quarter; and outbound freight separately stated on the invoice. Nothing else is deductible. The minimum guarantee is $600,000 for the contract year, paid in advance on 1 July and recoupable against the contract year's earned royalties; any balance unrecouped at 30 June is retained by the licensor. There is no separate advance and no marketing fund contribution.

Two quarters have been reported and accepted. The first quarter closed with net sales of $620,000 and earned royalty of $62,000 at 10%; the second with net sales of $800,000 and earned royalty of $80,000, also at 10%. Cumulative contract-year net sales entering the third quarter are therefore $1,420,000, leaving $580,000 of room in the 10% band before the $2,000,000 breakpoint. Cumulative earned royalty entering the third quarter is $142,000, and the unrecouped balance of the prepaid guarantee is $600,000 − $142,000 = $458,000. No prior-period returns have been credited against the first two quarters, so the cumulative figures carry forward unadjusted.

The third-quarter line — fleece sold wholesale in the United States, January through March — reads: gross invoiced sales of $1,480,000; returns credited in the quarter against third-quarter sales of $59,200; markdown allowances claimed of $74,000; and outbound freight separately stated of $22,200. The deductions section tests each type. Returns are permitted as actual credits and are allowed in full at $59,200. Markdown allowances are capped at 4% of gross: $1,480,000 × 4% = $59,200, so $59,200 is allowed and $14,800 stays in the base. Freight is permitted where separately stated and is allowed in full at $22,200. Allowed deductions total $59,200 + $59,200 + $22,200 = $140,600, which is 9.5% of gross. Net sales for the line are $1,480,000 − $140,600 = $1,339,400.

The rate section allocates the line's net sales across the tier bands. The first $580,000 fills the remaining room in the 10% band: $580,000 × 10% = $58,000. The remaining $1,339,400 − $580,000 = $759,400 falls in the 12% band: $759,400 × 12% = $91,128. Earned royalty for the quarter is $58,000 + $91,128 = $149,128. Expressed as rates, that is 11.13% on net sales and 10.08% on gross sales — a blended figure that matches neither band, which is exactly what the tier fields on the report exist to explain. Cumulative contract-year net sales after the quarter are $1,420,000 + $1,339,400 = $2,759,400, so fourth-quarter net sales will bear 12% from the first dollar.

The guarantee section recoups. The opening unrecouped balance of the prepaid guarantee is $458,000. Recoupment is the lesser of the quarter's earned royalty and that balance, so the full $149,128 is recouped and the closing balance is $458,000 − $149,128 = $308,872. Cumulative earned royalty for the contract year is $142,000 + $149,128 = $291,128 against the $600,000 guarantee, with $308,872 still to be earned before any cash royalty becomes payable. Net due for the quarter is $0. The report nonetheless shows earned royalty of $149,128 in full, the recoupment of $149,128 and the closing balance of $308,872, because the next report's opening balance and the year-end measurement both depend on those figures. If the fourth quarter earned less than $308,872, the shortfall would already have been paid through the prepayment and the unrecouped remainder would be retained by the licensor; if it earned more, the excess over $308,872 would be the first cash royalty of the contract year.

Had a return been credited in the quarter against second-quarter sales, it would not have appeared in the $59,200 returns line. It would have been a prior-period adjustment reversing royalty at the second quarter's rate of 10%, and because the tier is measured on cumulative net sales it would also have reduced the $1,420,000 entering the quarter, widening the 10% band by the same amount and changing the third-quarter split. That is why the adjustments section shows the effect on every cumulative figure, not only on royalty.

Worked example, continued: the same quarter on the statement page

The statement page of the same report renders the line above as the licensor's finance team will read it: the summary block in the licensor's order, with the positions rolled forward and the net due at the bottom. Nothing on it is new; every figure is one of the figures derived above, and the statement is a view over the calculation, not a second calculation. Where the report's detail and schedules let the licensing team test scope and rates, the statement lets finance foot, book and match cash.

Three things about the statement are worth noticing against the detail. The deductions show as allowed, with the claimed amount and the cap visible in the detail rather than on the statement page itself, so the statement foots to the royalty base the agreement produced. The rate shows as a blended effective figure on net sales and gross sales — 11.13% and 10.08% — with a reference to the tier schedule, because a single rate cell cannot carry a two-band allocation. And the guarantee block shows four figures rather than one: the guarantee, the opening unrecouped balance, the recoupment and the closing balance, so the reader can roll the position without opening the detail.

The remittance advice for the quarter, if one is sent at all when nothing is payable, would name the agreement, the third quarter of the contract year and a payment of $0, which is how the licensor's receivables team knows that the absence of cash is a reported position rather than a missed payment. The licensor's own books would show the $600,000 received on 1 July being earned down by $149,128 this quarter, with $308,872 of prepaid royalty remaining that either earns out in the fourth quarter or is retained at 30 June.

How the report changes by category

The document described above is licensed apparel's. The fields do not change in adjacent categories, but what populates them does, and a report that uses apparel's vocabulary for a footwear or home program has been exported rather than prepared. Four categories this site covers are worth a paragraph each; the reader's side of the same category differences is in the guide on how to read a royalty report.

In licensed footwear the unit is the pair, and the sales detail is organised by style, colorway and size run rather than by style-color alone. Width fits and extended size runs inflate SKU counts without adding styles, so a template that asks for SKU-level detail produces a long report whose category totals are small. Footwear programs run on a model year, and a carryover style — one that continues into the next model year — reports under the rate card in force for the period it sold in, not the model year it was introduced in. Closeouts of the prior model year through off-price channels are the line most exposed to a channel restriction, and the detail line has to show the channel so the restriction can be tested.

In home and fan gear the SKUs carry long lead times and the sales pattern follows floor sets and dealer prebooks rather than weekly replenishment, so a quarter's report can carry a prebook delivery that was ordered two quarters earlier under a rate card since amended; the sale reports at the rate in force on the sale date, whatever the order date. Container minimums make shipments lumpy, so period-over-period comparison on the report needs the shipment timing visible. The deductions section carries types apparel's does not: damage and breakage allowances, drop-ship handling fees deducted by the retailer on remittance, and returns settled as allowances rather than physical credits — each a contract question with its own answer, and each shown on its own line with its reason code.

In headwear and accessories colorways multiply under a single style, and fitted, adjustable and stretch-fit constructions can carry different price points under the same mark, so the sales detail needs colorway and construction where the template asks for them. Where headwear is licensed under its own agreement with its own rate card alongside an apparel agreement with the same licensor, there are two reports, two agreement references and no netting between them, even when the same retailer bought both. Bundle promotions — a cap sold with a jersey on one invoice line — have to be split by component before either report sees its share.

In licensed jewelry and watches the cost base is dominated by precious-metal and component costs that move with commodity prices, and an agreement may define the royalty base net of a stated metal-content allowance. Where that applies, the report carries a metal-cost line per style with the price basis and the date it was computed on, because a base net of metal content cannot be tested without them. Watches run on a model year with long component lead times, and limited or numbered editions attach the mark to a stated quantity, so the sales detail shows units against the edition size. Repairs, replacements and warranty exchanges are units carrying the mark that generate no sale, and the agreement's gratis or free-goods clause decides how they are reported.

Where this guide sits, and how the document is produced

This guide covers the document. The guide on how to read a royalty report covers what a licensor does with it; the guide on how to prepare a royalty statement covers the six steps that produce it; the guide on what royalty reporting is covers the obligation and the period cycle around it; and the guide on royalty reporting data requirements specifies the source data every field above depends on. The glossary entries on the royalty report and the royalty statement define the two terms this guide relies on, and the entries on the reporting period, the contract year, the tiered royalty rate, the audit trail, recompute history and statement reconciliation define the fields.

The design principle behind a defensible report is the one every section above has pointed at: compute once, into a canonical model that holds agreements, rate cards, deduction rules and their caps as structured terms with effective dates and resolves every sales line to property, category, channel and mark type at the transaction; render per licensor, treating each report as a view over the calculation rather than the place the calculation lives; and lock each period with its derivation intact. That is how Royalty Reporting is built: it generates the royalty statement each licensor expects, in the format that licensor requires, maintaining per-licensor statement templates and producing audit-ready output every period. Statements are generated, not assembled — tie-out between the statement and the underlying calculations is preserved, and every statement version is captured for audit. Its audit trail captures every change to every royalty calculation: original rate, recompute history, period-over-period changes, statement versions and adjustment notes.