Skip to content
Learn
Presentations P-00000 to P-00999
Turning Peppol on for a new company, and the queue your document actually lands in

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

Set up MyInvois and Peppol for a new company · presentation 3 of 4 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Set up MyInvois and Peppol for a new company · presentation 3 of 4

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

You can set up Peppol for a new company knowing which of the two switches does what, which screen to watch…

What you turn on

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

You will stop treating Peppol as a single toggle.

Screen capture pending the demo tenant

The company Peppol Config tab with the Peppol status select and the Notification Config checkboxes

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

You will know why a Peppol row appears even for a customer who is not ready.

What this step names
  1. The moment a document reaches final
  2. A background step asks three questions: is the document final
  3. Is this company's Peppol status enabled
  4. Is this a document type Peppol can carry

The screen to ignore

Step 3 — Ignore the posting queue

You will not spend an afternoon on an empty screen.

What you do
  1. Watch the waiting queue

Step 4 — Flag one identifier as default on each side

You will have set the two fields that actually decide whether a Peppol document can be built.

What this step names
  1. Register as many identifiers as you like on either side…
  2. The address comes back empty
  3. The document is stamped missing Peppol sender or receiver identifier and stops

The ask that is easy to forget

Step 5 — Ask for the processors to be scheduled

You will have made the request that decides whether any of this moves.

What this step names
  1. Every tenant is created with a standard set of scheduled jobs —…
  2. Generic documents
  3. The LHDN e-invoice pipeline end to end

Step 6 — Walk one real invoice through three screens

You will have proof rather than configuration.

Where this step sits
    flowchart TD
  s1["1. Know that there are two switches…"]
  s2["2. See how little is checked when…"]
  s3["3. Ignore the posting queue"]
  s4["4. Flag one identifier as default on…"]
  s5["5. Ask for the processors to be…"]
  s6["6. Walk one real invoice through three…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;

NarrationSlide 1 of 10

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on
The fields on a new company's E-Invoice tab that switch something on, and the four that do not — transcriptTurning Peppol on for a new company, and the queue your document actually lands in — transcript