Belgium 2026, What Tech Start‑Ups Need to Know About the Return of the Copyright Tax Regime for Software

The copyright tax regime Belgium software 2026 landscape has shifted decisively: the Programme Bill deposited on 17 December 2025 reintroduces computer programs into the scope of Belgium’s favourable copyright income tax regime, effective for income year 2026. For tech start‑ups, this reversal reopens a tax incentive for software developers in Belgium that was effectively closed to the IT sector under the 2023 reform, but capturing the benefit demands careful contract structuring, rigorous evidence and a clear understanding of the new rules around flat‑rate deductions. This guide provides the practical, lawyer‑level playbook that founders, general counsel and CFOs need to act on the change: from eligibility tests and sample assignment clauses to documentation checklists and advance‑ruling strategy.

• Software is back in scope. Computer programs qualify again for the copyright tax regime from 1 January 2026.
• Flat‑rate deductions largely abolished. Most taxpayers can no longer apply lump‑sum cost deductions, real expense evidence is now required (artists’ certificate holders excepted).
• 15 % withholding tax applies. Qualifying copyright remuneration is taxed as movable income at 15 % (précompte mobilier), rather than at progressive personal income tax rates plus social security.
• Contracts must be restructured now. Existing developer agreements, employment addenda and freelancer terms need explicit copyright assignment or licence clauses to support claims.
• Evidence is everything. Source‑code commit histories, statements of authorship and time‑allocation records should be created and retained from 1 January 2026 onward.
• Advance rulings reduce risk. Start‑ups with borderline eligibility or high‑value arrangements should apply to Belgium’s Service for Advance Decisions (SDA) for certainty.
• Patent vs copyright choice matters. The copyright route delivers a direct tax benefit; patents offer broader protection but different fiscal treatment, the two are not mutually exclusive.

What Changed in 2026, Scope and Effective Dates Under the Belgian Copyright Tax Regime 2026

The 2023 reform of Belgium’s copyright income provisions had narrowed the scope of the favourable tax treatment so significantly that most software developers and IT professionals were, in practice, excluded. Computer programs were no longer recognised as eligible works under the regime, effectively ending an era of widespread copyright‑based remuneration in the tech sector. The Programme Bill deposited before the Belgian Chamber on 17 December 2025 reverses that exclusion: it explicitly re‑admits computer programs into the list of protected works whose transfer or licensing can give rise to favourably taxed copyright income for income year 2026.

Alongside the scope expansion, the same legislative package abolishes the flat‑rate cost deductions that most copyright‑income recipients previously relied upon. From 2026, only holders of a recognised artists’ certificate may continue to apply flat‑rate deductions; all other taxpayers must evidence actual costs. This dual change, broader eligibility but stricter substantiation, defines the compliance challenge for start‑ups.

Legislative Timeline and Critical Dates

What the Change Means Practically for a Start‑Up

• Any payment to a developer (employee, contractor or founder) that constitutes remuneration for the assignment or licensing of copyright in original software can potentially be taxed at 15 % rather than progressive rates.
• The company paying the remuneration may deduct it as a business expense, provided the arrangement is genuine and properly documented.
• Without written assignment or licence agreements, timestamped evidence of authorship and a methodology for separating creative work from non‑creative tasks, the tax benefit is vulnerable to reclassification on audit.
• Industry observers expect Belgian tax authorities to scrutinise IT‑sector claims carefully, given the history of abuse that prompted the 2023 restrictions.

How the Copyright Tax Regime Works for Software, Legal Tests and Thresholds

Under the Belgian copyright tax regime for software in 2026, qualifying income is treated as movable income and subject to a 15 % précompte mobilier (withholding tax). This replaces the progressive personal income tax rates, which can reach above 50 % including municipal surcharges, and exempts the income from social security contributions. The economic advantage for individual developers can therefore be substantial, but only where the legal conditions are satisfied.

The Originality Test

Belgian copyright law, codified in Book XI of the Code of Economic Law (Code de droit économique / Wetboek van economisch recht), protects literary and artistic works, including computer programs, provided they are original. Originality, under both Belgian and EU law, means the work must be the author’s own intellectual creation, reflecting personal creative choices. For software, this means the code must go beyond purely functional or mechanical output: the developer’s architectural decisions, algorithm design, interface logic and code structuring must evidence creative freedom. Routine configuration, parameterisation or data entry is unlikely to meet the threshold.

