Skip to main content
Royalty Reporting
Guide · 25 min read

Rights and Royalties Management, Explained

Rights and royalties management is the work — and the category of software — that turns licensing agreements into correct royalty payments: holding the rights each agreement grants (licensed marks, product categories, territories, channels and term), tracking the approvals the licensor requires, calculating royalties, producing each period's statements and reports, settling advances and minimum guarantees, and keeping the audit trail that proves every figure. The work is not symmetrical. A licensor manages rights granted out to a roster of licensees and receives their statements; a licensee manages rights received from a portfolio of licensors and produces those statements from its own sales. Royalty reporting — the licensee's periodic calculation and declaration of what it owes — is one component of the category, and on the licensee side it is the component that carries the cash and the audit exposure. This guide maps each component to its owner, shows where spreadsheets break, lists a licensee's evaluation questions and works an illustrative quarter.

What rights and royalties management covers

The category name bundles two things that separate cleanly in practice. The rights side is the record of what an agreement permits: which marks, on which products, sold where, through which channels, for how long, and subject to which approvals. The royalty side is the money that follows: what is owed, how it is calculated, when it is paid, how it is reported and how it is proven. The two are bound together because the grant decides what is royalty-bearing — a sale outside the granted territory is not a cheaper royalty, it is outside the licence — so a calculation that cannot see the grant cannot tell a statement that foots from one that is complete.

The category travels under several names, and the names describe slices rather than rival products. Royalty tracking is the running positions: advance balances, guarantee progress, deduction and gratis caps consumed. Royalty accounting is the ledger: accruals, liabilities, payments and the general-ledger tie-out. Royalty reporting is the periodic output: the statement and the report behind it. Royalty management software, and rights and royalties software, are umbrella terms for systems that hold some or all of these together.

One boundary first. In film, television, music and publishing, rights management also tracks release windows, territorial availabilities and participations in content revenue. For consumer products the rights are marks, product categories, territories, channels and term, and the royalty follows units and sales. This guide is about consumer-product licensing, apparel first.

Licensor side and licensee side: one agreement, two different jobs

Every licensing agreement has two parties, each running it from a different seat. The licensor grants rights out. Its portfolio is a roster of licensees; its work is approving product, collecting statements, testing what each licensee declared against what it sees at retail, chasing late submissions, commissioning audits and recognising royalty income. The licensee receives rights in. Its portfolio is a set of licensors, each with its own agreement, definitions, template and calendar; its work is resolving each sale to the agreement and rate that governs it, producing a statement and report per licensor per period from one set of sales data, accruing royalty expense, paying, and defending the numbers under audit.

The two jobs need different systems because their central records differ. A licensor-side system is organised around the licensee roster and the statements coming in: it receives submissions in varied shapes, normalises them, flags the ones that look wrong, and runs the approval queue in front of product launches. It has no reason to hold a licensee's sales at line level, because the licensor does not see them in that form outside an audit. A licensee-side system is organised around the licensee's own transactions and the statements going out: it resolves every sales line to agreement, category, channel, territory, mark type and date, computes each licensor's royalty under that licensor's definitions, and renders the result in each licensor's format.

The controls point in opposite directions too. The licensor validates numbers someone else produced; the licensee produces numbers it must later prove. A licensor control asks whether a statement is plausible and complete. A licensee control asks whether every statement line traces to the sales behind it, under the rate card in force on the day of each sale, in a period that cannot silently recalculate. The ledger mirrors the split — royalty income and receivables on one side, royalty expense, accruals and liabilities on the other — and so does the audit clause, which the licensor exercises and the licensee answers. The first question in any evaluation is therefore which seat a product was designed for, not which features it lists.

Rights and contract management: the grant as data

The grant defines what the licensee may do, and each of its terms becomes a field the royalty calculation reads. Licensed marks name what the product may carry — team, league, event or player marks — and mark type can change the rate inside one agreement. Product categories name what may be made; the licensee's merchandise hierarchy is built for merchandising rather than for the agreement, so the mapping from styles to the agreement's categories is contract data, versioned like any other term. Territories and channels name where and how the product may be sold, and each can carry its own rate or sit outside the grant. The term sets when rights begin and end, followed by any sell-off period in which sales stay royalty-bearing.

