How to Draft and Negotiate Software Licensing Agreements in Belgium (2026): Royalties, Assignments, Open‑source and Key Clauses

Software licensing Belgium sits at the intersection of national copyright rules, EU directives and the practical realities of commercial negotiation, and 2026 brings a sharpened focus on how royalties are classified and how rights are transferred. This guide is written as a working reference for founders, in‑house counsel, SaaS vendors and licensors who need to draft and negotiate licences that hold up both commercially and legally. It walks through eligibility, a step‑by‑step negotiation and drafting workflow, required documents, a realistic timeline, costs, and the 2026 regulatory shifts that affect royalty mechanics and assignment language. Every section is grounded in Belgian and EU primary sources so that each drafting decision can be traced to an authoritative rule.

Where sample wording appears, it is illustrative only and must be adapted by local counsel.

Overview, what this guide covers and who should use it

This is a practitioner’s walkthrough for anyone structuring software licensing Belgium arrangements in 2026. If you are a startup founder packaging a product for sale, an in‑house lawyer negotiating a vendor contract, or a SaaS provider formalising subscription terms, you will find a stepwise drafting checklist, a negotiation timeline, a required‑documents table, sample clauses and a plain analysis of what changed this year.

The guide covers the full lifecycle: confirming ownership, defining the licensed asset, choosing a licence model, structuring royalties, handling assignment and sublicensing, allocating warranties and indemnities, managing open‑source obligations, and building operational and exit provisions for SaaS. It also distinguishes a licence from an assignment, because that single choice drives control, tax treatment and enforceability. In Belgium, copyright in computer programs is governed primarily by Book XI of the Code of Economic Law (Code de droit économique), which implements the EU copyright framework, including the Software Directive (Directive 2009/24/EC) and Directive (EU) 2019/790 on copyright in the Digital Single Market. For wider support, see our Intellectual Property services, Belgium (practice area).

Eligibility, when a software licence is the right tool (versus assignment)

Before drafting, decide whether you need a licence at all. A licence grants permission to use rights while the owner retains them; an assignment transfers the underlying economic rights. The right instrument depends on your commercial goal, your appetite for ongoing control, and the tax consequences of the payment flows.

When to choose a licence versus an assignment

Choose a licence when you want recurring commercial exploitation, a SaaS subscription, a sublicensing programme, or distribution to many customers, while keeping ownership and future freedom to exploit the same asset. Choose an assignment when the transaction is a genuine sale or exit, where the acquirer needs full control of the intellectual property and the seller is prepared to relinquish it.

The legal threshold matters. Under Belgian copyright law, transfers of economic rights must generally be proven in writing and are interpreted restrictively in favour of the author; a vague reference in an invoice or purchase order will not reliably move ownership. A notable exception applies to software created by employees in the course of their duties: under Book XI of the Code of Economic Law, the economic rights in such software are presumed to belong to the employer unless agreed otherwise. For contractors, however, rights do not transfer automatically, so a written assignment is essential. Either way, the chain of title must be clean: the licensor cannot license or assign what it does not own.

For questions of interpretation of copyright and contract, Belgian courts, ultimately the Court of Cassation, and the Court of Justice of the European Union guide how these instruments are read. Where a transaction is really a disposal of the asset, an assignment is appropriate; where it is ongoing use for value, a licence is the correct structure for software licensing Belgium deals.

Step‑by‑step: negotiating and drafting a software licence in Belgium

The following numbered workflow turns the drafting of a software licence agreement Belgium parties can rely on into a sequence of concrete tasks. Each step names the typical owner and feeds the timeline table below.

