Skip to content
Learn
Presentations P-00000 to P-00999
Reading To Peppol AP, Queue and History — what each Peppol screen is evidence of

Reading To Peppol AP, Queue and History — what each Peppol screen is evidence of

Send an invoice over Peppol · 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.

Send an invoice over Peppol · presentation 3 of 4

Reading To Peppol AP, Queue and History — what each Peppol screen is evidence of

You can read the three screens after the Waiting Queue and say, for each row, what has and has not happened: a document built…

To Peppol AP

Step 1 — Read a To Peppol AP row as "a document was built"

You will know what the first screen after the Waiting Queue proves.

Screen capture pending the demo tenant

The To Peppol AP listing with the Sender ID, Receiver ID, Buyer Name and Supplier Name columns

Step 2 — Read the three kinds of Validation Error

You will be able to tell a configuration mistake from a rule breach at a glance.

What you do
  1. Read the message; it is the closest thing to a reason you will get…

The status that promises too much

Step 3 — Treat SUBMITTED as handed over, not delivered

You will not tell a customer their invoice was delivered because a screen said SUBMITTED.

Where this step sits
    flowchart TD
  s1["1. Read a To Peppol AP row…"]
  s2["2. Read the three kinds of Validation…"]
  s3["3. Treat SUBMITTED as handed over…"]
  s4["4. Read the Queue: blank means in…"]
  s5["5. Read History as the partner's access…"]
  s6["6. Know there is no way back…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Queue and History

Step 4 — Read the Queue: blank means in flight, a status means it failed

You will know what to do with a row in the sending queue.

What this step names
  1. The row stays and its status becomes the sender's verdict…
  2. An error message from the receiving access point
  3. One of a few rarer results

Step 5 — Read History as the partner's access point signing for it

You will know the strongest proof of arrival you can offer.

Where this step sits
    flowchart TD
  s1["1. Read a To Peppol AP row…"]
  s2["2. Read the three kinds of Validation…"]
  s3["3. Treat SUBMITTED as handed over…"]
  s4["4. Read the Queue: blank means in…"]
  s5["5. Read History as the partner's access…"]
  s6["6. Know there is no way back…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Know there is no way back from a failed row, and what the builder filled in for you

You will fix master data before the first document rather than after.

Where this step sits
    flowchart TD
  s1["1. Read a To Peppol AP row…"]
  s2["2. Read the three kinds of Validation…"]
  s3["3. Treat SUBMITTED as handed over…"]
  s4["4. Read the Queue: blank means in…"]
  s5["5. Read History as the partner's access…"]
  s6["6. Know there is no way back…"]
  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
Who moves your invoice out of the Peppol Waiting Queue, and how often that actually happens — transcriptReading To Peppol AP, Queue and History — what each Peppol screen is evidence of — transcript