How Peppol fits beside MyInvois, e-mail and the e-invoice pools

The background to the Peppol configuration guide. Peppol delivers and LHDN clears. For a document type Peppol can carry, from a company with Peppol enabled, the two run side by side from the moment the document is finalised. This page explains what that means for each screen you will use, and how a setting made in one applet shows up in another. Read it before Step 1 if Peppol is new to you, or when something in Steps 1 to 8 surprises you.

What you need to know first

Peppol delivers; LHDN clears. MyInvois is a clearance channel — you send the tax authority a document and it comes back Valid. Peppol is a delivery network — your document travels from BigLedger’s access point to your partner’s access point, addressed by participant ID. They are two separate journeys for the same finalised document, and you need both.

Peppol runs beside the LHDN pipeline, not after it. The moment a document is finalised — before LHDN has been told anything — it lands in the Peppol waiting queue, on the strength of three things only: the document is FINAL, the company has Peppol enabled, and the document type is one Peppol can carry. Nothing at that point checks the buyer’s tax number, the addresses or the participant IDs. Three useful consequences:

• A document in an e-invoice pool is in the Peppol waiting queue as well. The two are not connected: the pool row is waiting for the buyer’s details, the Peppol row is not waiting for anything. It will fail later, one stage on, when the Peppol document is built and a sender or receiver ID is missing.
• A Peppol delivery can succeed while the LHDN submission is still Invalid, and vice versa. Neither tells you anything about the other.
• There is a second, separate switch — the peppol checkbox in Notification Config — which adds a second waiting-queue row the moment LHDN accepts the submission — which is before LHDN has said Valid, so this row does not wait for validation either. Step 1 covers both, because turning on one and not the other is the commonest way a new company ends up half-configured.

Peppol is not “for cross-border only”. The traffic BigLedger reports to OpenPeppol every month is overwhelmingly the Malaysian domestic billing profile. A Malaysian supplier delivering to a Malaysian buyer over Peppol is the ordinary case, not the exotic one.

You do not join the network yourself. BigLedger operates an accredited Malaysian access point. Registering your participant with the Malaysian service metadata publisher, the certificates, the network-side migrations and the statistics BigLedger has to file as a service provider are all handled for you. There is nothing for you to install and no certificate for you to obtain.

Peppol beside its neighbours: MyInvois, e-mail, pools, clocks

Peppol is configured on three applets and read by a fourth, and the consequence of a wrong setting shows up somewhere other than where you made it. The map:

• What must exist first. The company’s identity and your customers’ master data, completed for MyInvois (MyInvois Setup, Steps 2 and 5) — the Peppol document is built from the same company and customer records, and the e-invoice trigger template that MyInvois needs is the subscription the Peppol follow-on job runs under. The company’s Peppol Status and default ID on the Organisation applet’s Peppol Config tab; a default ID on each Peppol customer in the Customer applet; and a clock for the sweep in the Scheduler applet. Missing the first, nothing is written at finalise; missing the IDs, every document stops at Missing Peppol Sender or Receiver ID; missing the clock, the Waiting Queue fills and nothing empties it.
• What becomes possible. A partner receives your invoice in their own system on the day you finalise it, without waiting for LHDN; and your suppliers’ Peppol invoices arrive on From Peppol AP and line up for pairing against your purchases (Incoming Supplier E-Invoices).
• The siblings, and when to use which. Three ways a buyer can come to hold your invoice. MyInvois clears it with the tax authority and is not optional. The e-mail box beside the peppol box in Notification Config sends the buyer the validated PDF once LHDN says Valid (what that e-mail carries) — right for a buyer who reads invoices, wrong for one whose system ingests them. Peppol delivers the structured document into the buyer’s software and is the one to choose when the partner has asked for it by participant ID. The two boxes are independent: ticking peppol neither switches the e-mail off nor needs it on, and a partner on Peppol who also has an e-mail address on file receives both.
• What breaks elsewhere when this is wrong. Peppol Status is company-wide, so a company with two Peppol clients and fifty others builds a stopped Peppol document for every invoice to the fifty. A customer’s wrong participant ID delivers your invoice to another business and still writes a History receipt. Both switches on sends every invoice twice. And a correction made in an e-invoice pool does not reach the Peppol copy: Save and Resubmit there sends the e-invoice record and copies its buyer back onto the document’s e-invoice details, which the Peppol builder does not read — it reads the customer record (where a finalised document goes on the LHDN side; what happens after you finalise, for an integrator).
• What it is used alongside. In practice: the Sales Invoice applet, where the finalise that starts both pipelines happens; the Scheduler applet for the sweep; the My E-Invoice Admin applet for the LHDN side of the same documents — use it when the question is whether a document is valid for tax, and My Peppol Admin when the question is whether it travelled; and the Peppol AP Admin applet, BigLedger’s operator console, for the one check you cannot make yourself.

Related documentation

• Peppol Configuration Guide: the whole setup, with its success check.
• My Peppol Admin Applet: field-level reference for the queues.
• Organisation Applet: the Peppol Config tab.
• MyInvois Setup: the master data Peppol reuses.
• Pools & Submission Routing: the LHDN side of the same finalise.