1. Pre‑transaction review. Verify ownership and chain of title for the software, source code, documentation and all contributor inputs. Check that employee and contractor agreements contain valid assignment clauses so the economic rights sit with the licensor. Identify every third‑party and open‑source component before a single clause is drafted. Owner: in‑house or external IP counsel.
2. Define the licensed asset. Decide precisely what the licence covers, object code, source code, APIs, documentation, data models, training data and deliverables, and list exclusions such as third‑party modules and open‑source libraries. Ambiguity here is the single most common source of later dispute. Owner: licensor counsel.
3. Select the licence model and scope. Choose perpetual versus term; exclusive versus non‑exclusive; territory; field of use; and the permitted number of users or devices. Specify whether the deployment is SaaS or on‑premise, because that changes the operational clauses. Owner: commercial team with counsel.
4. Price it and structure royalties. Select a pricing model, a one‑off fee, a recurring subscription, usage‑based software royalties Belgium vendors increasingly favour, or a revenue share. Draft the royalty formula, the reporting cadence, payment mechanics, currency, late fees and audit rights. Clear, deterministic formulas are essential after the 2026 changes discussed below. Owner: commercial and finance with tax counsel.
5. Address assignment, sublicensing and transferability. State whether the licence is assignable, whether consent is required, and what happens on a change of control. Most licensors withhold the right to assign and restrict sublicensing; a well‑drafted change‑of‑control clause gives both sides certainty in an M&A scenario. Owner: counsel.
6. Allocate warranties, IP indemnities and liability. Tailor warranties for title, non‑infringement and performance, with explicit carve‑outs for open‑source components. Define the indemnity scope and cap liability proportionately; uncapped indemnities are a frequent negotiation trap. Owner: counsel with risk and commercial teams.
7. Handle open‑source obligations. Define notice requirements, redistribution obligations and copyleft risk. Where the engineering team contributes to or redistributes open‑source code, add a contributor agreement and set a corporate policy. This step relies directly on the software bill of materials prepared in step one. Owner: engineering with counsel.
8. Add data protection and security terms (for SaaS). Include data processing terms, subprocessor rules, security standards, breach notification and portability or escrow arrangements. If the service processes personal data on the customer’s behalf, a GDPR‑compliant data processing agreement under Article 28 GDPR is mandatory. Owner: DPO with counsel.
9. Draft operational and exit clauses. Set service levels, remedies for downtime, exit assistance and, where the licensee’s continuity depends on the software, code escrow with defined release triggers. Owner: product with counsel.
10. Execute, record and enforce. Arrange signatures, archive the executed documents, make any applicable filings, and schedule periodic royalty reporting and audits. Owner: legal operations.

Royalties and pricing mechanics in software licensing Belgium deals

Royalty design deserves particular care. For usage‑based SaaS, anchor the royalty to clear, measurable metrics, monthly active users, seats, API calls or compute, and express the calculation as a deterministic formula rather than a narrative. Define the reporting cycle, the currency and payment timing, a cap and a minimum where relevant, and a right to audit the licensee’s records. The classification of the payment as a royalty rather than a service fee affects how it is treated for VAT and withholding tax, so involve tax advisers early and, for cross‑border flows, obtain a written opinion. This is the area where 2026 developments bite hardest, as explained further down.

Step, owner and duration timeline

SaaS‑specific operational clauses

SaaS agreement Belgium drafting adds a layer the on‑premise model does not. Service levels must be measurable and tied to credits or termination rights; data protection terms must identify subprocessors and set breach notification timeframes; and the contract should address what happens at the end of the relationship. Termination, data escape and portability deserve a dedicated clause so the licensee can retrieve its data in a usable format and avoid lock‑in. For mission‑critical deployments, pair exit assistance with a code escrow arrangement that releases source code on defined triggers such as licensor insolvency or discontinued support. These provisions turn a software licence agreement Belgium customers sign into one they can safely depend on.

Required documents, the transaction file

Assemble the following before and during negotiation. A complete file speeds diligence and strengthens your warranties.

Note that copyright in software arises automatically on creation and is not subject to a national registration system in Belgium, so there is no official copyright register to file in. Registration considerations arise only where related rights, such as trade marks or patents, are involved.

Timeline and deadlines, a typical negotiation and execution schedule

