MyInvois e-Invoicing and Peppol: one ERP for Malaysia and EU buyers

01Malaysian e-Invoice after 1 January 2026

IRBM made e-Invoice mandatory in phases, assigned by the taxpayer’s annual turnover or revenue. Each e-Invoice is validated through MyInvois, either in the MyInvois Portal or by a system that calls the MyInvois API. IRBM’s implementation timeline (opens external site), last updated on 30 August 2026, sets the dates below.

The exemption threshold has been changed before; it replaced lower figures in earlier versions of the timeline. Date any internal note that relies on it, and look at the timeline again before each design decision.

02From a PDF to a validated e-Invoice

In the Malaysian model, the supplier’s system submits structured invoice data and MyInvois validates it. What counts for IRBM is the validated e-Invoice. A PDF printed from the ERP and attached to an email is not one, however complete it looks.

In Europe the idea is similar and the mechanics differ. An EU e-invoice is a structured file that software can process without a person interpreting it. Its content follows EN 16931, the European standard that defines the core data of an invoice. Scans, word-processor files and PDFs do not qualify, even when they come by email. A PDF copy may travel with the structured file for human readers; the structured data is the invoice. Across much of Europe the expected format is Peppol BIS Billing 3.0, which expresses EN 16931 in the UBL syntax for the Peppol network.

03Peppol in Malaysia: MDEC and Malaysia PINT

Peppol combines a cross-border network with common specifications so that businesses can exchange documents such as orders and invoices. Its governing body is OpenPeppol, a Brussels-based association that operates on a non-profit basis. In Malaysia, the Peppol Authority is the Malaysia Digital Economy Corporation (MDEC), an agency under the Ministry of Digital. MDEC publishes the Malaysian specification, Malaysia PINT (opens external site) (MY PINT), under its National E-Invoicing Initiative.

The roles are split. According to the Peppol country profile for Malaysia (opens external site), MDEC looks after e-invoicing for business digitalisation, while IRBM is responsible for tax reporting and compliance. IRBM recognises submission through a Peppol service provider as one option. A business therefore has a choice of routes: the MyInvois Portal, a direct integration with the MyInvois API, or a Peppol service provider that exchanges invoices with trading partners and handles the submission.

04How the Peppol network moves an invoice

The network follows what Peppol calls a four-corner model. Corner one is your ERP, which hands the invoice to your access point in corner two. Corner two delivers it to corner three, the access point your customer uses, and corner three passes it into corner four, the customer’s own system. To find the receiver, the sending access point consults the Service Metadata Locator, the network’s directory. That directory points to a Service Metadata Publisher, where the receiver’s registration and accepted document types are held.

The benefit is reach. A single agreement with one access point or Peppol service provider connects you with every participant, whatever provider they have chosen. For a Malaysian exporter that matters: the connection used for Malaysia PINT can also reach EU buyers who receive Peppol BIS Billing 3.0, provided the provider supports both specifications.

• Registration: your company is listed on the network under its identifier, together with the documents it is able to accept. An entry that is absent or incorrect often explains why invoices go astray.
• Validation: access points test each document against the rules of its specification, and a failing invoice is stopped before the customer sees it.
• Delivery status: the network confirms that a message arrived technically. Whether the buyer has accepted, disputed or paid travels in other messages, and only when both sides support them.

05Invoicing EU buyers and running EU subsidiaries

A Malaysian group that sells to EU buyers, or owns companies in the EU, meets a second set of rules, framed by two EU texts. Under Directive 2014/55/EU (opens external site), public buyers in the EU must accept electronic invoices that comply with EN 16931, so invoices to public bodies were the first to go electronic in most Member States. ViDA, the EU’s package on VAT in the digital age, includes Council Directive (EU) 2025/516 (opens external site), which the Council adopted on 11 March 2025 and which has been in force since 14 April 2025.

Under ViDA, a Member State no longer needs an EU derogation to make e-invoicing compulsory at home. From 1 July 2030, B2B supplies between Member States require e-invoices and digital reporting. National systems that report transactions in real time must be brought into line with the EU model by 1 January 2035.

