E-Invoice and Peppol
Malaysia gave you two electronic-invoicing obligations that look like one. This page explains how they differ, how BigLedger runs both from the same finalised sales document, and what BigLedger’s own position on the Peppol network is. If you want to do something rather than understand it, go straight to the e-invoice guides.
Two networks, two jobs
MyInvois is clearance. You send the Inland Revenue Board (LHDN) a document, it checks it, and it
comes back Valid with a unique identifier. The tax authority is the destination.
Peppol is delivery. A document travels from your access point to your trading partner’s access point, addressed by participant ID. Your customer’s accounts-payable system is the destination. The tax authority is not involved.
Most Malaysian businesses need the first. You need the second when your customers or suppliers use Peppol — which, in practice, increasingly includes domestic Malaysian trading partners. Peppol is often described as a cross-border thing; BigLedger’s own monthly traffic statistics show it carrying the Malaysian domestic business-to-business profile, so that description is out of date.
The two pipelines run beside each other, not one after the other
This is the point people get wrong most often. When you finalise a sales invoice at a company with
Peppol enabled, it goes into both queues at once — the LHDN posting queue and the Peppol waiting
queue. The Peppol side does not wait for LHDN to return Valid, and — corrected 2026-09-19 — it
does not run the mandatory-field check either: the Peppol row is written on the strength of FINAL, the
company’s Peppol status and the document type, nothing more.
So the two pipelines do not fail for the same reason. A document parked in an e-invoice pool because the buyer’s tax number is missing is, at the same moment, sitting in the Peppol waiting queue with nothing holding it back; it fails one stop later, when the Peppol document is built and the sender or receiver participant ID cannot be found. Fixing the customer record helps both, but you read them on different screens — the My Peppol Admin Applet page walks the Peppol side stop by stop.
BigLedger’s position on Peppol
BigLedger operates an accredited Malaysian Peppol access point, not just a connection to somebody else’s. In practice that means BigLedger carries the obligations of a service provider rather than those of a sender:
- Participants are created at the Malaysian Service Metadata Publisher, with MDEC’s automated know-your-customer check cross-verifying the participant’s name and registration number against the company registry before the Peppol ID is published to the Peppol Directory and the Service Metadata Locator.
- The network’s infrastructure migrations are BigLedger’s problem, not yours: the certificate authority move from G2 to G3, and OpenPeppol’s move of the lookup domains, were both handled at the access point.
- BigLedger files two monthly statistical reports to OpenPeppol — a Transaction Statistics Report and an End User Statistics Report — covering exchanges by transport protocol, opposite service provider, document type and country.
Two facts worth knowing before you plan around Peppol
Malaysian participant IDs use scheme 0230. A finished ID looks like 0230: followed by your
special identifier and registration number. Do not build one by copying a format from another
country’s documentation — an ID with the wrong scheme does not produce an error message, it produces
a delivery that silently never arrives. If your registered address is in Sabah or Sarawak, allow two
to ten working days for registration: those two special identifiers are checked manually at the local
authority counter.
Only four kinds of document are built for Peppol. A sales invoice or cash bill becomes a billing Invoice; a sales credit note or sales return becomes a billing Credit Note; a self-billed purchase invoice and a self-billed purchase debit note or purchase return become the self-billing versions of the same two. Anything else — a sales debit note, a sales refund note, a self-billed purchase credit note — produces no Peppol document at all, and nothing reports the gap. Plan your document types accordingly.