Skip to content
Finalise: what the button starts, and what it writes · 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.

Finalise: what the button starts, and what it writes · presentation 2 of 5

One press, and a fan-out you did not configure

You can name the three filters that decide which background jobs a finalised document sets off…

The fan-out

Step 1 — Meet the processor whose only job is to start others

You will have the shape.

What this step names
  1. The journal
  2. The stock ledger line
  3. The cashbook line
  4. The e-invoice matching queues
  5. Membership points
  6. Coupons

Step 2 — Learn the first filter, because it is the one that matters

You will know why two tenants behave differently.

What this step names
  1. It is why one tenant's finalised invoice writes a journal and another's…
  2. It is not visible from the document screen
  3. From the applet settings
  4. From anything a user can open

Step 3 — Learn the two filters that come after it

You will stop mistaking the override for the switch.

What this step names
  1. It is an override on top of the subscription
  2. Not the thing that enables anything
  3. Measured across every tenant it is unset on every company but a…

Three levels down

Step 4 — Follow the chain down, because it does not stop at one hop

You will understand where costing comes from.

Where this step sits
    flowchart TD
  s1["1. Meet the processor whose only job…"]
  s2["2. Learn the first filter…"]
  s3["3. Learn the two filters that come…"]
  s4["4. Follow the chain down…"]
  s5["5. Accept that you cannot add a…"]
  s6["6. Know the one failure that silences…"]
  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 — Accept that you cannot add a link, and ask for the list

You will know the boundary and the workaround.

What you do
  1. Ask for it in writing and keep it…

Step 6 — Know the one failure that silences everything

You will recognise a symptom that looks impossible.

Where this step sits
    flowchart TD
  s1["1. Meet the processor whose only job…"]
  s2["2. Learn the first filter…"]
  s3["3. Learn the two filters that come…"]
  s4["4. Follow the chain down…"]
  s5["5. Accept that you cannot add a…"]
  s6["6. Know the one failure that silences…"]
  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 9

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.