Digital transformation doesn’t come cheap — and for years, businesses claiming capital allowances on software upgrades faced pushback from the Inland Revenue Board (IRB), which routinely treated development and customization fees as non-qualifying expenses. The High Court of Malaya’s ruling in favour of Malayan Banking Berhad (Maybank) puts that position to rest, at least for functionally essential software.
The case turned on RM221.968 million Maybank spent upgrading its core banking software between 2014 and 2017 — and whether that spend qualifies as “plant” under Schedule 3 of the Income Tax Act 1967 (ITA). The reasoning has a familiar shape to readers of this series: courts increasingly look at what an expense actually does for the business, not just what it’s labelled.
Why Was IT Infrastructure Spend Disputed?
The dispute centred on Schedule 3 of the ITA, which allows businesses to claim capital allowances on qualifying “plant” expenditure. The trouble has always been that “plant” was written with machinery and physical equipment in mind — leaving software in a grey zone.
The IRB’s traditional stance was narrow: software upgrading, customization, and development costs didn’t fit the conventional definition of plant, and even where core software might qualify, the fees for tailoring it to a business’s specific needs should be stripped out and disallowed separately.
The Landmark Maybank Case That Changed the Rules
Between 2014 and 2017, Maybank ran a series of system updates across its enterprise IT ecosystem — upgrading existing software architecture, developing customized modules, and licensing core banking applications. Maybank claimed the full RM221.968 million as qualifying plant expenditure under Schedule 3 to claim capital allowances.
Following a 2019 tax audit, the IRB disallowed the claims entirely, asserting that software upgrading, customization, and development costs did not qualify as capital expenditure for “plant.” It issued additional assessments along with Section 113(2) penalties for filing an incorrect return.
Maybank appealed. In 2024, the Special Commissioners of Income Tax (SCIT) ruled unanimously in Maybank’s favour, setting aside both the additional assessments and the penalties. The IRB then took the matter to the High Court — and lost there too.
How Both Sides Argued Their Case
The IRB argued for a narrow, unbundled reading of Schedule 3. Its position was that software upgrading, customization, and development costs sit outside the traditional definition of “plant,” and that even where a software licence might qualify, the separate fees for custom development and coding adjustments should be stripped out and disallowed as non-qualifying expenses.
Maybank argued the software was functional plant, inseparable from its customization. Its case rested on:
- Core banking software being essential to processing customer transactions, account maintenance, ledger reconciliation, and regulatory compliance — the bank simply cannot operate without it.
- Off-the-shelf banking software being unusable without tailor-made integration, meaning customization isn’t a separate cost — it’s part of what makes the asset functional in the first place.
- Full, transparent disclosure of the expenditure in its tax computations throughout, with professional tax advice sought on the treatment.
From Special Commissioners to the High Court
Unlike some cases in this series, this one didn’t see a reversal at each stage — the taxpayer won consistently:
- The SCIT ruled unanimously in Maybank’s favour in 2024, setting aside the IRB’s additional assessments and Section 113(2) penalties.
- The IRB appealed to the High Court of Malaya, which affirmed the SCIT’s findings on all grounds and dismissed the Revenue’s appeal.
Why the Court Ruled in Maybank’s Favour
A. Software Can Be Functional “Plant”
The Court held that software platforms and their associated licences constitute “plant” for Schedule 3 purposes in a modern banking business. It pointed to banking software’s role in processing high-volume transactions, maintaining accounts, and supporting regulatory compliance, fraud monitoring, and risk management — without functional, updated software, a financial institution simply cannot operate. That satisfies what the Court called the functional test for plant.
B. Customization Isn’t a Separate, Disallowable Cost
Invoking Paragraph 2(1)(a) of Schedule 3, the Court rejected the IRB’s attempt to unbundle development and customization fees from the core software cost. It held that expenses incurred on preparing, altering, or customizing software to make it fully operational are akin to installation and alteration costs incidental to setting up plant — off-the-shelf software cannot function without tailored integration, so customization forms part of the total capital cost of acquiring the asset.
C. Technical Disputes Don’t Automatically Attract Penalties
The Court reinforced that imposing Section 113(2) penalties is a discretionary power that must be exercised reasonably — not a default response to a technical disagreement.
When Must Section 113(2) Penalties Be Set Aside?
The High Court set out a clear checklist. Penalties must be set aside where the dispute stems from a bona fide technical adjustment or a competing statutory interpretation, the taxpayer acted in good faith and sought professional tax counsel, and full, transparent disclosures were maintained in the tax computations throughout. Together, these form a practical playbook for pushing back on penalty notices tied to genuinely contestable positions — not just for software cases, but for any Schedule 3 or interpretive dispute with the IRB.
What This Means for Malaysian Businesses
The Maybank decision gives corporate taxpayers — particularly in tech-heavy sectors — three practical takeaways:
- A clear path for software and digital capital allowances. Businesses in fintech, banking, logistics, and telecommunications can claim Schedule 3 capital allowances on comprehensive IT upgrade programs, including customization and integration fees, rather than having them stripped out.
- Document “functional necessity” from the outset. Taxpayers should maintain contemporaneous documentation showing how customized IT infrastructure is essential to core business operations, to satisfy the functional test for “plant” if challenged.
- A stronger defense against penalties. The judgment reaffirms that standard technical disagreements between taxpayers and the Revenue don’t amount to “negligence” or “deliberate misrepresentation” under Section 113(2), provided the position is backed by full disclosure and professional advice.
Quick Recap: What’s Deductible for IT Upgrades?
| Expenditure | Amount | Outcome |
| Software upgrade, development & licensing costs | RM221.968 million | ✅ Qualifying plant expenditure (Schedule 3) |
| Customization & coding adjustment fees | Included in above | ✅ Incidental capital cost, not unbundled |
| IRB’s Section 113(2) penalties | — | ❌ Set aside — bona fide technical dispute |
Conclusion
The Maybank ruling brings Malaysia’s capital allowance framework closer in line with how modern businesses actually operate — recognising that digital infrastructure, not just physical machinery, can be essential “plant.” For businesses investing heavily in IT upgrades, the case is a reminder that documentation and a defensible, well-advised technical position matter just as much as the underlying tax treatment itself.
Tax deductibility and capital allowance eligibility often come down to the specific facts of each case. Understanding how the Malaysian courts have interpreted “plant” and reasonable taxpayer conduct can help businesses make more informed decisions on digital transformation spend and better manage audit risk.
To deepen your understanding, explore these related Malaysian tax case studies:
- Bumiputera Quota Release Payments: Are They Tax-Deductible for Property Developers?
- Borrowing Costs: The Shifting Landscape of Bank Guarantee Fees
- Capital Gain vs Business Income: When Is a Property Sale Taxed as Capital Gain or Business Income?
