E-Invoice Malaysia: Complete Guide to LHDN’s New System

We guide you through the Inland Revenue Board’s new e-invoicing rollout and show how to meet compliance without disrupting operations.

The mandate begins in August 2024 and phases by revenue bands through July 2026. We explain the phased implementation dates, the system model options, and which businesses must act now.

You will learn the required formats, the 55-field structure, the real-time validation steps, and the Unique Identification Number plus QR code process. We outline digital certificate needs and the 72-hour error window.

Our goal is to make the transition practical. We provide clear actions, risk controls, and a service model so your teams issue compliant documents and keep audit-ready records.

Key Takeaways

• Phased dates start August 2024; check your yearly revenue band to know your start date.
• All B2B, B2C, and B2G records validate in real time via the MyInvois system.
• Follow UBL 2.1, include mandatory fields, and use an IRBM digital certificate.
• Transactions above RM10,000 need individual e-invoices from Jan 1, 2026.
• Non-compliance carries fines or imprisonment; review exemptions and interim relief.

Why e-Invoicing Matters Now in Malaysia

Real-time validation of transactional documents is changing the rhythm of tax reporting for firms. We advise that all taxpayers with B2B, B2C and B2G flows must review systems and controls ahead of august 2024 start dates for larger turnovers.

Adopting e-invoicing and modern invoicing standards reduces manual entry, cuts disputes, and speeds collections. The IRBM has published practical guidance and an SDK to simplify implementation.

• Cleaner data: standardized fields and digital signatures lower posting errors and ease audits.
• Faster compliance: real-time checks improve reporting accuracy and reduce late adjustments.
• Operational lift: integrated systems shorten billing cycles and scale as transaction volumes grow.

You will need to update process owners, map information flows, and confirm technical requirements. Early alignment mitigates compliance risk and makes the transition predictable for your businesses.

e invoice malaysia

An e-invoice is a standardized, machine-readable document that IRBM validates in real time. It must follow UBL 2.1 and be submitted as XML or JSON so the system can verify required fields before the document is shared with the buyer.

Validated records receive a Unique Identification Number and a QR code. These elements confirm authenticity and let either party check status online. MyInvois supports manual and bulk uploads for low-volume use.

• Definition: a standardized, machine-readable invoice validated by IRBM before distribution to the buyer.
• Authentication: the UIN and QR code enable instant verification and reduce disputes.
• Transmission: use the portal as backup; choose API integration when volumes require automation.
• Data capture: ensure core fields and details are complete at issue to avoid rejections.
• Rollout: turnover thresholds set your start date—monitor revenue to know when you must comply.
• Benefit: validated invoices align billing accuracy and tax reporting for both parties.

Who Must Comply and What’s Exempt Today

We outline which entities must adopt the system now and which groups remain outside current scope. Understanding this lets you plan people, process, and technology work without surprises.

Scope: All individuals and legal entities carrying on business are included. This covers corporations, partnerships, and sole proprietors when their operations meet the threshold.

Current exemptions include taxpayers with annual revenue below RM500,000, foreign diplomatic offices, individuals not carrying on business, specified statutory bodies, and certain international organizations. Certain collections are exempt until 1 July 2025.

• We specify who is in scope and when mandatory adoption begins for each revenue band.
• Evidence to claim the exemption may be audited accounts or tax filings showing annual turnover below the threshold.
• Once mandated, you must continue compliance even if turnover later falls below RM500,000 to avoid stop‑start obligations.

We advise monitoring consolidated revenue streams and keeping clear records of documents and information that prove eligibility. This preserves audit readiness and reduces downstream tax risk.

Malaysia’s e-Invoicing Timeline & Phase Determination

Phased start dates link directly to your annual turnover. We guide you to place your FY/YA 2022 figures into the correct window so you know when to begin technical implementation and operational testing.

Use audited FY 2022 accounts or your YA 2022 tax return to identify your phase. If your accounting year changed, prorate turnover to align with the guidance. New operations that began in 2023 should expect a potential start date of 1 Jan 2027, pending formal notice.

Rollout by annual turnover

• > RM100m — start 1 Aug 2024; relaxation ends 31 Jan 2025.
• RM25–100m — start 1 Jan 2025; relaxation ends 30 Jun 2025.
• RM5–25m — start 1 Jul 2025; relaxation ends 31 Dec 2025.
• RM1–5m — start 1 Jan 2026; relaxation ends 30 Jun 2026.
• ≤ RM1m — start 1 Jul 2026; relaxation ends 31 Dec 2026.

Crossing the RM500,000 threshold

If your turnover later exceeds RM500,000, you must comply from the second year after crossing that threshold. Once enrolled, compliance continues even if revenue drops below the limit.