Belgium shows what a domestic obligation looks like in practice. From 1 January 2026, businesses established in Belgium and registered for VAT there have exchanged structured e-invoices with each other for domestic sales, using Peppol unless both parties agree otherwise. Guidance is on the Belgian federal e-invoicing site (opens external site), which FPS BOSA operates together with FPS Finance. Foreign companies with no fixed establishment in Belgium fall outside the rule, so the Belgian rule reaches a Malaysian group through a Belgian subsidiary rather than through invoices issued from Malaysia.

Other Member States follow their own timetable and architecture. France, Germany and Spain phase in domestic B2B obligations on dates between 2025 and 2028, and Italy has cleared B2B invoices through a national platform since 2019. A group with several EU companies therefore needs a single integration design that can serve several national channels.

06One ERP, two outlets: where the effort really lies

Submitting a first e-Invoice is an afternoon’s work. Sending every invoice through MyInvois, and through Peppol where buyers need it, without manual steps is a design task. The effort lies in master data, validation, incoming invoices and archiving, far more than in the connection itself.

• Master data comes first. Each customer record needs the identifiers its destination expects: for MyInvois, the buyer details IRBM specifies; for Peppol, the participant identifier and, for EU buyers, the VAT number. Every item also needs its unit and tax classification translated into the code lists of the standard. Verify registrations before the first submission and keep verifying, because companies switch providers.
• Validate inside your own process. Apply the rules MyInvois or the access point will apply before the invoice leaves the ERP. A rejection is then caught and corrected at the source instead of surfacing weeks later, when a buyer asks where the invoice is.
• Design the incoming flow. Structured supplier invoices can be matched by machine against the purchase order, the goods receipt and the supplier record, and go to an approver only where something disagrees. That is where most of the time is saved. Invoices that still come as paper or PDF, from smaller suppliers or from abroad, can enter the same flow through document capture.
• Preserve what was exchanged. The structured file with its validation or delivery evidence is the record. Store it unchanged for as long as the law requires, and make sure staff can still locate and open it when an auditor asks.
• Watch the flow. Rejected validations, failed deliveries and invoices stuck in approval need a dashboard and a named owner, never a shared mailbox.

For Odoo, check what the Malaysian localisation of your version covers for MyInvois, and what the localisations of your EU companies cover for Peppol; the remaining work is mainly setup, master data and approval rules. In an SAP landscape, teams usually weigh SAP’s own e-document compliance tools against a link to an outside provider, and both options depend on clean master data and sound error handling. When several ERPs, an online shop and a group finance system all issue invoices, a shared integration layer keeps formats, checks and monitoring together rather than repeated system by system.

07A practical plan

1. 01Map every invoicing flow. Note each system that sends or receives invoices, credit notes and debit notes, per country and per channel, not forgetting online shops, recurring billing and intercompany flows between Malaysian and EU companies.
2. 02Choose the routes. The MyInvois Portal where volumes are small, the MyInvois API or a Peppol service provider for system-to-system submission, and a Peppol access point for EU buyers. Base the choice on volumes, document types and countries.
3. 03Clean the master data. Identifiers, tax details, units and tax classifications, for every customer, supplier and item record.
4. 04Rehearse with real partners. Before switching over, trade test invoices with your biggest buyers and suppliers and see how their systems handle yours.
5. 05Automate incoming invoices. Matching, approval and posting, with people handling only the exceptions.
6. 06Archive and monitor. Retain each structured original with its validation or delivery evidence, and assign an owner to every message that fails.
7. 07Prepare for EU reporting. Shape data flows so that invoice data from EU companies can also feed digital reporting as ViDA and national rules introduce it.

08What to watch

• Changes to IRBM’s e-Invoice guidance and to the implementation timeline.
• New releases of the Malaysia PINT specifications from MDEC.
• How Member States put ViDA into national law, and which of them apply the 1 July 2030 obligation to sales at home as well.
• Updated releases of Peppol BIS Billing 3.0, and changes to the checks your access point runs.

The rules are still moving, in Malaysia and in nearly every EU country. Date each internal note on the subject, and return to the official sources before you settle a design.