Software Development Agreement Ireland: What to Include (2026)

Last updated October 2026. General information only, not legal advice.

Commissioning software is one of the few purchases where, unless the contract says otherwise, you can pay the full price and still not own what you paid for: under Irish copyright law the developer who writes the code owns it, not the client. That rule is the reason a written software development agreement matters, but it is far from the only thing it needs to cover. This guide explains what to include in a software development agreement in Ireland, from IP ownership and acceptance testing to data protection and the EU rules that now reach software. The Software Development Agreement template is a self-complete document that follows this structure.

Who owns the code? Copyright in software

The Copyright and Related Rights Act 2000 treats a computer program as a literary work, including its preparatory design material. Copyright arises automatically on creation; there is no registration system in Ireland. Section 17(3) makes clear that protection does not extend to the ideas and principles underlying the program, only to its expression.

Section 23(1) provides that the author is the first owner of copyright, with one key exception: a work made by an employee in the course of employment belongs to the employer. There is no equivalent exception for contractors. So where you engage an agency, a freelancer or an offshore team, the code they write belongs to them unless and until it is assigned to you.

Under section 120(3), an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor. Section 120(5) allows future copyright to be assigned in advance, which is what a development agreement does when it says deliverables “shall vest in the customer on creation”. Developers also have moral rights, including the right to object to derogatory modification of the work (section 109); section 116 allows these to be waived in writing signed by the person waiving, and a waiver is standard in commissioned software contracts.

Full assignment gives the customer complete control, which matters if the software is the product; a broad licence may be acceptable where the developer builds on its own platform or reuses components across clients. Either way, carve out the developer’s pre-existing tools and know-how (background IP), and require the developer to list open-source components and comply with their licences, because some impose conditions on how the combined work can be distributed.

Specification, milestones and acceptance

The specification is where most software disputes are won or lost. Attach it as a schedule, state that the developer will deliver software materially conforming to it, and set out a milestone plan with dates. Then define acceptance: who tests, against what criteria, within what period, and what happens on failure. A typical scheme gives the customer a fixed window to test, requires the developer to fix and resubmit, treats deliverables as accepted if used in live operation or if the customer does not respond in time, and allows a limited number of rejection cycles before either party can terminate.

Change control

A change control procedure sets out how either party proposes a change to scope, how the developer quotes the impact on price and timetable, and that nothing changes until a change note is signed. Agile projects can use the same structure by treating each sprint backlog as the controlled scope.

Fees and late payment

State whether the project is fixed price, time and materials, or a hybrid with a capped budget, and tie payments to milestones or acceptance rather than calendar dates alone. If the contract does not fix its own interest rate, the Late Payment in Commercial Transactions Regulations 2012 (S.I. 580/2012) apply: interest at the ECB main refinancing rate plus eight percentage points (10.4% a year from 1 July 2026), plus fixed compensation of €40, €70 or €100 depending on whether the debt is up to €1,000, up to €10,000, or over €10,000.

Warranties, implied terms and liability

Section 39 of the Sale of Goods and Supply of Services Act 1980 implies into any business supply of services terms that the supplier has the necessary skill, will act with due skill, care and diligence, and that materials are sound and reasonably fit for purpose. Between businesses, section 40 lets the parties negative or vary those terms by an express clause, so the agreement will usually replace them with specific warranties: conformity with the specification for a defined warranty period, no infringement of third-party IP, no deliberately introduced malicious code, and compliance with applicable law. Whether software itself counts as “goods” under Irish sale of goods legislation remains unsettled, which is another reason to write the warranties out expressly.

Liability is usually capped at the fees paid or payable under the agreement, with indirect and consequential loss excluded and standard carve-outs for death, personal injury and fraud. An IP indemnity from the developer, covering claims that the deliverables infringe third-party rights, is normal and often sits outside the cap or under a higher one.

Data protection and security

