Submit Article
Legal Analysis. Regulatory Intelligence. Jurisprudence.
Singapore

Linkforce Pte Ltd v Kajima Overseas Asia Pte Ltd [2017] SGHC 46

In Linkforce Pte Ltd v Kajima Overseas Asia Pte Ltd, the High Court of the Republic of Singapore addressed issues of Building and construction law — Dispute resolution.

Case Details

  • Citation: [2017] SGHC 46
  • Case Title: Linkforce Pte Ltd v Kajima Overseas Asia Pte Ltd
  • Court: High Court of the Republic of Singapore
  • Date of Decision: 13 March 2017
  • Judge: Foo Chee Hock JC
  • Coram: Foo Chee Hock JC
  • Case Number: Originating Summons No 947 of 2016 (Summons No 4806 of 2016)
  • Procedural History: Appeal to this decision in Civil Appeal No 27 of 2017 withdrawn on 17 April 2017
  • Plaintiff/Applicant: Linkforce Pte Ltd (formerly known as AMEC Group Singapore Pte Limited)
  • Defendant/Respondent: Kajima Overseas Asia Pte Ltd (formerly known as Kajima Singapore Pte Ltd)
  • Counsel for Applicant: Joseph Lopez, Intan Krishanty Wirayadi and Chong Li Tang (Joseph Lopez LLP)
  • Counsel for Respondent: Ng Kim Beng and Zhuang WenXiong (Rajah & Tann Singapore LLP)
  • Legal Area: Building and construction law — Dispute resolution
  • Issue Type: Adjudication — setting aside
  • Statutes Referenced: Building and Construction Industry Security of Payment Act (Cap 30B, 2006 Rev Ed) (“SOPA”); Building and Construction Industry Security of Payment Regulations (Cap 30B, Rg 1, 2006 Rev Ed)
  • Adjudication Determination: Dated 5 September 2016 (“AD”) by Adjudicator Mr Seah Choo Meng
  • Adjudication Award: $893,751.86 plus costs of $22,470
  • Payment Claim: Payment claim (“PC 33”) served 3 June 2016 for $1,198,978.14 (work up to 31 May 2016)
  • Adjudication Application: Lodged 8 July 2016 (“AA”)
  • Payment Response: Lodged 18 July 2016 (response raised premature AA objection); ultimately payment response provided on 20 July 2016

Summary

Linkforce Pte Ltd v Kajima Overseas Asia Pte Ltd [2017] SGHC 46 concerns an application to set aside an adjudication determination under Singapore’s Building and Construction Industry Security of Payment Act (SOPA). The dispute arose from a subcontract for the design, supply, installation, testing, commissioning and maintenance of a fire protection installation. Linkforce served a payment claim on 3 June 2016 and, after Kajima did not provide a timely payment response, Linkforce commenced SOPA adjudication. The adjudicator awarded Linkforce $893,751.86 and costs, but Kajima later sought to set aside the adjudication determination and the related court order enforcing it.

The High Court (Foo Chee Hock JC) held that the adjudication application was lodged prematurely, contrary to the strict timelines mandated by SOPA. Because the timelines are a critical part of SOPA’s legislative scheme to ensure prompt resolution of payment disputes, non-compliance with those timelines rendered the adjudication determination invalid. The court therefore granted Kajima’s application to set aside both the adjudication determination and the enforcement order.

What Were the Facts of This Case?

Under a subcontract dated 1 November 2012, Kajima appointed Linkforce to carry out fire protection installation works. These subcontract works were part of a larger project under a main contract between Kajima and Mediacorp Pte Ltd for the “Proposed Erection of 12 Storey Media Complex” at Mediapolis @ One North. The subcontract contained provisions governing the timing of interim payment applications and the service of payment claims.

On 3 June 2016, Linkforce served payment claim PC 33 on Kajima, claiming $1,198,978.14 for work done up to 31 May 2016. Linkforce’s position was that Kajima was required to provide a payment response within 21 days of the payment claim being served, pursuant to the subcontract’s payment response mechanism (as reflected in clause 27(b) of the subcontract). Linkforce alleged that Kajima failed to provide a timely payment response by the contractual deadline, and this triggered Linkforce’s intention to apply for adjudication.

