The DIFC Court of Appeal reinforces the necessity of strict adherence to court-ordered deadlines in cost assessment proceedings, confirming that a failure to provide a "good reason" for procedural delay will result in the court upholding Default Cost Certificates.
What specific procedural failure led to the issuance of Default Cost Certificates against Ernst & Young in the dispute with Shahab Haider?
The dispute centers on the assessment of Bills of Costs following litigation between Shahab Haider, acting as the Liquidator of Orion Holdings Overseas Limited, and Ernst & Young Middle East. After the Respondent served a Notice of Commencement of Assessment of Bills of Costs, the Applicant sought and was granted an extension of time to file their Points of Dispute. Despite this court-sanctioned extension, the Applicant missed the final deadline, prompting the Respondent to move for default relief.
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 attempted to rectify this by filing Application Notices to set aside the certificates, but the court found the delay inexcusable. The core of the conflict was the Applicant's inability to meet the agreed-upon timeline, which had been formalized by a previous court order.
Which judge presided over the application to set aside the Default Cost Certificates in CA 004/2011?
H.E. Justice Omar Al Muhairi presided over the matter in the DIFC Court of Appeal. The order was issued on 16 April 2013, following a review of the Application Notices filed on 2 April 2013 and the subsequent exchange of submissions between the parties regarding the validity of the Default Cost Certificates.
What arguments did Ernst & Young and Shahab Haider advance regarding the missed deadline for filing Points of Dispute?
Ernst & Young, as the Applicant, sought to set aside the Default Cost Certificates issued on 1 April 2013, effectively asking the court to overlook their failure to file Points of Dispute by the 31 March 2013 deadline. Their position necessitated an explanation for the delay to satisfy the court's threshold for relief. Conversely, Shahab Haider, the Respondent, maintained that the certificates were properly issued following the Applicant's failure to comply with the court’s earlier order.
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 supported by the objective fact that the deadline had passed without the required filings, leaving the court with little room to exercise discretion in the absence of a compelling justification.
What was the precise legal question H.E. Justice Omar Al Muhairi had to answer regarding the application of RDC 40.24?
The court was tasked with determining whether the Applicant had demonstrated a "good reason" to justify setting aside or varying the Default Cost Certificates under the Rules of the DIFC Courts (RDC). The legal question was not merely whether the Applicant had eventually filed their Points of Dispute, but whether the circumstances surrounding the initial failure to meet the 31 March 2013 deadline met the threshold required by the RDC to grant relief from the consequences of that procedural default.
How did H.E. Justice Omar Al Muhairi apply the "good reason" test to the Applicant's request?
The judge applied a strict interpretation of the court's procedural rules. Upon reviewing the timeline—specifically the fact that the Applicant missed the deadline despite having previously requested and been granted an extension—the court concluded that the Applicant failed to provide any valid justification for the delay.
However, the Applicant failed to file its respective Points of Dispute by 12pm on 31 March 2013.
The reasoning was straightforward: the court’s power to set aside a certificate is contingent upon the existence of a "good reason." Finding that the Applicant had provided no such reason, the court held that it had no basis to exercise its discretion to set aside the certificates. The judge emphasized that the procedural integrity of the cost assessment process relies on parties adhering to the deadlines they themselves have negotiated and the court has ordered.
Which specific RDC rules and procedural steps governed the issuance of the Default Cost Certificates in this case?
The primary authority applied was Rule 40.24 of the Rules of the DIFC Courts (RDC), which grants the court the discretion to set aside or vary a Default Costs Certificate if it appears that there is "some good reason" for the proceedings to continue. The court also relied on the procedural history of the case, noting the sequence of filings:
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 sequence highlights the court's commitment to managing costs disputes efficiently, ensuring that once a default occurs, the path to resolution—or the finality of the default—is handled through expedited directions.
How did the court interpret the requirement for a "good reason" under RDC 40.24?
The court’s interpretation of RDC 40.24 was restrictive. The judge noted that the burden of proof lies with the party seeking to set aside the certificate to demonstrate why the court should intervene. By stating, "Before me there is no good reason identified," the court signaled that the threshold for "good reason" is not met by mere oversight or administrative delay. The court treated the deadline as a firm boundary, reinforcing that the RDC is designed to prevent the indefinite prolongation of cost assessments.
What was the final disposition of the application and the specific orders regarding costs and payment?
The court refused the Applicant's request to set aside the Default Cost Certificates. Consequently, the Applicant was ordered to bear the costs of the applications.
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 certificates to ensure a clear, enforceable deadline for the Respondent to receive the sums due.
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.
What are the wider implications for DIFC practitioners regarding procedural deadlines in cost assessments?
This case serves as a stern reminder that the DIFC Courts prioritize procedural finality in cost assessment proceedings. Practitioners must anticipate that the court will not readily exercise its discretion under RDC 40.24 to excuse missed deadlines. If a party fails to file Points of Dispute by a court-ordered date, the resulting Default Cost Certificate is highly likely to stand unless the party can provide a truly exceptional and compelling "good reason" for the failure. This reinforces the necessity for rigorous internal docket management and the avoidance of last-minute filings in the DIFC.
Where can I read the full judgment in Shahab Haider v Ernst & Young Middle East [2013] DIFC CA 004?
The full judgment can be accessed via the official DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/court-appeal/ca-0042011-order-he-justice-omar-al-muhairi or via the CDN link: https://littdb.sfo2.cdn.digitaloceanspaces.com/litt/AE/DIFC/judgments/court-appeal/DIFC_CFI-033-2009_20130416.txt.
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | No external precedents cited in this specific order. |
Legislation referenced:
- Rules of the DIFC Courts (RDC), Rule 40.24