Skip to content
Work the pools until nothing is stuck · presentation 6 of 6 · 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.

Work the pools until nothing is stuck · presentation 6 of 6

What runs for you, and how you know

You can name the work around the pools that BigLedger does without being asked, say which e-mail or screen tells you it ran…

Step 1 — Name what genuinely runs without you

You can list the work you are not doing by hand.

Valid

…processor polls LHDN and writes Valid or Invalid back onto each record

Step 2 — Find out which of them are switched on for you

You will know what to ask, and who to ask.

What you do
  1. Open each company's E-Invoice tab and read the three switches that are yours rather…

Step 3 — Let the Individual Pool come to you

You have a way of hearing about failed individual-pool rows without opening the pool.

Where this step sits
    flowchart TD
  s1["1. Name what genuinely runs without you"]
  s2["2. Find out which of them are…"]
  s3["3. Let the Individual Pool come to…"]
  s4["4. Let the documents that never started…"]
  s5["5. Have last month's proof generated for…"]
  s6["6. Name the three things that are…"]
  s7["7. Run the thirty-second round that covers…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — Let the documents that never started come to you too

You know where the hardest failure announces itself.

What this step names
  1. A standing detection sweep looks for exactly this shape
  2. Finalised documents that e-invoicing should have picked up and did not
  3. Records each one
  4. E-mails a digest when it confirms one

Step 5 — Have last month's proof generated for you

Your month-end reconciliation can start with a report you did not have to build.

Where this step sits
    flowchart TD
  s1["1. Name what genuinely runs without you"]
  s2["2. Find out which of them are…"]
  s3["3. Let the Individual Pool come to…"]
  s4["4. Let the documents that never started…"]
  s5["5. Have last month's proof generated for…"]
  s6["6. Name the three things that are…"]
  s7["7. Run the thirty-second round that covers…"]
  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 — Name the three things that are not automatic

You will stop waiting for things that are never coming.

What this step names
  1. First
  2. Nothing ages a pool row
  3. Nothing recovers one

Step 7 — Run the thirty-second round that covers the gap

You have the routine that sits exactly where the automation stops.

What this step names
  1. Batch Pool
  2. Filtered to this month: rows unprocessed
  3. No processed-but-failed rows hiding underneath them

NarrationSlide 1 of 8

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.