Skip to content
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, and only one rings a 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 the storefront door has…"]
  s4["4. Find the requests that do wait…"]
  s5["5. Make the pools your inbox…"]
  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 before you touch it, which decides everything else.

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 the storefront door has no bell

You will stop waiting for a message that is never sent.

What this step names
  1. Nothing e-mails you
  2. Nothing appears in a list of things to action
  3. No counter anywhere goes up by one

Step 4 — Find the requests that do wait for a person

You will know where the other door's traffic collects.

  • Read it as a register rather than a worklist…
Screen capture pending the demo tenant

Internal Submission → Portal Request, showing document numbers, amount and user request status, with no action buttons on the toolbar

Step 5 — Make the pools your inbox, on a schedule

You will have a habit that closes the gap both doors leave.

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 the storefront door has…"]
  s4["4. Find the requests that do wait…"]
  s5["5. Make the pools your inbox…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;
  

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.