The FPS Economy’s official copyright FAQ reinforces that a work must satisfy the originality criterion under Book XI to qualify; the tax regime cannot apply to remuneration for activities that do not produce a copyrightable output.

Quantitative Ceilings and the 70/30 Framework

The regime applies an annual ceiling on the amount of copyright income that can benefit from the 15 % rate. The precise indexed amount for 2026 should be confirmed against the latest official publication, but the framework continues to operate on the basis that copyright remuneration must not exceed a set threshold and should represent a reasonable proportion of total compensation. The commonly referenced 70/30 guideline, where no more than roughly 30 % of total remuneration is treated as copyright income, remains a practical reference point, although it is not codified as a rigid statutory rule. Taxpayers exceeding the ceiling or the proportionate benchmark face reclassification of the excess as ordinary professional or employment income.

Worked Example: Salary vs Copyright Payment

Consider a developer with total annual compensation of €80,000. The start‑up structures €50,000 as salary and €30,000 as copyright remuneration for the assignment of rights in original code. Under the copyright tax regime, the €30,000 is subject to 15 % withholding (€4,500 tax), rather than progressive rates that could result in an effective marginal rate well above 40 %. Critically, however, the developer can no longer apply a flat‑rate deduction to that €30,000 unless they hold an artists’ certificate; actual expenses must be documented. If no real costs are evidenced, the full €30,000 is taxable at 15 % without further reduction.

Who Qualifies, Entities, Employees, Contractors and Compensation Types

The copyright tax regime Belgium software 2026 rules apply to individuals who are the original authors of copyrightable software and who transfer or license their rights to a third party (typically their employer, a client company, or their own company). Understanding which relationships and payment structures qualify, and which are likely to attract scrutiny, is essential for compliance.

Reporting and Tax Treatment by Payer Type

Likely Accepted vs Borderline Works

• Likely accepted: Original application source code, bespoke algorithm implementations, creative UI/UX design code, proprietary database architectures, original game engines.
• Borderline or unlikely: Routine system administration scripts, standard configuration files, parameterisation of off‑the‑shelf software, data migration scripts with no creative choices, purely mechanical code generation.

The practical test asks: did the developer exercise creative freedom and make intellectual choices that could have been made differently? If yes, the output is likely copyrightable. If the task was purely mechanical or dictated entirely by functional constraints, it is not.

Practical Steps to Qualify, Contracts, Assignments and Licences for the Copyright Tax Regime Belgium Software 2026

This is the implementation core of the Belgian copyright tax regime 2026 for tech start‑ups. The following step‑by‑step checklist and sample clause snippets provide a framework for restructuring developer relationships. Each step should be adapted to the start‑up’s specific circumstances with the assistance of qualified Belgian IP and tax counsel.

Implementation Checklist (12 Steps)

1. Audit existing developer relationships. Map every person (employee, contractor, founder) who creates software and identify which outputs are potentially copyrightable.
2. Assess originality per role. For each developer, document the creative choices involved in their work, this is the foundation of any copyright claim.
3. Draft or amend written assignment/licence agreements. Every copyright payment must be backed by a signed agreement that specifies the work, the rights transferred, the territory, the duration and the remuneration.
4. Separate copyright remuneration from salary. The copyright payment must appear as a distinct line item, not simply a relabelling of existing salary.
5. Apply a defensible allocation methodology. Document how the proportion of creative work vs non‑creative work was determined (time tracking, project classification, job descriptions).
6. Ensure scope covers reproduction and public communication. The assignment or licence must convey rights that fall within the scope of copyright exploitation (e.g., the right to reproduce, distribute or communicate the software to the public).
7. Address moral rights. Under Belgian law, moral rights cannot be fully waived but the author can agree not to exercise certain moral rights in specified contexts, include appropriate language.
8. Create a statement of authorship annex. Each developer should confirm in writing that they are the original author of the works described.
9. Establish a contribution log. For contractors and freelancers, require regular delivery notes that describe the creative outputs and link them to invoices.
10. Review cap‑table and investor implications. If a founder assigns IP to the company for copyright remuneration, confirm that the arrangement is reflected in the shareholders’ agreement and does not create conflicts with investors’ expectations regarding IP ownership.
11. Set up withholding and reporting. The payer must withhold 15 % précompte mobilier on copyright payments and report them on the relevant tax filings (fiche 281.45).
12. Consider an advance ruling (SDA). For high‑value or complex arrangements, apply for a binding advance decision to confirm eligibility before the first payment.