“Map your systems to the timeline and use the relaxation window for data clean-up, format tests (XML/JSON UBL 2.1) and integration sequencing.”

We recommend a phased implementation plan that sequences system work, data validation, and API integration. Follow Inland Revenue Board guidelines for format and transmission models to reduce risk and meet tax filing details on time.

Step-by-Step e-Invoicing Process: From Issuance to Sharing

Follow a simple sequence to issue, validate, and share digital billing documents with confidence. We break the workflow into clear steps so AR teams apply consistent controls and avoid rejections.

B2B flow

Suppliers submit an e-invoice via the MyInvois System using the portal or API. IRBM validates fields in real time.

On clearance, IRBM issues a UIN and QR code and notifies both supplier and buyer. The supplier then shares the cleared invoice with the buyer.

B2C flow

If a buyer requests real-time delivery, issue immediately through the system. If not, consolidate transactions and send monthly consolidated e-invoices.

Human-readable files (PDF/JPG) may be attached after validation for buyer convenience.

Rejection and cancellation

Suppliers may reject or cancel within 72 hours with justification. Keep documented reasons and internal approvals to support any adjustments.

• Key actions: validate mandatory fields to reduce errors.
• When to use the portal: manual or low-volume uploads; API for scale.
• Align: match billing cut-offs and reporting cycles so teams operate consistently across businesses.

Transmission Models & Integration Paths

Selecting a transmission path determines how smoothly your billing systems talk to the Inland Revenue Board.

Two core mechanisms exist: the MyInvois portal for manual or bulk upload, and API integration that connects your software directly to the MyInvois System.

MyInvois Portal: When manual and bulk upload make sense

The portal is free and fits MSMEs or teams that need a contingency route. Use it for low volume, ad hoc uploads, or during API outages.

Direct API integration to the MyInvois System

API integration suits high-volume e-invoicing and real‑time flows to inland revenue endpoints. It reduces manual work and improves control over payload, format, and UIN code handling.

Middleware and Peppol options for complex ERPs

Middleware vendors and service firms bridge ERPs, centralizing updates and reducing ERP change scope. Peppol is available via the national initiative to support standardized cross-system exchange.

• Compare portal vs API: portal for contingency and MSMEs; API for scale and automation.
• Middleware benefits: central updates, multi-entity scaling, faster SDK-led delivery.
• Technical checks: payload controls, format validation, and code verification cut transmission failures.
• Operational plan: map ERP workstreams, testing cycles, cutover tasks, and SLAs for service resilience.

Digital Certificate & Security Requirements

Digital credentials form the backbone of secure, verifiable billing exchanges under the new system. A digital certificate is mandatory and issued by IRBM using your TIN and supporting information. Certificates are valid for three years and bind your organisation to each signed record.

IRBM-issued certificate, signatures, and timestamps

We require every e-invoice to carry a digital signature and timestamp. This ensures integrity, authenticity, and non-repudiation for tax filings.

• Request and lifecycle: apply with TIN details; align expiry with internal PKI and renew proactively.
• Signature & timestamp: embedded in the payload to enable tamper detection and traceability.
• Fields & references: mandatory field identifiers must link the signature to the issuing party and the IRBM UIN or code.
• Security controls: encrypt transmissions in transit, encrypt storage at rest, and segregate duties for key custody.
• Governance: update keystores across environments without downtime and keep records to support compliance.

Signed artifacts and QR linkage strengthen auditability and customer trust. Follow these controls to reduce rejection risk and protect your information exchange.

Data & Document Requirements You Must Meet

Clear data structure and consistent payloads are the foundation of successful adoption. You must prepare both master data and transactional payloads to meet UBL 2.1 rules. The tax gateway accepts XML or JSON.

UBL 2.1, payloads and the 55 fields

Each e-invoice uses a 55-field schema; 37 of those fields are mandatory. Populate identifiers, tax codes, amounts, and timestamps exactly as specified to avoid rejections.

Document types and when to use them

Four document types exist: invoice, credit note, debit note, and refund note. Use credit or debit notes to correct or adjust prior records. Use refund notes for customer repayments.

Master data and operational controls

Maintain canonical seller/buyer profiles, product catalogs, and tax code mappings. Align your ERP outputs to the 55-field model so all channels submit consistent details.

• Self-billed rules: apply for specified imports and buyer-led billing; follow IRBM guidance when assigning responsibility.
• Human-readable copies: PDFs or JPGs may be attached after validation for buyer convenience.
• Validation checklist: test required fields, tax calculations, and signature/timestamp elements in staging and production.

B2C Rules & the RM10,000 Change in 2026

