Royalty Audit Preparation Software for Licensed Apparel.
Royalty audit preparation is the work of producing, for a licensor or its appointed auditor, the evidence behind every royalty figure reported across a look-back period — often two to three years. Royalty Reporting retains that evidence at the point of calculation, so preparation is a query against an immutable trail rather than a reconstruction from spreadsheets that have since been edited.
Used by apparel finance teams facing licensor audits where the look-back window predates the people, the file structure, and sometimes the ERP that produced the original numbers.
What this reporting workflow looks like in practice
Audit clauses, look-back windows and notice periods live in the contract record and feed the reporting calendar, so an audit window surfaces before the letter arrives rather than after.
Every calculation retains the rate applied, its effective date, the source transactions, and the user activity around it — the four things an auditor asks for and the four things spreadsheets lose first.
Recompute history means a figure that changed can be explained: what it was, what it became, when, and what triggered the change.
Statement versions are preserved as issued, so the question "what did you actually report in Q3 two years ago" has an answer that does not depend on anyone's file naming.
Product-to-property mapping history matters as much as the rates. Most findings trace to a SKU attributed to the wrong licensor, and the defence is showing when the mapping was set and what it was at the time of the sale.
Deduction support is per line and per contractual provision, because "why did you deduct this" is the most common challenge and the least well documented in spreadsheet workflows.
Cooperative-mark splits retain both sides of the distribution, so an auditor for one licensor can see that the other portion went where the contract said it should.
Prior-period true-ups are shown as adjustments against the original period rather than folded silently into a later one, which is the treatment most agreements actually require.
What Royalty Reporting tracks
Royalty Reporting calculates, reports, and audits royalties by every dimension finance and licensing teams actually work with — not just the high-level totals.
- Licensor and audit clause terms
- Look-back window
- Reporting periods in scope
- Original calculation and rate applied
- Rate-card version and effective date
- Source transaction lineage
- Product-to-property mapping history
- Deduction lines and contractual basis
- Recompute history
- Statement versions as issued
- Advance and guarantee activity
- Cooperative-mark splits
- User activity log
Frequently asked questions
How far back can a royalty audit look?
It is set by the agreement, and two to three years is common, with some licensors reserving longer. The practical implication is that the evidence for a period has to survive well past the point where the people who produced it remember the detail — which is why the trail has to be captured automatically rather than assembled on request.
What are the most common royalty audit findings?
Under-reported units from SKUs mapped to the wrong property, deductions taken without contractual basis, returns trued up in the wrong period or not at all, advance recoupment double-counted, and cooperative-mark product reported to one licensor but not the other. Almost all of them are attribution or timing errors rather than rate errors.
What does an auditor typically request first?
The statements as remitted for the periods in scope, then the calculation support behind a sample of lines — source sales, the rate applied, the deduction basis, and any adjustments. If the sample reconciles cleanly the scope usually narrows; if it does not, it widens.
How do you defend a figure that has since been restated?
By showing both: the original calculation and statement version as issued, and the recompute history explaining what changed and when. Restatement is normal and expected. What creates exposure is being unable to show what was originally reported or why it moved.
Can audit preparation start before an audit is announced?
It should. Audit windows and notice periods are contract terms, so they can be tracked and surfaced in advance. Teams that treat audit readiness as a continuous property of the data rather than a project triggered by a letter spend materially less time when the letter arrives.
Does this replace an external audit-defence advisor?
No. It changes what they spend their time on. Advisors on royalty audits typically spend a large share of an engagement assembling and reconciling the underlying support before any judgement work begins. Retaining that support automatically moves the engagement toward the interpretive questions where the advice is actually worth paying for.
Go deeper on this workflow.
See royalty audit preparation in practice.
Walk through how Royalty Reporting handles royalty audit preparation against your licensor mix, your rate cards, and your data — in a 30-minute demo with our team.