Media & ContentFeatured

Royalty Statement Auditor

Checks the statement against the contract that governs it

Version 2Published Sep 2, 2026
Watch it work▶ Try it on your own figures — free

5 of 12 statement lines pay less than the contract rate, a shortfall of $34.1K.

12 lines checked. 5 are short, $34.1K in total. The oldest shortfall ended 273 days ago.

Raise Orbit Foods 2026-03 first. Orbit Foods owes the most.

Net sales are as the licensee states them, so this finds arithmetic and rate gaps, not under-reported sales.

$34.1K
5/12
Lines short
5
12
Shortfall
$34.1K
Oldest (days)
273
Share flagged
42%

Why rows were flagged

5
  • Paid below contract rate80%
  • Sales reported, royalty zero20%

Value flagged by Licensee

  • Orbit Foods$14.4K
  • Atlas Brands$10.2K
  • Pixel Games$6,700
  • Nova Retail$2,800

Statement lines to query, largest shortfall first

ItemLicenseeValueDaysWhy
Orbit Foods 2026-03Orbit Foods$14.4K91Sales reported, royalty zero
Atlas Brands 2026-03Atlas Brands$10.2K91Paid below contract rate
Pixel Games 2026-03Pixel Games$4,00091Paid below contract rate
Nova Retail 2025-09Nova Retail$2,800273Paid below contract rate
Pixel Games 2025-12Pixel Games$2,700181Paid below contract rate

What to do this week

  • Write to the licensee on Orbit Foods 2026-03: royalty paid is below the contract rate.
  • Ask Orbit Foods for a corrected statement and payment for every short period.
  • Chase the oldest periods first: audit and claim windows may be closing.

Do

  • Recalculate royalty from net sales and the contract rate on every statement.

Don't

  • Don't accept a zero royalty line without asking why.

How to improve

  • Add each licensee's audit-rights window so the next report can flag periods about to close.
  • Add gross sales and deductions so the next report can test the net sales figure too.

Demo

Try it now — free

Type your figures (or fill in samples) and get the answer in a minute.

Start from a template

Make it decision-ready

Also include

No card · no API key · your figures are not stored

Overview

Rights holders are paid on statements prepared entirely by the counterparty, from usage data they cannot see, against contract terms nobody re-reads after signature. The statement arrives as a net figure and the practical options are to accept it or commission a formal audit that costs more than most statements are worth.

So almost nobody checks, and the same errors persist for years. They are rarely deliberate — royalty accounting is genuinely complicated and it is usually somebody's third priority.

A rate applied from the wrong contract tier, because an escalation that triggers at a threshold was never applied. A deduction the contract does not permit, or one permitted but capped and applied uncapped. Currency converted at a rate and date the agreement does not specify. Reserves against returns held past the period the contract allows and never released. Territories or formats simply missing — the hardest to catch, because an absent line looks like no activity.

And statements that quietly restate a prior period.

This agent reads each statement against the agreement and reports every line the contract does not support, with the clause behind it. It raises no claim and contacts nobody: an audit clause has notice requirements and a limited window, and invoking one is a legal step.

Benefits

A statement you can actually check

Instead of a net figure to accept.

Errors caught before the window closes

Most agreements limit how far back a claim can reach.

A position before any conversation

With the clause behind every line.

What it does

  • Checks the rate tier was applied

    An escalation that triggers at a threshold and was never applied is the commonest error and the quietest.

  • Tests every deduction against the contract

    Permitted, capped, or not permitted at all. Uncapped application of a capped deduction is routine.

  • Finds reserves never released

    Held against returns, past the period the contract allows, and simply never released back.

  • Checks the currency basis

    Which rate, and on which date. Agreements specify this and statements frequently do not follow it.

  • Finds what is missing

    A territory or format absent from the statement looks like no activity, and it is the hardest error to see.

  • Raises no claim

    An audit clause has notice requirements and a limited window. Invoking one is a legal step, not a report.

What this changes

What this changes about your week

It takes over
Checking a royalty statement against the agreement that governs it.
Done today by
Nobody. The options are to accept it or commission a formal audit.
How often
Every statement, in theory. In practice never.
Typical manual effort
Rate tiers, deductions, reserves and currency basis all have to be read against the contract.

Why Media & Content in particular. The statement is prepared entirely by the party who owes the money, from usage data the rights holder cannot see. A missing territory reads as no activity, which is why it survives for years.

  • Runs unattended

    Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.

  • The same standard every time

    The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.

  • It cannot act on its own

    Royalty Statement Auditor has no path to sending, spending or committing. That limit is why its output is safe to act on.

How it runs

This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.

  1. 1InputValidated against the agent input schema
  2. 2Modelclaude-opus-5 with automatic fallback
  3. 3Toolssearch_knowledge, extract_structured_data
  4. 4PermissionsRuns READ actions automatically; anything higher waits for approval
  5. 5OutputStructured result matching the output schema
  6. 6LoggingTokens, duration and every step recorded

Requirements

Integrations

No integrations required.

Before you start

  • The royalty or licensing agreement, in a knowledge base
  • Statements for the periods under review
  • Prior statements, for restatement checks
  • Your own sales or usage records, where you hold any
  • Requires the All-Access plan or higher

Use cases

Every statement received

Checked while an objection is still open.

Before a formal audit

Whether one is justified, and on which points.

A statement that dropped unexpectedly

Whether it is activity, rate, deduction or an absent line.

Renegotiation

How the current terms have actually been applied.

Pricing

All-Access

Billed monthly through your PROMIVO subscription. Cancel at any time.

Runs consume your plan allowance for agent executions and tokens. See plan limits

FAQ

Does it invoke the audit clause or make a claim?

No. Audit clauses carry notice requirements and limited windows, and invoking one is a legal step with consequences for the relationship. It gives you the findings and the clauses.

Can it verify the underlying usage?

No, and no desk review can. It checks the statement against the contract and against your own records where you have them, and it says plainly that the counterparty's usage data cannot be verified from outside.

Is it legal advice?

No. It reports what the agreement says and what the statement does. Whether a finding is a breach, and what remedy exists, is a question for your own lawyer.

Reviews

Reviews open once customers have run this agent.

Need this agent to work differently?

Tell us what to change and our team will scope a customised version for your business.

Customize this agent