Most of the e-invoice penalty questions we get start with the same sentence: "We are already on MyInvois, so we are fine, right?" Not always. Being connected is one thing. Issuing a correct e-invoice for every transaction that needs one is another, and LHDN now has the data to tell the difference.
This guide explains what the law says about penalties, why nothing much has been enforced on smaller businesses yet, what changes when the relaxation period ends, and how the e-Invoice Special Voluntary Disclosure Programme (SVDP) gives you a clean way to fix past gaps. It is written for finance managers and owners of trading, manufacturing and services companies who want to sort this out before it becomes urgent.
Why This Matters Now
Three things happened in the last few weeks that are worth knowing about.
- LHDN is using the data. On 21 October 2026, LHDN said it had received more than 2.09 billion e-invoices from over 269,000 taxpayers, and that analytics built into the system automatically filter and analyse taxpayers' financial profiles as invoices come in (Bernama).
- Budget 2027 left the timeline alone. Budget 2027, tabled on 9 October 2026, did not announce new e-invoice relief, so the existing dates stand.
- Validation got stricter. From 24 October 2026, MyInvois production enforces a maximum of 26 digits on amount fields and a 12 character limit on passport numbers, according to the MyInvois SDK release notes.
None of this is a crackdown on its own. Together, it tells you the system is maturing, and the grace periods are not permanent.
What the Law Says About E-Invoice Penalties
Failing to issue an e-invoice when required is treated as an offence under Section 120(1)(d) of the Income Tax Act 1967. The penalty is a fine of RM200 to RM20,000, imprisonment of up to six months, or both. Industry guides read this as applying per offence, which is what makes it serious for a company issuing hundreds of invoices a month.
In practice, LHDN has said repeatedly that its first aim is compliance, not punishment. When it spoke about the 2.09 billion figure, it also said data variations may come from account adjustments or reporting timelines and do not by themselves mean a taxpayer is at fault. That is reassuring, but it is not a promise that errors will be ignored after the relaxation period.
Common gaps LHDN has pointed out
- Issuing e-invoices only for stock sales and missing other income, such as disposal of business assets and rental income.
- Confusion over self-billed e-invoices for suppliers who are not yet required to adopt e-invoicing. Self billing only covers the specific transactions set out in the guidelines.
- Consolidating transactions that should have had their own e-invoice, such as a single sale above RM10,000.
We covered more of the setup side in our post on e-invoice setup mistakes in Malaysia.
Where Each Phase Stands Today
| Phase | Annual turnover or revenue | Mandatory from | Relaxation ended or ends |
|---|---|---|---|
| Phase 1 | Above RM100 million | 1 August 2024 | 31 January 2025 |
| Phase 2 | Above RM25 million to RM100 million | 1 January 2025 | 30 June 2025 |
| Phase 3 | Above RM5 million to RM25 million | 1 July 2025 | 31 December 2025 |
| Phase 4 | Up to RM5 million, above the exemption threshold | 1 January 2026 | 31 December 2027 |
| Exempt | Below RM3 million, subject to LHDN criteria | Not required, voluntary adoption encouraged | Not applicable |
The exemption threshold was raised from RM1 million to RM3 million, as LHDN confirmed in October 2026. If you are unsure which side of the line you fall on, our guide to the RM3 million e-invoice exemption walks through the rules. Always check the latest version of the guidelines on the LHDN e-invoice guidelines page, because LHDN updates them often.
What the relaxation period actually allows
During relaxation, Phase 4 businesses may issue consolidated e-invoices more widely and use more flexible descriptions, and LHDN does not impose Section 120 penalties for non-compliance as long as basic requirements are met. From 1 January 2028, full enforcement applies to Phase 4. Phases 1 to 3 are already past their relaxation periods.
The SVDP: A Clean Way to Fix Past Gaps
The e-Invoice Special Voluntary Disclosure Programme is the part most businesses have not looked at properly. It was introduced in July 2026 and runs until 31 December 2027. LHDN added two document versions to MyInvois for it, SVDP 1.2 without a digital signature and SVDP 1.3 with one, and both can only be used during the programme period.
Who it is for
- Businesses that did not submit e-invoices from their mandatory date.
- Businesses that submitted e-invoices with errors or incomplete information.
- Businesses that left out certain transactions or periods.
- Businesses already under, or notified of, an e-invoice compliance review.
What you get
Disclosures made in good faith that meet the programme requirements receive a full penalty waiver. The SVDP document versions also allow a backdated issuance date, going back as far as your phase's mandatory date, so the corrected e-invoice reflects when the transaction really happened.
What it does not cover
Fraud, wilful default and negligence are excluded, based on the specific guideline as reported by tax advisers. Protection is also not automatic. The corrected e-invoices must still pass normal MyInvois validation rules, and unreported consolidated e-invoices must be submitted month by month, matching the month of the original transactions.
A Practical SVDP Review, Step by Step
When we help clients with this, the work is mostly about data, not the portal. Here is the sequence we follow.
- Confirm your phase and dates. Work out your mandatory date and whether you were ever under the exemption threshold.
- List every income stream. Sales of goods, services, rental, asset disposals, recharges to related companies and anything else that hits revenue or other income.
- Match your ledger to MyInvois. Export validated documents from MyInvois and compare them with invoices and credit notes in your ERP or accounting system, month by month.
- Sort the gaps. Separate missing documents, rejected documents never resubmitted, wrong buyer details and transactions wrongly consolidated.
- Prepare SVDP submissions. Use SVDP 1.2 or 1.3 through your API connection or the latest Batch Upload template.
- Fix the cause. Correct master data, tax codes and the trigger in your system so the same gap does not reappear next month.
- Keep the file. Document what you found, what you submitted and why, in case LHDN asks later.
Step six is the one people skip. A disclosure fixes the past, but if your system still lets an invoice go out without a valid buyer TIN, you will be back in the same position in a few months.
What a Typical Review Turns Up
Here is an illustrative picture of what a reconciliation often finds. Imagine a Klang Valley trading company with about RM20 million in turnover that went live on MyInvois in July 2025. Sales invoices flow through fine. But when the ledger is matched against MyInvois for the following twelve months, three kinds of gap appear.
- Rental income from sublet warehouse space was never e-invoiced, because it was billed from a spreadsheet, not the sales module.
- A handful of walk in cash sales above RM10,000 were swept into the monthly consolidated e-invoice.
- Dozens of invoices were rejected for a wrong buyer TIN and never resubmitted, because nobody was watching the rejection list.
None of this is deliberate, and each gap is usually quick to fix once found. That is exactly the situation the SVDP was designed for.
How Your System Affects Your Risk
Penalty risk is mostly a data problem, and the system you use decides how much manual checking your team has to do.
| Setup | Typical risk | What helps |
|---|---|---|
| Manual MyInvois portal entry | Missed invoices, typing errors, no link back to the ledger | Move to API or batch upload from your accounting system |
| Accounting software with e-invoice connector | Fine for simple sales; gaps in other income and self billing | Monthly reconciliation of ledger to MyInvois |
| ERP with integrated e-invoice | Lower, as long as master data is maintained | Mandatory fields on customers and items, approval before posting, exception reports |
In SAP Business One, for example, we make buyer TIN, registration number and classification codes required fields on master data, so a user cannot post an invoice that would fail validation. Our MyInvois API integration guide explains how the connection works. If you are still on cloud accounting and wondering whether an ERP would help, our companion post this week compares SAP Business One vs Xero for Malaysian SMEs.
One note for clients who ask: SAP Business One has no built in payroll or HR module, so payroll documents are not part of this review. Your payroll stays in local payroll software, with journals posted to SAP.
What We Recommend Doing Before 2028
- This quarter: run a one off reconciliation of your ledger against MyInvois for every month since your mandatory date.
- By mid 2027: make any SVDP submissions and fix the root causes in your system.
- Before 31 December 2027: stop relying on relaxation rules. Issue individual e-invoices where required and make sure self billing is set up only for allowed transactions.
- Every month after that: keep a short reconciliation routine so gaps are caught within weeks, not years.
If your finance team is stretched, this is also where outside help pays off. Our e-invoice integration service covers setup and review, and the top accounting software guide is a useful check if you are weighing a system change at the same time. Some businesses also fund system upgrades through digitalisation grants; see our MSME Digital Grant guide and check vendor eligibility with the agency.
Frequently Asked Questions
What is the e-invoice penalty in Malaysia?
Failing to issue an e-invoice when required is an offence under Section 120(1)(d) of the Income Tax Act 1967. The penalty is a fine of RM200 to RM20,000, imprisonment of up to six months, or both. During a phase's relaxation period, LHDN does not impose these penalties as long as basic requirements are met.
When does the Phase 4 relaxation period end?
For Phase 4 businesses, with annual turnover up to RM5 million and above the exemption threshold, the relaxation period runs until 31 December 2027. Full enforcement applies from 1 January 2028. Phases 1 to 3 have already passed their relaxation periods, so they are expected to comply fully now.
What is the e-Invoice SVDP?
The e-Invoice Special Voluntary Disclosure Programme lets businesses correct past e-invoice non-compliance, such as missing, late or wrong e-invoices, with a full penalty waiver for good faith disclosures. It runs until 31 December 2027 and uses special MyInvois document versions, SVDP 1.2 and SVDP 1.3, that allow backdated issuance dates.
Who cannot benefit from the SVDP?
Disclosures involving fraud, wilful default or negligence are excluded, based on the guideline as reported by tax advisers. Protection is also not automatic: the corrected e-invoices must pass MyInvois validation and meet the programme requirements. Businesses should keep records explaining what was found and corrected in case LHDN asks later.
Is my business exempt from e-invoicing?
Businesses with annual turnover or revenue below RM3 million may be exempt, subject to LHDN criteria. The threshold was raised from RM1 million. Exempt businesses are still encouraged to adopt e-invoicing voluntarily, and buyers may ask for e-invoices anyway. Check the latest LHDN guideline before relying on the exemption.
Does an ERP reduce e-invoice penalty risk?
It helps, mainly by enforcing clean data. An ERP such as SAP Business One can make buyer TIN, registration number and classification codes required fields, send e-invoices automatically when invoices post, and report on rejected or missing documents. It does not remove the need for a monthly reconciliation between your ledger and MyInvois.
Not sure whether your past e-invoices would stand up to a review? We can reconcile your ledger against MyInvois, show you the gaps and help you decide whether an SVDP submission makes sense.
Book an E-Invoice Review