Malaysia · 5 minute read

Jack-In Pile v Bauer: Why an Old Contract Defeated a CIPAA Payment Claim

An unpaid invoice can be recent while the contract behind it is old. This Federal Court case shows why that difference must be checked before using CIPAA.

Payment claimsCIPAA adjudicationCourt procedure

At a glance

  • Check when the construction contract was made, not just when the unpaid invoice arose.
  • Keep the original claim, revised claim and adjudicated sum separate in the account.
  • An unavailable CIPAA route does not itself decide every contractual remedy.

The payment problem behind the case

A subcontractor finishes work, submits a progress claim and expects the payment process to follow. The main contractor responds that its own employer has not paid. For a business paying workers and suppliers, that answer creates an immediate cash-flow problem. Jack-In Pile concerned exactly the sort of payment chain that makes statutory adjudication attractive, but the decisive obstacle was the age of the contract.

Bauer appointed Jack-In Pile to supply and install spun piles under a letter of award dated 16 March 2011. The subcontract price was RM1,850,000. Clause 11.1 linked payment to Bauer receiving the corresponding progress payment from its employer, followed by a seven-day payment period. These were agreed payment terms, not simply an explanation invented after the invoice arrived.

The amount claimed was not the final outcome

Jack-In Pile served a CIPAA payment claim on 3 August 2016. Progress Claim 8 initially sought RM1,053,034, later reduced during adjudication to RM906,034. The adjudicator awarded that reduced amount. The High Court permitted enforcement and refused Bauer's application to set the decision aside; the Court of Appeal reversed that outcome.

The Federal Court dismissed Jack-In Pile's appeals. It held the adjudication proceedings and decision void because CIPAA did not govern this earlier contract. The RM906,034 therefore cannot accurately be described as damages finally recovered by the subcontractor. The judgment records dismissal with costs but does not specify a costs figure in its concluding order. It does not establish what, if anything, was eventually paid under another process.

Why the contract date controlled the result

CIPAA came into operation on 15 April 2014. The court held that the Act operates prospectively and does not apply to construction contracts made before that commencement. A later payment dispute does not, by itself, move an earlier contract into the statutory scheme. That distinction matters because the adjudication was begun well after commencement, yet the underlying bargain remained earlier.

The court considered that CIPAA affected substantive contractual rights. In particular, section 35 could invalidate conditional payment provisions of the kind relied on here. Applying that change to an earlier bargain would do more than provide a convenient new place to argue: it would change the parties' agreed legal position. The court found no sufficient legislative direction for that retrospective effect.

Earlier reasoning in UDA Holdings had supported retrospective application. Jack-In Pile rejected that approach. The judgment also explained that View Esteem had not decided the same prospectivity issue. Reading a favourable passage from an earlier case without checking its actual issue and later treatment can therefore produce the wrong starting point.

What the decision does and does not answer

The result concerned access to this statutory adjudication process. It did not assess every possible contractual route for collecting the money, and it should not be used to declare that all older conditional payment clauses are automatically enforceable in every situation. The language of the particular agreement, the factual trigger for payment and other available legal arguments still require examination.

For a newer contract, equally, the existence of an unpaid invoice does not alone establish a successful CIPAA claim. Identify the contractual party responsible for payment, the work or services supplied, the contractual basis for the amount and when it became due. A strong valuation file cannot repair a basic mistake about the contract to which the claim belongs.

Variations and replacement agreements deserve particular care. A later instruction, revised price or extension does not necessarily create a new contract. Conversely, genuinely replacing the bargain may raise a different analysis. Keep the signed documents and correspondence that show what the parties actually agreed; do not simply select the date that makes the desired procedure appear available.

Preparing the file before spending on a claim

Start with a chronology that separates contract formation, work, certification, invoicing and non-payment. Put the letter of award beside any acceptance, formal agreement, amendments and incorporated conditions. Then match each unpaid item to its supporting measurement, certificate, invoice and payment history. This makes it possible to identify whether the dispute is about value, maturity of payment or the available forum.

Where the other side relies on an upstream-payment condition, ask for the actual wording and the evidence said to trigger it. A general statement that the employer has not paid is different from a properly analysed contractual defence. Record correspondence requesting certification and payment, and preserve evidence of any part-payments so that the amount pursued remains accurate.

Before commencing proceedings, assess the appropriate contractual dispute process, any arbitration agreement, time limits and realistic recovery prospects. Those questions are separate from whether the work was performed satisfactorily. The practical lesson of Jack-In Pile is that selecting the payment procedure belongs at the beginning of the claim review. An adjudication victory is expensive to defend if the legislation never applied to the bargain in the first place.

A useful check on the payment schedule

Keep the contract price separate from the outstanding balance. A contract price describes the agreed commercial scope; it is not automatically the amount presently payable. A progress claim may reflect only part of the works, while certification, previous payments and agreed reductions can change the balance. In this case the original progress claim, the reduced claim and the subcontract price were different figures, serving different purposes.

A sensible working schedule should show those stages in separate columns and explain every deduction. If the claim is reduced, record whether that reflects a payment, an agreed correction or a withdrawn item. Do not invent a reason where the evidence is silent. That discipline helps both parties evaluate the dispute and keeps a settlement discussion focused on the actual unpaid items.

Judgment and sources

  1. Jack-In Pile (M) Sdn Bhd v Bauer (Malaysia) Sdn Bhd & Another Appeal — grounds of judgment — Paras 1, 5–9: commencement, contract, conditional payment, claim and award; paras 26–30, 45–55: prospectivity and earlier authorities; para 72: dismissal, award void, costs without stated sum.

Plain-language explanations of published Malaysian judgments. Practical guidance is commentary; the original judgment remains the authoritative account of the court’s findings.