This order clarifies the intersection of eRegistry technical visibility and the requirements for effective service of a defence, confirming that email transmission can cure procedural invisibility.
Why did Shufti Pro Digital ID Verification Services file a request for default judgment against Ahmad Jamal in CFI 079/2025?
The dispute arises from a procedural impasse regarding the filing and service of a defence in a Part 7 claim. Shufti Pro Digital ID Verification Services Limited initiated the claim on 21 August 2025, and following the Defendant’s acknowledgment of service, the parties entered a period of procedural friction. The Claimant, operating under the assumption that no defence had been served within the prescribed 28-day window, sought to secure a default judgment to resolve the matter summarily.
As noted in the court records:
The Claimant filed a request for default judgment on 8 October 2025 on the basis that no defence had been filed in accordance with RDC 16.9 (the “Application for Default Judgment”).
The Claimant’s position was predicated on the absence of any visible defence on the DIFC Courts’ eRegistry portal. Because the portal did not display the document, the Claimant maintained that the Defendant had failed to comply with the mandatory timelines for pleading, thereby triggering the right to seek a default judgment under the Rules of the DIFC Courts (RDC).
Which judge presided over the hearing of the Application for Default Judgment in CFI 079/2025?
The matter was heard before H.E. Justice Rene Le Miere in the Court of First Instance. The hearing took place on 8 December 2025, following the Claimant’s urgent application for a determination on the validity of the Defence and the subsequent evidentiary submissions by the Defendant, who appeared as a litigant in person.
What were the competing legal arguments presented by Shufti Pro and Ahmad Jamal regarding the validity of the defence?
Shufti Pro argued that the Defendant failed to effectuate service of the Defence in accordance with RDC 16.13. The Claimant contended that the Defendant’s email dated 9 October 2025—which contained the Defence as an attachment—was procedurally insufficient because it was bundled within a "Reply to the Application for Default Judgment" rather than being served as a distinct, formal document. The Claimant maintained that this failure to serve rendered the Defence invalid, thereby entitling them to a default judgment.
Conversely, Ahmad Jamal, appearing as a litigant in person, argued that he had complied with the RDC by lodging his Defence on the eRegistry portal on 23 September 2025, well within the 24 September 2025 deadline. He asserted that any lack of visibility on the Claimant’s end was due to technical issues within the eRegistry system, specifically that the document was erroneously marked as "hidden from others" without his knowledge. He further argued that his subsequent email to the Claimant on 9 October 2025, which explicitly attached the Defence, satisfied the requirements for effective service.
What was the precise doctrinal issue the Court had to resolve regarding the interplay between eRegistry filings and RDC service requirements?
The Court was tasked with determining whether a document that is technically "filed" on the eRegistry but remains invisible to the opposing party due to system settings can be considered properly served, and whether an email attachment sent in response to a default judgment application can cure such a defect. The doctrinal issue centered on whether the Court should prioritize the technical reality of the filing date over the Claimant’s lack of notice, and whether the Defendant’s email communication satisfied the criteria for "effective service" under the RDC despite the unconventional manner of its delivery.
How did Justice Rene Le Miere apply the doctrine of effective service to the Defendant’s email transmission?
Justice Le Miere determined that the Defendant had indeed filed the Defence within the required timeframe, noting that the eRegistry had acknowledged the filing on 24 September 2025. The Court found that the subsequent invisibility of the document was a technical error rather than a failure of the Defendant to perform his procedural duty. Furthermore, the Court held that the email sent by the Defendant on 9 October 2025 served as a valid mechanism for service.
The Court’s reasoning is summarized as follows:
An additional issue is whether the Defendant’s sending of his Defence by email on 9 October 2025, as part of his Reply to the Claimant’s Application for Default Judgment, constitutes valid service under the Rules of the DIFC Courts
The Judge concluded that because the Claimant had provided an email address for service, the transmission of the document—which was clearly identified as the Defence—met the threshold for service under RDC Part 9. By providing the Claimant with the document, the Defendant effectively cured any prejudice caused by the eRegistry’s technical failure, rendering the Claimant’s application for default judgment moot.
Which specific RDC rules were central to the Court’s determination in CFI 079/2025?
The Court relied heavily on RDC 16.9(2), which mandates that a defendant must file a defence within 28 days after service of the particulars of claim. Additionally, the Court examined RDC 16.13, which governs the service of a defence, and RDC Part 9, which outlines the permissible methods for electronic service. The Court also considered RDC 13.5, which provides the framework for default judgments, ultimately finding that the conditions for such a judgment had not been met because a defence had been filed and subsequently served.
How did the Court interpret the requirements for electronic service under RDC Part 9?
The Court interpreted RDC Part 9 as a flexible framework designed to facilitate communication between parties, provided there is clear evidence of receipt. The Court noted:
RDC Part 9 permits service by electronic means, including email, where the receiving party has indicated willingness to accept service by such means. It is not disputed that the Claimant had provided an email address for service.
By linking this to the Defendant’s actions on 9 October 2025, the Court established that the attachment of the Defence to the email was sufficient. The Court emphasized that the document was "clearly identified" within the email, which satisfied the requirements of RDC 16.13. This interpretation underscores the Court's preference for substance over form, particularly when a litigant in person has made a good-faith effort to comply with the rules.
What was the final disposition of the Claimant’s Application for Default Judgment and the associated costs order?
The Court dismissed the Claimant’s Application for Default Judgment in its entirety. Justice Le Miere ordered that the Claimant be granted a 21-day extension from the date of the order to file and serve its reply to the Defence. Regarding costs, the Court determined that each party should bear its own costs, noting the lack of legal expenditure by the self-represented Defendant and the Claimant's acknowledgment regarding the potential for a failed application.
As stated in the record:
The Defendant did not apply for an order for costs. He is self-represented, and there is no evidence that he has incurred legal costs in relation to the Application.
and
The Claimant acknowledged that it will not be awarded the costs of the Application if it does not succeed in its Application for Default Judgment.
What are the wider implications of this ruling for practitioners navigating the DIFC eRegistry?
This case serves as a critical reminder that technical glitches within the eRegistry do not automatically entitle a claimant to default judgment if the defendant has made a timely attempt to file. Practitioners should anticipate that the Court will look beyond the "visibility" of a document on the portal to determine if a filing was actually made. Furthermore, the ruling confirms that email service remains a robust and valid method for serving pleadings, even when the document is attached to a reply or other procedural correspondence, provided the document is clearly identified. Litigants should be cautious about pursuing default judgments when there is any ambiguity regarding the status of a filing, as the Court is likely to favor procedural fairness and the resolution of claims on their merits.
Where can I read the full judgment in Shufti Pro Digital Id Verification Services Limited v Ahmad Jamal [2025] DIFC CFI 079?
The full judgment can be accessed via the DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/court-first-instance/cfi-0792025-shufti-pro-digital-id-verification-services-limited-v-ahmad-jamal
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | No external precedents cited in the provided order. |
Legislation referenced:
- Rules of the DIFC Courts (RDC):
- RDC 16.9(2)
- RDC 16.13
- RDC 13.5
- RDC 4.2
- RDC Part 9
- RDC Part 1