Approvals sit beside the grant. A licensor can require sign-off on concept artwork, pre-production and production samples, packaging, labels and marketing materials, and a style that ships without its approvals is a compliance exposure however correctly its royalty was calculated. The licensor owns the approval process and the system it runs in; the licensee owns the evidence — the approval reference and status held against the style, so an open approval is visible before an order rather than after a statement.

Amendments add categories, move rates and extend territories, each with an effective date, and a contract record without effective dates describes the agreement only as it stands today — the wrong record for any period closed before the last amendment. The licensor authors the grant; the licensee has to hold it as structured, dated data, because the licensee's transactions are what the grant is tested against.

Royalty calculation: base, rates, per-unit terms and minimums

The calculation applies two inputs from the agreement — the base definition and the rate structure — to the licensee's sales data. The base is built in two steps. Scope first: which sales are royalty-bearing at all, decided by the grant plus the agreement's treatment of gratis units, seconds and closeouts. Value second: gross sales less the deductions the agreement enumerates — returns, allowances, discounts, freight, taxes — where a deduction cap can limit one deduction or the total to a stated share of gross sales. A deduction claimed above the cap is not a smaller deduction; the excess stays in the base.

Rates apply in several shapes, and one agreement can combine them: a flat percentage; tiers that step as cumulative volume crosses thresholds, on a basis and with a retroactive or prospective reading the agreement has to state; rates by product category, channel, territory or mark type; and rates that change at each amendment's effective date. A rate is resolved per sale and transaction date, not looked up once per period.

A per-unit royalty replaces the percentage with a fixed amount per royalty-bearing unit — per piece, pair or set. The unit count carries the calculation: returned units reverse, price and markdowns do not move the amount owed, and the unit definition has to match between the agreement and the product master. A greater-of term charges the higher of a percentage and a per-unit floor on each unit, so the calculation computes both and keeps the larger, line by line.

Minimums take two forms: the per-unit floor, and a minimum guarantee over a measurement period — a quarter, a contract year or the term — covered with advances below. The licensee owns the calculation, computing it from its own sales under each licensor's definitions; the licensor re-tests it, from the statement in the ordinary course and from the licensee's records under the audit clause.

Statements and royalty reports

Each period produces a submission per agreement, and two words for it are worth pinning down. A royalty statement is the summary document: gross sales, deductions, net sales, rate, royalty amount, advance and guarantee position, adjustments and net due, in the licensor's format. A royalty report is the full submission: the statement plus the detail and schedules the agreement requires so the licensor can test it — line-level royalty-bearing sales by style or SKU, category, channel, customer and territory; per-unit lines with their counts; separate schedules such as gratis units against their cap or a marketing fund contribution; adjustment lines attributed to the periods they correct; and the officer's certification. In conversation the two words name the same submission. The distinction matters when a licensor's portal asks for both files, or when an auditor asks for the detail behind a total.

The two fail differently. A statement can foot and still be wrong — every figure agreeing with every other while a whole sales feed never reached the calculation. Only line detail exposes that, which is why the report's granularity is set by the licensor's template rather than by what the licensee finds convenient to export.

The licensee produces both; the licensor owns the template, cadence, due date and intake. Across a portfolio each licensor sets those differently, so one set of sales data becomes several statement formats every period. The defensible design is one calculation rendered into every licensor's format, so that every statement and report reconciles to the same computed figures rather than to separately built workbooks.

Advances, minimum guarantees and recoupment

Two instruments change what is paid without changing what is earned. An advance is paid upfront — at signing or on a schedule the agreement sets — and recouped against earned royalties until the balance reaches zero; after earn-out, royalties are paid in cash again. A minimum guarantee is a floor over a measurement period: if earned royalties fall short, the licensee pays the difference as a shortfall at the boundary.

The interactions are contract terms, not conventions. Whether advance payments count toward the guarantee decides whether a shortfall is reduced by the advance or owed on top of an unrecouped balance. Whether properties, categories or contract years are cross-collateralized decides whether one basket's excess absorbs another's shortfall. Whether the guarantee is measured quarterly or at the contract-year end decides when a shortfall is payable. Identical sales produce different cash under each reading, so the position has to be carried per agreement and per measurement period, with the terms that govern it.

Both parties track these positions. The licensor carries a receivable and recognises income. The licensee carries the cash forecast, the accrual — including a building shortfall estimate where an agreement is running short — and the evidence that each recoupment hit the right balance. A projected shortfall is a budget line; a discovered one is an unbudgeted invoice.

