How an Irish business should document a failed software implementation and seek repayment

If a paid software implementation for your business has failed, your practical route to repayment is governed mainly by the contract and Irish contract law — not consumer rules. Begin by preserving the contract, acceptance records, test logs and all communications; comply exactly with any contractual notice and cure procedures; send a focused written demand for refund or damages; and consider mediation or court only after you have collated technical and financial evidence. This article explains what to gather, why it matters under Irish law, and how to proceed logically.

Why consumer protections usually do not help a business buyer

If both parties are businesses (B2B), statutory consumer protections for digital content or services do not apply; your remedies flow from the written contract and general contract law. For guidance about the scope of consumer rules — and to confirm whether your purchase might instead be treated as a consumer transaction — see the government summary of consumer rights on gov.ie: Consumer rights and guarantees related to buying goods and services. For consumer-facing digital-content rules the Competition and Consumer Protection Commission explains remedies, but these pages are aimed at individuals rather than companies: Resolving an issue with digital content and services.

Why this matters: the statutory protections available to consumers (refunds, repair, replacement) are not the default for commercial buyers. Instead you must rely on the contract's express terms (scope of work, acceptance criteria, warranties, caps) and common-law remedies for breach.

What to document first — the evidence that actually matters

Collecting every file imaginable is tempting; prioritise the materials courts and technical experts will use to decide whether the supplier failed and what you lost.

• The contract and SOW: the signed agreement, statements of work, schedules, milestone definitions, acceptance criteria, SLAs, and all change orders. These are the primary legal controls for any claim. (See the Sale of Goods and Supply of Services Act 1980 for implied duties about services as background: Sale of Goods and Supply of Services Act, 1980).
• Acceptance records and milestone sign-offs: signed acceptance forms, demo recordings, evidence of failed acceptance tests, and any written approvals or rejections by date.
• Communications timeline: email chains, meeting minutes, messages, and contemporaneous notes showing who said what, when. Use absolute dates (day/month/year) for every event — Irish courts expect precise chronology.
• Technical artefacts: error logs, screenshots, crash reports, build versions, time-stamped deployment records, source-code snapshots, backups, and test-data results. Preserve originals and create a checksum or read-only copy to show integrity.
• Defect tracking: tickets, severity classifications, response times, and the supplier’s remediation attempts (or lack of them).
• Financial records and mitigation costs: invoices paid to the supplier, invoices for third-party consultants, extra staff hours, temporary workarounds, and a clear list of additional costs you incurred trying to keep operations running.
• Clauses limiting liability: note any warranty caps, limitation periods for claims, and dispute-resolution steps in the contract — they shape what you can reasonably seek.

Practitioner guidance emphasises early preservation of technical artefacts and contemporaneous records; see a practical overview of technology sourcing and remedies for Ireland: Ireland — Technology Sourcing Laws and Regulations 2023.

How to structure your factual case (concise chronology + losses)

Create a concise, date-ordered chronology (one page preferred) with entries like: "01/03/2025: Milestone 1 demo — failed acceptance test: feature X returns error code 0x1234; screenshot and log file 'error_01032025.log' attached." Follow the chronology with a short, itemised loss schedule: direct costs (payments, consultants) and consequential losses (lost margin) with explanation of how you calculated lost profit. Courts award compensatory damages for proven losses but expect claimants to have mitigated their losses.

Procedural next steps before litigation

1. Check whether the contract requires notices, cure periods, expert determination, or mediation and comply strictly with those steps. Failure to follow mandatory contractual processes can jeopardise remedies. (See the ICLG overview for practical context.)
2. Send a clear written breach and repayment demand that: states the contract breaches, lists supporting evidence (attach the key documents), quantifies the refund/damages sought, and sets a realistic deadline for a response or remedy. Keep proof of service (email delivery receipts, registered post receipts). A well-drafted demand letter often prompts settlement and is expected before court action.
3. Consider ADR or mediation. Irish courts and practitioners favour parties who attempt ADR, and many IT contracts require it before litigation. The CCPC’s platform‑to‑business pages discuss ADR routes available in regulated digital contexts: Platform to Business regulation.

What a demand achieves and its limits: a demand letter clarifies your position, narrows issues, and creates a paper trail. It does not guarantee payment, create legal rights beyond the contract, or replace the need to prove loss if the supplier disputes the facts.

Remedies, courts and realistic outcomes

• Repayment or damages: the primary remedies for B2B are repayment (where unjust enrichment or fundamental breach is shown) or compensatory damages to place you where you would have been but for the breach. Precise outcomes depend on contract wording and evidence; see the practitioner guide for discussion of remedies and their limits: ICLG — Ireland technology sourcing.
• Specific performance is rare in software disputes — courts usually award money rather than force a supplier to complete complex technical work.
• Where to sue: small-value claims can be pursued through District Court/Small Claims or online money-claim routes; larger or complex matters go to Circuit Court or the High Court; commercially significant or IP-heavy disputes may be heard in the Commercial Court (a High Court list).

When to instruct an Irish solicitor and what to expect

Seek specialised legal advice if the claim involves large sums, limitation/indemnity clauses, source-code ownership, or threatened counterclaims. A solicitor experienced in IT and commercial litigation can advise on whether the evidence justifies a repayment demand, a negotiated settlement, or court proceedings.

If you prefer professional help drafting a precise demand letter based on your materials, you can use a specialist document service that prepares professional demand letters from customer-supplied information: . Remember such services do not give legal advice or represent you in court; consider them a drafting support while you decide next steps.

Final practical note

Document early, prioritise the contract, acceptance records and technical logs, and comply exactly with contractual notice and dispute-resolution processes. A clear, evidence‑backed demand and willingness to attempt ADR give you the best chance of recovering fees without protracted litigation. If the supplier disputes your facts or relies on a limitation clause, legal advice is the sensible next step.

For help preparing a professional demand letter, BeforeSuit can help you prepare your next steps.