Submit Article
Legal Analysis. Regulatory Intelligence. Jurisprudence.
Search articles, case studies, legal topics...
Singapore

PRADEEPTO KUMAR BISWAS v SABYASACHI MUKHERJEE & Anor

In PRADEEPTO KUMAR BISWAS v SABYASACHI MUKHERJEE & Anor, the Court of Appeal of the Republic of Singapore addressed issues of .

300 wpm
0%
Chunk
Theme
Font

Case Details

  • Citation: [2019] SGCA 79
  • Title: Pradeepto Kumar Biswas v Sabyasachi Mukherjee & another
  • Court: Court of Appeal of the Republic of Singapore
  • Date of Decision: 29 November 2019
  • Judges: Andrew Phang Boon Leong JA, Tay Yong Kwang JA and Quentin Loh J
  • Case Type: Civil Appeal (with Summons)
  • Civil Appeal No: Civil Appeal No 2 of 2019
  • Summons No: Summons No 91 of 2019
  • Related Suit: Suit No 1270 of 2014
  • Parties: Pradeepto Kumar Biswas (Appellant/Defendant in the suit) v Sabyasachi Mukherjee & Gouri Mukherjee (Respondents/Applicants/Plaintiffs in the suit)
  • Procedural Focus: Enforcement of an “unless order”; striking out for non-compliance with the Rules of Court and court directions
  • Key Procedural Device: Unless Order administered on 12 September 2019
  • Outcome: Appeal struck out for breach of the Unless Order
  • Reported Length: 14 pages; 3,321 words
  • Cases Cited (as provided): [2019] SGCA 79; Mitora Pte Ltd v Agritrade International (Pte) Ltd [2013] 3 SLR 1179

Summary

In Pradeepto Kumar Biswas v Sabyasachi Mukherjee & another ([2019] SGCA 79), the Court of Appeal considered whether an appeal should be struck out for breach of an “unless order” previously administered by the court. The Unless Order required the appellant to rectify deficiencies in his record of appeal and core bundle, serve relevant documents on the respondents, and tender those documents to the Registry by a specified deadline, failing which the appeal would be struck out.

The Court of Appeal held that the appellant breached the Unless Order. The breach was not only a late filing/serving of the documents by one day, but also involved continued non-rectification of deficiencies—documents relevant to the appeal remained omitted. The court further found the breach contumelious and not disproportionate to enforce, applying the established approach in Mitora that an unless order’s adverse consequences are triggered automatically, with the burden on the defaulting party to show the breach was not intentional or contumelious. The appeal was therefore struck out.

What Were the Facts of This Case?

The litigation began in the High Court as Suit No 1270 of 2014, where Sabyasachi Mukherjee and Gouri Mukherjee were the plaintiffs and Pradeepto Kumar Biswas was the defendant. The case later proceeded to the Court of Appeal, giving rise to Civil Appeal No 2 of 2019. The procedural history in the Court of Appeal is central to the decision, because the court’s enforcement of the Unless Order was grounded in repeated and persistent non-compliance with the Rules of Court and court directions.

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 his Case, the record of appeal, a core bundle of documents, and a bundle of authorities by 12 April 2019. The appellant requested an extension of time on 9 April 2019, but did not file a formal application because the respondents had not consented. As a result, the extension was not properly obtained.

On 12 April 2019, the appellant filed his Case and forms of record of appeal and core bundle, but the respondents wrote on 18 April 2019 pointing out contraventions of the ROC requirements and the appellant’s failure to file a bundle of authorities. A case management conference (“CMC”) was held on 30 April 2019. At that CMC, 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 any application by 10 May 2019, although he filed a bundle of authorities.

After further correspondence, the court directed on 28 May 2019 that the appellant file by 7 June 2019 an application to rectify defects in his record of appeal and core bundle. If the appellant failed to do so, the respondents would be at liberty to proceed with their own application. The court also stayed timelines for the respondents’ Case to the later of specified dates depending on whether applications were filed and determined. A further CMC on 31 May 2019 reiterated the court’s directions. The appellant indicated he would provide revised documents by 4 June 2019, but the respondents said he did not. On 7 June 2019, the appellant filed CA/SUM 66/2019 seeking leave to refile the record of appeal and core bundle, and leave was granted to refile by 10 July 2019. The appellant then filed revised documents on 10 July 2019, but the respondents maintained that he remained in non-compliance, including by failing to file and serve relevant documents.

By 1 August 2019, the respondents filed CA/SUM 91/2019 seeking to strike out the appeal for failure to comply with the ROC requirements. The Court of Appeal found the appellant’s failure to comply amounted to contumelious conduct, but granted one last opportunity by administering an Unless Order on 12 September 2019. The Unless Order required the appellant to rectify deficiencies in his record of appeal and core bundle, serve relevant documents on the respondents, and tender the relevant 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 at 6:08pm after it had closed. He was therefore unable to serve the documents then, and sought to serve them by email at 9:01pm. On 1 October 2019—one day after the Unless Order deadline—the appellant filed the forms of the record of appeal and core bundle and served the documents at the respondents’ solicitors’ office.

