What Defences Are Available to a Breach of Contract Claim in Malaysia?

Being sued for breach of contract does not mean the only question is whether your company did something wrong.

A claimant still has to prove the case it has pleaded: what the contract required, that the relevant obligation was binding and due, how your company breached it, that the breach caused recoverable loss, and why the amount claimed is legally and factually justified.

For a defendant, that creates several possible lines of defence. Some attack liability entirely. Others reduce the scope of the alleged breach, break the link between breach and loss, rely on the claimant's own conduct, or limit the amount that can be recovered.

The strongest defence is rarely found by choosing a legal label first. It is found by rebuilding the contract, chronology and evidence, then asking which part of the claimant's case does not hold together.

Start with what the claimant actually says your company promised

Many contract disputes become distorted once the relationship breaks down. The claimant may describe the commercial expectation broadly—"you promised to deliver the project", "you guaranteed the result", "you agreed to pay"—while the written contract contains a narrower obligation.

The defence should start with the executed contract, schedules, specifications, statements of work, purchase orders, amendments and any documents incorporated into the agreement.

Then isolate the exact obligation said to have been breached.

Was the company required to achieve a result, or only to perform a defined scope? Was the deadline fixed, conditional or capable of extension? Did payment depend on certification, acceptance or another event? Was a particular risk allocated to the claimant rather than your company?

A defendant should not concede the claimant's interpretation simply because the commercial relationship ended badly.

Had the obligation actually become due?

Sometimes the alleged breach assumes that an obligation had already crystallised when the contract made performance dependent on something else happening first.

A payment may depend on an invoice, certification or delivery milestone. A contractor may need site access before work can proceed. A supplier may require approved specifications. A technology provider may depend on the customer providing data, credentials or decisions.

If a condition, approval, dependency or reciprocal obligation had not been satisfied, the defence may need to focus on whether your company's duty had actually become enforceable in the way the claimant alleges.

This is why chronology matters. The question is not only "what did our company do?" but also "what had the other side done, and what was supposed to happen next under the contract?"

Did your company actually fail to perform the obligation alleged?

A claim often compresses months of performance into a single accusation of non-performance.

The defence should separate the work into what was completed, what was rejected, what remained outstanding, what was disputed and what was changed during the project.

For example, a claimant may say delivery was incomplete. Your records may show that the agreed scope was delivered but additional work was later requested. A customer may say the product failed specifications, while the accepted testing record shows the product met the original specification before the specification changed.

The underlying documents matter more than retrospective descriptions. Acceptance records, completion certificates, emails, meeting minutes, delivery notes, test results and payment approvals can materially change the picture.

Did the claimant's own conduct affect performance?

A business accused of breach should test the claimant's own obligations with the same discipline.

Did the claimant fail to pay an earlier invoice? Delay an approval? Refuse access? Provide incorrect information? Change the scope without extending time? Fail to supply material that your company needed in order to perform?

The claimant's conduct does not automatically excuse every failure by the defendant. The effect depends on the contract and facts. But it may affect whether a breach occurred, whether performance was prevented or delayed, whether time was extended, and whether the claimant can prove the loss it attributes to your company.

A useful defence chronology therefore has two tracks: what your company was required to do, and what the claimant was required to do at the same time.

Did the parties change the deal in practice?

Long-running commercial contracts rarely operate exactly as they did on signing day.

Deadlines move. Specifications change. Interim solutions are accepted. Payment schedules are revised. Project managers approve deviations. Parties continue performance after a missed milestone.

Those facts can raise issues involving contractual variation, waiver, election, estoppel or agreed extensions. Their legal effect is fact-sensitive and can depend on formal variation clauses, authority, communications and the parties' conduct.

For the defence team, the immediate task is evidential: identify every occasion on which the claimant accepted a different course of performance from the one it now says was mandatory.

An email saying "proceed on the revised timeline" may matter more than an internal recollection that everyone informally knew the original date was unrealistic.

If termination is part of the dispute, test it separately

Termination can change the shape of a breach claim.

If your company terminated the contract and the claimant says that termination was itself wrongful, the defence needs a separate analysis of the termination clause, notice requirements, cure periods, timing and the conduct of both parties.

Do not collapse that analysis into a general argument that "the other side breached first". A valid complaint about the claimant's performance does not necessarily answer whether the contractual or legal right to terminate had arisen and was exercised correctly.

That issue is covered in more detail in our dedicated guide to a company that terminated a contract and is now being sued for wrongful termination.

Even if there was a breach, did it cause the loss claimed?

Liability and quantum are different questions.

A company can be in breach of one obligation without being responsible for every financial problem the claimant experienced afterwards.