Linkforce notified Kajima on 7 July 2016 of its intention to apply for adjudication and lodged the adjudication application on 8 July 2016. Kajima then lodged an adjudication response on 18 July 2016. In that response, Kajima raised a jurisdictional objection: it argued that Linkforce’s adjudication application was premature because PC 33 had been served before the contractually stipulated date for interim payment applications. Kajima relied on clauses 32(b) and 27(a) of the subcontract, which indicated that interim payment applications were to be made on the last day of each month (or the next business day if the last day fell on a Sunday or public holiday). On Kajima’s case, PC 33 should have been served on 30 June 2016, not 3 June 2016, and therefore Kajima’s payment response was not due by 24 June 2016.

To counter Kajima’s jurisdictional objection, Linkforce relied on an email dated 25 August 2014 from Kajima’s project manager. Linkforce adduced this email for the first time during the adjudication proceedings via supplementary submissions. The email instructed contractors that from the next progress claim, they needed to submit supporting documentation by 5 October 2014 and that if they did not provide the specified documents, Kajima would not accept the claim. Linkforce argued that this email amounted to a waiver or variation of the subcontract’s requirement that payment claims be submitted on the last day of the month, effectively shifting the deadline to the fifth day of each month. The adjudicator accepted this reasoning and dismissed Kajima’s objection, finding that the adjudication application was lodged on time. The adjudicator further held that, due to SOPA’s bar on considering late payment responses, he was precluded from considering Kajima’s payment response provided on 20 July 2016, with the result that Kajima’s backcharge counterclaim was not considered.

The central legal issue was whether the adjudication application (AA) was lodged prematurely. This question was determinative because SOPA’s adjudication regime depends on strict compliance with statutory timelines. If Linkforce lodged the AA before the payment response period had expired, the adjudicator would lack jurisdiction, and the adjudication determination would be liable to be set aside under SOPA.

Related to the premature-lodgement issue was the question of whether the subcontract’s payment claim deadline had been varied, waived, or estopped by Kajima’s conduct—specifically, whether the 25 August 2014 email could properly be treated as evidence that the parties had shifted the timing for submitting payment claims from the last day of each month to the fifth day of each month. If the deadline was indeed shifted, then Kajima’s payment response would have been due later, and the AA might not have been premature.

A further issue raised by Kajima was procedural fairness and statutory compliance in the adjudication process. Kajima argued that Linkforce should not have been entitled to rely on the email during the adjudication conference because it was not attached to the AA, allegedly breaching SOPA requirements read with the SOPA regulations. Kajima also argued that the adjudicator’s decision not to consider Kajima’s payment response, coupled with Linkforce’s belated adduction of the email, violated natural justice and the adjudicator’s duties under SOPA.

How Did the Court Analyse the Issues?

Foo Chee Hock JC began by restating the legal test for setting aside an adjudication determination under SOPA. The court referred to the established approach in Lee Wee Lick Terence v Chua Say Eng [2013] 1 SLR 401, where the court may set aside an adjudication determination if the claimant has not complied with provisions under the Act that are so important that it is the legislative purpose that an act done in breach should be invalid. The court emphasised that such provisions may be treated as mandatory or essential to the legislative scheme, and breach results in invalidity.

The judge then identified the relevant provision: s 13(3)(a) of SOPA. This provision concerns the timing for lodging an adjudication application. The court held that the timelines under SOPA are indeed such important provisions. The judge relied on earlier decisions including YTL Construction (S) Pte Ltd v Balanced Engineering & Construction Pte Ltd [2014] SGHC 142 and Grouteam (HC) (UES Holdings Pte Ltd v Grouteam Pte Ltd [2016] 1 SLR 312) to support the proposition that out-of-time adjudication applications invalidate adjudication determinations because SOPA timelines must be strictly followed. Although Grouteam (HC) was later overruled on its facts by Grouteam Pte Ltd v UES Holdings Pte Ltd [2016] 5 SLR 1011, the Court of Appeal did not disagree with the broader discussion that time limits are critical to SOPA’s purpose of ensuring prompt resolution of payment disputes.

Importantly, the court treated the “premature” lodgement scenario as analytically equivalent to an “out-of-time” lodgement scenario. Even though the earlier authorities often involved adjudication applications lodged after the seven-day period, the judge reasoned that the same strictness applies when the AA is lodged before the statutory period begins. The legislative purpose is served only if the adjudication process is triggered at the correct time, ensuring that the payment response period has run its course and that the adjudication is not commenced prematurely.