A straightforward licence can move from first draft to signature in roughly four to six weeks; a complex SaaS arrangement with heavy data protection and open‑source review commonly runs eight to twelve weeks. The pre‑transaction review and title search take one to two weeks, scoping a further week, and drafting of commercial terms one to two weeks. Negotiation and redlining is the most variable stage at two to six weeks. Security, data protection and open‑source compliance review can run concurrently over one to three weeks. Final sign‑off typically takes three to seven days, with SaaS onboarding adding one to four weeks after execution.

Software licences do not require a mandatory public filing in Belgium, so there is rarely a statutory deadline. Where a transaction involves a registered right (such as a trade mark or patent) and an assignment that must be recorded, factor in administrative processing time and confirm the current requirements with the Benelux Office for Intellectual Property (for Benelux trade marks and designs) or the relevant patent office. Build royalty reporting dates and audit windows into the contract itself so post‑execution compliance has fixed, enforceable milestones.

Costs and fees, legal, registration and tax considerations

Budget realistically. The figures below are illustrative ranges only and will vary significantly by complexity, firm and transaction; obtain tailored estimates and VAT advice before committing.

On tax, the central distinction is between a royalty for the use of intellectual property and a fee for services, because the two can attract different VAT and withholding treatment, particularly on cross‑border payments. The substance of the arrangement, not merely its label, determines the outcome. For guidance on IP administration and policy context, consult the FPS Economy, and for the tax characterisation of any particular royalty flow obtain a written opinion from a Belgian tax adviser, taking account of applicable double‑tax treaties.

For help finding counsel, the relevant Belgian bar associations (such as the Ordre des barreaux francophones et germanophone and the Orde van Vlaamse Balies) publish directories, and you can also find an IP lawyer in Belgium through the GLE directory.

What changed in 2026, the regulatory update for software licensing Belgium

The 2026 picture for software licensing Belgium is shaped less by a single new statute than by the maturing application of the EU copyright framework to software and digital services, combined with heightened scrutiny of how royalty payments are characterised for tax purposes. The authoritative starting points are Book XI of the Code of Economic Law, the guidance of the FPS Economy on intellectual property, and, at EU level, the Software Directive (Directive 2009/24/EC) and Directive (EU) 2019/790 on copyright in the Digital Single Market, whose principles continue to inform how member states treat digital exploitation and the fair remuneration of rightsholders.

Of particular note in Belgium is the ongoing reform of the favourable tax regime for copyright income (the régime fiscal des droits d’auteur), which was significantly restricted by the Programme Act of 26 December 2022 and whose scope, especially its application to software developers and IT professionals, has been the subject of continuing debate and administrative and constitutional litigation into 2025 and 2026. Any specific position on whether software‑related income qualifies for the copyright tax regime should be verified directly against the current wording of the Income Tax Code, FPS Finance circulars and recent case law before it is relied upon in a contract.

Where an implementing Royal Decree exists, the operative text is the one published officially in the Moniteur belge, not secondary commentary, and that is the source to cite.

The Court of Justice of the European Union continues to issue judgments that shape how software copyright and licensing terms are interpreted across the single market, and the Belgian Court of Cassation provides the authoritative domestic reading of copyright and contract questions.

The practical effect for drafters is threefold. First, royalty clauses benefit from being more explicit than before: a deterministic formula, a defined reporting cadence and a clear statement of what the payment is consideration for all reduce the risk of reclassification and dispute. Given continued regulatory attention to the royalty‑versus‑fee distinction, precise drafting is a practical hedge. Second, assignment language should leave no doubt that economic rights are transferred where that is the intention, with contributor assignments confirmed in the chain of title. Third, open‑source and data protection obligations should be documented with the same rigour as commercial terms, because compliance failures in these areas are increasingly treated as material.

Contracts drafted loosely in prior years may need review, and counterparties are increasingly asking for tighter royalty and audit provisions. When citing the 2026 position in your own documents, link to the official Moniteur belge entry, the FPS Economy or the FPS Finance announcement rather than to social media or community discussion.

