LHDN E-Invoice: How Malaysia’s Tax Authority E-Invoicing Works

We explain the new government framework that standardizes digital billing across Malaysian perniagaan. In March 2023, the lembaga hasil negeri introduced mandatory e-invois for B2B, B2G, and B2C transaksi. This system routes each record through the MyInvois portal for validation and immediate tracking.

MyInvois validates data fields, issues a Unique Identification Number and a QR code, and stores the verified record. The change tightens pentadbiran cukai, reduces errors, and makes audits clearer for hasil negeri and taxpayers.

Adopting e-invois changes how perniagaan capture data, submit workflows, and communicate with buyers. We outline what to expect and how to align finance, IT, and tax teams so every invois meets new compliance checks.

Key Takeaways

• The e invoice lhdn framework requires real-time submission through MyInvois.
• Validated e-invois include a UIN and QR code for online verification.
• Businesses must update data capture and submission workflows.
• The initiative strengthens pentadbiran cukai and reduces billing disputes.
• This panduan helps you plan a phased rollout and stakeholder alignment.

What LHDN e-Invoicing is and why it matters now

A validated e-invois is a structured digital record that sends transactional maklumat straight to the lembaga hasil for immediate verification.

This system is more than a PDF bil. It creates a tax-ready record that supports accurate, real-time reporting. For perniagaan and syarikat, that means fewer disputes and clearer tuntutan.

CelcomDigi will begin issuing e-invois from Julai 2025. Customers may request on-demand documents or receive monthly consolidated records based on account type.

Benefits include streamlined billing, integrated cukai filing, faster payment cycles, and reduced paper use. Operational impacts require disciplined data capture and system updates.

Challenges are integration complexity, staff training, and ensuring data accuracy. We recommend evaluating penyelesaian early so you can melaksanakan e-invois without last-minute risk.

• Why act now: better transparency and audit readiness.
• Who it affects: perniagaan of all sizes and individual pembayar cukai.
• Practical step: assess systems, assign roles, and map keperluan for transaksi reporting.

Updated implementation timeline and grace periods in Malaysia

The government has set a clear timeline that phases perniagaan by turnover and provides predictable grace windows.

Phased rollout: Aug 2024 to Jul 2026 by annual turnover

We list the mandatory start dates and the end of each grace tempoh so you can set internal milestones ahead of statutory cut-offs.

How to determine your annual turnover for phasing

Use your FY2022 Statement of Comprehensive Income if audited. If you filed unaudited returns, use the Income Tax Return form for YA2022.

If your financial year changed, pro-rate the 2022 income to a 12‑month equivalent. That calculation identifies your phase and the tempoh that applies to your syarikat.

Practical next steps: lock your data model, schedule a pilot, and test submissions across typical transaksi and bil cycles before the grace period ends.

Who must comply and who is exempt under LHDN guidelines

Regulatory scope now defines which legal entities must issue validated digital billing records and which remain outside immediate scope.

Entities required to issue e-documents

Companies, partnerships, limited liability partnerships, cooperatives, business trusts, REITs, property trusts, branches and bodies of persons must issue e-invois where applicable. This applies across most perniagaan structures operating in Malaysia.

Exemptions and temporary carve-outs to 1 July 2025

Foreign diplomatic missions, representative and regional offices, and individuals not carrying on business are out of scope. Until 1 July 2025, statutory/local authorities for statutory fees and certain international organisations have narrow temporary relief.

Threshold notes for smaller taxpayers

Pembayar cukai with annual revenue under RM150,000 are currently excluded. Note prior guidance referenced RM500,000; verify your classification against the latest garis panduan and document it for review by the lembaga hasil.

Practical tip: Treat exemptions as narrow and time-bound. If you run mixed activities, issue e-invois for taxable transaksi and keep clear records to support classification.

The data you need to issue an LHDN e-Invoice

Accurate transactional data is the foundation of a compliant Malaysian e-invois system. You must capture defined maklumat to avoid submission errors and to support cepat pengesahan.

Required fields and core elements

Core data elements: seller and buyer details, TIN, alamat, item lines, quantities, unit prices, discounts, tax lines, header totals, and payment terms.

• 55 fields cover full seller/buyer maklumat, item descriptions, taxes, totals, and payment details.
• Include internal invoice number and currency, but know the government will return a Unique Identification Number.
• Document types: invoice, credit note, debit note, refund note — each requires specific header and line fields.

Format standards and UIN / QR handling

Submissions must follow UBL 2.1 and be sent in xml json payloads via MyInvois portal or API. Well-formed files reduce resubmissions.

After e-invois dijana and validated, the portal issues a unique identification number (UIN) and a QR code. Embed that nombor and QR into the final dokumen you share with buyers post-pengesahan.

Quality controls: map tax rates, apply consistent rounding rules, reconcile line vs header totals, and maintain a master data checklist so you can menjana e-Invois reliably across your perniagaan.