If the developer will have access to personal data, during build, testing with live data, support or hosting, it will almost always be acting as a processor for the customer. Article 28(3) of the GDPR then requires a written contract covering the subject matter, duration, nature and purpose of processing, the data types and data subjects, and the processor’s obligations: documented instructions only, staff confidentiality, Article 32 security, prior authorisation of sub-processors, assistance with data subject rights and breaches, deletion or return at the end, and audit rights. The Data Protection Commission publishes a practical guide to these clauses. Use anonymised test data where possible and set minimum security standards for the developer’s environment.

Source code, escrow and exit

If you are getting a licence rather than an assignment, consider depositing the source code with an escrow agent for release if the developer becomes insolvent or stops supporting the product. Either way, the exit clause should require delivery of current source code, build instructions, documentation and credentials, with a handover period during which the developer cooperates with a replacement supplier.

New EU rules that reach software

Three pieces of EU legislation have changed the backdrop over the past two years and belong on any developer’s radar:

• The revised Product Liability Directive (EU) 2024/2853 expressly includes software in the definition of a product. Member States must transpose it by 9 December 2026, and it applies to products placed on the market after that date. As at October 2026 Ireland had not yet published its transposing legislation.
• The EU AI Act became generally applicable on 2 August 2026, including transparency duties for AI systems that interact with people or generate content. The Digital Omnibus on AI (Regulation (EU) 2026/1744, in force from 27 July 2026) pushed back the high-risk obligations to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems. If the software includes AI, the agreement should allocate responsibility for compliance.
• The Cyber Resilience Act (Regulation (EU) 2024/2847) applies in full from 11 December 2027, with its vulnerability and incident reporting obligations already live since 11 September 2026 for products with digital elements placed on the EU market.

Signing and governing law

Electronic signatures are valid under the Electronic Commerce Act 2000, provided the recipient consents to signing electronically. State that Irish law governs and the Irish courts have jurisdiction, and consider an escalation clause (project managers, senior management, then mediation) before litigation.

What a template can and cannot do

The Software Development Agreement template gives you an Irish-law contract with schedules for the specification, milestones, acceptance, fees and data processing, which you complete yourself. It cannot write your technical specification, assess whether an open-source licence suits your business model, or advise on AI Act classification. For a product your business depends on, a multi-jurisdiction deal or a dispute over ownership of existing code, speak to a solicitor; the Law Society’s Find a Solicitor service lists practitioners by area. Our guides to IP protection for Irish businesses and non-disclosure agreements in Ireland cover the related ground, and all of our business law templates are here.

Frequently asked questions

Who owns the copyright in commissioned software in Ireland?

The developer, unless the contract assigns it. Section 23 of the Copyright and Related Rights Act 2000 makes the author the first owner, with an exception only for employees. A contractor’s code must be assigned in writing signed by the developer under section 120(3).

Does a software development agreement need to be in writing?

A services contract can be oral, but an assignment of copyright is not effective unless it is in writing and signed, so the IP transfer at the heart of the deal only works on paper (or electronically, which the Electronic Commerce Act 2000 permits with the recipient’s consent).

What is acceptance testing in a software contract?

Acceptance testing is the agreed process by which the customer checks a deliverable against the specification within a set period, reports defects, and either accepts it or sends it back for correction. The contract should say when a deliverable is deemed accepted and how many rejection cycles are allowed.

Do software developers need a GDPR data processing agreement?

Yes, whenever the developer processes personal data on the customer’s behalf, for example by handling live data in testing, support or hosting. Article 28(3) GDPR requires a written contract containing specific mandatory terms.

Is software covered by product liability law in the EU?

It will be. Directive (EU) 2024/2853 includes software in the definition of a product and must be transposed by 9 December 2026, applying to products placed on the market after that date. As of October 2026 Ireland’s transposing legislation had not yet been published.

Sources: Copyright and Related Rights Act 2000, s.23 · Copyright and Related Rights Act 2000, s.120 · Sale of Goods and Supply of Services Act 1980, s.39 (revised) · Data Protection Commission – Data processing agreements · Directive (EU) 2024/2853 on liability for defective products · Department of Enterprise – Late payment interest rate

OnlineLegalServices.ie is not a solicitor’s practice and does not give legal advice. For advice on your own situation, speak to a solicitor.