e-Invoice start date Malaysia, e-Invoice phases LHDN

This Ultimate Guide answers the most searched question first: the start date and how the phased rollout works for the national e-invoice program.

Mandatory means invoices must be sent to LHDN for validation through MyInvois, either via the Portal or API. PDFs emailed to clients do not meet the rule.

The rollout begins on 1 August 2024 and runs in phases through July 2026. Each phase includes a six-month relaxation window. After that window ends, full compliance and stricter validations apply.

Phase assignment depends on annual turnover bands, commonly using FY2022 figures for established businesses. New firms and those that cross thresholds face special cases and timing differences.

Key milestones to note: January 2026 brings the RM10,000 individual transaction rule, and July 2026 affects Phase 5 and MSME exemption considerations.

Later sections will give practical checklists to confirm your phase, choose Portal vs API, prepare required data fields, and cut rejection and cancellation headaches.

Key Takeaways

• Mandatory e-invoicing via MyInvois starts 1 August 2024 and rolls out by phase.
• Each phase has a six-month relaxation period before full enforcement.
• Phase assignment is based on annual turnover bands, often using FY2022.
• Watch January 2026 (RM10,000 rule) and July 2026 (Phase 5/MSME notes).
• Use the guide checklists to confirm your phase, pick Portal or API, and prepare fields.

Malaysia’s e-Invoice mandate in a nutshell (LHDN/IRBM + MyInvois system)

Under the mandate, invoices must be submitted as structured data to the national validation platform. The Inland Revenue Board operates the MyInvois system to receive and validate those files.

What “beyond PDF” means: e-invoices are machine-readable records (XML or JSON). They carry fields for tax IDs, amounts, and timestamps. A PDF copy sent by email no longer meets the validation rule.

The scope covers B2B, B2C, and B2G activity. It also applies to domestic and international transactions tied to local business operations. This ensures near real-time visibility of taxable transactions.

The phased rollout focuses on larger firms first so systems scale safely. The goal is better compliance, faster audits, and digitized administration by the revenue board.

Quick reference

Next you will learn about turnover bands, the six-month relaxation period, consolidated and self-billed rules, and workflow details.

Malaysia e-Invoice Implementation Timeline Explained (all phases and key dates)

Here’s a concise calendar of phase start dates so you can match your annual turnover to a compliance window.

Phase start dates by annual turnover (Aug 2024 to July 2026)

Quick schedule:

• 1 August 2024 — companies above RM100 million
• 1 January 2025 — RM25 million to RM100 million
• 1 July 2025 — RM5 million to RM25 million
• 1 January 2026 — RM1 million to RM5 million
• 1 July 2026 — up to RM1 million

What changes after each phase’s six-month relaxation period ends

The relaxation period is a soft-landing where authorities allow flexibilities and fewer penalties if minimum standards are met.

After that grace time, enforcement tightens, validations become stricter, and businesses must issue structured invoices in the correct format without exception.

Quick view: which turnover band hits January 2026 and July 2026

January 2026 affects firms with RM1 million to RM5 million annual turnover revenue. July 2026 covers those below rm1 million.

Next: the following sections break down what each phase means operationally and how to prepare in good time.

Phase details: August 2024 start date for businesses above RM100 million turnover

From 1 August 2024, organisations above the RM100 million turnover band must submit sales invoices and related documents to the national validation system before they are treated as official tax records.

What “mandatory from August 2024” means operationally

Day-to-day this means sales invoices, credit notes, debit notes, and refund notes are sent to MyInvois for validation prior to client delivery. PDFs alone do not meet the requirement.

Most large firms adopt API integration into ERP or billing platforms for high-volume flows. The Portal acts as a backup during outages and for exception handling.

Relaxation period window and practical flexibilities for early waves

The six-month relaxation period gives large taxpayers time to stabilise integrations and master data without immediate enforcement. During this window, authorities allow targeted flexibilities.

“The soft-landing allows businesses to fix data gaps and reduce rejections before full compliance is enforced.”

• Broader allowance for consolidated invoices where permitted.
• More flexible product/service descriptions to ease mapping.
• No prosecution under Section 120 ITA 1967 when minimum flexibilities and guidelines are followed.

Treat the soft-landing as a controlled rollout: pick pilot units, track validation rejections, and tune master data. Lessons on TIN capture and validation workflows will be vital for the next wave, which covers the rm5 million band.