Marketing fund contributions

A marketing fund contribution is an amount an agreement requires the licensee to pay, on top of royalties, into a fund the licensor uses to market the licensed property. Agreements name it variously — a marketing fund, a common marketing fund, an advertising contribution — and set it under its own clause: a percentage of net sales, a fixed amount per contract year, or a percentage with an annual minimum. Its base is whatever that clause defines, which need not match the royalty base.

It is not a royalty, so its own clause, not the royalty clause, decides how it behaves. Whether it counts toward the minimum guarantee, can be recouped against an advance, falls under the same audit clause, or carries a minimum measured on the contract year are questions that clause answers. Where it is measured on net sales it inherits every scope and deduction decision in the royalty calculation, so a disallowed deduction understates both lines at once.

It is reported beside the royalty, not inside it: its own line on the statement or its own schedule in the report, computed from the same sales detail for the same period. On the ledger it goes to whichever account the licensee's policy assigns, which need not be royalty expense — so the statement reconciliation has to know the line exists, or the gap between statements issued and royalty expense reads as an error when it is a classification. The licensor owns the fund; the licensee owns the calculation, the reporting and any minimum check at the boundary.

Audits and the audit trail

The audit clause lets the licensor examine the records behind the licensee's statements, over a lookback window the clause defines, through an audit firm the licensor appoints. The procedure starts on the licensee's side: total licensed-product sales reconciled down to royalty-bearing sales reported, every exclusion explained; then rates against the rate card in force on each transaction date, deductions against the agreement's list and caps, gratis units against their cap, per-unit counts against shipments and returns, positions against the terms, and marketing fund contributions against their clause. An underpayment found is owed with any interest the agreement provides, and the clause can shift the cost of the audit to the licensee above a threshold it states.

An audit trail turns that procedure from a reconstruction into a retrieval. It holds every rate card version with its effective dates, the category mapping as it stood in each period, the recompute history for any calculation that changed, each statement and report as issued with its sales detail, and each adjustment attributed to the period it corrects. The test is whether a competent reader who was not there could recompute any statement in the lookback window from the records alone.

The licensor commissions the audit and owns its findings; the licensee owns the records and the defence. A statement produced from a workbook edited since cannot be reproduced as issued, and a figure that cannot be reproduced stands as a finding until the licensee shows otherwise.

Payments and accruals

Payment follows the statement on the agreement's cadence, in the contract currency, net of recoupment and any withholding tax. The expense is recognised earlier: a royalty accrual books each month's royalty expense in the period the royalty-bearing sales occur, with a matching liability, because the statement that settles it arrives weeks or months later — on a quarterly cadence, up to a full quarter plus the agreement's statement due window after the sale.

Accrual and cash diverge for structural reasons. Returns lag keeps moving net sales after a period closes; recoupment accrues expense while no cash leaves; a guarantee shortfall builds as an estimate and settles once at the boundary; and a marketing fund contribution may accrue to a different account from the royalty beside it. The control is a three-leg reconciliation per agreement — statements issued, general ledger, cash paid or credited to an advance — with every difference named as timing, which rolls forward with a date, or error, which is corrected with attribution to its period.

The licensor carries the mirror image: royalty income, receivables and expected cash. The licensee's side sits inside its own close and its own external audit, which is why its accrual, statement and ledger need to read from one calculation history rather than three.

Where spreadsheets break

Spreadsheets are a reasonable place to start a licensing program and a poor place to run a portfolio, for reasons of mechanism rather than volume. No sales figure makes a workbook indefensible; structural properties make it wrong without anyone noticing.

The rate tab gets copied. A rate card is pasted into each licensor's statement workbook every period; an amendment updates the source and not every copy, and every statement after the effective date calculates correctly against the wrong rate — the pattern called stale-master drift.

Scope is set by the export, not the grant. Whichever sales reports were wired in at setup define what gets reported, so a new marketplace channel, territory or licensed category that never reaches the export never meets a rate, and the statement still foots.

Closed periods recalculate. Live formulas re-compute history when a rate cell or mapping table changes, so last quarter's statement no longer reproduces from its own file — and a statement that cannot be reproduced cannot be reconciled to the payment made.

Positions are carried by hand. Advance balances, guarantee progress, deduction-cap and gratis-cap usage, and marketing fund minimums are typed from last period's file into this one; one missed carry-forward and every later period inherits the error.

