Skip to content
Taking it back: void, undo and discard · 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.

Taking it back: void, undo and discard · presentation 3 of 4

Can your tenant unpost what it posts?

You can prove, with one test document and thirty seconds, whether your own tenant reverses everything it posts — and read a half-finished void…

Your list, not the platform's

Step 1 — Know that the void list is a subscription, not a code path

You will stop assuming the manual applies to you.

What this step names
  1. The platform registry offers ten: the journal
  2. The tax
  3. The stock ledger
  4. The cash book
  5. The knock-off queue
  6. The contra

Step 2 — Know that posting and unposting are two separate subscriptions

You will know the question worth asking.

What this step names
  1. For stock it is about one in five
  2. For the cash book about one in eight
  3. For loyalty points it is close to half

The thirty-second check

Step 3 — Read the Posting tab, because a document has more than one status

You will have a routine you can run on any document.

  • Open the document, open its Posting tab, and read the columns
Screen capture pending the demo tenant

The Posting tab of a voided sales invoice, showing journal, inventory, cash book and tax statuses side by side

Step 4 — Separate a job that failed from a job that never existed

You will stop treating two different problems as one.

What this step names
  1. The Posting tab cannot tell them apart
  2. Trace Document can: a job that failed leaves a record with a…
  3. A job that was never queued leaves nothing at all

Step 5 — Know why nothing retries the failure for you

You will stop waiting for a recovery that is not coming.

Where this step sits
    flowchart TD
  s1["1. Know that the void list is…"]
  s2["2. Know that posting and unposting are…"]
  s3["3. Read the Posting tab…"]
  s4["4. Separate a job that failed from…"]
  s5["5. Know why nothing retries the failure…"]
  s6["6. Prove it once, with a test…"]
  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 — Prove it once, with a test document

You will have the answer for good rather than for today.

What you do
  1. Key a small document in a quiet company, finalise it, wait for the chain…

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.