Submit Article
Legal Analysis. Regulatory Intelligence. Jurisprudence.
Singapore

Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another [2019] SGCA 79

In Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another, the Court of Appeal of the Republic of Singapore addressed issues of Civil Procedure — Judgments and orders, Civil Procedure — Rules of Court.

Case Details

  • Citation: [2019] SGCA 79
  • Title: Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another
  • Court: Court of Appeal of the Republic of Singapore
  • Date of Decision: 29 November 2019
  • Case Number: Civil Appeal No 2 of 2019 (Summons No 91 of 2019)
  • Tribunal/Coram: Andrew Phang Boon Leong JA; Tay Yong Kwang JA; Quentin Loh J
  • Judges: Andrew Phang Boon Leong JA, Tay Yong Kwang JA, Quentin Loh J
  • Parties: Pradeepto Kumar Biswas (appellant/applicant) v Sabyasachi Mukherjee and another (respondents)
  • Counsel: The appellant in person; Ng Ka Luon Eddee, Muk Chen Yeen Jonathan, Chan Yi Zhang and Toh Zhen Teck Jeremy (Tan Kok Quan Partnership) for the respondents
  • Legal Areas: Civil Procedure — Judgments and orders; Civil Procedure — Rules of Court; Civil Procedure — Striking out
  • Procedural Posture: Appeal from the High Court decision in [2018] SGHC 271; Court of Appeal considered whether to strike out the appeal for breach of an unless order
  • Key Procedural Instruments: Unless Order administered on 12 September 2019; Court of Appeal Summons No 91 of 2019 seeking striking out
  • Judgment Length: 6 pages; 3,010 words (as indicated in metadata)
  • Related/Referenced Case: Mitora Pte Ltd v Agritrade International (Pte) Ltd [2013] 3 SLR 1179

Summary

In Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another ([2019] SGCA 79), the Court of Appeal enforced an “unless order” and struck out the appellant’s appeal for non-compliance with procedural requirements governing the filing, service, and completeness of appeal documents. The case arose from a prolonged pattern of non-compliance with the Rules of Court, including repeated failures to file and serve the record of appeal and core bundle in the required form and within the required timelines.

The Court held that the appellant breached the unless order by failing to meet the deadline and by attempting to justify late service through an invalid method of service (email). The Court further found that the appellant did not rectify the deficiencies in his appeal documents, and that the breach was contumelious. Applying the principles in Mitora, the Court concluded that the adverse consequence specified in the unless order—striking out—should be enforced, as it was proportionate in the circumstances.

What Were the Facts of This Case?

The dispute reached the Court of Appeal after the High Court decision in Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another ([2018] SGHC 271). The appellant, Mr Biswas, proceeded with Civil Appeal No 2 of 2019. However, the appeal’s progress was dominated by procedural defaults relating to the preparation and submission of the appeal record and bundles required under the Rules of Court.

On 12 February 2019, the Registry served a notice that the record of proceedings was available. Under O 57 rr 9 and 9A of the Rules of Court (Cap 322, R 5, 2014 Rev Ed) (“ROC”), the appellant was required to file, by 12 April 2019, his Case, the record of appeal, a core bundle of documents, and a bundle of authorities. The appellant sought an extension of time on 9 April 2019, but did not file a formal application because the Registry indicated that formal application was required in the absence of respondents’ consent. The appellant nonetheless filed the Case and the relevant forms on 12 April 2019.

Shortly thereafter, the respondents wrote to the Registry on 18 April 2019 complaining that the appellant’s forms of the record of appeal and core bundle were in contravention of the ROC and that he had failed to file a bundle of authorities. A case management conference (“CMC”) was held on 30 April 2019, where the parties agreed that the appellant would take out an application to remedy his non-compliance by 10 May 2019, and that the respondents would file their Case by 31 May 2019 pending further directions. The appellant did not file the required application by 10 May 2019, although he did file a bundle of authorities.

After further exchanges, the Court issued detailed directions on 28 May 2019. The appellant was required to file by 4pm on 7 June 2019 such application as he deemed appropriate to rectify defects in the record of appeal and core bundle. If he filed the application, the respondents were to indicate by 4pm on 14 June 2019 whether they consented. If he failed to file by 7 June, the respondents were at liberty to proceed with their own application by 4pm on 19 June 2019. The timelines for the respondents’ Case were stayed pending determination of the applications. A further CMC on 31 May 2019 reiterated these directions and suggested that the appellant could provide revised documents to the respondents for comments before filing. The appellant indicated he would provide the documents by 4 June 2019, but the respondents’ position was that he did not.

The central legal issue was whether the Court should enforce the unless order and strike out the appellant’s appeal for breach. This required the Court to determine (i) whether there was a breach of the unless order, and (ii) if so, whether enforcement was appropriate, including whether the breach was contumelious and whether enforcement would be disproportionate.

A second issue concerned the validity of the appellant’s attempt to justify late service. The appellant argued that he had served the relevant documents on 30 September 2019 via email, despite the unless order requiring rectification and service by 30 September 2019. The Court therefore had to consider whether email service was a permissible method of service under the ROC and whether the respondents had agreed to such service or whether the Court had directed it.

How Did the Court Analyse the Issues?

The Court’s analysis began with the procedural chronology, which it described as crucial to its decision. The Court emphasised that the appellant had been given multiple opportunities to remedy non-compliance with the ROC. The Court noted that the appellant’s failures were not isolated; rather, they were repeated and persisted even after the Court had intervened through directions and applications.

