Royalty audit: stages and deadlines
A royalty audit lets a licensor verify that a licensee's payments match actual sales or usage under an IP licence. The process runs in four stages: notice, document exchange, review, and findings. Deadlines come almost entirely from the licence agreement itself, not from statute, so the clock starts the day the audit notice is served.
What happens, in order
Most licence agreements describe the audit as a contractual right, not a court procedure. That has a practical consequence: the stages below are typical, but the exact sequence and every deadline inside it depend on the wording of the clause you signed. Read that clause before you read this page.
- Notice. The licensor sends written notice naming the audit period, the scope of records, and the proposed start date.
- Document request. The licensee produces sales ledgers, invoices, distribution and sub-licensing agreements, and any prior audit correspondence.
- Review. An auditor, often external and bound by confidentiality, checks the records against the royalty statements already submitted.
- Findings and response. The auditor issues a report; the licensee has a set window to comment before the figures are treated as final.
How to start
Serve written notice under the audit clause. State the period under review, name the auditor, and confirm confidentiality terms in the same letter. Attach the list of records you expect to see, so the other side cannot claim ambiguity later.
- Confirm who bears the audit cost if the clause splits it by outcome.
- Fix the review window in calendar days, not "reasonable time".
- Ask for records in a stated format; unreadable exports restart the clock.
Where the underlying right involved a prior transfer of ownership, the audit trail usually needs to reach back to that transfer. How transfer of results on termination ownership of results sets out which documents a receiving party should have kept from that point.
Who decides disputes
An audit rarely reaches a court on its own. The report either settles the gap by agreement, or the disagreement moves to whatever forum the licence names: arbitration, expert determination, or the courts named in the governing-law clause. The forum decides, not the auditor; the auditor's report is evidence, not a ruling.
| Stage | Typical duration | Who acts |
|---|---|---|
| Notice to document handover | 2–4 weeks | Licensee |
| Desk or on-site review | 2–8 weeks | Auditor |
| Draft findings to final report | 1–3 weeks | Auditor and both parties |
| Response window before figures stand | Set by clause, commonly 2–4 weeks | Licensee |
These ranges come from how audit clauses are usually drafted; your contract may set shorter or longer windows, and only your contract controls.
If the case differs
Not every licence follows the pattern above. Three variations come up often enough to name.
- No audit clause at all. Without a contractual right, the licensor has no procedure to fall back on and must negotiate access or plead a separate breach.
- Licensee refuses access. Refusal past the notice deadline is usually treated as a breach in itself, independent of what the audit would have found.
- The licence sits inside a wider relationship that is ending. Where a franchise or distribution relationship is also winding down, the audit and the exit run on separate but overlapping clocks; see A franchise partner leaves with the sign trade mark for how those two clocks interact.
Royalties tied to on-chain usage or token issuance raise a different question: what counts as a reportable event in the first place. Mint tokenised rights defines the trigger that audit clauses in these licences usually reference.
What this page does not cover
This page describes the procedure, not the substance of any dispute it may uncover. It does not tell you how a shortfall is calculated, what interest applies to underpaid royalties, or how a cross-border enforcement claim proceeds once the audit is finished. Those are separate questions and depend on the governing law chosen in your licence.
We also do not cover the audit's interaction with data protection duties when personal data appears in usage logs; that sits outside this procedure and outside this page.
Verified
This page reflects how royalty audit clauses are typically drafted and applied in IP licences we review, checked against current file practice. It does not cite statute or case law, because no audit procedure of this kind is set by statute: the clause you signed is the only binding source. Personal data handled during an audit falls under our standard notice; see Privacy notice: two roles, two bases for how we separate the two roles involved.
FAQ
How long does a royalty audit take in practice?
Most audits run eight to twelve weeks from notice to final report, but the clause you signed sets the real deadlines. Complex sub-licensing chains extend the review stage; simple single-territory licences shorten it.
Which documents are needed to start?
Sales ledgers, invoices, the licence and any sub-licence agreements, and prior royalty statements for the period under review. State the format you expect before the licensee assembles them.
What happens if the other side does not respond?
Silence past the notice deadline is usually treated under the licence as a refusal, which most clauses convert into a separate breach. Check whether your clause requires a further reminder before that conversion applies.
Related publications
Termination and wind-down covers what happens once the licence itself, rather than a single audit, comes to an end.