Having established that non-compliance with s 13(3)(a) is capable of invalidating the adjudication determination, the court turned to the merits of the adjudicator’s reasoning on the subcontractual deadline. The adjudicator had accepted Linkforce’s argument that the email evidenced waiver or variation, shifting the deadline for payment claims to the fifth day of each month. The High Court’s analysis therefore required examination of whether the email could realistically be treated as altering the contractual timing for serving PCs, and whether Kajima’s payment response was therefore due later than Kajima contended.

While the excerpt provided is truncated, the court’s approach is clear from the reasoning visible in the judgment: the court treated the premature-lodgement issue as a threshold matter and indicated that it could examine the merits of the adjudicator’s decision because the jurisdictional defect (premature AA) could also lead to a breach of natural justice—specifically, the wrongful exclusion of Kajima’s payment response from the adjudicator’s consideration. This is consistent with the logic that if the adjudicator’s jurisdiction is improperly invoked, the adjudicator’s subsequent procedural consequences (including the application of SOPA’s late-response bar) may be undermined.

In effect, the court’s analysis placed the statutory timeline at the centre of the inquiry. Even if the adjudicator’s interpretation of the email and subcontract provisions might otherwise be arguable, the statutory scheme required the court to determine whether the AA was lodged at a time when SOPA permitted adjudication to be commenced. If the AA was lodged before the payment response period ended, the adjudication determination could not stand.

What Was the Outcome?

The High Court granted Kajima’s application to set aside the adjudication determination dated 5 September 2016 and the related court order obtained by Linkforce on 19 September 2016 to enforce the AD. The practical effect was that Linkforce could not rely on the adjudication award as a basis for enforcement under the SOPA adjudication regime.

Although Linkforce appealed, that appeal was withdrawn on 17 April 2017. Accordingly, the High Court’s decision remained the final determination on the validity of the adjudication process and the enforceability of the adjudication award.

Why Does This Case Matter?

Linkforce v Kajima is significant for practitioners because it reinforces the strict, time-sensitive nature of SOPA adjudication. The decision underscores that both premature and late adjudication applications can undermine the validity of an adjudication determination. For contractors and subcontractors, this means that careful attention must be paid not only to statutory timelines but also to the contract provisions that determine when payment claims are properly served and when payment responses become due.

Second, the case illustrates the evidential and contractual complexity that can arise when parties seek to argue that contractual payment claim deadlines have been waived, varied, or estopped by conduct. While the adjudicator in this case accepted that an email could shift the deadline, the High Court’s willingness to scrutinise the jurisdictional timing demonstrates that such arguments will not necessarily save an adjudication determination if the statutory trigger for adjudication was not satisfied.

Third, the decision highlights the interaction between jurisdictional defects and natural justice concerns. Where an adjudication is commenced prematurely, the procedural consequences—such as the adjudicator’s refusal to consider a payment response on the basis of SOPA’s late-response bar—may be characterised as wrongful exclusion. This can strengthen an application to set aside by linking statutory non-compliance to fairness in the adjudication process.

Legislation Referenced

  • Building and Construction Industry Security of Payment Act (Cap 30B, 2006 Rev Ed) (“SOPA”), including ss 12(5), 13(3)(a), 15(3)(a), 16(3)(c)
  • Building and Construction Industry Security of Payment Regulations (Cap 30B, Rg 1, 2006 Rev Ed), including reg 7(2)(d)

Cases Cited

  • Lee Wee Lick Terence v Chua Say Eng [2013] 1 SLR 401
  • UES Holdings Pte Ltd v Grouteam Pte Ltd [2016] 1 SLR 312 (“Grouteam (HC)”)
  • Grouteam Pte Ltd v UES Holdings Pte Ltd [2016] 5 SLR 1011
  • YTL Construction (S) Pte Ltd v Balanced Engineering & Construction Pte Ltd [2014] SGHC 142
  • Chase Oyster Bar v Hamo Industries [2010] NSWCA 190
  • [2014] SGHC 142
  • [2015] SGHC 226
  • [2017] SGHC 46

Source Documents

This article analyses [2017] SGHC 46 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.