B2C billing rules now balance consumer convenience with stricter value-based issuance requirements. For buyer-requested documents, suppliers must issue a real-time e-invoice. When the consumer does not ask, suppliers may use a monthly consolidated approach.

When to issue consolidated e-invoices

Monthly consolidations are permissible for low-value consumer sales where no request for immediate documentation exists. Use consolidation to reduce operational burden and simplify end-of-month reporting.

Align calendar cut-offs and reconciliation so each consolidated batch maps to transaction records. This helps finance meet audit-ready standards and maintain continuous compliance.

No consolidation for transactions above RM10,000 from Jan 1, 2026

From 1 January 2026, any transaction exceeding RM10,000 must be issued as an individual e-invoice. Consolidation is not allowed for those sales.

• Adjust POS and online processes: capture buyer details at sale to enable real-time issuance when required.
• QR code & validation: ensure the code and UIN appear on consumer receipts for after-sales service and warranty reporting.
• Segment by value: separate high-value transactions so teams issue single documents while consolidating low-value flows.

Note: taxpayers in the RM5m–RM25m band should factor the 1 July 2025 phase when sequencing system updates and staff training.

Cross-Border Transactions and Self-Billing

Cross-border transactions introduce extra steps when a local buyer must document imports for tax and accounting purposes. We explain when e-invoices are required for imports and buyer-led billing so you can close gaps before shipment arrival.

Capture import details, foreign currency amounts, and seller references in your billing payloads. Keep exchange-rate entries and original receipts alongside the validated payload so accounting teams reconcile totals and postings without delay.

Prepare document packages that combine customs manifests, payment vouchers, and supplier records. Retain these documents to support audits and defend tax positions if authorities query cross-border flows.

• Integration: map logistics, procurement, and finance systems so information passes cleanly to the tax gateway.
• Model: choose a self-billing or supplier model based on contractual terms and operational control.
• Turnover: monitor growth and new markets, since expanded volumes can change your obligations and controls.

We recommend testing multi-currency scenarios, timezone stamps, and language fields during pilot runs to ensure continuous compliance across jurisdictions.

Interim Relaxation Period and Flexibilities

During each phase, authorities provide a six‑month interim relaxation to ease implementation and limit operational risk. This window reduces immediate pressure on your teams and your billing system while you adopt new processes.

Six-month grace: consolidation and description flexibility

You may issue consolidated e-documents across industries, including self‑billed cases. Monthly consolidation is allowed even if a buyer requests immediate paperwork during the window.

Free-form entries in the description field are permitted to reduce rejections while product catalogs are harmonised. This eases reporting and avoids blockages in early runs.

No prosecution window and ACA incentives

If you meet the minimum flexibilities and maintain required controls, there will be no prosecution under Section 120 ITA 1967 during the grace period. Keep logs and approvals to evidence good faith compliance.

Taxpayers that implement promptly without relying on flexibilities may claim an Accelerated Capital Allowance for qualifying ICT equipment and software in YA 2024–2025.

• What to do: document processes, enable system logs, and run test batches.
• Controls: retain reconciliations and change approvals to support any review under the guidelines.

Compliance, Controls & Penalties

A clear audit trail and disciplined retention policy are the backbone of reliable tax governance. We set out practical controls you can adopt as you implement new requirements.

Internal controls, audit trail, and record retention

Establish a maker-checker model for issuance and approvals. Require documented sign-offs for exceptions and cancellations.

Keep an audit trail of validations, rejections, and adjustments. Retain financial documents for the typical 7-year period to meet audit needs.

Non-compliance risks: Fines and imprisonment

Know the penalty landscape. Not issuing required records can be an offense under Section 120(1)(d) of the ITA 1967. Penalties range from RM200 to RM20,000 or imprisonment up to six months, or both, per instance.

• Field-level validation and workflow segregation prevent duplicate or erroneous submissions.
• Monitor failed validations, rejections, and cancellations with clear metrics and SLAs.
• Use SOPs, regular training, and periodic internal audits to reduce exposure and speed remediation.

“Embed controls during phased implementation so governance scales with volume and complexity.”

Readiness Assessment: People, Process, Technology

Start by verifying team roles and skillsets so your project has clear ownership from day one. This lets you plan resources against the mandated timelines.

We review how your current issuance of invoice, debit and credit notes, and refunds maps to IRBM requirements. Then we assess master data quality and IT capacity.

• Conduct a fit-gap to identify blockers across processes and systems.
• Map order-to-cash and procure-to-pay flows to align with e-invoicing implementation milestones.
• Define master data cleansing for customer, supplier, and product records to meet field accuracy standards.
• Evaluate integration points across ERP and adjacent software and plan test data and cutover scripts.