Submitting via Portal MyInvois or API: choosing your model

Selecting portal or API affects cost, control, and day-to-day billing operations for your syarikat. We outline both paths so you can match volume and process needs.

Portal MyInvois: manual entry and bulk upload basics

The portal myinvois supports single record key-in and CSV bulk templates. You fill required maklumat, upload files, and wait for validation.

After validation, the system returns a UIN by email. You must embed the QR and send the dokumen to pelanggan. This route suits lower-volume perniagaan and ad hoc bil cycles.

API integration: automated XML/JSON submission and responses

The API accepts xml json payloads and returns a UIN and timestamp in the response. This enables straight-through processing and automated e-invois dihantar to customers.

Use the sandbox on the lhdn portal and follow security best practices when your systems masuk portal endpoints.

SDKs and accounting solutions to streamline compliance

Solution providers offer SDKs and connectors. Accounting platforms like ABSS and Financio can generate compliant files and post via API or upload to the portal myinvois.

How to generate, validate, and share e-Invoices step by step

Follow a clear, repeatable workflow to create, validate, and distribute compliant e-invois in minutes.

B2B flow — practical steps

First, capture complete maklumat and menjana e-invois in your system. Submit the file via the portal myinvois or the API.

After submission, the system returns a unique identification number and timestamp when the e-invois dijana. Embed the QR and produce the final PDF or digital bil for the pelanggan.

B2C options

For direct pengguna requests, issue e-invois in real time. If a buyer does not request, consolidate transaksi into a monthly e-invois and deliver on the billing cycle.

CelcomDigi benchmarks: postpaid and fiber bills are delivered within three days; on-demand requests are handled within 24 hours. Applications for monthly consolidation close on the 3rd calendar day of the next month.

Buyer review and rejection handling

The buyer has a 72-hour tempoh from the validation timestamp to accept or reject. This window includes weekends and public holidays.

If the buyer rejects, issue a credit note, correct the maklumat, and resubmit. If you miss the window, cancel and reissue with a new identification number to reflect proper pengesahan and cukai records.

Operational tip: define internal SLAs for pembayaran posting and dispute handling that mirror the garis panduan. Clear roles reduce rework and speed cash collection.

e invoice lhdn

Many teams underestimate how small data mistakes trigger complete rejections during submission.

From validation errors to re-submission: common pitfalls

Common rejection causes include malformed xml json, missing buyer TIN, tax miscalculation, and mismatched totals.

When a file fails, you must correct the butiran and resubmit. Track each attempt using the unique identification number returned after a successful pengesahan.

“Keep one number trail per dokumen to avoid duplication and audit friction.”

Reconciling e-Invoices with bills and statements in practice

Operational bil often include third-party charges and rounding. Tax e-invois exclude those items. Reconcile by mapping the invois lines to ledger entries and recording adjustments separately.

• Prevent duplicate submissions with an exception queue and idempotent checks.
• Respect the 3rd-day cutoff for past transaksi requests to avoid customer disappointment.
• Store validated e-invois, timestamps, and UINs for tuntutan and audits.

Quick penyelesaian: add automated pre-validation, tax code mapping, and a customer script for individu and pengguna to retrieve documents from portal myinvois.

Getting ready: accounts, TIN, deadlines, and internal processes

Start by registering on MyTax to collect accurate Tax Identification Numbers (TIN) and align taxpayer profiles before any production submissions.

Accessing MyTax/MyInvois and capturing identification numbers

Register at mytax.hasil.gov.my to retrieve TINs and confirm taxpayer details. Store each TIN in a secure master table linked to customer records.

Use the MyInvois pre-production environment to validate payloads. Capture the government-issued UIN and keep the nombor pengenalan with each record.

Time-bound actions and monthly cutoffs

Map your billing calendar to the 3rd-day application cutoff for on-demand or monthly bil requests. Track phase-based grace periods to meet statutory deadlines.

Change management, training, and system integration

We recommend training tracks for finance, IT, and operations to melaksanakan e-invois with minimal disruption.

Controls: tax code mapping, product master standards, approval roles, and audit trails when you masuk portal.

Readiness checklist: test submissions, monitor responses, set incident response steps, and inform buyers, suppliers, and auditors to reduce disputes and support tuntutan.

Conclusion

Timely data, strong controls, and stakeholder alignment are the foundations of successful e-invois adoption. We recommend mapping your phase, testing systems, and training teams now so your syarikat meets grace dates and avoids last-minute disruption.

Choose the right channel — portal or API — and scale automation as volume grows. Maintain audit-ready dokumen, UINs, and validation records to support cukai reporting and tuntutan.

Remember the buyer 72-hour tempoh for review, and use credit notes to resolve late disputes. Proactive outreach to pelanggan and robust penyelesaian will reduce errors, speed bayaran, and smooth pelaksanaan e-invois across transaksi and bil cycles.