Which pool a document lands in — 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 the books at GadgetSphere and you have just opened the three pools for the first time with intent. In about ten minutes you will be able to take any finalised sale and say, before you look anything up, which pool it is in and which of four facts put it there. You will also meet the sale that is in no pool at all, which is the one that costs the most to find late.

Step 1 — Name the four things that decide

After this step you can say what BigLedger reads the moment a sale is finalised. Four things, in this order. The document’s e-invoice submission type, which is Individual, Consolidated, Single General, or simply not set. The document type, because only a sales invoice and a cash bill are treated specially. The amount. And whether every field LHDN insists on is actually filled in. Those four decide between four destinations: straight to LHDN, or one of the three pools. None of it is negotiable and none of it happens while anyone is watching the screen, so by the time you are looking at a pool row, all four have already been read. The rest of this lesson walks one GadgetSphere sale down each route.

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

Step 2 — Follow a counter receipt into the Batch Pool

After this step you can explain why nearly every GadgetSphere receipt is in the Batch Pool, and why that is right. A counter sale is rung up as a point-of-sale cash bill, and during setup that document type was given the submission type Consolidated. Finalise one for under RM 10,000 and it goes to the Batch Pool with no check on the buyer at all, because a walk-in shopper genuinely has no tax number to check. Around 38,000 receipts a month land there across the 22 branches, and they wait for the monthly consolidation. So a Batch Pool holding tens of thousands of rows is not a backlog. It is a healthy retailer. Lesson four is about the handful of rows in it that are something else.

Reference: E-Invoice Pools & Submission Routing — Submission types

Step 3 — Follow a five-figure sale into the Individual Pool

After this step you can predict which sales are pulled out of the batch before anybody looks at them. A sales invoice or cash bill marked Consolidated whose total reaches RM 10,000 is diverted to the Individual Pool, and the reason is written on the row: amount transaction is greater or equal to RM10000. The line is inclusive, so exactly RM 10,000 is already over it, and GadgetSphere sees about 112 of these a month. Now the part that catches people at month-end. That divert covers those two document types and nothing else. A credit note, debit note, refund note or sales return of RM 10,000 or more that carries a Consolidated submission type is not diverted at all; it goes quietly into the Batch Pool. Check those yourself.

Reference: E-Invoice Pools & Submission Routing — The RM 10,000 rule

Step 4 — Follow a document that is simply incomplete

After this step you can say what incomplete means, in the system’s terms rather than yours. Before anything is sent, BigLedger builds the record LHDN will see and checks it. The header needs both parties’ name, tax number, identity type and identity value; your own industry classification code and business activity description; both addresses with a line one, a city and a state; both contact numbers, between eight and twenty characters; the e-invoice type, version, issue date and time, the currency and the three totals. Every line needs a classification code, an item name, a unit price, a tax type and a tax amount. Miss any one of them and the document is not sent. It is parked, with the reason attached, in the pool its submission type points at.

Reference: E-Invoice Validation Rules & Troubleshooting — Mandatory fields

Step 5 — Follow the two remaining routes

After this step you can finish the table in your head. A document marked Single General gets one attempt as an individual e-invoice using general buyer details, then falls back to consolidation. If it is complete it goes out individually. If it is incomplete and under RM 10,000 it waits in the Single General Pool. If it is incomplete and RM 10,000 or more it waits in the Individual Pool instead, because the threshold outranks everything else. And when the submission type was never set, BigLedger decides for you on the same two facts: complete goes out individually, incomplete under RM 10,000 goes to the Batch Pool, incomplete at RM 10,000 or more goes to the Individual Pool.

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

Step 6 — Look for the sale that went nowhere at all

After this step you know about the failure none of the three pools will show you. The entry gate only starts the pipeline if four things were true at the moment of finalising: the company’s e-invoice setting was enabled, the document type is one e-invoicing covers, the document was not marked Skip E-Invoice, and no active queue row already existed for it. If any of them failed, the event was dropped. No pool row, no queue row, no error message. A standing detection sweep now finds these and e-mails a digest. No e-invoice screen will ever show you one, because nothing reads that list — but the digest comes to you, and at month-end the Discrepancies Report shows the same document as a gap between your books and e-invoicing, which is where the rejections course goes to find them. Ask support to push it through, and enable e-invoicing on a company before anybody sells in it.

Reference: My E-Invoice Admin Applet — Troubleshooting

How the steps fit together

    flowchart TD
  s1["Step 1 — Name the four things that decide"]
  s2["Step 2 — Follow a counter receipt into the Batch Pool"]
  s3["Step 3 — Follow a five-figure sale into the Individual Pool"]
  s4["Step 4 — Follow a document that is simply incomplete"]
  s5["Step 5 — Follow the two remaining routes"]
  s6["Step 6 — Look for the sale that went nowhere at all"]
  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: Read a pool row before you touch it · Back to the series · Play this as a presentation