Red rows in the Batch Pool: what each status means and what actually clears them

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can read a Batch Pool row the way the consolidation run reads it, say why a healthy pool is full of red, find the rows the automatic run can no longer see and clear them yourself, avoid the one button that turns a waiting row into a stuck one, and recover a stuck row by the only route that exists.

Before this series: Run the month-end e-invoice cycle

Presentations

1. Three status columns on a Batch Pool row, and only one of them decides anything — about 10 minutes, narrated
2. The one month the consolidation run can see, and the months it cannot — about 12 minutes, narrated
3. The button that strands a row, and the guard that is only on its neighbour — about 11 minutes, narrated
4. Getting a stranded Batch Pool row back, and the four things that will not do it — about 12 minutes, narrated

Modules this series draws on

• E-Invoice & PEPPOL Module
• Financial Accounting Module
• Sales Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• My E-Invoice Admin Applet
• The Month-End E-Invoice Cycle (1st to 7th)
• E-Invoice Pools & Submission Routing
• Pools and queues

All presentations · Presentations for the whole-system operator