Phase details: January 2025 start date for RM25 million to RM100 million turnover

Phase 2 affects mid-sized firms that must plan a controlled cutover by 1 January 2025. Start planning internal cutover dates, controls, and customer/supplier communications before year-end.

Operationally, invoicing shifts from “issue then archive” to issue, submit, validate, then share. This change affects timing, approval steps, and who owns validation exceptions.

The six-month relaxation period acts as a practical transition runway. Use it for sandbox testing, user training, and stabilizing month-end processes.

• Confirm which entities fall in your annual turnover band and scope.
• Align billing systems and master data to MyInvois fields.
• Decide Portal vs API based on invoice volumes and automation needs.

Document mapping between invoice fields and the validation schema. Create SOPs for cancellations, credit notes, and dispute handling to reduce rejections.

“Treat the relaxation window as a controlled test: fix data, refine processes, and train staff.”

Start now — readiness is mostly data and process work, not just IT. July 2025 firms should begin early for the same reasons.

Phase details: July 2025 start date for RM5 million to RM25 million turnover

Phase 3 begins on 1 July 2025 for businesses with rm5 million to rm25 million annual turnover. Mid-sized firms often feel the squeeze because volumes demand automation, but systems may not be enterprise-grade yet.

System and data readiness milestones to hit before July 2025

Confirm your turnover band and assign a project owner who spans Finance and IT. Decide whether Portal or API submission fits your volume and resources.

• Data hygiene: clean customer and supplier profiles, standardize addresses, and harmonize item/service names to cut validation failures.
• System checks: verify your accounting platform can export required fields and assess middleware or add-on software for integration.
• Test cycles: plan sandbox runs, track rejection rates, and fix mapping errors before go-live.

Start with minimum viable compliance — capture must-have fields and controls first, then add automation, dashboards, and reconciliations. Finally, prepare for Phase 4 (January 2026) by prioritizing master data and TIN collection across customers and suppliers.

Phase details: January 2026 start date for RM1 million to RM5 million turnover

From early January 2026, many small and medium firms must update billing practices to meet new validation rules.

What SMEs should prioritize ahead of this date

Keep the plan simple. Focus on fixes that make day-to-day billing reliable without hiring a big project team.

• Clean customer and supplier records to reduce rejection risk.
• Standardize invoice fields so systems map correctly every time.
• Capture and verify tax IDs before issuing invoices.

Common gaps: master data, TIN collection, and process controls

Missing or wrong TINs are a frequent blocker. They trigger validation failures and slow payments.

Set simple process controls: who submits, who checks validation status, who resolves rejections, and how disputes are logged.

Use the six-month relaxation period wisely: stabilize habits and data standards while flexibilities reduce risk. Next: July 2026 rules, MSME exemption notes, and why smaller firms still need a clear plan.

Phase details: July 2026 start date, MSME exemption, and businesses below RM1 million

Small firms should plan ahead: Phase 5 begins mid-2026 and includes a six-month relaxation period through 31 December 2026.

What this means: from 1 July 2026, the rule covers businesses with annual turnover up to rm1 million. The relaxation period gives time to settle processes, reduce rejections, and train staff.

MSME exemption basics and group/independence traps

The MSME exemption is not automatic. Firms with turnover ≤ rm1 million may qualify, but LHDN applies tests. Independence and group structure matter. If your entity sits inside a group that breaches thresholds, the group’s figures can affect eligibility.

Why small businesses still need a simple plan

Even if most sales are low-value B2C, high-value transactions can trigger full validation rules. Set a lightweight approach:

• Choose the Portal for low volumes or plan API later.
• Assign who submits and who checks validation status.
• Keep customer tax details tidy to avoid rejects on large invoices.

“Don’t assume exemption — verify eligibility and prepare for occasional high-value transactions.”

How to confirm your business’s e-Invoice phase (annual turnover, FY2022, and edge cases)

Begin with a clear ruling on which fiscal year and entity scope you will use to calculate annual turnover. This step fixes the baseline for the mandatory date and avoids surprises when multiple companies or group reporting apply.

Using annual turnover/revenue bands to map your mandatory date

Follow this simple checklist to confirm your phase:

1. Pick the fiscal year (many taxpayers annual use FY2022 for existing entities).
2. Extract total revenue lines and confirm they meet the annual turnover definition in guidance.
3. Match the figure to the published bands to find your start date.

New businesses commencing 2023–2025

