This order clarifies the high threshold required for a party to set aside a Default Costs Certificate in the DIFC Courts, emphasizing that procedural extensions are not to be taken lightly once the court-ordered deadline has lapsed.
Why did Ernst & Young Middle East seek to set aside Default Cost Certificates in CFI 033/2009?
The dispute arose from the assessment of Bills of Costs following litigation involving Orion Holdings Overseas Limited. After the Respondent, Shahab Haider, served a Notice of Commencement of Assessment, the parties initially agreed to an extension for the filing of Points of Dispute. Despite this, the Applicant failed to meet the revised deadline, leading the Respondent to secure Default Cost Certificates.
On 1 April 2013 the Respondent filed three P40/02 Requests for Default Cost Certificates (CFI 033/2009/05, CA 004/2011/06 & CA 004/2011/07).
The Applicant subsequently filed applications to set aside these certificates, essentially attempting to reopen the assessment process after the procedural window had closed. The core of the dispute was whether the Applicant’s failure to adhere to the agreed-upon timeline could be excused by the Court, thereby allowing the substantive arguments regarding the Bills of Costs to be heard despite the default.
Which judge presided over the application to set aside the Default Cost Certificates in CFI 033/2009?
The application was heard by H.E. Justice Omar AlMuhairi sitting in the DIFC Court of First Instance. The order was issued on 16 April 2013, following a rapid exchange of submissions between the parties in early April 2013 regarding the validity of the Default Cost Certificates issued by the Registry on 1 April 2013.
What were the specific arguments advanced by Ernst & Young Middle East and Shahab Haider regarding the missed deadline?
The Applicant, Ernst & Young Middle East, argued for the setting aside of the certificates, effectively seeking a second chance to present their Points of Dispute after missing the 31 March 2013 deadline. Their position was predicated on the filing of Application Notices on 2 April 2013, which sought to rectify the procedural lapse by submitting the Points of Dispute alongside the request to set aside the default.
The Respondent, Shahab Haider, opposed this application, maintaining that the procedural rules had been followed correctly and that the Applicant had failed to provide a valid justification for the delay. The procedural history was documented as follows:
On 24 February 2013 the Applicant filed three Application Notices (CA 004/2011/04, CA 004/2011/05 & CFI 033/2009/04) requesting an extension to 31 March 2013 to file their Points of Dispute to the Respondent's Bills of Costs, the extension was agreed between the parties and the Court subsequently issued the Order of 28 February 2013 granting the Applicant's extension request.
The Respondent’s position was bolstered by the fact that the Applicant had already benefited from one court-sanctioned extension, making the subsequent failure to file by the 12pm deadline on 31 March 2013 inexcusable in the eyes of the Respondent.
What was the precise legal question Justice Omar AlMuhairi had to answer regarding the application of RDC Rule 40.24?
The Court was tasked with determining whether the Applicant had demonstrated a "good reason" to set aside or vary the Default Cost Certificates under the Rules of the DIFC Courts (RDC). The legal question was not merely whether the Applicant wanted to contest the costs, but whether the circumstances surrounding the failure to file by the agreed deadline met the threshold required by the RDC to justify the Court’s intervention in an already finalized default process.
How did Justice Omar AlMuhairi apply the "good reason" test to the Applicant's failure to file Points of Dispute?
Justice AlMuhairi’s reasoning focused on the lack of justification provided by the Applicant for missing the court-ordered deadline. The Court noted that the Applicant had been granted a specific extension, yet failed to comply with the final date set by the Court. The judge emphasized that the power to set aside a certificate is discretionary and contingent upon a showing of a "good reason" for the delay.
However, the Applicant failed to file its respective Points of Dispute by 12pm on 31 March 2013.
The Court found that the Applicant’s submissions, which were reviewed alongside the Respondent’s responses, failed to establish any such reason. Consequently, the Court determined that the procedural integrity of the cost assessment process outweighed the Applicant's desire to relitigate the quantum of the costs, leading to the refusal of the application.
Which specific RDC rules and procedural steps were central to the Court's decision in CFI 033/2009?
The primary authority cited was Rule 40.24 of the Rules of the DIFC Courts (RDC). This rule provides the specific mechanism by which the Court may set aside or vary a Default Costs Certificate. The Court also relied on the procedural timeline established by the Order of 28 February 2013, which had granted the initial extension. The Registry’s role in issuing the certificates on 1 April 2013 was also a critical procedural fact, as it marked the point at which the Applicant’s failure to file became a formal default.
How did the Court manage the expedited timeline for the submissions in this matter?
The Court utilized its power to manage the case efficiently, ensuring that the dispute over the Default Cost Certificates did not languish. The Registry issued specific directions to expedite the exchange of arguments between the parties.
On 2 April 2013 the Registry issued directions expediting the Response and Reply to Response submissions to the Application Notices CA 004/2011/08, CA 004/2011/09 & CA 004/2011/10.
This allowed the Court to consider the arguments of both sides—the Respondent’s filing on 9 April 2013 and the Applicant’s reply on 11 April 2013—in a timely manner, ensuring that the final order could be issued shortly thereafter on 16 April 2013.
What was the final disposition of the application and the specific orders regarding costs and payment?
The Court refused the applications to set aside the Default Cost Certificates. As a consequence of this refusal, the Applicant was held liable for the costs associated with the application process.
The Applicant shall pay the Respondent's Costs of these Applications, to be assessed if not agreed.
Furthermore, the Court amended the payment terms of the original Default Cost Certificates to provide a clear, final deadline for the Applicant to satisfy the judgment debt.
The sums in paragraphs 2, 3 and 4 above to be paid by the Paying Party to the Receiving Party by no later than 12pm on 1 May 2013.
How does this ruling change the approach for practitioners regarding cost assessment deadlines in the DIFC?
This case serves as a stern reminder that the DIFC Courts maintain a strict stance on procedural deadlines, particularly in cost assessment proceedings. Practitioners must anticipate that once a court-ordered extension has been granted, any subsequent failure to file will be viewed with extreme skepticism. The "good reason" test under RDC 40.24 is not a low bar; it requires a compelling explanation for the delay. Litigants should not expect the Court to exercise its discretion to set aside a Default Costs Certificate simply because the defaulting party wishes to contest the underlying costs.
Where can I read the full judgment in CFI 033/2009 Shahab Haider v Ernst & Young Middle East?
The full judgment can be accessed via the DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/court-first-instance/cfi-0332009-shahab-haider-v-ernst-young-middle-east
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | No external precedents cited in the order. |
Legislation referenced:
- Rules of the DIFC Courts (RDC), Rule 40.24