Non-percentage lines are bolted on. A per-unit royalty, a greater-of floor or a marketing fund contribution added as a column computes on its own separately kept base, which drifts from the royalty's. Approvals live in email, away from the style that ships. And nothing traces in either direction: no statement line points back to its sales lines, and no sales line points forward to a statement or to a recorded reason it was excluded.

Each of these produces a plausible statement and raises no error. They surface when someone asks a question the workbook cannot answer — a licensor querying a line, or an auditor reconciling total licensed sales to what was reported.

Evaluating rights and royalties software as a licensee

Start with scope, not vendors: the licensors and agreements in the portfolio now and over the next year, the categories and channels sold, the rate structures in force, the positions carried, the audit history, and who calculates, reviews, approves and pays. The questions below are vendor-neutral and apply equally to purpose-built software, an ERP module and a hardened internal build.

Which seat was the system designed for? Ask what its central record is — the licensee's own sales lines or incoming statements — and have the vendor show one sales line becoming a statement line for the right licensor.

Is the agreement held as dated data? The grant, rate card versions, deduction rules and caps, gratis caps, advance and guarantee terms, marketing fund clauses, statement templates and the reporting calendar should each carry effective dates, so that a historical period computes under the terms then in force.

How are rates resolved? Per transaction by property, category, channel, territory, mark type and date, or per period from a summary? Ask to see a tiered rate, a per-unit term, a greater-of term and a capped deduction, each without a workaround column.

How are positions carried? Advance recoupment, guarantees measured quarterly or annually, cross-collateralized pools and marketing fund minimums should compute from history rather than being typed in.

What happens after a period closes? Returns should attribute to the original-sale period, adjustments should post as attributed lines, closed periods should lock, and a recompute history should show every change and which version reached the licensor.

What comes out? Each licensor's statement and report detail from one calculation, at each template's granularity; accruals and a general-ledger tie-out; the three-leg reconciliation; and any statement in the lookback window reproduced exactly as issued.

What goes in? Ask how sales, returns, the product master and approval status arrive from the ERP, e-commerce and marketplace systems, and confirm that those systems remain the systems of record.

What does it take over three years? Ask which parts of your agreements are configured during setup and which are handled natively, what the services scope is, and what the three-year total is including services and support. Then run the test that answers several of these questions at once: put one real agreement and one period of real sales data through the system, and compare its statement line by line with the one you filed.

Worked example: one licensee, two licensors, one quarter

This example is illustrative — an unnamed apparel licensee, two agreements and round numbers chosen for legible arithmetic, not a benchmark and not drawn from any brand or agreement. Agreement A sets a 12% royalty on net sales of apparel; permits returns, markdown allowances and freight, with total deductions capped at 8% of gross sales and any excess left in the base; and requires a 2% marketing fund contribution on the same net sales, reported separately, not counted toward any guarantee, with no minimum. Agreement B sets a 10% royalty on net sales of apparel with returns as the only deduction and no cap, a $1.25 per-unit royalty on licensed drinkware, and a $50,000 minimum guarantee measured each quarter, with any shortfall payable with that quarter's statement.

Agreement A. Gross royalty-bearing sales for the quarter are $850,000. Claimed deductions are returns of $41,000, markdown allowances of $22,000 and freight of $12,000 — $75,000, all permitted types. The cap is 8% of $850,000, or $68,000, so $68,000 is allowed and the $7,000 excess stays in the base. Net sales are $850,000 − $68,000 = $782,000; the royalty is 12% of $782,000, or $93,840; the contribution is 2%, or $15,640. Statement A totals $109,480. Missing the cap and deducting the full $75,000 would have given net sales of $775,000, a $93,000 royalty and a $15,500 contribution — understated by $840 and $140, $980 in all, with nothing in the arithmetic to flag it.

Agreement B. Apparel gross sales of $400,000 less $18,000 of returns give net sales of $382,000 and a 10% royalty of $38,200. Drinkware ships 6,400 units and 240 come back; 6,160 units at $1.25 is $7,700, whatever each unit sold for. Earned royalties are $38,200 + $7,700 = $45,900, which is $4,100 short of the $50,000 quarterly guarantee, so Statement B carries both royalty lines and a $4,100 shortfall — $50,000 in total. Under Agreement B the quarter costs $50,000 whether earned royalties are $45,900 or $30,000, which is why the guarantee position has to be known before anyone reads a movement in B's earned royalty.