If your operation began between 2023 and 2025 and your annual turnover revenue reaches RM1,000,000 or more, the mandatory date is 1 July 2026.

Businesses commencing 2026 onward and the second-year rule

For firms that start in 2026 or later, implement from 1 July 2026 or from your commencement date. If first-year turnover revenue is below RM1,000,000, the obligation triggers on 1 January of the second year after you exceed that threshold.

Edge cases and voluntary early adoption

Seasonal businesses, fast-growing SMEs, and short financial years need care when annual figures skew. Use pro-rated or consolidated reporting only as allowed by guidance.

Voluntary early adoption can help if you invoice large buyers, want cleaner audits, or seek fewer manual reconciliations. It also smooths transition if you are close to a higher band.

“Confirm your fiscal baseline first — most disputes start with the wrong date or wrong entity scope.”

MyInvois Portal vs API integration: choosing the right submission model

Deciding between a manual web portal and an automated link from your billing system is a practical first step. The two submission paths suit very different needs and resource levels.

MyInvois Portal for lower volumes and simple setups

The portal is fast to adopt. It requires minimal technical work and suits small teams or low invoice volumes.

Use the portal as a quick start, for exceptions, or as a continuity plan when integrations fail.

API integration for high-volume automation

Application programming interface (API) integration sends invoices directly from ERP or accounting software. This reduces manual steps and human error.

Large firms gain speed and scale, while finance teams keep tighter control of data flow.

Authentication and setup considerations

API setup needs a digital certificate for authentication, callback endpoints for notifications, and ongoing maintenance effort.

Plan for internal testing and a small support team to handle certificate renewals and schema updates.

“Many firms pick API for core flows and keep the portal for exceptions.”

Pick the model that matches invoice volume, staff capacity, and how mature your accounting system is. Whatever you choose, the validation rules on the myinvois system still apply and you must submit required fields correctly via myinvois.

End-to-end workflow with LHDN validation (what happens to each invoice)

A structured submission triggers near real-time checks and a visible validation outcome for both sides.

The supplier creates and submits the invoice either through the myinvois portal or API call via myinvois. The platform runs rapid validation and returns a verified record.

Validation output and verified elements

The validation returns a Unique Identifier Number (UIN), a date/time stamp, a validation link, and a QR code. These items prove the invoice passed system checks and support future audit trails.

Notifications and sharing

The myinvois portal notifies supplier and buyer via portal message and email. API users receive system-to-system alerts through the Notification API.

Storage, retrieval, and corrections

Accepted invoices are stored in the myinvois system database. Users can pull key fields and status from the dashboard for reconciliation and reporting.

Rejections and the 72-hour rule

Buyers or suppliers may reject or cancel within 72 hours. After that window the invoice is treated as accepted and further fixes usually require credit/debit or a new issuance.

Data and documentation requirements businesses need to prepare for

Preparing accurate invoice data is the single biggest task finance teams face before go‑live. LHDN guidance requires up to 55 structured fields per invoice, and that changes how daily billing works.

The “55 required fields” reality and what it means

More fields = more checks. Manual entry via the Portal becomes slow and error-prone when staff must fill dozens of fields for each transaction.

For teams using APIs, automation helps — but only if master files are clean.

Key identifiers to get right

Validation-sensitive fields commonly cause rejects:

• Supplier and buyer TINs (tax identification)
• Supplier MSIC code and correct billing addresses
• Item descriptions, quantities, unit prices, and totals

How errors happen and a simple data prep plan

Most errors come from inconsistent customer records, missing TINs, or messy product names that do not map to structured fields.

Start with these steps:

1. Clean customer and supplier master files; verify TINs and addresses.
2. Standardize item and service catalogs with clear codes and short descriptions.
3. Create templates for common transaction types to speed Portal entry and reduce mistakes.

Documentation matters. Keep SOPs that record who updates master records, why changes were made, and how validation issues were resolved.

“Clean master data shortens billing cycles, cuts rejections, and lowers tax and compliance risk.”

Consolidated e-Invoices, industry restrictions, and the RM10,000 rule from January 2026

Where allowed, businesses can aggregate multiple retail receipts into a single official submission after month-end. This option is most useful for B2C sellers when buyers do not ask for an individual document.

When consolidation is permitted

Consolidated e-invoices let you issue normal receipts at the point of sale and then submit one aggregated file for the month. Use this when customer-level invoicing is not required.

Deadline and a clear compliance step

