Content
1 IN THE HIGH COURT OF MALAYA AT KUALA LUMPUR IN THE STATE OF WILAYAH PERSEKUTUAN, MALAYSIA (CIVIL DIVISION) ORIGINATING SUMMONS NO: WA-24C-69-04/2017 In the matter of an Adjudication between Ritma Hebat Sdn Bhd and Kayangan Kemas Sdn Bhd And In the matter of the Adjudication Decision dated 31.3.2017 by R. Jayasingam Ratnasingam And In the matter of Section 28 of the Construction Industry Payment and Adjudication Act 2012 (“CIPAA”) And In the matter of Order 92 of the Rules of Court 2012 BETWEEN RITMA HEBAT SDN BHD (Company No. 646348-H) … PLAINTIFF AND 2 KAYANGAN KEMAS SDN BHD (Company No. 476046-U) … DEFENDANT (Heard together with) IN THE HIGH COURT OF MALAYA AT KUALA LUMPUR IN THE STATE OF WILAYAH PERSEKUTUAN, MALAYSIA (CIVIL DIVISION) ORIGINATING SUMMONS NO: WA-24C-90-05/2017 In the matter of an adjudication between Ritma Hebat Sdn Bhd and Kayangan Kemas Sdn Bhd And In the matter of Sections 4, 41 and 42 of the Specific Relief Act 1950 And In the matter of Sections 5, 6, 7, 12, 13, 15, 16, 25, 27 and 37(3) of the Construction Industry Payment and Adjudication Act 2012 (“CIPAA”) And In the matter of Order 92 of the Rules of Court 2012 3 BETWEEN KAYANGAN KEMAS SDN BHD (Company No. 476046-U) … PLAINTIFF AND RITMA HEBAT SDN BHD (Company No. 646348-H) … DEFENDANT THE JUDGMENT OF YA LEE SWEE SENG [1] Kayangan Kemas Sdn Bhd (“Kayangan Kemas”) as a Main Contractor had appointed Ritma Hebat Sdn Bhd (“Ritma Hebat”) as a Subcontractor by way of a Letter of Acceptance dated 25.10.2012 for the construction of a hotel in Sepang, Selangor. The original contract sum was for RM34,303,757.72. [2] Disputes having arisen between the parties after the completion of the project with respect to payments for work done, Ritma Hebat had proceeded with Adjudication against Kayangan Kemas under the Construction Industry Payment and Adjudication Act 2012 (“CIPAA”). 4 [3] The parties shall be referred to as “Ritma Hebat” and “Kayangan Kemas” or as Claimant and Respondent respectively as they were referred to in the Adjudication. Problem [4] In the Payment Claim served by the Claimant on the Respondent on 22.9.2016 the Claimant claimed an amount of RM3,845,456.95 for work done. The Respondent on 30.9.2016 served a Payment Response on the Claimant disputing the Claim. Proceedings in the Adjudication [5] In the Adjudication Claim served subsequently, the Claimant contended that they had completed its scope of Works under the Project and that the Certificate of Practical Completion (“CPC”) had been issued on 10.4.2014. The Claimant argued that as the Defects Liability Period for the Works had expired on 29.9.2015 the Retention Sum ought to have been released. [6] No Certificate of Making Good Defects (“CMGD”) has been issued and the Respondent’s reason for that was because the Claimant had failed to rectify the defects in the Lists of Defects given to them. 5 [7] The Claimant submitted their final claim in Claim No. 20 in the sum of RM3,845,456.54. The Respondent thereafter issued their Payment Certificate No. 20 together with a draft Statement of Final Account on 9.6.2015 where the amount certified to be paid to the Claimant was RM783,255.48 (excluding Retention Sum). [8] The Claimant took the position that there is an under-certification of its Final Claim. They further contended that pursuant to Clause 7 of the Letter of Acceptance dated 25.10.2012 the Retention Sum ought to be released upon the issuance of the CMGD. [9] The Claimant therefore claimed in their Adjudication Claim, after taking into consideration Payments previously paid by the Respondent, the outstanding sum of RM2,756,395.26. [10] The Adjudication Decision in favour of Ritma Hebat requires Kayangan Kemas as Respondent to make a payment of RM2,729,871.73, being the adjudicated sum, together with 5% interest per annum on the adjudicated sum from 6.1.2016 until full payment and cost of the adjudication proceedings. The Payment was ordered to be made not later than 14.4.2017. The said Adjudication Decision is exhibited in Exhibit A-3 of Ritma Hebat’s Affidavit in Support of the Enforcement Application. 6 Prayers [11] There are 2 Originating Summonses before the Court arising out of a Statutory Adjudication under the CIPAA. One is filed by Ritma Hebat dated 20.4.2017 for the enforcement of the Adjudication Decision (“Enforcement Application”) dated 31.3.2017 against Kayangan Kemas. There is also the Second Originating Summons filed by Kayangan Kemas to set aside the said Adjudication Decision (“Setting Aside Application”) by way of an Originating Summons dated 30.5.2017. There was also a further prayer for Stay of the Adjudication Decision until the disposal of a Writ action filed in the High Court of the same matter. [12] Both Originating Summonses were directed to be heard together as one is the flip side of the other. [13] Ritma Hebat had applied for the said Adjudication Decision to be enforced by this Court for the following reasons: a. The Adjudicator had considered all submissions, documents and authorities served on him by both parties; b. The Decision was delivered within 45 working days from the date of the service of the Adjudication Reply, pursuant to Subsection 12(a) of the CIPAA; 7 c. The Decision was made in writing, reasoned and had set out the adjudicated sum awarded, the manner of payment and time for payment as required by Subsections 12(3) and 12(4) of the CIPAA; d. The Decision is valid and the Adjudicator did not contravene any of the provisions set out in Section 15(a) – 15(d) of the CIPAA. [14] In enforcing an Adjudication Decision, Ritma Hebat submitted that the Court should not dwell into whether the Adjudicator had indeed achieved the right answer but merely whether the Adjudicator had answered the right questions referred to him. (See: Carillion Construction Ltd v Devonport Royal Dockyard Ltd [2005] EWCA Civ 1358; ACFM Engineering & Construction Sdn Bhd v Esstar Vision Sdn Bhd [2015] MLJU 1951; Bouygues (UK) Limited v Dahl-Jensen (UK) Limited [2000] BLR 522; View Esteem Sdn Bhd v Bina Puri Holdings Sdn Bhd [2015] MLJU 695. [15] Kayangan Kemas, on the other hand, opposed the Enforcement Application and had applied for the said Adjudication Decision to be set aside on the following grounds: 8 a. That the Adjudicator has acted in excess of jurisdiction and in breach of natural justice and not acting impartially/not in good faith in failing to take cognizance of the existence of the said Statement of Final Account between both parties which is a settlement between the parties, having the effect of terminating the Adjudication; b. That the Adjudicator has acted in excess of jurisdiction and/or made an error of law in failing to take into account the Statement of Final Account which was signed by both parties dated 2.3.2017 (“the said Statement of Final Account”) and which is a settlement of the dispute between the parties; c. That the issue of Debit Notes, Back Charges and Retention Sum raised in the Adjudication Response should have been considered by the Adjudicator and that there was a breach of natural justice when he failed to consider it merely on the narrow ground that these were not raised in the Payment Response filed. Principles [16] Section 15 of the CIPAA provides for setting aside of an Adjudication 9 Decision on the limited grounds set out as follows: “Improperly Procured Adjudication Decision An aggrieved party may apply to the High Court to set aside an adjudication decision on one or more of the following grounds: a) The adjudication decision was improperly procured through fraud or bribery; b) There has been a denial of natural justice; c) The adjudicator has not acted independently or impartially; or d) The adjudicator has acted in excess of his jurisdiction” (emphasis added) Whether a Settlement had been arrived at by the parties before the delivery of the Adjudication Decision such that the Adjudicator had no jurisdiction or had exceeded his jurisdiction to proceed with the Adjudication [17] The Claimant contended that the Adjudicator had acted well within his jurisdiction accorded to him under Section 27(1) of the CIPAA in not dealing with the said Statement of Final Account as the said Statement of Final Account was an issue which arose towards the tail end of the 10 adjudication proceeding. It was further submitted for the Claimant that there was no agreement made between parties to extend the jurisdiction of the Adjudicator to include the said Statement of Final Account in the proceeding. [18] To be fair to the Adjudicator, when the Respondent raised this new issue of the Statement of Account been duly signed between the parties, the Adjudicator in the exercise of his powers to give directions to the parties before him, had invited both parties to submit on the validity of the said Statement of Final Account. [19] The Respondent, on the other, had taken the position that the said Statement of Final Account between both parties was in effect the full and final settlement of the above dispute between both parties and the adjudication proceeding ought to be withdrawn or terminated. [20] Learned counsel for the Respondent, was candid in that he admitted that there was no jurisdictional challenge raised before the Adjudicator on the fact that if there is a settlement as alleged then, the Adjudicator lacked the jurisdiction to continue with the Adjudication. [21] Both learned counsel for the Claimant and Respondent are agreed that being a jurisdictional issue that goes to the core jurisdiction of the 11 Adjudicator, the jurisdictional challenge may be raised at any time and even at the setting aside stage. Section 37(3) of the CIPAA clearly provides that: “(3) An adjudication proceeding is terminated if the dispute being adjudicated is settled by agreement in writing between the parties or decided by arbitration or the court.” (emphasis added) [22] It is thus clear that if the parties had arrived at a settlement, then the parties should convey this to the Adjudicator and terminate the Adjudication. However the Adjudicator is given the liberty to proceed in a case where the challenge raised is a jurisdictional one as allowed under section 27(3) of the CIPAA as follows: “(3) Notwithstanding a jurisdictional challenge, the adjudicator may in his discretion proceed and complete the adjudication proceedings without prejudice to the rights of any party to apply to set aside the adjudication decision under section 15 or to oppose the application to enforce the adjudication decision under subsection 28(1).” (emphasis added) [23] Thus, contrary to what the learned counsel for the Respondent submitted in that nowhere in his Adjudication Decision, had the Adjudicator referred to the Settlement raised, the Adjudicator may choose the path of 12 least resistance in continuing with and concluding the Adjudication with the delivery of his Decision. [24] The law allows for the issue to be raised for the first time in the setting aside application, and this Court at that stage is able to revisit the issue afresh and unfettered by why the Adjudicator had decided one way or the other. The Court of Appeal in Martego Sdn Bhd v Arkitek Meor & Chew Sdn Bhd and another appeal [2016] MLJU 1827 considered this point of a jurisdictional issue not raised in the High Court and observed as follows: “[30] In resolving the conflicting submissions of counsel, we must look at whether the jurisdiction relates to the adjudicator’s initial jurisdiction. If we find that CIPAA 2012 caters for interim claims only, then any adjudication on a final claim would be void ab initio as the adjudicator lacked jurisdiction ab initio. This sort of jurisdiction challenge in our view can be mounted before us even when it had not been challenged or when there was no reservation of right to challenge at the adjudication process. [31] Other such challenges permitted under CIPAA 2012 would include: 13