The quarter in total. Cash to licensors is $109,480 + $50,000 = $159,480. Royalty expense is $93,840 + $45,900 + $4,100 = $143,840, and the $15,640 contribution is booked to the account the licensee's policy assigns — in this example, marketing expense — so expense and contribution together equal the cash. Agreement A's reconciliation therefore expects statements of $109,480 against royalty expense of $93,840 and names the $15,640 difference as a classification, not an error; for Agreement B, statements, expense and cash agree at $50,000.

One sales dataset produced two statements under four mechanisms — a capped deduction stack, a percentage rate, a per-unit count and a quarterly floor — plus a contribution reported like a royalty and accounted for like something else. A licensor holding only the statements can check the multiplication; a licensor holding the reports behind them — deduction lines, drinkware shipments and returns, apparel sales lines — can check the scope.

Licensed product categories: what changes in the base and the approvals

Licensed goods span apparel, headwear and accessories, footwear, home, toys and games, baby and juvenile, jewelry and watches, beauty and wellness, sporting goods, and outdoor. The components above apply to all of them; what changes by category is what counts as a unit, what the base is measured on, when the sale is recognised, and what the licensor approves before product ships.

Apparel reports at style-color-size, with mark type deciding the rate, wholesale returns landing after their period, gratis samples running against a cap, and approvals from concept artwork to production sample gating each style. Headwear and accessories run an evergreen core in hero colors beside team and event drops; a colorway change is an approval event, and a gift set pairing a licensed cap with an unlicensed item needs its price split before a base exists. Footwear counts pairs across size runs and widths sold against prebooks — and a prebook is an order, not a sale, so nothing is royalty-bearing until the sale event the agreement defines.

Home and furniture turns on finishes, options, container quantities and ocean lead times. A direct-import sale taken at origin is invoiced without freight and duty, and some agreements rate it separately; landed cost moves the licensee's margin but not the royalty base unless the agreement says so; and special orders raise whether the sale happens at order, shipment or delivery. Jewelry and watches carry piece-level inventory, low velocity and metal cost moves: whether a passed-through metal surcharge is royalty-bearing is an agreement term, and pieces on memo or consignment need the agreement to say whether shipment or the retailer's sale is the royalty-bearing event.

Toys and games concentrate volume into the fourth quarter against retailer commitments made months earlier, can carry per-unit or greater-of terms where the licensed element is one component of the product, and add safety standards and test reports to the approval file; a licensed window tied to a release date brings the sell-off period forward. Baby and juvenile hard goods run on registry demand and model-year changeovers, with safety standards in the approval file. A registry purchase can be made well ahead of the event and returned or exchanged after it, so its return lands in a later period than its sale; a model-year changeover sends the outgoing model to closeout, where the grant decides whether those sales carry the same rate; and a recall lands returns and credits on periods already stated.

Beauty and wellness licensing explodes by shade and runs on launches: testers carry the licensed mark without a sale, so they are a gratis question, and opened testers are discarded once past their PAO; unsold product past its expiry date or shelf life is destroyed rather than sold, and the licensor can require the destruction to be certified; and promotions settled against retailer POS data arrive as deductions after their period. Sporting goods runs on team and season demand, dealer prebooks and model years: team orders can run through channels the grant rates separately or excludes, a dealer prebook is an order rather than a royalty-bearing sale, and model-year closeouts raise the closeout-channel question. Outdoor sells model years into dealer prebooks under MAP policies; MAP governs the price a dealer advertises, not the price the licensee invoices, so it does not set the royalty base, and counter-seasonal categories put each category's heavy shipping quarter at a different point in the contract year, which matters wherever a tier or guarantee is measured on the year.

The formula is the same in every category — royalty-bearing base times rate, measured against the positions the agreement sets — and a system that hard-codes one category's inputs misreports any category added later whose unit, base or sale event differs.

Where Royalty Reporting fits

Royalty Reporting is built for the licensee seat in this category: a cross-functional operating system for licensed-merchandise royalty reporting at apparel and consumer-product licensees — apparel first, with headwear, footwear, home and fan gear, and other licensed hard goods. It gives licensing, finance and accounting, sales operations, merchandising and product, and operations and sourcing teams one shared system for licensor obligations, royalty rules, sales data and audit-ready reporting.