Suppose a supplier delivered two weeks late, but the claimant's project was already delayed by regulatory approvals. Or a service provider made an error, but the customer continued using the system for months before a separate event caused the alleged loss.

The defence should ask what loss was actually caused by the breach relied on, what loss would have happened anyway, and what other events contributed to the outcome.

This is often where expert, accounting or operational evidence becomes as important as the contract itself.

Challenge the amount, not just the allegation

A large damages figure is not self-proving.

The claimant needs evidence for the loss it says was caused by the breach. The defence should test the calculation, supporting documents, assumptions and whether the same loss has been claimed under more than one heading.

It should also examine whether the claimant took reasonable steps to reduce avoidable loss after the alleged breach, and whether parts of the claim are too remote from the contractual breach to be recoverable.

From a commercial perspective, this can be decisive. A defendant may have limited room to dispute that something went wrong, yet still have a strong case that the amount claimed is substantially overstated.

Read the contract's risk-allocation clauses before assuming exposure

The contract may contain clauses that materially affect the claim.

These may include liability caps, exclusions of particular categories of loss, agreed damages provisions, indemnities, warranty limitations, notification requirements, force-majeure provisions, exclusive-remedy clauses, dispute procedures or contractual time bars.

None should be treated as automatically decisive. Their effect depends on the drafting, applicable law and facts.

But a defence that focuses only on whether a breach occurred can miss the commercial protections the parties negotiated before the dispute existed.

Build a separate list of every clause that changes who bears the risk, how a claim must be notified or how much can ultimately be recovered.

Check whether the claim is out of time

Limitation should be checked early rather than left until the end of the defence.

The relevant time limit can depend on where the claim is brought, the applicable limitation legislation, the type of claim and when the cause of action accrued. Malaysia does not have one limitation statute that should simply be applied identically across Peninsular Malaysia, Sabah and Sarawak.

The defence team should therefore identify the governing limitation regime and calculate the relevant dates from the actual cause of action instead of relying on a generic rule of thumb.

If limitation is potentially available, preserve it carefully in the pleadings and legal strategy.

Is there a set-off or a separate counterclaim?

Sometimes the claimant is owed money, but your company is also owed money arising from the same relationship or a separate breach.

That does not automatically erase the claim. The legal and procedural treatment of set-off and counterclaims needs to be assessed properly.

But commercially, the existence of a genuine cross-claim can change settlement leverage, the net exposure and the way the dispute should be pleaded.

If your company may have its own claim, see our guide on whether a defendant should counterclaim rather than treating the claimant's lawsuit as the whole dispute.

What evidence changes the defence?

A good defence theory should be tied to documents that can prove it.

Preserve and review:

• the executed agreement, schedules and amendments;

• statements of work, purchase orders and specifications;

• notices, demands and responses;

• project plans, milestone records and acceptance documents;

• payment records, invoices and certification documents;

• emails, messaging records and meeting minutes showing extensions, approvals or changes;

• records of the claimant's own delays or failures;

• internal contemporaneous reports explaining what happened;

• documents supporting or challenging the claimant's alleged loss; and

• insurance, indemnity or third-party recovery documents where relevant.

The goal is not to collect every document the company has. It is to identify the evidence that answers each element of the claimant's case.

Build a defence matrix before deciding your position

A practical way to assess the case is to reduce it to a working matrix.

This exercise forces the business to distinguish a real defence from a position it merely hopes is true.

Should the company defend, narrow the dispute or settle?

A defensible point is not always worth taking to trial.

Once the defence matrix is built, management should consider the value at stake, evidence quality, cost of litigation, management time, operational distraction, relationship impact, insurance position and realistic settlement range.

Some disputes should be defended firmly. Some are better narrowed to a smaller set of issues. Some should be settled early because the legal upside does not justify the commercial cost.

The key is to make that decision after the case has been analysed, not because the claim amount is intimidating or because the business is angry.

When should litigation counsel become involved?

If proceedings have already been served, legal advice should be obtained immediately because court deadlines and procedural consequences can arise quickly. Our guide on what a company should do after being sued deals with that immediate-response stage.

For the substantive defence, counsel should review the contract, pleadings or demand, chronology, evidence, claimant conduct, alleged loss and risk-allocation clauses together.

Legal That Works assists Malaysian businesses defending commercial breach-of-contract claims, including assessing substantive defences, responding to proceedings, managing evidence, negotiating resolution and conducting the litigation where required.

This article is for general information only and does not constitute legal advice. Every transaction and every set of facts is different. Obtain specific advice from a qualified adviser before acting on any part of it.

View our civil litigation defence for breach of contract service if your company has received a claim or is already facing proceedings.