On the first issue—breach—the Court found that the appellant breached the unless order. The unless order administered on 12 September 2019 required the appellant to rectify deficiencies in the record of appeal and core bundle, serve relevant documents on the respondents, and tender the documents to the Registry by 30 September 2019, failing which the appeal would be struck out. The appellant tendered documents to the Registry on 30 September 2019 but went to the respondents’ solicitors’ office after business hours (at 6:08pm), meaning he could not serve the documents on that date. He then sought to serve via email at 9:01pm. The Court rejected this argument and held that service by email was invalid for multiple reasons: first, email was not among the methods of service provided under O 62 r 6(1)(a)–(c) of the ROC; second, there was no indication that the respondents agreed to service via email within the meaning of O 62 r 6(1)(d); and third, the Court had not directed service via email within the meaning of O 62 r 6(1)(e).

In addition to the late service, the Court found that the appellant failed to rectify the deficiencies in his appeal documents. The Court observed that there were still numerous relevant documents omitted from the appellant’s appeal documents. While the Court did not list every omitted document, it highlighted that the deficiencies were significant and that the appellant did not achieve compliance even after earlier opportunities to do so.

On the second issue—whether to enforce the unless order—the Court applied the established approach in Mitora Pte Ltd v Agritrade International (Pte) Ltd ([2013] 3 SLR 1179). In Mitora, the Court of Appeal held that breach of an unless order automatically triggers the adverse consequences specified in the order. The onus then shifts to the defaulting party to demonstrate that the breach was not intentional and contumelious, so as to avoid the adverse consequences. The Court also noted that proportionality guides the exercise of discretion to enforce an unless order.

Applying these principles, the Court was satisfied that the appellant’s breach was contumelious and that enforcement was not disproportionate. The Court reasoned that the appellant’s conduct suggested that his attempt to comply was not bona fide. It stressed that the appellant had been afforded at least two opportunities to remedy non-compliance: first, at the CMC on 30 April 2019, where the parties agreed he would take out an application by 10 May 2019; and second, when the Court directed on 28 May 2019 that he file an application by 7 June 2019. Although the appellant eventually filed CA/SUM 66/2019 on 7 June 2019 and was granted leave to refile by 10 July 2019, the Court found that the documents filed remained non-compliant. The Court further noted that the respondents had agreed to provide comments on the documents before the appellant was due to file them, yet the appellant did not even bother to send the documents for comments.

Crucially, the Court linked the appellant’s non-compliance to procedural delay and inefficiency. It observed that because of the appellant’s failures, three CMCs were held and the hearing of CA/CA 2/2019 would be delayed by at least two months. The Court then made clear that it was giving the appellant one last opportunity through the unless order. The Court’s reasoning indicates that the unless order was not a mere technicality; it was a final procedural mechanism designed to ensure compliance and protect the respondents from further delay and expense.

Although the provided extract truncates the remainder of the judgment, the portion reproduced already demonstrates the Court’s core logic: (i) breach occurred (late service and incomplete rectification), (ii) the breach was not excused by an invalid service method, (iii) the appellant’s conduct showed a lack of bona fide effort, and (iv) enforcement was proportionate given repeated opportunities and the resulting delay. These findings supported the conclusion that the adverse consequence—striking out—should follow automatically.

What Was the Outcome?

The Court of Appeal struck out Civil Appeal No 2 of 2019 for breach of the unless order. This meant the appellant’s appeal could not proceed, and the procedural default had the substantive effect of terminating the appeal at the appellate stage.

Practically, the decision underscores that unless orders in Singapore appellate procedure are not discretionary “warnings” but binding procedural instruments. Once breached, the defaulting party faces a strong presumption that the specified consequence will be enforced unless the party can show that the breach was not intentional or contumelious and that enforcement would be disproportionate.

Why Does This Case Matter?

This case is significant for practitioners because it illustrates how the Court of Appeal treats non-compliance with appellate procedural requirements, particularly where an unless order has been administered. The Court’s approach reflects a broader judicial policy: procedural rules are designed to ensure fairness, efficiency, and certainty, and courts will enforce compliance where parties repeatedly fail to meet obligations.

From a precedent perspective, Biswas v Mukherjee reinforces Mitora by applying the “automatic trigger” principle for unless orders. It also demonstrates that attempts to cure non-compliance must be both timely and effective. Here, even though the appellant tendered documents to the Registry by the deadline, the failure to serve the respondents properly and the continued omission of relevant documents were sufficient to constitute breach.

For litigators, the decision is a cautionary tale about service and document completeness. The Court’s rejection of email service highlights the importance of understanding the ROC’s prescribed methods of service and the need for either consent or a court direction to depart from those methods. It also shows that courts will scrutinise whether the defaulting party has genuinely attempted to comply, not merely whether some steps were taken.

Legislation Referenced

  • Rules of Court (Cap 322, R 5, 2014 Rev Ed): O 57 rr 9 and 9A
  • Rules of Court (Cap 322, R 5, 2014 Rev Ed): O 62 r 6(1)(a)–(e)

Cases Cited

  • Mitora Pte Ltd v Agritrade International (Pte) Ltd [2013] 3 SLR 1179
  • Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another [2018] SGHC 271
  • Pradeepto Kumar Biswas v Sabyasachi Mukherjee and another [2019] SGCA 79

Source Documents

This article analyses [2019] SGCA 79 for legal research and educational purposes. It does not constitute legal advice. Readers should consult the full judgment for the Court's complete reasoning.

Written by Sushant Shukla

More in

Legal Wires

Legal Wires

Stay ahead of the legal curve. Get expert analysis and regulatory updates natively delivered to your inbox.

Success! Please check your inbox and click the link to confirm your subscription.