Key takeaway
Specify what an audit is meant to verify and how evidence will be inspected. A reporting obligation, an audit right and a remedy for a finding do separate jobs.
Define the question before negotiating access
A license can say “audit rights” without explaining what anyone may inspect. Begin with the decision: verify a royalty calculation, confirm a permitted-use representation, investigate a discrepancy, or satisfy another actual duty. Identify the relevant records and what an auditor needs to see. An unrestricted copy of the recipient’s production environment may be unnecessary for one narrow question and inadequate for another.
The UK government’s Model Services Contract v2.2A provides one structured reference. Its core terms distinguish recordkeeping, financial reports and audit rights. Schedule 15 Part C separately addresses purpose, frequency and exceptions, conduct, notice, costs and findings. This is a government services model, not a private data-license default. Its qualified notice and frequency provisions should not be shortened into an unconditional right or obligation.
Use the structure to ask better questions rather than importing its numbers. Which reviewer is allowed? Can evidence be inspected in a controlled environment? How will other customers’ information be protected? Which legitimate or mandatory requests need a different process? Have counsel check the proposed limits against the agreement and any applicable statutory duties.
A completed protocol for a narrow reporting discrepancy
Hypothetical example: a license recipient’s annual usage report disagrees with the relevant billing records. The owner wants to verify the royalty base, not copy the recipient’s full customer database. The fictional protocol below is a negotiation agenda with proposed commercial limits, not a contract template or a statement of legal minimums. Its annual frequency and ten-working-day notice are invented choices for this example, not the government model’s requirements.
A workable protocol should allow the reviewer to inspect the necessary underlying evidence while protecting unrelated information. Merely receiving the same summary again would not resolve the discrepancy. If the limited approach cannot answer the question, the parties need a defined escalation instead of silently widening access.
| Protocol field | Illustrative proposed entry | Review boundary |
|---|---|---|
| Purpose and records | Verify reported royalty base against relevant usage/billing evidence | No general access to unrelated customer records. |
| Reviewer and confidentiality | Named independent reviewer; approved confidentiality undertaking | Confirm competence, conflicts and handling of protected information. |
| Access method | Controlled inspection; report relevant reconciled totals and exceptions | Underlying evidence must be sufficient; no unnecessary production database copy. |
| Routine frequency and notice | One annual routine review; proposed ten working days | Commercial proposal only; misconduct and mandatory-duty exceptions need review. |
| Cost allocation | Ordinary costs and discrepancy-triggered allocation stated separately | Define thresholds, actual charges and dispute handling before use. |
| Findings and remedy | Written discrepancy record, response owner and correction deadline | No automatic inference of fraud or unilateral penalty. |
| Decision | Scope is defined; exceptions and final wording unresolved | Review and approve the actual protocol before granting access. |
Compare the cash effect without ignoring other reasons to audit
For a hypothetical twelve-month license, assume USD 48,000 already received, USD 4,000 preparation cost and a possible USD 1,200 underpayment. The proposed review uses eight internal hours valued at USD 100 per hour plus USD 1,400 external cost: USD 2,200. The internal time is imputed effort, not an assumed additional cash payment. If the full underpayment is verified and actually paid, the incremental contribution after valued time and external cost is USD 1,200 minus USD 2,200, or negative USD 1,000. Considering cash alone under these assumptions, USD 1,200 received minus USD 1,400 external spending is negative USD 200. Overall before-tax contribution after preparation and review is USD 43,000, compared with USD 44,000 before the review.
These invented figures do not prove an audit should be skipped. An audit might address ongoing reporting failure, misuse or another important issue, and a narrower review or negotiated cost allocation may change the economics. Keep monetary recovery, risk reduction and any mandatory duty visible without assigning unsupported values to them. In the original no-deal case, the USD 4,000 spent preparation would remain a negative outcome with no license proceeds; that is separate from this post-payment review.
Record agreed reporting definitions, relevant retention, inspection conditions, finding procedures and who authorizes expanded review. Use offer comparison to assess this alongside the royalty base and deductions, and due diligence to examine whether the recipient can actually produce the evidence. This guide does not set statutory audit rights, a universal retention period, audit prices or enforceable clause language. VOID’s referral process does not perform a license audit or promise that an audit will recover money. Named introduction, sample and licensing decisions remain separate.