Nematix
E Invoicing
 E-Invoicing for Malaysian Manufacturers and Exporters
Feb 22, 2026 - Last updated on Feb 22, 2026

E-Invoicing for Malaysian Manufacturers and Exporters

Malaysian manufacturers and exporters face both LHDN MyInvois compliance and cross-border PEPPOL requirements. Here is how to handle both together.

Manufacturers and exporters operate in the most demanding e-invoicing environment of any business type in Malaysia. High invoice volumes make manual portal submission operationally impossible. Multiple buyer types — domestic distributors, foreign importers, government tenders — each carry different invoicing requirements. And the phased rollout of the MyInvois mandate placed most large manufacturers in scope under Phase 1 and brought mid-sized manufacturers into compliance obligations under Phase 2.

On top of domestic compliance, exporters face a second layer: cross-border buyers in Singapore, Australia, and EU markets increasingly require or prefer invoice delivery via PEPPOL, the global B2B e-invoicing network. Managing both layers together — domestic IRBM validation and cross-border PEPPOL delivery — without duplicating effort or maintaining two separate systems is the central challenge this guide addresses.

The Compliance Picture for Manufacturers

Phase 1 of the MyInvois mandate, which took effect in August 2024, brought the largest Malaysian businesses into scope — including most large manufacturers with annual revenue exceeding RM100 million. Phase 2, effective January 2025, extended requirements to mid-sized manufacturers. Manufacturers below the Phase 2 threshold have later deadlines, but planning and implementation should not wait for the mandate date.

What compliance means operationally for a manufacturing business goes beyond simply issuing electronic invoices. Every invoice issued — whether to a domestic distributor, a Singaporean OEM buyer, a government entity, or a logistics company — must be submitted to IRBM’s system for cryptographic validation before or at the point of issuance. The validated invoice carries an IRBM-assigned UUID and a QR code. That validated document — not the pre-submission version — is the legally valid invoice that must be transmitted to the buyer, stored in your records, and retained for the minimum statutory period.

A point that catches many export-focused finance teams off guard: export invoices are not exempt from MyInvois validation. The SST or VAT treatment of exported goods may qualify for zero-rating or exemption, but the obligation to validate the invoice through IRBM’s system is separate and applies regardless of the buyer’s country. This means a Johor manufacturer invoicing a Singapore buyer must still run that invoice through MyInvois before delivery.

Finally: at the volumes most manufacturers operate — hundreds to thousands of invoices per month — the MyInvois web portal is not a viable compliance path. API integration with your ERP is the only operationally sustainable approach.

Managing High Invoice Volumes

Manufacturing B2B invoice volumes vary widely, but even conservative mid-sized manufacturers routinely process 300 to 2,000 invoices per month. At those volumes, the MyInvois portal — which requires line-by-line manual entry or file upload with manual review — becomes an operational bottleneck within weeks of go-live.

API integration eliminates this bottleneck by connecting your ERP directly to IRBM’s submission endpoint. Invoices are submitted programmatically at generation time without human intervention, validation responses are logged automatically, and the validated documents are retrieved and stored without manual steps.

The key architectural decisions for high-volume manufacturing environments are:

Batch vs individual submission: IRBM’s API supports both individual invoice submission and batch submission. For manufacturing environments with high daily volumes, batch submission — grouping invoices into submission windows (e.g., every 15 minutes or every hour) — is more efficient and easier to rate-limit. Individual real-time submission is appropriate for customer-facing invoicing where the buyer needs immediate confirmation.

Night-batch processing: Many manufacturing operations run invoice generation as a back-of-house batch process overnight. Your MyInvois integration must accommodate this — invoices generated at 02:00 must be submitted and validated before the next business day begins. Build the integration to handle batch windows, not just real-time triggers.

Reconciliation: ERP invoice records must be reconciled against IRBM validation responses. Every invoice in your ERP should have a corresponding IRBM UUID stored against it. Invoices without a UUID have not been validated and are not legally compliant. A daily reconciliation job that flags unvalidated invoices is a fundamental part of the integration architecture.

