Turning Peppol on for a new company, and the queue your document actually lands in — transcript

Presentation 3 of 4 in Set up MyInvois and Peppol for a new company · about 11 minutes · for the whole-system operator — you run the books.

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for whoever has been asked to deliver invoices to a corporate customer over Peppol, has read the setup steps, and wants to know what is actually going to happen when the first invoice is finalised. In about eleven minutes you will know which screens to watch and which to ignore.

Step 1 — Know that there are two switches, not one

After this step you will stop treating Peppol as a single toggle. On the company’s Peppol Config tab there is a Peppol status, enabled or disabled, and separately a Notification Config panel with a checkbox called peppol. They are not two names for the same thing. The status decides whether a finalised document is offered to the Peppol pipeline at all, at the moment you finalise it. The checkbox decides whether a second attempt is made later, after LHDN has accepted the e-invoice. You want both on. Turning on one and leaving the other is the commonest way a new company ends up half-configured, and nothing on the screen pairs them for you.

Screen: the company Peppol Config tab with the Peppol status select and the Notification Config checkboxes

Reference: Organization — Company Peppol Config tab

Step 2 — See how little is checked when the document is finalised

After this step you will know why a Peppol row appears even for a customer who is not ready. The moment a document reaches final, a background step asks three questions: is the document final, is this company’s Peppol status enabled, and is this a document type Peppol can carry. If all three are yes, a row goes into the Peppol waiting queue. That is the whole test. Nobody is asked for a tax number, an address or a participant identifier. So a sale to a customer whose record is incomplete lands in the Peppol waiting queue and in an e-invoice pool at the same instant, for completely unrelated reasons.

Reference: My Peppol Admin Applet — The two routes into the Waiting Queue

Step 3 — Ignore the posting queue

After this step you will not spend an afternoon on an empty screen. The applet has a Posting Queue beside the waiting queue, and a great deal of older material describes a journey from one to the other. That route still exists in the code, and its entrance is a single company field that no screen has written since June 2024, when the Peppol Config tab replaced it with a list of identifiers. The table behind that screen holds no rows on any BigLedger tenant at all. So the Posting Queue is empty everywhere, permanently, and a document that has not appeared in it is not stuck — it was never going there. Watch the waiting queue.

Reference: My Peppol Admin Applet — The two routes into the Waiting Queue

Step 4 — Flag one identifier as default on each side

After this step you will have set the two fields that actually decide whether a Peppol document can be built. When the waiting-queue row is turned into a Peppol invoice, two addresses are looked up: your company’s participant identifier, taken from the company’s own list of Peppol identifiers, and your customer’s, taken from theirs. Both lookups ask for the one flagged as default. Register as many identifiers as you like on either side; if none of them carries that flag, the address comes back empty, and the document is stamped missing Peppol sender or receiver identifier and stops. That stamp is the first place either mistake becomes visible.

Reference: My Peppol Admin Applet — Before you can use it

Step 5 — Ask for the processors to be scheduled

After this step you will have made the request that decides whether any of this moves. Every tenant is created with a standard set of scheduled jobs — stock balances, generic documents, and the LHDN e-invoice pipeline end to end. Not one Peppol job is in that set. So the switches go on, the waiting queue fills up correctly, and nothing ever builds a Peppol document or sends one, with no error and no message anywhere. Across the whole customer base the job that drains the waiting queue is scheduled on a handful of tenants, against about sixty-five for the equivalent LHDN sweep. Put the request in the same message as the one asking for applet access.

Reference: My Peppol Admin Applet — Before you can use it

Step 6 — Walk one real invoice through three screens

After this step you will have proof rather than configuration. Finalise one small invoice to the customer you set up, then look at three screens in order. The waiting queue, where it should already be sitting — press Process rather than waiting for a schedule. Then internal submission to Peppol, where the row carries a sender and a receiver identifier, and where you find out whether your two default flags took. Then the submission queue and history, where a successful transmission ends up. And then the only check that counts: ask the person at the other end whether it arrived.

Reference: Peppol Configuration Guide — Step 1: Turn Peppol on for the company

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

1. You set the company's Peppol status to enabled and left Notification Config alone. What have you switched on? The route that puts a row in the waiting queue when a document is finalised, but not the one that runs after LHDN accepts the e-invoice
Both routes — the notification checkbox only controls e-mail
Neither; the notification checkbox is the real switch

2. A sale to a customer with no tax number is finalised at a Peppol-enabled company. Where does it go? To an e-invoice pool only; the Peppol side rejects it
To an e-invoice pool and to the Peppol waiting queue, because the Peppol step checks neither the buyer's details nor any identifier
To the Peppol posting queue, where it waits for the customer record to be completed

3. Your first Peppol invoice never appears in the Posting Queue. What does that tell you? The company's Peppol status is not enabled
The document type cannot be carried over Peppol
Nothing is wrong — that route is dormant on every tenant and the screen is always empty

4. A to-Peppol document is stamped *Missing Peppol Sender or Receiver ID*. What is the most likely cause? Identifiers are registered on the company or the customer but none is flagged as the default
The access point has not finished registering your participant
The customer's identifier uses the wrong scheme prefix

5. Everything is configured and the waiting queue keeps growing, with no errors anywhere. What should you check first? Whether the customer's access point is reachable
Whether the Peppol processors are scheduled for your tenant — none of them is in the default set
Whether the LHDN submissions have come back Valid

Answer key

The route that puts a row in the waiting queue when a document is finalised, but not the one that runs after LHDN accepts the e-invoice — Organization — Company Peppol Config tab
To an e-invoice pool and to the Peppol waiting queue, because the Peppol step checks neither the buyer's details nor any identifier — My Peppol Admin Applet — The two routes into the Waiting Queue
Nothing is wrong — that route is dormant on every tenant and the screen is always empty — My Peppol Admin Applet — The two routes into the Waiting Queue
Identifiers are registered on the company or the customer but none is flagged as the default — My Peppol Admin Applet — Before you can use it
Whether the Peppol processors are scheduled for your tenant — none of them is in the default set — My Peppol Admin Applet — Before you can use it

This is a self-check. Your answers are marked in your browser and stay there — nothing is sent anywhere, nothing is recorded, and the marking is readable in the page source, so it is not a credential. Open the answer key at any time.

Next: Proving a new company is live, and the four things that look like proof and are not · Back to the series · Play this as a presentation

Last updated on September 19, 2026

Turning Peppol on for a new company, and the queue your document actually lands in Proving a new company is live, and the four things that look like proof and are not