How to Do an E-Invoice in Malaysia: Step-By-Step Guide

We present a clear, practical introduction for Malaysian companies preparing for the LHDN mandate that began August 1, 2024. The new system requires XML or JSON in UBL 2.1 format, a digital signature issued by IRBM, and real-time validation that returns a Unique Identification Number (UIN) and a QR code.

We outline the core process so your finance, IT, and operations teams can plan workstreams, select either the MyInvois portal or API integration, and manage document flows such as credit notes and self-billed records.

Key compliance points are retention for seven years, exemptions for annual revenue under RM500,000, and penalties up to RM20,000 or jail for breaches. From January 1, 2026, individual e-invoices are required for amounts above RM10,000 without consolidation. MDEC oversees Peppol access points for reliable connectivity.

Key Takeaways

• e-invoicing uses UBL 2.1 XML/JSON and IRBM digital signatures for real-time validation.
• Choose MyInvois (manual/batch) or API (automated) based on volume and readiness.
• Retain validated records seven years; follow rules for cancellations and adjustments.
• Exemptions exist under RM500,000 annual revenue; penalties are severe for noncompliance.
• Jan 1, 2026 rule: single-document requirement for transactions over RM10,000.

Malaysia’s e-Invoicing at a Glance: What Businesses Need to Know

The inland revenue board launched a May 1, 2024 pilot and then moved the regime into phased mandate status.

From August 2024 the first phase applied to entities with turnover above RM100 million. Subsequent phases follow a clear timetable: Jan 1, 2025; Jul 1, 2025; Jan 1, 2026; and Jul 1, 2026. This staged approach brings all taxpayers under the new clearance model.

The revenue board malaysia requires that all B2B, B2C and B2G transactions get real-time validation. E-documents must be structured (XML/JSON), digitally signed and validated. Upon clearance the system issues a UIN and QR code for authenticity and online verification.

• Cross-border imports: Malaysian buyers self-bill to meet requirements.
• There is a 72-hour window for rejection and justified cancellations.
• MyInvois portal and APIs serve as the universal portal for submission and validation via myinvois portal.

We recommend teams align systems and controls ahead of their phase date to meet the new regulations and streamline the process for compliant documents and transactions.

Scope and Eligibility: Who Must Comply and Who Is Exempt

The regulations cast a wide net across companies, branches, partnerships and other commercial entities. Most businesses operating in Malaysia fall within scope and should verify status early.

Mandatory taxpayers include companies, branches, partnerships, associations and business trusts. Phase allocation uses audited financials or tax returns (generally YA2022). Newer companies will be assessed on available filings.

Common exemptions

Exclusions cover foreign diplomatic offices, individuals not carrying on business, certain statutory/local authorities for collections before Jul 1, 2025, and international organizations for transactions before that date. Taxpayers with annual revenue below RM500,000 are also exempt.

Practical note: Once an entity becomes required, it must continue compliance even if revenue falls below RM500,000. We recommend documenting your scope determination, aligning internal data sources, and setting milestones for a smooth MyInvois portal transition.

Malaysia’s e-Invoice Timeline and Key Dates to Plan Around

Milestone dates set by the revenue board give businesses fixed targets for system readiness and rollout. We map those dates against your turnover band so teams can plan implementation activities with confidence.

Phase rollouts by turnover

Phases are assigned by turnover and each has an initial relaxation period for stabilization.

• Aug 1, 2024 — >RM100m
• Jan 1, 2025 — RM25–100m
• Jul 1, 2025 — RM5–25m
• Jan 1, 2026 — RM1–5m
• Jul 1, 2026 — ≤RM1m

Important cutoffs and a key policy change

Note the July 2025 milestone for RM5–25m taxpayers and plan buffer time for testing and issue resolution.

From Jan 1, 2026, any transaction above RM10,000 must be issued as an individual e-invoice. This removes consolidation options for higher-value transactions and affects B2C flows and accounting processes.

Practical planning checklist

• Schedule solution selection, integration, testing, data cleansing, and rehearsals backward from your phase date.
• Build cutover and contingency plans; keep manual portal fallbacks ready in case of API downtime.
• Inform stakeholders in finance, sales, IT, procurement, and audit; align phase dates with contract cycles and customer messages.
• Calendarize post-go-live reviews and set KPIs such as validation success rate and clearance cycle time.

Core Requirements Set by the Inland Revenue Board (IRBM/LHDN)

The Inland Revenue Board sets clear technical and record-keeping rules that underpin every valid Malaysian e-invoice. These requirements define file format, signing, validation, archival, and the minimum dataset for each submission.

Structured formats

Only UBL 2.1 in XML or JSON is acceptable for submission. PDFs and image files remain useful for human-readable copies after validation, but they are not valid submission formats under the regulations.

Digital certificate and signing

All e-invoices must be digitally signed with an IRBM-issued certificate. Certificates are valid for three years. You should define certificate lifecycle ownership within finance and IT and secure private keys in a certified signing service.