Throughput rate: IRBM enforces per-minute and per-day rate limits on API submissions. For manufacturers with large overnight batches, this means the submission window must be sized to respect rate limits while completing before business hours. Design your submission queue with rate-limit awareness from the start.

Export Invoices: MyInvois and PEPPOL Together

The most sophisticated requirement for Malaysian manufacturers and exporters is the two-layer invoice workflow — domestic IRBM validation combined with cross-border PEPPOL delivery, handled from a single integration without duplication of effort.

Here is how the two-layer approach works in practice:

When a Malaysian manufacturer generates an invoice for an overseas buyer, the invoice data goes to the integration layer (typically managed by Nematix). The integration simultaneously:

  1. Submits the invoice to IRBM’s MyInvois API for domestic validation. IRBM validates the document, attaches a UUID and QR code, and returns the validated invoice.
  2. If the overseas buyer is PEPPOL-registered, routes the validated invoice to the PEPPOL network via Storecove’s access point. The invoice arrives in the buyer’s ERP as a structured UBL document — no email, no PDF conversion, no manual keying on the buyer’s side.

For buyers not on the PEPPOL network (which applies to some markets in the Middle East, parts of ASEAN, and smaller international buyers), the validated PDF is transmitted by email or through the buyer’s supplier portal as before. But the IRBM validation has been completed regardless.

A concrete example: a Selangor auto parts manufacturer supplies a Singapore automotive OEM. The invoice is generated in their SAP system. The Nematix integration submits it to IRBM, receives the validated document with QR code, then routes it to the Singapore buyer’s ERP via PEPPOL — all within seconds of invoice generation. The accounts payable team at the Singapore OEM receives a structured invoice directly in their ERP, eliminates keying, and the invoice is matched against the purchase order automatically. Payment is initiated without friction.

The same workflow applies to Australian buyers (which have strong PEPPOL adoption), EU buyers, and any other PEPPOL-connected trading partner. The domestic compliance layer is invariant — every invoice goes through IRBM. The PEPPOL layer activates only for buyers who are PEPPOL-registered.

Multi-Currency and Exchange Rate Handling

Manufacturers exporting in USD, EUR, SGD, or other foreign currencies face a specific MyInvois compliance requirement that is distinct from standard domestic invoicing.

IRBM requires that every invoice submitted to MyInvois include:

  • The invoice currency (ISO 4217 code — e.g., USD, EUR, SGD)
  • The exchange rate to MYR at the transaction date
  • The MYR-equivalent amounts for tax calculation purposes

This is because Malaysian SST and income tax calculations are conducted in MYR. IRBM needs the MYR equivalents even when the buyer-facing invoice is denominated in a foreign currency.

The most common mistake: submitting the foreign currency amounts without MYR conversion, causing tax calculation mismatches that result in validation failures or, worse, silent compliance gaps if the submission is accepted but the tax amounts are incorrect.

Best practice: source the exchange rate from Bank Negara Malaysia’s (BNM) official reference rate published for the invoice date. BNM publishes daily reference rates for major currencies; these rates are the accepted standard for Malaysian tax purposes. Embed the exchange rate in your UBL or JSON submission data at invoice generation time — do not attempt to apply exchange rates retrospectively during reconciliation.

For ERP systems that manage exchange rates internally (common in SAP and Oracle environments), verify that the rate your ERP stores for the transaction date matches the BNM reference rate for that date, or implement a BNM rate feed to keep rates aligned.

Credit Notes, Debit Notes, and Returns

Manufacturing frequently involves credit notes and debit notes — price adjustments post-delivery, quantity discrepancies, returned goods, and retrospective rebates. Under MyInvois, credit notes and debit notes are treated as independent documents that must reference the original validated invoice.

Key requirements for credit and debit notes:

  • The credit or debit note must include the UUID of the original validated invoice it relates to. This linkage is mandatory — IRBM uses it to trace adjustments to original transactions.
  • Credit notes have a defined time window for submission relative to the original invoice. Submit credit notes promptly; delayed credit notes may fail IRBM validation if they fall outside the permitted window.
  • The credit note amount must not exceed the original invoice amount. Validation checks enforce this.