We recommend considering external solutions such as gap analyses, project management or middleware to accelerate compliance. Align plans to your turnover and business model so implementation stays predictable.

Integration with ERP, Accounting, and Billing Systems

A robust integration architecture prevents billing outages and preserves month-end close schedules. We recommend choosing an approach that suits your ERP roadmap and support model.

Direct API integration links your core systems to the MyInvois System for automated UIN issuance, corrections, and real-time validation. This model reduces manual steps and speeds reconciliation.

Alternatively, middleware vendors such as PwC and BDO provide a managed solution that centralizes change management. Middleware can absorb format updates and monitor flows across multiple systems with less ERP change.

Design payloads in XML or JSON using UBL 2.1. Map invoice objects to the mandatory fields early to cut build time and test cycles.

Define error handling and retries so your systems recover from validation failures. Maintain a portal contingency for bulk uploads and as a backup during API outages to preserve business continuity.

• Architecture choice: direct API for scale; middleware for governance and reduced ERP effort.
• Payload design: map fields to UBL 2.1 and validate formats before production.
• Resilience: implement retries, reconciliation reports, and portal fallback.
• Governance: apply software lifecycle controls to absorb tax updates without disrupting close cycles.

Change Management, Training, and Support

We design a pragmatic change plan that readies teams for new processes and system changes.

Training programs cover the MyInvois Portal and role-specific tasks for AR/AP, sales, procurement, HR, and internal audit. We use short workshops and hands-on labs so staff practice issuance, validation, sharing, and error resolution in realistic scenarios.

Post-go-live support includes service-level workflows, escalation paths, and health checks. Providers deliver dashboards that give you real-time information on status, exceptions, and throughput across entities.

We align communications, quick-reference guides, and SOPs to your business controls so people can act with confidence. Continuous improvement cycles refine field accuracy, lower queries, and sustain compliance.

Adopt these solutions to secure ongoing service levels and to keep your teams informed. Clear roles, short practice sessions, and visible metrics make the transition predictable and maintainable.

Incentives and Cost Planning for Implementation

We recommend a pragmatic budget that separates one‑time investments from recurring costs. Align spending with turnover milestones so your teams stage integration and training rather than front‑loading all expenses.

Key incentives may offset the upfront burden. Eligible taxpayers can claim tax deductions of up to RM50,000 per year (subject to gazettal) for qualifying setup costs from 2024–2027. There is also an Accelerated Capital Allowance for ICT equipment and software that shortens the claim period to two years for YA 2024–2025 when implementation avoids flexibilities.

We itemize cost categories so you can model total cost of ownership: integration, software licensing, vendor service fees, training, and change management. Include data quality workstreams to reduce rework and hidden operational costs.

• Budgeting: separate one‑off vs recurring spend and stage by turnover-driven dates.
• Value tracking: define KPIs for reporting such as validation success and cycle-time reduction.
• Governance: enforce vendor SLAs and periodic cost reviews to control long‑term expense.

Action Plan: How to Implement e-Invoicing Efficiently

Prioritise quick wins that secure data quality and system connectivity before full-scale integration. Start by confirming your phase using YA 2022 annual turnover and set a realistic timeline for rollout. This gives you clarity on deadlines and the relaxation window available to your business.

We sequence the work into clear steps so teams can act with confidence. First, choose a transmission model: the MyInvois portal, direct API, or middleware. Next, finalise architecture, security, and digital certificate arrangements.

Build a data map to the 55 required fields using UBL 2.1 in XML or JSON. Align master data and configure validation rules before user testing. This reduces rejections and speeds acceptance during live runs.

• Execute ERP and systems integration with robust error handling and retries.
• Run end-to-end tests with representative buyers and sample payloads.
• Prepare SOPs for issuance, sharing, and 72-hour rejection/cancellation handling.
• Train roles, deploy dashboards, and set SLAs for exception resolution.

Cutover planning includes a portal contingency, daily monitoring during stabilisation, and a handover to BAU support. After go‑live, iterate formats, reduce defects, and scale solutions across entities in line with guidelines.

“Sequence work to protect month‑end cycles and use the relaxation window to fix data and format issues.”

Conclusion

We end with a concise checklist to help you prioritise technical work and governance as phase dates approach. Follow the phased schedule tied to annual turnover and make the 55-field UBL 2.1 format, digital signature and UIN/QR validation core deliverables.

Prioritise data accuracy, select the right mix of portal, API or middleware solutions, and design controls that keep your teams accountable. These steps protect you from penalties and support reliable tax reporting.

Choose professional service partners who provide end-to-end support. We deliver assessment, integration, change management and post-go-live service so your businesses meet deadlines and extract operational value.