The first key issue was whether the appellant had breached the Unless Order. This required the court to examine both (i) whether the appellant met the deadline for tendering and serving the relevant documents, and (ii) whether the appellant actually rectified the deficiencies in the record of appeal and core bundle as required by the Unless Order. The court also had to assess the appellant’s argument that service by email on 30 September 2019 was valid and should be treated as compliance.

The second issue was whether the Unless Order should be enforced, leading to the striking out of the appeal. Even where a breach is established, the court retains a discretion whether to enforce the adverse consequences. The Court of Appeal therefore had to apply the proportionality framework and the principles governing enforcement of unless orders, including the approach articulated in Mitora.

How Did the Court Analyse the Issues?

1. Breach of the Unless Order

The Court of Appeal held that the appellant breached the Unless Order. The court’s reasoning proceeded in two main steps. First, it found that the appellant did not meet the deadline. Although the appellant tendered documents to the Registry by 30 September 2019, he served the documents on the respondents only on 1 October 2019, one day after the Unless Order deadline. The appellant attempted to argue that he had served the documents on 30 September 2019 via email, and that this should count as compliance.

The court rejected the email service argument as invalid. It relied on the service provisions in O 62 r 6(1)(a)–(c) of the ROC, which set out the methods of service. Email service was not among the methods listed in O 62 r 6(1)(a)–(c). The court also found no indication that the respondents had agreed to service via email within the meaning of O 62 r 6(1)(d). Further, the court noted that it had not directed the appellant to effect service via email within the meaning of O 62 r 6(1)(e). In other words, the appellant could not unilaterally choose email service to cure a missed deadline when the ROC and the court’s directions did not permit it.

2. Continued failure to rectify deficiencies

Second, the court found that the appellant failed to rectify the deficiencies in his appeal documents. The Unless Order was not merely about filing and serving documents by a deadline; it required rectification of deficiencies in the record of appeal and core bundle. The court observed that numerous documents relevant to CA/CA 2/2019 were still omitted. While the court did not list all omitted documents in the excerpt provided, it emphasised that the omissions were significant enough to show that the appellant had not complied with the substantive requirement to rectify deficiencies.

This aspect of the analysis is important because it demonstrates that compliance with an unless order is assessed holistically. Even if some documents were tendered to the Registry on time, the Unless Order could still be breached if the record and core bundle remained deficient and relevant materials were missing.

3. Whether enforcement was appropriate

Having found a breach, the Court of Appeal turned to whether the Unless Order should be enforced. The court applied the approach in Mitora, where it was held that breach of an unless order automatically triggers the specified adverse consequences. The onus then shifts to the defaulting party to demonstrate that the breach was not intentional and contumelious, so as to avoid enforcement. The court also stated that proportionality guides the exercise of discretion.

The court was satisfied that the appellant’s breach was contumelious and that enforcement was proportionate. It reasoned that the appellant’s conduct suggested the attempt to comply was not bona fide. The court had previously highlighted that the appellant had been afforded at least two opportunities to remedy non-compliance, but failed to take them. The first opportunity arose at the CMC on 30 April 2019, when the parties agreed the appellant would take out an application to remedy non-compliance by 10 May 2019; the appellant did not file any application by that date. The second opportunity arose when the court directed on 28 May 2019 that the appellant file an application by 7 June 2019; while the appellant did take out CA/SUM 66/2019 and was granted leave to refile, the court found that further non-compliance persisted.

The court’s reasoning reflects a broader judicial concern: unless orders are designed to ensure procedural discipline and fairness to the opposing party. Where a litigant repeatedly fails to comply with procedural requirements despite warnings and opportunities to remedy, the court is more likely to enforce the adverse consequences. In this case, the appellant’s pattern of non-compliance, combined with the failure to rectify deficiencies even after the Unless Order was administered, supported enforcement.

What Was the Outcome?

The Court of Appeal ordered that Civil Appeal No 2 of 2019 be struck out. The practical effect was that the appellant’s appeal could not proceed, and the respondents were spared the further time and expense associated with an appeal that had not been properly prepared and served in accordance with the ROC and court directions.

The decision also underscores that the enforcement of unless orders is not a mere technicality. Once the court is satisfied that the Unless Order was breached and that the breach is contumelious and proportionate to enforce, the specified consequence—here, striking out—will follow.

Why Does This Case Matter?

This case is significant for practitioners because it illustrates the Court of Appeal’s strict approach to compliance with unless orders and the procedural requirements governing appeal documents. The decision reinforces that unless orders are not discretionary “warnings” but mechanisms with real consequences. When a deadline is stated and the adverse consequence is specified, the court will generally enforce it unless the defaulting party can show the breach was not intentional or contumelious.

From a litigation management perspective, Biswas v Mukherjee highlights the importance of understanding the ROC’s service rules and the limits of unilateral action. The appellant’s reliance on email service—without agreement or a specific court direction—was rejected. This serves as a cautionary lesson for counsel: service must comply with the ROC and any relevant court directions, particularly when deadlines are tied to enforcement consequences.

Finally, the case contributes to the jurisprudence on proportionality in enforcement decisions. While the court acknowledged that proportionality guides discretion, it found that repeated opportunities to cure non-compliance, coupled with continued deficiencies, made enforcement proportionate. For law students and practitioners, the decision provides a clear example of how courts evaluate contumelious conduct and why procedural non-compliance can become fatal to a party’s appeal.

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

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
1.5×

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.