Skip to content
Learn
Presentations P-00000 to P-00999
Two doors, one machine, and no bell

Two doors, one machine, and no bell

Handle the e-invoice requests your buyers raise · presentation 1 of 5 · 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.

Handle the e-invoice requests your buyers raise · presentation 1 of 5

Two doors, one machine, and no bell

You can tell the two ways a buyer asks GadgetSphere for an e-invoice apart…

Step 1 — Know what your buyer is actually asking for

You will know what is at stake in a request that looks trivial.

Where this step sits
    flowchart TD
  s1["1. Know what your buyer is actually…"]
  s2["2. Tell the two doors apart"]
  s3["3. Accept that both doors run without…"]
  s4["4. Find the register that writes every…"]
  s5["5. Check the failures on a schedule"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s1 here;

Step 2 — Tell the two doors apart

You will know which door a request came through, which decides who the buyer is on your records.

Screen capture pending the demo tenant

The storefront e-invoice widget's search form beside the portal applet's Request E-Invoice panel, opened one after the other

Step 3 — Accept that both doors run without you

You will stop waiting for a request to reach your desk.

What this step names
  1. Whichever door the buyer used
  2. The request goes straight into the same queue processor
  3. The processor does the work at once

Step 4 — Find the register that writes every request down

You will know where to look first.

  • Read the list as a register: it does not correct anything
Screen capture pending the demo tenant

Internal Submission → Portal Request, showing document numbers, amount and user request status

Step 5 — Check the failures on a schedule

You will have a habit that closes the gap the missing alert leaves.

What you do
  1. Open Portal Request on a fixed rhythm — daily during the month…

NarrationSlide 1 of 6

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
Close a branch, and prove the settings — transcriptTwo doors, one machine, and no bell — transcript