Real-time validation

When you submit an e-invoice, the system performs real-time validation and returns a Unique Identification Number (UIN) and QR code. Share that validated output with suppliers and trading partners for instant authenticity checks.

Archiving obligations

Validated documents must be retained for seven years. Offshore storage needs permission from the Customs Director General. Ensure retrieval and audit controls meet statutory access standards.

Data completeness

Each record must contain 55 mandatory fields covering seller and buyer details, line items, quantities, taxes, totals, and payment references. Plan your data model and implement source validation to reduce rejections.

• Format rules: UBL 2.1 XML/JSON for submission; PDFs/JPGs for human-readable sharing.
• Certificate management: Assign roles for issuance, renewal, and secure key storage.
• Retention: Seven-year archiving with retrieval controls; offshore storage requires approval.

We recommend mapping current templates and processes against these rules now, so compliance and operational continuity are assured when your phase date arrives.

Transmission Methods: MyInvois Portal vs API Integration

We present practical transmission choices that affect speed, control, and cost for Malaysian businesses moving into the new clearance regime.

MyInvois portal supports single entry and batch spreadsheet uploads of up to 100 documents per file. It suits MSMEs and low-volume accounting teams that need a simple, compliant application for manual submissions.

API integration for scale

Integration links ERP, billing, or accounting systems for automated, real-time processing. LHDN provides an SDK that accelerates mapping of internal data fields to UBL 2.1 and supports robust testing.

“Automation reduces manual errors and shortens clearance cycles when implemented with governance and monitoring.”

1. Prerequisites: ERP readiness, data mapping, authentication, and error handling.
2. Operational resilience: define fallback to portal, retry logic, and dashboard monitoring.
3. Vendor choice: prefer MDEC‑accredited Peppol access points or certified middleware partners.

Recommendation: adopt a hybrid model—API for BAU and the portal for exceptions. Define SLAs for validation success rates and response times. Establish version control and regression testing as schemas evolve.

How to Do E Invoice via MyInvois Portal

We guide your company through the MyInvois portal setup and everyday submission process. The sequence below reduces errors and speeds validation on your chosen date for go‑live.

Account setup through MyTax and role application

Register on MyTax and apply for organizational roles such as Director or Organization Administrator. Attach supporting documents (Form 49 or Section 58) during the application.

Once approved, accept the portal T&Cs and choose sandbox or live access for system testing and production submissions.

Configuring the taxpayer profile, branding, and notifications

Review and update taxpayer information, default language, and notification email(s).

Upload your company logo and set preferences so each document carries consistent branding and contact details.

Creating documents and self-billed options

Use the portal to create invoices, credit notes, debit notes, refund notes, and self-billed variants. Enter buyer details and validate TIN/BRN before submission.

Populate line items and tax types, ensuring all required fields are complete so the system accepts the record on first pass.

Submitting, signing, printing, and exporting

Submit for digital signing; the system returns a UUID/UIN and QR for validated records. Print human-readable PDFs and copy validation links for customers.

“Batch uploads of up to 100 documents speed high-volume days while drafts and ‘copy as draft’ streamline repeat entries.”

1. Batch upload up to 100 documents where appropriate.
2. Edit drafts, submit for validation, then export or search archived records as needed.
3. Cancel within 72 hours with a reason; track changes for audit purposes.

Checklist: confirm roles, validate buyer identifiers, complete line items, confirm digital signing, and verify UUID/UIN and QR before sharing.

Step-by-Step Implementation Plan for Businesses

Start by mapping your company’s phase date against audited turnover and expected transaction volumes. This gives a baseline for resource and timeline planning.

Assess eligibility and readiness by turnover band, then size effort by daily and peak document throughput. Use audited financials and projected growth to set realistic milestones.

Choose your transmission model and partner

Decide between portal, API, or a hybrid model based on throughput and integration complexity. Prefer partners with MDEC-accredited access points, proven middleware, or ERP-native connectors.

Integrate, configure, test, and go live

Map your data to UBL 2.1 and clean master records (buyer TIN/BRN, tax/item codes). Implement environment setup, authentication, digital signing, submission handling, and retry logic.

Run sandbox submissions, edge-case and load tests, and set validation-rate targets. Establish draft-to-approval workflows, exception handling, and reconciliation with accounting systems.

Change management and stabilization

Train users, publish SOPs, and assign RACI for finance and IT. Communicate changes with customers and suppliers and run a documented cutover plan with support shifts.

• Go-live checklist: cutover plan, monitoring dashboards, and a stabilization playbook.
• Continuous improvement: KPI reviews, schema updates, and seven-year archiving controls for audit readiness.

“A phased, test-driven approach reduces disruption and keeps validation success rates high.”

B2B vs B2C Flows: Real-Time Clearance, Consolidation, and Exceptions