In this guide's terms, it covers the parts of the licensee side listed here. Agreements live in a structured contract data model — rate cards versioned with effective dates, advance schedules, minimum guarantees, audit clauses, amendments and term dates. The calculation engine resolves per-licensor rate cards across flat, tiered, product-category and mark-type rates, treats returns lag as a first-class concept, and distributes cooperative-mark royalties across licensors per contract terms. Statements render from per-licensor templates; licensed styles carry their licensor, property, category and approval-status attributes; per-agreement guarantee and advance positions are tracked; and an immutable audit trail is kept at every calculation.

Two boundaries, stated plainly. Licensor-side licensee coordination is a different product category, and Royalty Reporting does not offer it. Non-apparel categories such as toys and housewares can be supported but are not the primary design target, so a licensee whose portfolio is weighted toward toys, games or housewares should evaluate a generalist consumer-products platform alongside it. Either way, the evaluation test applies here too: run your own agreement, per-unit and marketing fund clauses included, and one period of your own data through it before deciding.

Frequently asked questions

What is rights and royalties management?

Rights and royalties management is the work, and the category of software, that turns licensing agreements into correct royalty payments. It covers the rights each agreement grants — licensed marks, product categories, territories, channels and term — and the approvals the licensor requires; royalty calculation under the agreement's rates, per-unit terms, deductions and minimums; the statements and reports each period demands; advances, minimum guarantees and recoupment; marketing fund contributions; audits and the audit trail; and payments and accruals. Royalty reporting, the licensee's periodic calculation and declaration of what it owes, is one component of the category.

How is the licensee side of royalty management different from the licensor side?

The licensor grants rights out to a roster of licensees: it approves product, receives and validates statements, commissions audits and recognises royalty income. The licensee receives rights from a portfolio of licensors: it resolves each of its own sales to the agreement and rate that governs it, produces a statement and report per licensor per period, accrues royalty expense, pays, and defends the numbers under audit. The central records differ — incoming statements for the licensor, the licensee's own sales lines for the licensee — so a system designed for one seat models the other seat's central record thinly.

What is the difference between a royalty report and a royalty statement?

A royalty statement is the summary document for a period: gross sales, deductions, net sales, rate, royalty amount, advance and guarantee position, adjustments and net due, in the licensor's format. A royalty report is the full submission — the statement plus the sales detail and schedules the agreement requires, such as line-level sales by style, category, channel and territory, per-unit counts, gratis and marketing fund schedules, attributed adjustments and the certification. In conversation the terms name the same submission; the distinction matters when a licensor asks for the detail behind a total, because a statement can foot while the scope behind it is incomplete.

Are royalty tracking, royalty accounting and royalty management software the same thing?

They describe overlapping slices of one category. Royalty tracking refers to running positions — advance balances, guarantee progress, deduction and gratis caps consumed. Royalty accounting refers to the ledger — accruals, liabilities, payments and the general-ledger tie-out. Royalty reporting refers to the periodic statement and report. Royalty management software, and rights and royalties software, are umbrella terms for systems that hold some or all of these together. Which slices a given system covers shows up in a demonstration run on your own agreement, not in the product name.

What should a licensee ask when evaluating rights and royalties software?

Which seat the system was designed for; whether the agreement — grant, rate card versions, deduction rules and caps, gratis caps, advance and guarantee terms, marketing fund clauses, templates and calendar — is held as dated data; whether rates resolve per transaction by property, category, channel, territory, mark type and date; how per-unit, greater-of and tiered terms are expressed; how positions are carried; whether closed periods lock and adjustments attribute to their original period; what it produces, including accruals and reconciliations; how data arrives from existing systems; and the three-year total cost including services. Then run one real agreement and one period of real data through it and compare the result with the statement you filed.

How is a marketing fund contribution reported alongside royalties?

As its own line. The contribution is calculated under its own clause — a percentage of net sales, a fixed amount per contract year, or a percentage with an annual minimum — and appears as a separate line on the royalty statement or a separate schedule in the royalty report, computed from the same sales detail for the same period. Whether it counts toward the minimum guarantee, can be recouped against an advance, or is audited with royalties is decided by the clause, not assumed. It may be booked to an account other than royalty expense, so the statement reconciliation needs to name it as a classification rather than an error.

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.