Malaysia’s e-Invoice mandate requires businesses to clear invoices through the Inland Revenue Board’s (LHDN) MyInvois platform before they are valid. The rollout is nearly complete: three phases are already enforced, and the final phase started in January 2026. For SAP teams, the work centers on source-data quality, invoice generation, integration design, response handling, and controls across Business-to-Business (B2B), Business-to-Consumer (B2C), and Business-to-Government (B2G) flows.
Key dates
1 Jul 2025
RM5–25M turnover: MyInvois clearance mandatory
1 Jan 2026
RM1–5M turnover: mandatory (relaxation period to 31 Dec 2027)
At a glance
- Mandate: Clearance e-invoicing via MyInvois before invoice is legally valid
- Formats: UBL-based XML/JSON (~55 defined fields)
- Platform / channel: MyInvois (LHDN/IRBM)
- Authority: LHDN (Lembaga Hasil Dalam Negeri Malaysia / IRBM)
- SAP scope: SD billing, FI invoices, tax identifiers (TIN), master data + integration/monitoring
August–October 2026 technical update
Malaysia now has two parallel SAP change tracks: MyInvois authority clearance and PINT Malaysia business-document exchange through Peppol. They share source data but have different payloads, responses, identifiers and legal statuses.
| Date | Confirmed requirement | SAP response |
|---|---|---|
| 1 August 2026 | TIN plus identification value, including BRN, validation active | Validate and cache identity at Business Partner maintenance. |
| 15 August 2026 | MyInvois date, length and controlled-code checks active in Production | Run source and payload prevalidation before authority submission. |
| 18 August 2026 | SAP DRC supports PINT Malaysia 1.3.1 | Record the actual tenant validator result and rule IDs. |
| 7 September 2026 | PINT Malaysia Billing and Self-Billing 1.3.1 mandatory | Certify invoices, credit notes and both self-billing paths separately. |
| 23 October 2026 | 26-digit limit for listed monetary fields and 12-character PASSPORT limit | Audit SAP domains, master data and final XML/JSON serialization. |
Keep the two integration layers separate
SAP billing or accounting document
|
+--> MyInvois authority clearance
|
+--> PINT MY exchange through Peppol
|
+--> Independent responses, corrections and evidenceA successful MyInvois clearance does not prove Peppol delivery, and a successful PINT exchange does not prove authority clearance. Store separate payload fingerprints, identifiers, acknowledgements and SAP statuses.
Detailed release analysis and regression matrix: Malaysia MyInvois and PINT MY 1.3.1: SAP Changes for September and October 2026. Update verified: 24 August 2026.
Compliance Summary
| Area | Status (as of July 2026) |
|---|---|
| Mandate | Malaysia e-Invoice (MyInvois clearance) |
| Authority | Lembaga Hasil Dalam Negeri Malaysia (LHDN / IRBM) |
| Rollout (by FY2022 turnover) | Above RM100M: since 1 Aug 2024 · RM25–100M: since 1 Jan 2025 · RM5–25M: since 1 Jul 2025 · RM1–5M: since 1 Jan 2026 (relaxation period to 31 Dec 2027) · under RM1M: exempt only when the current LHDN exemption conditions are met; otherwise the concessionary implementation date is 1 July 2026 |
| Consolidation rule | During relaxation periods consolidated monthly e-invoices are tolerated; from 1 January 2026 individual e-invoices are mandatory for transactions above RM10,000 |
| Primary SAP impact | Billing data, tax identifiers (TIN), customer/vendor master data, invoice validation, API or portal integration, and response monitoring |
What Is Malaysia e-Invoice?
Malaysia runs a clearance model: the invoice (UBL-based XML/JSON with ~55 defined fields) is submitted to MyInvois, validated, assigned a unique identifier and QR-verifiable link, and only then shared with the buyer. Buyers can reject an invoice within a defined window, and cancellations follow a platform-controlled process — both are workflow states SAP needs to track, not just document statuses.
Business Impact for Finance and Tax Teams
- Data completeness: validation depends on accurate tax identification numbers (TINs), buyer/supplier details, and transaction values — missing buyer TINs are the most common go-live blocker.
- Process timing: invoice issuance, validation, buyer rejection, correction, and cancellation flows need tighter controls than paper-era processes.
- Consolidation decisions: B2C flows can use consolidated e-invoices, but the RM10,000 individual-invoice rule (from January 2026) requires transaction-level logic.
- Exception handling: rejected or incomplete invoices need operational follow-up and traceability.
SAP Impact Areas
| SAP area | Preparation question |
|---|---|
| SD billing / FI invoices | Can invoice data be extracted and mapped consistently to the MyInvois field set? |
| Master data | Are customer, supplier, and TIN details complete enough for validation? |
| Tax configuration | Are tax treatments and document scenarios mapped to the required e-Invoice types (invoice, credit note, debit note, refund note, self-billed)? |
| Integration | API or portal — and how are validation responses and QR data captured back into SAP? |
| Monitoring | How will finance and IT teams identify, correct, and resubmit failed records within the buyer-rejection window? |
Practical Preparation Steps
- Confirm the company’s phase position and any relaxation-period concessions still applicable.
- Map affected transaction types across B2B, B2C (incl. consolidation), B2G, self-billing, and cross-border flows.
- Review SAP source fields for invoice, customer, supplier, company, and tax data — especially TINs.
- Define the integration model and response-monitoring process.
- Run test scenarios for standard invoices, cancellations, buyer rejections, corrections, and high-volume cases.
Primary Sources and Verification
Verified on: 24 August 2026. Reconfirm the applicable rollout phase and exemption conditions, and use the current MyInvois SDK and OpenPeppol PINT Malaysia release for implementation.
- HASiL — e-Invoice implementation timeline
- HASiL — MyInvois SDK release and validation updates
- OpenPeppol — PINT Malaysia mandatory versions and dates
- OpenPeppol — PINT Malaysia 1.3.1 specification
- SAP — Document and Reporting Compliance Cloud Edition updates
Plan Malaysia e-Invoice Integration in SAP
S4FN can help your SAP Basis, FICO, SD, and finance teams review source data, transaction scope, validation workflow, and integration options for Malaysia e-Invoice.