We clarify how suppliers and buyers must handle real-time clearance for business and consumer sales under the new regulations. The rules affect issuance, validation, dispute windows, and whether a consolidated e-invoice may be used.

B2B flow

Suppliers submit documents via the myinvois portal or API. IRBM validates each record in real time and returns a UIN and QR code.

Share the validated output with the buyer for proof of authenticity and archival.

B2C flow

Retail customers may request individual e-invoice issuance. When no request exists, a monthly consolidated e-invoice may cover multiple retail sales.

A buyer has a 72-hour window for rejection; suppliers may cancel with a valid reason within that period, typically handled within hours.

January 1, 2026 change

From Jan 1, 2026 any transaction above RM10,000 must be issued individually. This ends consolidation for those transactions and affects POS and back-office mappings.

• System setup: auto-detect B2B vs B2C and apply consolidation logic.
• AR workflows: send validation links/QR and track clearance status.
• Controls: log 72-hour disputes, reconcile monthly summaries with item-level tax data.
• Exceptions: document split sales, returns, and post-window adjustments in SOPs.

Handling Cancellations, Rejections, and Adjustments

When a validated record needs correction, timing and traceability determine the permitted remedy.

The 72-hour window: Buyer-initiated rejection and supplier cancellation

Within hours of validation, a buyer may request rejection and a supplier may cancel with a clear reason. The system logs the request and the justification for audit.

Set alerts and ownership so disputes are handled inside the 72-hour window. Use role-based approvals in finance for any cancellation action.

Using credit notes, debit notes, and refund notes for post-window changes

After 72 hours, adjustments must use formal documents. Issue credit notes for reductions and debit notes for increases. Use refund notes to record returned payments.

Link each adjustment to the original invoices with reference fields. Maintain an audit trail and store exports for reconciliation.

• Automate bulk cancellations and reissuance via myinvois or API to reduce manual error.
• Configure templates and workflows so the correct document type is chosen every time.
• Track rejection rates and root causes; apply corrective actions in the process.

“Clear roles, fast alerts, and precise linking of documents preserve compliance and customer trust.”

Document Types You Must Be Ready to Issue

Preparing the correct document type prevents rejections and keeps cash flow steady for Malaysian firms. Below we explain the core records your finance team must issue and track under the new clearance regime.

Invoices and self-billed forms

Standard invoices are the primary commercial record for sales. Where permitted, a self-billed variant may be used when an agent or distributor issues the billing on behalf of a supplier.

Every e-invoices submission must go through the IRBM validation channel, either via myinvois or API. After clearance you may share a human-readable PDF with customers.

Credit notes and debit notes

Use credit notes to reduce amounts for overcharges, discounts, or returns without a cash refund. Credit notes must reference the original validated record and its UIN.

Debit notes record added charges such as surcharges, incremental services, or corrections that increase value. Link each adjustment back to the original transaction for traceability.

Refund notes

Refund notes document money returned to the buyer and must reconcile with collections and bank records. Issue these via the same system and include references to the original UIN and payment details.

Practical controls: standardize internal policies so sales, customer service, and finance select the right document type every time. Use batch uploads where applicable and retain validated records for seven years for audit readiness.

Compliance, Penalties, and Incentives to Reduce Costs

Non-compliance carries significant legal exposure under Malaysia’s tax laws and can disrupt business operations.

Legal risk: Failure to issue validated e-documents is an offence under Section 120(1)(d) of the Income Tax Act 1967. Penalties range from RM200 up to RM20,000 and/or up to six months’ imprisonment per instance, as enforced by the inland revenue board.

We recommend embedding compliance controls into daily routines. Build validated submission checks, archived proof, and live status dashboards. Track data quality and validation rates as core KPIs.

“Document implementation spend and timelines carefully so incentive claims are supported at audit.”

Cost-offset incentives: qualifying businesses may claim a tax deduction up to RM50,000 per year (2024–2027) for implementation expenses. Accelerated capital allowance applies for ICT equipment and software with a two-year claim period when adoption occurs within relaxation windows.

• Coordinate claims with your tax agent for evidence and timing.
• Establish governance forums with KPIs and remediation actions.

Conclusion

We advise swift alignment of data, roles, and technology so your team meets each phase date and the August 2024 starting point in the mandate. Plan integration with the MyInvois portal or API and verify your signing and validation system early.

Remember: IRBM validation returns a UIN and QR that prove authenticity. Manage the 72-hour rejection window, keep accurate information for payments, and track validated e-invoices and e-invoicing metrics.

Prepare for the Jan 1, 2026 rule on individual e-invoice for high-value sales and the end of consolidation for certain retail flows, including any consolidated e-invoice impacts. Leverage available incentives to offset implementation costs and embed seven-year archiving into your controls.

We stand ready to support your company with strategy, integration, and ongoing optimization. Finalize your roadmap, mobilize the project team, and begin testing so you meet the timeline confidently.