Sample Clause Snippets for Copyright Assignment Belgium

The following are illustrative clause outlines. They are not a substitute for tailored legal drafting and must be adapted to the specific facts, applicable law and commercial context of each arrangement.

• (i) Copyright assignment, broad form. “The Author hereby assigns to the Company, on an exclusive basis, all patrimonial rights in the Works (as defined in Schedule 1), including the right to reproduce, adapt, translate, distribute and communicate the Works to the public, in any form and by any means, for the entire duration of copyright protection, worldwide.”
• (ii) Licence for exploitation, territory and duration. “The Author grants to the Company a non‑exclusive licence to exploit the Works in the territory of the European Economic Area for a period of [X] years from the date of delivery, renewable by mutual written agreement.”
• (iii) Moral rights clause. “The Author undertakes not to exercise their moral rights in a manner that would impede the Company’s reasonable commercial exploitation of the Works, including the right to make technical modifications necessary for the intended use of the software.”
• (iv) Developer invoice / statement of authorship annex. “The Contractor confirms that each deliverable invoiced under this Agreement constitutes an original work of which they are the sole author, created through their personal intellectual effort and reflecting their own creative choices.”
• (v) Founder vesting and assignment confirmation. “Upon each vesting date, the Founder confirms the irrevocable assignment to the Company of all patrimonial copyright in the software developed during the preceding vesting period, as described in the attached Contribution Log.”
• (vi) Contractor originality and contribution log. “The Contractor shall maintain and deliver monthly a Contribution Log describing: (a) the creative outputs produced; (b) the design and architectural choices made; (c) the hours allocated to copyrightable creative work vs non‑creative tasks. The Contribution Log shall accompany each invoice.”

Red Flags and Reclassification Risks

• No real transfer of rights. If the developer retains full control over the code and the company does not exploit the rights, the payment may be reclassified as salary.
• Disproportionate allocation. Treating 100 % of a developer’s compensation as copyright income when a significant portion of their time is spent on non‑creative work (meetings, project management, testing) invites reclassification.
• Missing or vague agreements. Oral understandings or generic “IP assignment” clauses that do not specify the works, rights, territory and duration are insufficient.
• Employee vs contractor misclassification. Using the copyright regime does not change the employment‑law analysis. A software licensing Belgium structure layered on top of a de facto employment relationship creates both labour‑law and tax risk.
• Equity‑for‑IP pitfalls. Issuing shares in exchange for IP without establishing a market‑value remuneration creates valuation and tax problems on both sides.

Evidence and Documentation, What to Keep and How to Calculate Remuneration

With flat‑rate deductions abolished for most taxpayers under the copyright tax regime Belgium software 2026 rules, the burden of proof shifts squarely to the taxpayer. Start‑ups must build and maintain a documentary record that supports every copyright payment from 1 January 2026 onward. The likely practical effect will be that insufficiently documented arrangements are the first to be challenged on audit.

Evidence Checklist

• Signed assignment or licence agreement. The legal foundation, without it, no copyright income treatment is defensible.
• Statement of authorship. A written declaration by the developer confirming original creation.
• Source code commit history (timestamped). Git logs, version control records and deployment histories that demonstrate who wrote what and when.
• Task briefs and acceptance records. Documentation showing the scope of creative work requested and delivered.
• Design documents and architectural decisions. Evidence of the creative choices that distinguish the code from mechanical output.
• Time‑allocation records. Logs showing the proportion of time spent on copyrightable creative work vs administrative or non‑creative tasks.
• Invoices with copyright references. Each invoice should identify the works, the applicable agreement, and the copyright remuneration amount.
• Payroll or withholding reconciliation. Records showing the 15 % précompte mobilier was correctly withheld and reported.
• Receipts for actual costs. Where the developer claims real expense deductions, supporting receipts (hardware, software licences, workspace costs) must be retained.

Sample Evidence Log

Calculating the Copyright Remuneration Split

There is no single mandatory formula, but a defensible methodology typically involves: (1) classifying the developer’s tasks into copyrightable creative work and non‑creative activities; (2) tracking time allocation per category over a reference period; (3) applying the proportional split to total compensation; and (4) verifying the result falls within applicable ceilings and the proportionate benchmark. The methodology should be documented in a written policy, applied consistently and reviewed at least annually. Early indications suggest that authorities will favour methodologies validated through an advance ruling.

