What one receipt at your counter sets off — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This lesson is for you if you run one of GadgetSphere’s shops and somebody at head office has started asking you about e-invoices. You are not going to work the pools in this lesson, or press anything in an applet you probably cannot open. In about nine minutes you will know what your counter actually starts, what happens to it after it leaves your shop, and which part of the month is genuinely yours.

Step 1 — Know the one moment that matters

After this step you will know why nobody at your branch decides anything about e-invoicing. A cash bill in progress at the counter does nothing at all. It touches no ledger, no stock figure and no tax authority. Everything happens at one instant: Final. In that instant BigLedger posts the sale to the journal, moves the stock and recomputes the item’s moving average, records the money against the settlement method’s cashbook, updates the customer’s balance or their loyalty points, and starts the e-invoice pipeline. Nine consequences from one keystroke, and only one of them is on the screen the cashier is looking at. The e-invoice strand is the one this series follows, and it is the one that leaves your shop.

Reference: Core Concepts — 1. FINAL is the only moment that matters

Step 2 — Watch the receipt choose its route

After this step you can predict where any of your receipts goes without asking anyone. The instant a bill is final, BigLedger reads four things about it: the e-invoice submission type written on it, the document type, the amount, and whether every field the Inland Revenue Board, LHDN, insists on is filled in. Those four decide between four destinations. Straight to LHDN as its own e-invoice, or into one of three holding pools. Your ordinary counter receipts were given the submission type Consolidated during setup, so a bill under RM 10,000 with no buyer details goes into the Batch Pool, with no check on the customer at all. That is the route almost every sale in your shop takes.

Reference: E-Invoice Pools & Submission Routing — Where does a finalised document go?

Step 3 — Stop reading the Batch Pool as a backlog

After this step you will not be alarmed by a very large number. The Batch Pool at GadgetSphere holds something like 38,000 rows on the 2nd of the month, across all 22 branches, and that is not a queue of failures. It is a month of ordinary walk-in sales waiting to be reported together. A walk-in shopper genuinely has no tax number to give, which is exactly the case consolidated reporting exists for. The pool you should worry about is the other one. A Batch Pool full of receipts is a healthy retailer; an Individual Pool full of receipts is revenue nobody has reported yet, because every row in it is a sale that was meant to go to LHDN on its own and could not.

Reference: Pools and queues — What it is not

Step 4 — Learn the shape of the month

After this step you will know when your part ends. LHDN requires last month’s consolidated e-invoice to be validated by the 7th of this month. BigLedger runs the consolidation and the submission for your company on a schedule set a few days before that, deliberately, so there is time to fix whatever comes back rejected. Nobody at your branch presses it and nobody at head office normally does either. What that means for you is simple and easy to get wrong: your window closes before the 1st, not on the 7th. A receipt that still needs something from a customer has to be dealt with while the month is open. The last lesson in this series is about that week.

Reference: E-Invoice Pools & Submission Routing — The monthly consolidation cycle

Step 5 — Understand that the run drips rather than sweeps

After this step a half-emptied pool will not look like a failure. The automatic consolidation does not take the whole month in one pass. It takes at most a hundred unprocessed rows of a sales document type each time it fires, builds consolidated e-invoices from those, marks them processed and stops. It then fires again, through the day, until the month is gone. So on any given morning during the run you will see part of the month consolidated and part of it still waiting, and both are correct. If somebody tells you the pool is clearing slowly, the honest answer is that it clears a hundred at a time. What you watch is not the speed but whether anything is left behind at the end.

Reference: My E-Invoice Admin Applet — 3. Pools — what the buttons do

Step 6 — Know what you can see and what you cannot touch

After this step you will stop looking for screens you do not have. From your shop, on any finalised bill, the E-Invoice tab shows Progress: four stages, re-read every three seconds, telling you whether the sale is still being routed, waiting in the Batch Pool, queued for LHDN, or already sent. That is your window. Everything that acts on a pooled sale — completing the buyer’s details, moving a row between pools, consolidating, skipping — happens in the My E-Invoice Admin applet, which the finance desk runs. So your job is not to fix pool rows. It is to make sure the sale never needed fixing, and to say clearly which sale needs a person when one does.

Reference: POS General — The E-Invoice tab on a cash bill

How the steps fit together

    flowchart TD
  s1["Step 1 — Know the one moment that matters"]
  s2["Step 2 — Watch the receipt choose its route"]
  s3["Step 3 — Stop reading the Batch Pool as a backlog"]
  s4["Step 4 — Learn the shape of the month"]
  s5["Step 5 — Understand that the run drips rather than sweeps"]
  s6["Step 6 — Know what you can see and what you cannot touch"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Next: Why that sale went into the monthly batch · Back to the series · Play this as a presentation