Operational implication for returns workflows: your returns and adjustment processes must change. Finance teams cannot issue a credit note without first locating the IRBM UUID of the original invoice. If your ERP does not store the UUID as a field on the original invoice record, your returns workflow will break at the point of credit note generation. Storing the IRBM UUID on the invoice record — alongside your internal invoice number — is a mandatory requirement of a complete MyInvois integration, not an optional enhancement.

For businesses with complex returns patterns (high-volume return-to-vendor processes, credit note pools, volume rebate agreements structured as periodic credit notes), the design of the returns workflow within the MyInvois integration requires dedicated attention during implementation.

Government Procurement and B2G Invoicing

Malaysian manufacturers that supply government agencies — federal ministries, state bodies, GLCs, or statutory authorities — follow the same MyInvois validation flow as commercial B2B invoicing. The buyer being a government entity does not change the IRBM validation requirement.

What is different for B2G invoicing is the buyer identification. Government entities have TINs and, in some cases, specific identifier codes used within government procurement systems. Verify the correct TIN and buyer details for each government entity before submitting invoices — government entities are less tolerant of invoicing errors than commercial buyers, and correction workflows for government invoices can involve bureaucratic friction.

For manufacturers supplying to foreign government procurement — Singapore government agencies and statutory boards, Australian federal and state governments — PEPPOL connectivity is increasingly a qualification criterion. Singapore’s Government Technology Agency (GovTech) mandated PEPPOL for all government procurement in 2019. Australian government procurement has been phasing in PEPPOL requirements across agencies. A Malaysian manufacturer tendering for a contract with a Singapore government body or a Singapore GLC will frequently encounter PEPPOL connectivity as either a mandatory requirement or a strongly preferred capability.

To check whether a government entity is PEPPOL-registered, query the PEPPOL SMP (Service Metadata Publisher) directory using the entity’s identifier. Nematix handles these lookups as part of trading partner onboarding.

Implementation Approach for Manufacturers

A realistic implementation approach for manufacturers combines phased rollout with clear workstream separation:

Phase 1 — Portal for exceptions, integration in build (Weeks 1-4): While ERP integration is being designed and built, use the MyInvois portal for any invoices that fall due before the integration is live. This is not sustainable at scale, but it ensures compliance during the integration build period. Limit portal usage to low-volume exception cases; do not attempt to run ongoing operations through the portal.

Phase 2 — API integration for standard invoice flows (Weeks 4-12): ERP integration goes live for the main invoice workflow — standard sales invoices, domestic and export. This covers the compliance core. The integration handles submission, status polling, validated document retrieval, archival, and error routing.

Phase 3 — PEPPOL connectivity for cross-border buyers (Weeks 8-16, overlapping with Phase 2): PEPPOL access point registration and trading partner onboarding begins in parallel with API integration. For exporters with significant Singapore, Australia, or EU invoice volumes, this phase starts as early as possible to maximise the benefit window before mandate pressure in those markets intensifies.

ERP pre-built connectors: Nematix provides pre-built connectors for SAP, Oracle, and Microsoft Dynamics. These connectors reduce the integration timeline significantly compared to custom API development — the connector handles the MyInvois API communication layer, and configuration focuses on field mapping from your ERP’s invoice data model to IRBM’s required fields.

Timeline expectations: a standard API integration with a supported ERP and pre-built connector typically takes 6 to 10 weeks. Custom ERP integrations, complex multi-entity structures, or integrations combining MyInvois API with PEPPOL connectivity typically run 10 to 16 weeks.

Closing

For manufacturers and exporters, e-invoicing is as much a supply chain issue as a compliance issue. A well-implemented MyInvois and PEPPOL integration does not merely satisfy IRBM requirements — it reduces friction across the entire invoice-to-payment cycle, cuts manual processing costs on both sides of each transaction, and positions Malaysian manufacturers as operationally preferred suppliers to PEPPOL-registered buyers in Singapore, Australia, and beyond.

The compliance deadline is the forcing function, but the operational benefit — structured invoices arriving directly in buyer ERP systems, automated matching against purchase orders, faster payment initiation — is the durable value that makes this investment worthwhile long after the compliance pressure has faded.

Ready to simplify your e-invoicing transition? Talk to our team about seamless MyInvois and PEPPOL integration for your business.