Red rows in the Batch Pool: what each status means and what actually clears them · presentation 4 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.

Red rows in the Batch Pool: what each status means and what actually clears them · presentation 4 of 4

Getting a stranded Batch Pool row back, and the four things that will not do it

You can recover a processed Batch Pool row using the only route that exists, say how we know nothing else resets one…

What does not exist

Step 1 — Accept that there is no reset, and know how that was established

You will stop looking for an undo.

Where this step sits

    flowchart TD
  s1["1. Accept that there is no reset…"]
  s2["2. Use the round trip…"]
  s3["3. Expect the new row to be…"]
  s4["4. Rule out the two alternatives that…"]
  s5["5. Rule out the other two…"]
  s6["6. Recognise the rows no route will…"]
  s7["7. Check the work a week later"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s1 here;

The route

Step 2 — Use the round trip, which is the route that works

You will have the recovery in two clicks.

Select the stranded rows and press **Move to Individual**
Open the Individual Pool, select the same rows, and press **Move To Batch Pool**

Screen capture pending the demo tenant

The Individual Pool listing with rows selected and the Move To Batch Pool button above the grid

Step 3 — Expect the new row to be red, and check its date

Nothing about the result will alarm you.

What you do

Finish the job by selecting it and pressing Consolidate

What will not work

Step 4 — Rule out the two alternatives that sound most plausible

You will not waste a cycle.

What this step names

Nothing ages a pool row
Nothing alerts on one
The recovery processors that could move rows between pools are switched on…
The fifth cannot be put on a timetable at all

Step 5 — Rule out the other two, including the one support would reach for

You will know why an obvious request gets a strange answer.

Where this step sits

    flowchart TD
  s1["1. Accept that there is no reset…"]
  s2["2. Use the round trip…"]
  s3["3. Expect the new row to be…"]
  s4["4. Rule out the two alternatives that…"]
  s5["5. Rule out the other two…"]
  s6["6. Recognise the rows no route will…"]
  s7["7. Check the work a week later"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Recognise the rows no route will help

You will stop trying on a small, stubborn group.

What this step names

The automatic run asks for six sales document types — invoice
Cash bill
Credit note
Debit note
Refund note
Return

Knowing you are done

Step 7 — Check the work a week later

You will know when to stop.

Valid

Then finding that e-invoice and confirming it reads Valid

NarrationSlide 1 of 12

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.