Common pitfalls and negotiation traps

• Vague licence scope. Leaving users, territory or field of use unspecified invites disputes and erodes the value of the grant. Define every dimension explicitly.
• Unmanaged open‑source components. Failing to identify open‑source licence Belgium obligations through an SBOM can trigger copyleft virality or redistribution breaches that contaminate proprietary code.
• No audit or reporting rights. Without the ability to verify usage, a royalty formula is difficult to enforce in practice; build in reporting and audit from the outset.
• Missing code escrow. For critical SaaS, the absence of escrow leaves the licensee exposed if the licensor fails or discontinues support.
• Misclassified payments. Treating a royalty as a service fee, or vice versa, can produce unexpected VAT and withholding consequences.
• Unconfirmed contractor assignments. A gap in the chain of title means you may be licensing rights you do not own; remember that, unlike employee‑created software, rights in contractor work do not transfer automatically.
• Overbroad indemnities or weak liability caps. Unbalanced risk allocation is a frequent sticking point and a source of later litigation.

Comparison: assignment versus licence

Prefer an assignment when the deal is a disposal and the buyer needs unqualified control. Prefer a licence when value flows from continued use, where retaining ownership preserves your ability to exploit the same asset elsewhere.

Sample clauses and a drafting checklist

Sample, for illustrative purposes only. Each clause must be adapted and reviewed by local counsel before use.

• Scope. “Licensor grants Licensee a non‑exclusive, non‑transferable licence to use the Software in object‑code form within [Territory] solely for [Field of Use], limited to [number] authorised users.”
• Royalty formula. “Licensee shall pay a royalty equal to [rate] per [metric: seat / MAU / API call] per [period], subject to a minimum of EUR [amount] and a cap of EUR [amount], reported within [X] days of each period end.”
• Audit right. “Licensor may, on [X] days’ notice and no more than once per year, audit Licensee’s records relevant to royalty calculation; underpayments exceeding [threshold] shall bear the reasonable cost of the audit.”
• Assignment restriction. “Licensee shall not assign this Agreement, in whole or in part, without Licensor’s prior written consent, save that a change of control shall require [consent / notice] as set out in Clause [X].”
• Open‑source indemnity carve‑out. “Licensor’s warranties of non‑infringement do not extend to open‑source components listed in Schedule [X], which are provided subject to their respective licences.”
• Code escrow. “The Parties shall deposit the Source Code with [Escrow Agent]; release shall occur only on the Release Events defined in the Escrow Agreement, including Licensor insolvency or cessation of support.”
• Sublicensing. “Licensee may sublicense only to the extent expressly permitted in Schedule [X] and on terms no less protective of Licensor’s rights than this Agreement.”
• Data protection (SaaS). “The Parties shall comply with the Data Processing Agreement at Schedule [X], which governs processing, subprocessors, security measures and breach notification in accordance with Article 28 GDPR.”

Use the checklist as a final pass: ownership confirmed, asset and scope defined, royalty formula deterministic, reporting and audit rights present, assignment and sublicensing addressed, warranties and caps balanced, open‑source obligations documented, data protection covered, and escrow and exit provisions in place.

Next steps

Getting software licensing Belgium right in 2026 means grounding every royalty, assignment and open‑source decision in primary sources and documenting it precisely. If you need help drafting or negotiating a software licence for Belgium, consult a qualified Belgian IP lawyer for a tailored review. This article is for informational purposes only and is not legal advice.

Sources

1. FPS Economy, Intellectual Property (Belgium)
2. Belgian Official Gazette / e‑Justice (Moniteur belge)
3. Benelux Office for Intellectual Property (BOIP)
4. EUR‑Lex, Directive (EU) 2019/790 on Copyright in the Digital Single Market
5. EUR‑Lex, Directive 2009/24/EC on the legal protection of computer programs
6. Court of Justice of the European Union (Curia)
7. FPS Finance (Belgium)
8. KU Leuven, Centre for IT & IP Law (CiTiP)