Looking for the official start date for mandatory e-invoicing? The short answer: there isn’t a single day that fits every company. The rollout is phased by annual turnover, so the exact date depends on which group your business falls into.
The phased approach runs from August 2024 to July 2026. Each phase includes a six-month relaxation period before full enforcement. That window lets firms adapt systems, train staff, and test connections without penalties.
LHDN (also referred to as IRBM) uses the MyInvois platform at the center of validation, notifications, storage, and audit trails. Mandatory means you must issue, submit invoices for validation, share the validated document, and keep records as required.
This guide previews the five phases, explains who is affected, covers new business rules, and shows what changes during the relaxation window. It also explains voluntary early adoption and why many businesses choose it to reduce last‑minute disruption.
Key Takeaways
- There is no single start date; phased rollout depends on turnover.
- Phases run Aug 2024–Jul 2026 with a six‑month relaxation period each.
- MyInvois handles validation, storage, and auditability for LHDN/IRBM.
- Mandatory means issuing, validating, sharing, and keeping e-invoice records.
- Early voluntary adoption is allowed and helps companies avoid rush compliance.
What Malaysia’s e-Invoice mandate means for businesses today
The inland revenue board now requires structured invoice data to flow into a central portal for near real‑time tax reporting. This change modernizes tax rules, boosts compliance visibility, and supports the digital economy through consistent digital records.
Why the change was introduced
The core aim is simple: improve tax collection and reduce errors. The revenue board malaysia wants faster audits and clearer trails so tax risks are visible earlier.
Which transactions are covered
The rule applies to all taxpayers running a business — companies and individuals carrying on commercial activity. It covers B2B, B2C, and B2G transactions and affects both sales (AR) and procurement (AP).
Domestic and international scope
Domestic invoices and cross‑border transactions submitted to the system must be reported. If a local business buys from a foreign supplier, that transaction can still trigger reporting or later self‑billing rules.
“Invoice data quality is now a compliance requirement, not just an accounting preference.”
- Structured data: invoicing uses XML/JSON for automated validation and storage.
- Operational impact: fields must be accurate; poor data may cause rejections.
- Consolidation: allowed in some cases, but rules and exceptions apply.
Key agencies and platforms: LHDN, IRBM, and the MyInvois system
Invoices sent for validation pass through either a web portal or a machine-to-machine API, creating instant proof of issuance.
Who does what: The revenue authority (LHDN/IRBM) acts as the validating body, while the myinvois system is the platform that validates, notifies, stores, and enables retrieval of records.
How validation happens through the MyInvois Portal and API
Validation operates in near real‑time. You can submit a single document manually via the myinvois portal, or send batches using API integration from your accounting or ERP system.
Portal submission suits low-volume users. API integration fits high-volume or automated workflows and supports callbacks for instant notifications to finance teams.
What a validated e-invoice includes (UIN, timestamp, QR code)
Once accepted, a validated record contains an LHDN Unique Identifier Number (UIN), the date and time of validation, a validation link, and a QR code buyers can scan.
- Why it matters: these artifacts form the audit trail for reconciliation and dispute resolution.
- Verification: QR scanning or the validation link confirms existence without manual checks.
- Notifications: Portal users get email alerts; API users receive callbacks, which affects AR/AP workflows.
“Validation is the moment an invoice becomes an official, audit-ready record.”
Malaysia e-Invoice Implementation Timeline Explained
Each phase begins on a fixed date tied to turnover bands, giving businesses a predictable roadmap for readiness. Below is a clear match of annual turnover bands to mandatory start dates and the six-month relaxation window.
| Turnover band | Start date | Relaxation ends |
|---|---|---|
| > RM100 million | 1 August 2024 | 31 January 2025 |
| RM25m – RM100m | 1 January 2025 | 30 June 2025 |
| RM5m – RM25m | 1 July 2025 | 31 December 2025 |
| RM1m – RM5m | 1 January 2026 | 30 June 2026 |
| Up to RM1m* | 1 July 2026 | 31 December 2026 |
Phase notes
Phase 1 (1 August 2024): large taxpayers must be in steady-state, not testing mode. Systems and controls should be final.
Phase 2 (1 January 2025): mid-sized groups with high invoice volume should validate workflows and API throughput.
Phase 3 (1 July 2025): scale processes for businesses moving from manual to automated issuance. Focus on master data quality.
Phase 4 (1 January 2026): year-end timing makes cutover planning critical for accounting closes.
Phase 5 (1 July 2026): companies up to RM1 million still need to comply if they do not meet MSME exemption criteria.
Voluntary early adoption is allowed and often reduces implementation risk.
Use the six-month relaxation strategically to stabilise systems, train staff, and fix data issues rather than postpone readiness. The phased dates let teams plan a staged rollout with less disruption.
How to identify your phase using annual turnover and revenue thresholds
The simplest way to identify your phase is to confirm which turnover band your accounts place you in.
Start by checking your annual turnover and map that band to the mandatory start date and the relaxation end date in the phase chart.
Which financial year is used
For established businesses, guidance commonly references a baseline year such as FY2022 when showing examples.
Always confirm the exact basis in current LHDN guidance for your entity, because official rules may specify a different reporting year.
Turnover edge cases: groups and independence
Treat turnover revenue consistently across audited accounts and management reports to avoid misclassification.
Related groups may aggregate revenue. If ownership or control links multiple entities, the MSME exemption can be lost even when a single entity looks small.
- Gather audited accounts or management accounts.
- Prepare a group structure chart and ownership details.
- Pull a revenue breakdown by entity and by product line.
Use this mini-checklist to aid phase identification and to show to advisers or the tax authority if needed.
“Clarify group links early—ownership and control change how thresholds apply.”
If you are a newly commenced business, the phase and effective dates may differ. See the next section for rules that cover new starts and the usual transition approach.
Start dates for new businesses and newly commenced operations
New operations follow special timing rules because a partial financial year can make annual figures misleading. The tax authority therefore provides fixed dates so startups are treated fairly while still joining the validation system on a clear timetable.
Businesses commencing from 2023 to 2025: if your first full-year revenue or annual turnover is at least rm1 million, your required start date for compliance is 1 July 2026.
Commencements from 2026 onward
If you start in 2026 or later, your compliance date may be 1 July 2026 or your actual commencement date. Timing depends on when your first-year receipts reach the threshold.
The “second‑year January” rule (simple example)
If Year 1 revenue is under rm1 million but you cross that mark later, your start date shifts to 1 January in the second year after the year you exceeded the threshold.
“Track monthly receipts closely—crossing the threshold changes when you must begin validation and sharing.”
- Why this matters: billing, buyer requests, and validation steps can affect cash flow and AR.
- Practical steps: track turnover monthly, document when you cross rm1 million, and prepare a go‑live plan that won’t interrupt billing cycles.
The six-month relaxation period (soft landing) and what it allows
The relaxation window is a planned buffer for firms to test integrations and tidy their invoicing data without harsh penalties. It gives time to stabilise systems, train users, and adapt internal processes while participating in the new validation flow.
Consolidated e-invoices allowed during the grace period
Consolidated e-invoices, including permitted self-billed documents, may be used to reduce operational load. This helps teams avoid issuing an individual record for every small sale during the first six months.
Data-field flexibility for product or service descriptions
Businesses can enter broader descriptions in the product or service field while they standardize item masters and tax coding. This temporary data flexibility speeds up onboarding and lowers rejection risks.
No prosecution window under Section 120 (when minimum rules are met)
There isno prosecutionunder Section 120 of the Income Tax Act 1967 during the relaxation period, provided the minimum rules are followed. This is not a blanket waiver; meet the basic requirements to benefit from the soft landing.
Accelerated capital allowance for ICT and software (YAs 2024–2025)
Qualifying taxpayers who upgrade systems within the claim window can use an accelerated capital allowance for ICT equipment and software, shortening the claim to two years. This incentive can improve the business case for earlier system work and faster compliance.
“Use the six months to stabilise your model, automate where possible, and reduce manual fixes before full enforcement.”
Compliance risks after the relaxation period ends
Once the six‑month buffer lapses, tolerance for exceptions drops and operational gaps become compliance risks. Teams must meet every required field and follow submission rules without relying on temporary workarounds.
Penalties and how fines can add up
Under Section 120(1)(d) of the Income Tax Act 1967, non‑compliance is an offence. Penalties range from RM200 to RM20,000 per instance, and may include imprisonment up to six months.
Because fines apply per instance, a single rejected batch can multiply exposure across thousands of invoices. Treat this as a direct financial and operational risk to your accounts and reporting.
Enforcement timing by phase
Enforcement begins after each phase’s six‑month relaxation ends (for example, Phase 1 enforcement starts 1 Feb 2025; Phase 2 starts 1 Jul 2025). In short: mandatory start date + six months = stricter enforcement.
Common failure points and mitigation
- Missed validation, incorrect buyer TIN, or incomplete required fields.
- Late cancellations beyond 72 hours and weak storage or audit trails.
- Mitigation: implement daily monitoring, exception handling, and reconciliation routines early.
Proactive governance matters: assign owners for schema changes, master data upkeep, and period‑end controls to keep compliance steady as enforcement tightens.
“Design controls now so enforcement later becomes routine, not a crisis.”
End-to-end e-invoicing workflow in Malaysia
The lifecycle of a validated invoice is short and visible. A typical transaction moves from creation to a stored record with clear checkpoints for both seller and buyer.
Creation and submission via MyInvois Portal or application programming interface
Suppliers can enter invoices manually on the myinvois portal or send them from their accounting system using an application programming interface.
Manual entry suits low volumes. Automated payloads via API speed up bulk processes and reduce human error when sending documents via myinvois.
Near real-time validation and notification to supplier and buyer
After submission, the authority performs near real‑time validation and returns a UIN, timestamp, validation link, and QR.
Finance teams should monitor validation responses, not only ERP status, to catch rejects fast and avoid disputes over processing time.
Sharing rules and the role of QR verification
Suppliers must share the validated file with buyers. The embedded QR lets recipients confirm authenticity and view the validation link for trust and quick checks of the e-invoices.
Rejection and cancellation within 72 hours
Either party may reject or cancel a validated invoice within 72 hours. After that window closes, documents auto-accept and adjustments use credit/debit notes.
Storage in LHDN database and dashboard retrieval of e-invoice data
Accepted records are stored centrally and can be retrieved via dashboard services for audit, reconciliation, and month-end close.
“Design processes that track validation results and notification callbacks to keep reconciliations clean.”
Choosing your transmission model: MyInvois Portal vs API integration
Start by assessing daily invoice volumes and your accounting software capabilities before selecting a transmission model.
The right choice depends on volume, internal IT resources, and whether you need real‑time automation.
When the MyInvois Portal fits best for low-volume invoicing
The myinvois portal is ideal for small batches and teams with limited IT support. Manual entry keeps costs low and reduces setup time.
Use the portal if you are an SME, have occasional invoices, or need a resilient backup during outages.
When API integration fits best for high-volume and ERP/accounting users
Choose API integration when you have high transaction volumes or multiple billing channels. Direct links from your ERP or accounting software speed processing and cut errors.
Keep in mind integration requires upfront work and ongoing maintenance, but it scales far better for growing companies.
Operational planning: digital certificate, authentication, and callbacks
Plan for these essentials before you go live:
- Digital certificate: obtain and manage the LHDN-issued credential.
- Authentication: align your system with the authority’s auth method.
- Callbacks: expose endpoints to receive validation responses and monitor response codes.
Practical tip: pilot with the portal or a limited API scope, then expand as master data and controls mature. Also set up support, incident response, and change control to avoid outages at peak billing times.
“Match your route to capacity — ease now, automation later, or both in phases.”
Data requirements and the impact of the required fields
Preparing accurate invoice payloads starts with a clear master data strategy. LHDN guidance shows each record may need up to 55 fields, which changes how teams work day to day.
What the “up to 55 required fields” feels like
For manual Portal users, filling many fields is time-consuming and increases error risk. High-volume teams see cycle times lengthen and cash collection slow when rejects occur.
Manual vs automated processes
Manual entry forces staff to type recurring items and TINs, raising mistakes. API/ERP automation can prefill fields from masters and cut rework dramatically.
Master data you’ll need ready
- Supplier and buyer TIN and legal names.
- Billing addresses, contact details, and MSIC code.
- Consistent item/service descriptions and pricing models.
“Clean master data reduces rejects, shortens billing cycles, and keeps accounting teams focused on value work.”
| Area | Manual Impact | Automated Benefit |
|---|---|---|
| TIN / Legal name | Typing errors, rejects | Auto-validated, fewer rejections |
| MSIC / Item codes | Inconsistent entries | Standardised mapping |
| Addresses / Contacts | Delayed deliveries | Prefilled from master |
Readiness steps: run a master data cleanup, map fields between systems, and assign data owners in Finance, Sales Ops, Procurement, and IT. Strong governance lowers rejection rates and the risk of penalties after the relaxation period ends.
Consolidated e-invoices: rules, deadlines, and prohibited industries
Consolidated billing lets businesses bundle many small sales into one validated record to simplify reporting. This approach reduces the need to issue an individual e-invoice for every low-value or non-requested sale.
Common B2C use cases and month-end submission within seven calendar days
Retailers, cafes, and ticketed venues commonly use consolidated records for daily receipts. Each consolidated file must be submitted within seven calendar days after month-end.
Month-end discipline matters: timely submission keeps reconciliations clean and avoids late rework when validation returns errors.
Industries restricted from consolidated records under the guidelines
Certain sectors cannot use consolidation. These include automotive, aviation, luxury goods and jewellery, construction, licensed betting/gaming, and payments to agents, dealers, or distributors.
For those industries, most transactions require an individual validated record, raising system and process demands.
Special rules effective January 2026
From january 2026, any single sale above RM10,000 must be issued as an individual e-invoice. Wholesalers and retailers of construction materials may consolidate except when a sale exceeds RM10,000 or when a buyer requests an individual document.
Operational tip: add POS/ERP decision rules to decide when to consolidate, when to create an individual record, and how to log buyer requests to prove compliance over time.
Self-billed e-invoices and when the buyer must issue them
In self-billing, the buyer becomes the issuer of the e-invoice, shifting responsibility for creation and submission.
This model requires the buyer to generate, submit, and retain a validated record with the tax authority. The buyer captures details that normally come from the supplier and must ensure the document meets validation requirements.
How self-billed arrangements change roles
Buyer responsibilities: collect supplier identity, create the self-billed e-invoice, submit for validation, and keep proof of validation and sharing.
Supplier duties: provide accurate legal name, address, and TIN when requested, and reconcile payments against self-billed documents.
Common triggers that require self-billing
- Payments to agents, dealers, or distributors where the buyer manages commissions.
- Transactions with foreign suppliers or payout platforms in e-commerce models.
- Profit distributions, dividends, liquidation or capital reduction payouts.
- Certain payouts such as betting/gaming winners, insurance claims, or interest where suppliers are individuals.
Information buyers must collect to remain compliant
Missing supplier TIN or incomplete identity fields causes validation failures and can weaken tax deductibility. Collect the core fields before issuing a self-billed record.
| Required item | Why it matters | Practical step |
|---|---|---|
| Legal name & address | Identifies supplier for audit | Capture from ID or onboarding form |
| TIN | Needed for validation and tax proof | Require TIN on supplier profile; flag missing TINs |
| Transaction details | Description, qty, and price drive accuracy | Map PO or payout record to invoice fields |
| Supporting docs | Evidence for deductions and disputes | Attach contracts, receipts, or payout summaries |
Controls to reduce risk: set approval workflows, use templates for recurring self-bill cases, and reconcile self-billed e-invoices against payment registers monthly.
“Treat self-billing as a governance issue: collect clean data, enforce approvals, and keep validation proof for audits.”
Getting your business ready for implementation and ongoing compliance
Start with a simple roadmap and align people, processes, and systems before you go live. A staged approach reduces surprises and keeps operations steady during the transition to validated invoice flows.
System readiness: accounting software upgrades, ERP fit-gap analysis, sandbox testing
Assess your accounting and ERP landscape for gaps in invoice numbering, customer/vendor masters, tax codes, and MSIC mapping. Run an integration fit‑gap to identify where software changes or configuration are needed.
Sandbox testing with the myinvois system (or portal) cuts go‑live risk. Validate payloads, test callbacks, and confirm UIN handling before switching on production.
Process readiness: AR/AP workflow changes, reconciliation, and audit trail monitoring
Redesign AR/AP processes to include validation wait points, rejection handling, and credit/debit note flows. Plan consolidated submission cutoffs and month‑end deadlines so reconciliations stay clean.
Reconciliation must match validated UINs to ERP invoices daily and surface exceptions early. Monitor audit trails and retention procedures to prove compliance.
People readiness: staff training, change management, and cross-functional collaboration
Train Finance, Sales Ops, Procurement, IT, and Customer Service on required data fields (TIN, MSIC, billing details) and new workflows. Use short role‑based sessions and run real scenarios in the sandbox.
Assign owners for master data stewardship and cross‑team escalation paths to keep data quality consistent.
Go-live checklist for smoother issuance, validation, and exception handling
- Decide Portal vs API and prepare a digital certificate if using API.
- Keep Portal access as a backup and enable monitoring dashboards.
- Document escalation paths and buyer request handling rules.
- Confirm 72‑hour rejection/cancellation procedures and test them.
- Set governance: schema updates, master data owners, and compliance reporting.
“Treat readiness as ongoing: test, train, govern, and monitor to make compliance routine.”
Conclusion
Your required start date depends on your annual turnover; verify which band applies so your e-invoicing plan is based on facts, not guesswork.
Remember the rollout sequence: Aug 2024 → Jan 2025 → Jul 2025 → Jan 2026 → Jul 2026, each with a six‑month relaxation window to stabilise systems and staff.
Practically: submit through the myinvois portal or API, get a UIN/timestamp/QR, share the validated e-invoice, and manage rejects or cancellations within 72 hours.
Key operational lesson: clean master data and clear workflows cut rejections, speed billing, and make ongoing compliance far easier after the soft landing.
Use consolidated records where rules allow, note the Jan 2026 RM10,000 individual invoice rule, then decide Portal vs API, run sandbox tests, train teams, and adopt early if you want less risk at go‑live.