Patent vs Copyright for Software, Strategic Decisions

The return of software copyright Belgium to the favourable tax regime does not mean copyright is always the right, or the only, IP strategy for startups in Belgium. Patents and copyright protect different aspects of software innovation, and the two can coexist.

Four‑Point Decision Matrix

1. Prioritise copyright when the primary value lies in the code itself (custom applications, SaaS products) and the immediate tax benefit outweighs the need for broader method protection.
2. Pursue a patent when the software implements a novel technical solution to a technical problem and competitors could independently develop functionally equivalent code.
3. Combine both when the innovation has both distinctive code expression and a novel technical method, copyright for the tax regime, patent for defensive or licensing leverage.
4. Add trade secrets for algorithms, training data or internal processes that are not disclosed in published code and where secrecy provides competitive value.

An effective IP strategy for startups Belgium should address all three dimensions, copyright, patents and trade secrets, and align the choice with both commercial objectives and the tax structuring opportunity that the 2026 reform creates. For broader context on intellectual property protection strategies across jurisdictions, start‑ups should consider how the Belgian framework fits within their international IP portfolio.

How to Apply for Rulings and Manage Audit Risk

Belgium’s Service for Advance Decisions (SDA, Service des Décisions Anticipées / Dienst Voorafgaande Beslissingen) provides a mechanism for taxpayers to obtain a binding advance ruling on the tax treatment of a proposed arrangement. For start‑ups implementing the copyright tax regime Belgium software 2026 rules, an advance ruling is the most effective tool for reducing reclassification risk, particularly where the arrangement involves high‑value payments, borderline originality assessments or unusual structures such as founder‑to‑company assignments.

What to Include in a Ruling Request

• A detailed description of the proposed arrangement, including the parties, the works, and the payment structure.
• Copies of draft assignment or licence agreements.
• The allocation methodology with supporting time‑tracking data or task classification.
• Evidence of the originality of the software (design documents, architecture diagrams, sample code).
• The proposed valuation method for the copyright remuneration.
• A summary of the legal basis relied upon (relevant articles of the Income Tax Code, CIR92, and Book XI of the Code of Economic Law).

Industry observers expect typical SDA processing times of several months, so start‑ups should initiate applications well ahead of the first copyright payment. The ruling, once granted, provides certainty for the period and facts covered, but must be adhered to precisely. Any material deviation from the facts presented voids the ruling. Start‑ups should consider engaging a qualified Belgian IP or tax lawyer to prepare and submit the application.

Conclusion, Immediate Steps for Tech Start‑Ups Under the Copyright Tax Regime Belgium Software 2026

The return of software to Belgium’s copyright tax regime represents a significant opportunity for tech start‑ups to reduce effective tax rates on developer compensation, but only where the legal, contractual and documentary foundations are in place. Three actions should be taken immediately: first, review and restructure all developer contracts, employment addenda and freelancer agreements to include explicit copyright assignment or licence clauses that satisfy Belgian requirements; second, establish a documentation and evidence protocol, including contribution logs, time‑allocation records and source‑code archives, effective from 1 January 2026; third, where the arrangement involves material amounts or any element of uncertainty, apply for an advance ruling with the SDA to lock in certainty before the first payment is made.

Developing a sound IP strategy for startups in Belgium means aligning these tax‑driven structures with broader commercial and protection objectives, ensuring that the copyright tax regime works as a complement to, not a substitute for, a robust intellectual property portfolio.

This article is general information and does not constitute legal or tax advice. Readers should consult a qualified Belgian IP and tax lawyer for guidance tailored to their specific circumstances. Last reviewed: 28 April 2026.

Sources

1. KPMG Belgium, Favourable tax regime for copyright in the IT sector
2. EY Belgium, Personal Income Tax reform: copyright compensation status update
3. Bird & Bird, Belgian copyright tax regime: two key reform proposals
4. Belgian Chamber, Parliamentary document (Programme Bill references)
5. FPS Economy, Belgian official copyright FAQ
6. Simont Braun, Copyright income and software development (2026)
7. Tentoo, Practical explanation of 2026 copyright rules
8. Securex, The copyright scheme will reopen to the computer field in 2026