The Small Claims Tribunal (SCT) dismissed a claim for a refund of AED 247,668.75, ruling that the Claimant’s continued reliance on the software through renewed maintenance contracts undermined its allegations of breach and non-performance.
What was the specific nature of the dispute between Latha and Lavni regarding the AED 247,668.75 refund claim?
The dispute centered on a tri-party agreement dated 30 June 2019, under which the Claimant, Latha, engaged the Defendant, Lavni, and a third party to develop and implement a software program. The Claimant alleged that the software failed to meet the agreed specifications and that the Defendant neglected to rectify these deficiencies despite multiple notifications. Consequently, the Claimant sought a full refund of the fees paid.
On 28 January 2022, the Claimant filed a claim in the DIFC Courts’ Small Claims Tribunal (the “SCT”) seeking a refund of the fees paid to the Defendant pursuant to the Agreement in the sum of AED 247,668.75.
The Claimant’s position was rooted in the argument that the Defendant had defaulted on its contractual obligations, triggering the refund mechanism stipulated in the Agreement. However, the Defendant maintained that the software was successfully implemented and that the Claimant’s subsequent conduct—specifically the renewal of an annual maintenance contract—contradicted the assertion that the software was unfit for purpose. The full details of the claim and the court's analysis can be found at the DIFC Courts website.
Which judge presided over the Latha v Lavni SCT proceedings and when was the judgment issued?
The proceedings were presided over by SCT Judge Delvin Sumo. Following a consultation before SCT Judge Maitha AlShehhi on 16 February 2022, which failed to yield a settlement, the matter was referred to Judge Sumo for determination. A hearing was held on 15 March 2022, and the final judgment was issued on 21 March 2022.
What were the primary legal arguments advanced by Latha and Lavni during the SCT hearing?
Latha argued that the software failed to achieve its required purpose as of May 2021, citing earlier deficiencies reported in August 2020. The Claimant relied on specific clauses of the Agreement, asserting that the Defendant’s failure to rectify these issues after receiving a formal notice of breach on 30 September 2021 entitled the Claimant to a full refund.
As the deficiencies continued to remain, the Claimant sent the Defendant an official notice letter dated 30 September 2021, stating that:
“Lavni failed to development and implement the software as per the agreed terms and per the {agreed} timeline.
Conversely, Lavni argued that it had fulfilled all obligations under the Agreement. The Defendant highlighted that the Claimant continued to utilize the software and had entered into an annual maintenance contract (AMC) that was renewed twice. The Defendant contended that such renewals are standard practice only after the successful completion of an initial software project, thereby negating the Claimant’s argument that the software was never implemented.
What was the jurisdictional question the court had to answer regarding the tri-party agreement?
The court had to determine whether it possessed the requisite authority to adjudicate the dispute given the nature of the tri-party agreement and the specific jurisdictional clause contained therein. The issue was whether the parties had validly opted into the DIFC Courts' jurisdiction, notwithstanding the involvement of a third party who was not a participant in the SCT proceedings.
How did Judge Delvin Sumo apply the doctrine of contractual opt-in to establish jurisdiction?
Judge Sumo examined the Agreement to determine if the parties had explicitly consented to the DIFC Courts' authority. The judge found that the contract contained a clear opt-in provision, which served as the basis for the Tribunal’s jurisdiction over the matter.
It must be noted that by virtue of an opt-in clause found at clause 19 of the Agreement, I am of the view that the parties have opted into the DIFC Courts’ jurisdiction to hear and determine this matter.
The reasoning focused on the principle of party autonomy in commercial contracts. By including a clause designating the DIFC Courts as the forum for disputes, the parties effectively waived objections to the court's authority to hear the merits of the case, regardless of the complexities introduced by the tri-party nature of the underlying software development arrangement.
Which specific statutes and RDC rules were applied by the court in Latha v Lavni?
The court relied on Article 5(A) of the Judicial Authority Law (Dubai Law No. 12 of 2004), which governs the jurisdiction of the DIFC Courts. Additionally, the proceedings were conducted in accordance with Rule 53.2 of the Rules of the DIFC Courts (RDC), which outlines the procedures for the Small Claims Tribunal. These authorities provided the framework for the court to accept the case and manage the dispute resolution process between the parties.
How did the court use the Claimant's conduct as an evidentiary authority to evaluate the breach of contract claim?
The court utilized the Claimant's post-implementation behavior as a key evidentiary tool to assess the credibility of the breach claim. Specifically, the court noted that the Claimant had failed to terminate the Agreement despite the alleged deficiencies.
Moreover, even though the Claimant had sent the Defendant a notice of breach dated 30 September 2021, the Claimant failed to terminate the Agreement.
By observing that the Claimant continued to engage the Defendant through an annual maintenance contract, the court inferred that the software had reached a state of operational utility. This conduct was weighed heavily against the Claimant's assertions of non-performance, leading the court to conclude that the claim for a refund was not supported by the factual reality of the parties' ongoing commercial relationship.
What was the final outcome of the Latha v Lavni proceedings and the court's order regarding costs?
The court dismissed the claim in its entirety. Judge Sumo found that the Claimant had not justified the refund under the Agreement, particularly because the fees were not paid in full and the software had been implemented and maintained by the Claimant. Regarding the financial burden of the litigation, the court ordered that each party bear its own costs, reflecting the standard approach in the SCT for such disputes.
What are the wider implications of this ruling for software development contracts in the DIFC?
This case serves as a reminder that subsequent conduct, such as renewing maintenance agreements, can be fatal to a claim of total failure of consideration or breach of contract. Practitioners should advise clients that if they intend to pursue a refund for non-performance, they must act consistently with that position by terminating the contract and ceasing the use of the disputed software. Failure to do so creates a strong evidentiary presumption that the software was, in fact, functional and accepted.
Where can I read the full judgment in Latha v Lavni [2022] DIFC SCT 022?
The full judgment is available on the DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/small-claims-tribunal/latha-v-lavni-2022-sct-022 or via the CDN link: https://littdb.sfo2.cdn.digitaloceanspaces.com/litt/AE/DIFC/judgments/small-claims-tribunal/DIFC_SCT-022-2022_20220321.txt
Legislation referenced:
- Judicial Authority Law, Dubai Law No. 12 of 2004, Article 5(A)
- Rules of the DIFC Courts (RDC), Rule 53.2