Skip to content
Sales you skip because a platform e-invoices them · presentation 2 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.

Sales you skip because a platform e-invoices them · presentation 2 of 5

Pick the level, and know what it costs

You can choose between skipping one document, one customer and one whole branch at GadgetSphere, predict how much each choice catches…

Step 1 — Skip one document when one document is the exception

You will know the safest of the three and its one limitation.

What you do
  1. Use it for the genuine one-off: an order that turned out to be somebody…

Step 2 — Skip a customer when the relationship is the exception

You will use the customer flag for what it is for.

Where this step sits
    flowchart TD
  s1["1. Skip one document when one document…"]
  s2["2. Skip a customer when the relationship…"]
  s3["3. Skip a branch only when the…"]
  s4["4. Recognise the design the branch flag…"]
  s5["5. Audit all three before you trust…"]
  s6["6. Write the reason down…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — Skip a branch only when the whole shop is the exception

You will treat the branch flag with the respect it needs.

Where this step sits
    flowchart TD
  s1["1. Skip one document when one document…"]
  s2["2. Skip a customer when the relationship…"]
  s3["3. Skip a branch only when the…"]
  s4["4. Recognise the design the branch flag…"]
  s5["5. Audit all three before you trust…"]
  s6["6. Write the reason down…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — Recognise the design the branch flag was built for

You will see why this is a feature and not an oversight.

Where this step sits
    flowchart TD
  s1["1. Skip one document when one document…"]
  s2["2. Skip a customer when the relationship…"]
  s3["3. Skip a branch only when the…"]
  s4["4. Recognise the design the branch flag…"]
  s5["5. Audit all three before you trust…"]
  s6["6. Write the reason down…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Audit all three before you trust any of them

You will have a way to see the flag you did not set.

What you do
  1. Work backwards — which branch, which customer — rather than reading three screens hoping…

Step 6 — Write the reason down, because the tick outlives it

You will have saved your successor a bad afternoon.

What this step names
  1. These flags are typically set once
  2. During a migration or when a new channel opens
  3. By somebody who had a perfectly good reason
  4. Is no longer in the room

NarrationSlide 1 of 7

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.