Submit consolidated records within seven calendar days after month-end. Treat this as a fixed compliance calendar item to meet validation requirements.

Industry restrictions and practical impact

Certain sectors cannot use consolidation: automotive, aviation, luxury goods and jewellery, licensed betting and gaming, and payments to agents/dealers/distributors. Construction and wholesalers of construction materials are restricted—however, from january 2026 they may consolidate except where a single transaction exceeds RM10,000 or a buyer requests an individual e-invoice.

High-value transactions and small-business note

From 1 January 2026 any single transaction above RM10,000 must be issued as an individual e-invoice. Even businesses below rm1 million should plan a simple high-value flow to meet those requirements.

“Make consolidated submission timing and high-value exceptions part of your month-end checklist.”

Self-billed e-Invoices: when the buyer must issue the e-Invoice

When a supplier cannot or does not issue a compliant record, the buyer may create and submit the official e-invoice to meet validation rules.

What this role reversal means

Self-billing is simple: the buyer issues the invoice on behalf of the supplier so the taxable transaction has a validated record. This protects expense claims and keeps audit trails complete.

Common scenarios where buyers issue invoices

• Agent, dealer, or distributor commissions where the supplier cannot submit structured records.
• Payments to foreign suppliers or individuals who lack local filing capability.
• E-commerce platform flows where the marketplace handles payments and billing.
• Profit distributions, dividends, insurance claim payouts, and similar settlement payments.

Buyer responsibilities and key data to capture

Buyers must gather accurate supplier and buyer names, addresses, and TINs before issuing self-billed invoices.

Also capture clear service or goods descriptions, dates, and exact amounts to avoid validation failures.

“Missing supplier TINs, inconsistent names/addresses, unclear descriptions, and mismatched amounts are the most frequent gaps.”

Practical controls to reduce risk

• Define who may issue self-billed e-invoices and require written approval for each type of transaction.
• Link invoices to contracts or payment authorizations when reconciling.
• Keep a short checklist that verifies TIN, address, description, and amount before submission.

Compliance strategy and transition planning (processes, people, and tax risk)

Treat e‑invoicing as a finance transformation, not just a tax formality. Focus on how new validation rules change daily work across billing and payables.

How e‑invoicing changes Accounts Receivable and Accounts Payable workflows

Accounts Receivable teams must delay client delivery until validation is recorded. This affects cutoffs, credit notes, and dispute timelines.

Accounts Payable faces more self‑billed cases, stronger invoice matching needs, and a need for validated documents to support deductions.

Using the six‑month relaxation period to test, standardize, and stabilize

Use the relaxation period to pilot real flows, fix master data, and reduce rejection rates.

Lock consistent descriptions, run sandbox cycles, and train staff on common rejection causes before full enforcement.

Penalties and enforcement risk under Section 120 of the Income Tax Act 1967

After the soft‑landing, prosecution and penalties become a real tax risk. Follow published guidelines during the relaxation period and document any flexibilities used.

Incentives: accelerated capital allowance for qualifying ICT/software investments (YAs 2024–2025)

Taxpayers who implement timely without relying solely on flexibilities may qualify for accelerated capital allowance on qualifying software and ICT purchases for YAs 2024–2025.

Practical readiness checklist: system integration, sandbox testing, training, supplier/customer alignment

• Decide Portal vs API and complete system integration tests.
• Run sandbox/UAT cycles and measure rejection rates.
• Train teams on 72‑hour cancellation/rejection workflows.
• Align suppliers and customers to capture TINs and standard descriptions.
• Monitor reconciliations and keep audit trails for any relaxation-period choices.

“Translate compliance into clear processes that protect cash flow and reduce tax risk.”

Conclusion

Treat the rollout as a change project: set owners, map simple milestones, and track readiness against your annual turnover band so actions are timely and visible.

Confirm your phase, pick the submission path (use the MyInvois Portal for low volumes or plan integration for scale), and start cleaning master data now. Small fixes to names, TINs, and item codes cut rejections fast.

Operational success looks like clear steps: create invoices, submit them, receive validation (UIN + QR), then share. Timing and controls matter for cash flow and audits.

Remember key dates: August 2024 began the rollout, January 2026 brings the RM10,000 rule, and July 2026 affects smaller firms and MSME checks. Use the relaxation window as a testing and stabilisation period.

With trained staff, tidy data, and simple processes, e-invoicing will reduce errors, speed transactions, and make compliance routine.