Royalty enforcement: stages and deadlines
Royalty enforcement for tokenised rights runs through four stages: notice, internal escalation, a formal claim, and execution. Each stage carries its own deadline, set by the paying platform's own terms or by the forum handling the dispute rather than by a single fixed rule. Which forum applies varies by register and jurisdiction; our Coverage map: 40 jurisdictions, 13 register families in detail lists where enforcement routes differ. The full cycle can run from a few weeks to several months, depending on how quickly the counterparty responds.
What changes once enforcement starts
Before notice is sent, a missed royalty payment is a private disagreement. Once formal notice goes out, the clock on the response window starts running, and that window is usually fixed by the platform's own dispute policy rather than negotiated case by case. Missing that window does not end the claim, but it removes the option of a quick internal resolution and pushes the matter towards a formal claim.
The practical risk is timing, not entitlement. A rights holder who waits too long to escalate loses leverage inside the platform's own process and is left with the slower, external route as the only option.
What to do
- Collect the royalty schedule, the payment history, and the smart contract terms — the rights holder's finance or operations team.
- Send a formal notice identifying the shortfall and the period in dispute — counsel or the designated in-house handler.
- Record the date notice was sent and set an internal reminder for the response window — whoever manages the file.
- Escalate to the platform's dispute desk if there is no response within that window — the assigned handler.
- Prepare the formal claim package once internal escalation has run its course — counsel.
- File with the competent forum identified in the underlying agreement — counsel, within the forum's own filing deadline.
Who decides
| Stage | Who decides | Timing |
|---|---|---|
| Notice | Rights holder or counsel | Sent as soon as a shortfall is confirmed |
| Internal escalation | Platform's dispute desk | Set by the platform's own dispute policy |
| Formal claim | Court or arbitral tribunal named in the agreement | Set by that forum's own procedural rules |
| Execution | Enforcement authority where the debtor's assets sit | Depends on asset location and cooperation between registers |
No single body owns the whole process. Each stage hands off to a different decision maker, and the deadline for one stage does not extend automatically into the next.
Forks
If the paying party is a supervised platform, a regulatory complaint channel may run alongside the civil claim, without replacing it. If the smart contract already enforces the payment split automatically, the dispute is not about execution at all but about the underlying entitlement — a different question with a different starting point. If a burn event has altered the token's supply before enforcement began, the entitlement itself may have shifted; see A burn changes the supply token issuance who decides. If issuer, custodian, and paying platform sit in three different jurisdictions, the timing of the whole enforcement chain follows the slowest of the three forums, not the fastest.
What this page does not decide
This page sets out the stages and the deadlines that attach to each one. It does not size a claim, calculate a royalty split, or estimate the probability of a successful outcome — those depend on facts specific to the agreement and the register involved.
Royalty enforcement often surfaces a question that should have been settled earlier: was the underlying asset properly licensed in the first place. An Asset report before a licence is signed answers that question on its own track.
The same dispute looks different from the paying side. A Debtor report before writing off covers how far an obligation can be reduced before enforcement becomes the only remaining option.
Verified
Verified: 4 March 2025. This page describes the stages and deadlines that apply to royalty enforcement in general terms. No statutory article or regulation is cited by design: the applicable procedure depends on the paying platform's own terms and on the forum named in the underlying agreement, not on a single fixed rule that could be listed here.
Related publications
Royalty disputes often follow a custody question that was left open earlier in the same relationship. See How custody and control review tokenised rights runs in.
FAQ
How long does royalty enforcement take in practice?
The full cycle, from notice to execution, commonly runs from a few weeks to several months. The exact length depends on the platform's own response window and on which forum ultimately hears the claim.
Which documents are needed to start?
A rights holder needs the royalty schedule, the payment history showing the shortfall, and the underlying agreement or smart contract terms. Without these three, a formal notice has nothing concrete to point to.
What happens if the other side does not respond?
Silence within the response window moves the matter to internal escalation, and from there to a formal claim if escalation also produces no result. Non-response does not pause any deadline; it simply removes the option of an early, informal resolution.