What happens behind the scene when you skip — transcript

Presentation 3 of 5 in Sales you skip because a platform e-invoices them · about 11 minutes · for the whole-system operator — you run the books.

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 want to know what BigLedger does with a skipped GadgetSphere sale, rather than what the screen implies. About eleven minutes. The short version is that most of the machinery does nothing at all, one part of it does something you have probably never looked at, and the consequences of that combination are the whole of this lesson.

Step 1 — Watch the entry gate consume the event

After this step you will know why there is nothing to find. Finalising a sales document raises an event, and a trigger picks it up and decides whether e-invoicing applies. It proceeds only if the company is enabled for e-invoicing, the document type is one e-invoicing covers, the skip flag is false, and no active queue row exists already. If any of those fails — and a skip fails the third — the event is consumed. No posting-queue row is created. No pool row is created. No error is raised and nothing is logged for you. The document is finalised and the e-invoice pipeline never knew about it.

Reference: My E-Invoice Admin Applet — 1. Entry gate (trigger processor, at FINAL)

Step 2 — Know that a skip and a ghost look identical from a pool

After this step you will stop trying to tell them apart on the wrong screen. A document dropped because it was skipped and a document dropped because the company was not yet enabled for e-invoicing leave exactly the same trace, which is none. Both are finalised, in no pool and in no queue. There is a detection sweep for the accidental kind, but measured across every production tenant it is scheduled on none of them, so it does not run and no digest arrives. Do not wait for one. The place the two become distinguishable is the monthly report, where deliberate skips are totalled separately.

Reference: My E-Invoice Admin Applet — Troubleshooting

Step 3 — Know where a skipped sale is actually registered

After this step you will know about a screen almost nobody opens. Skipping a sales document does not leave it with no record anywhere. A second processor watches for exactly the opposite condition to the gate: a document that is finalised, belongs to a company enabled for e-invoicing, is a sales document type, and is skipped. Every one of those is written into the sales-document matching queue, which sits under Reconciliation, Sales in the admin applet. So the list of sales you chose not to report is a real list, it builds itself, and it is the only register of them you have.

Screen: Reconciliation (Sales) → SD Matching Q. listing, showing skipped sales documents with their reference number, date and amount

Reference: My E-Invoice Admin Applet — 7. Incoming e-invoices and reconciliation

Step 4 — Know that the flag never reaches backwards

After this step you will avoid the commonest mistake with this feature. The three flags are read once, when a document is finalised. Ticking Skip E-Invoice on a branch today does nothing whatever to the documents that branch finalised yesterday; they already have their answer and they are already in pools or already submitted. The same is true in the other direction — clearing a flag does not pull last month’s documents back into the pipeline. When configuration was wrong for a period, treat the documents from that period as a separate clean-up job with its own recovery route.

Reference: Organization — Recovering documents finalised before the configuration was right

Step 5 — Know what else quietly stops happening

After this step you will have the full blast radius in your head. A skipped document never becomes a validated e-invoice, so everything downstream of a validated e-invoice never happens for it either. It is never picked up for Peppol delivery, because that queue takes validated e-invoices. It never produces a validated PDF, so no e-mail with one goes to the buyer. It has no LHDN identifier and no QR code, so a buyer scanning a QR on a printed copy finds nothing, and a portal search finds nothing to request against. All of that is correct, and all of it will be reported to you as a fault.

Reference: My E-Invoice Admin Applet — Where it fits

How the steps fit together

    flowchart TD
  s1["Step 1 — Watch the entry gate consume the event"]
  s2["Step 2 — Know that a skip and a ghost look identical from a pool"]
  s3["Step 3 — Know where a skipped sale is actually registered"]
  s4["Step 4 — Know that the flag never reaches backwards"]
  s5["Step 5 — Know what else quietly stops happening"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5

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.

1. What is written when a skipped document is finalised? A pool row with a validation message naming the flag
A posting-queue row that is later discarded
Nothing — the event is consumed, with no queue row, no pool row and no error

2. How do you tell a deliberate skip from a document dropped because the company was not enabled? By the validation error on the pool row
On the monthly report, where skipped documents are totalled separately
By the digest the ghost-detection sweep e-mails you

3. Where does a skipped sales document get registered? In the sales-document matching queue under Reconciliation, Sales
In the Batch Pool, marked as skipped
Nowhere — a skipped document leaves no record at all

4. You tick Skip E-Invoice on a branch today. What happens to yesterday's documents from that branch? Nothing — the flag is read once, at the moment each document is finalised
They are removed from their pools overnight
They are cancelled at LHDN if already submitted

5. A buyer scans the QR code on a printed copy of a skipped sale and gets nothing. Why? The QR code expired
The document never became a validated e-invoice, so there is no LHDN record behind the code
The buyer must sign in before scanning

Answer key

Nothing — the event is consumed, with no queue row, no pool row and no error — My E-Invoice Admin Applet — 1. Entry gate (trigger processor, at FINAL)
On the monthly report, where skipped documents are totalled separately — My E-Invoice Admin Applet — Troubleshooting
In the sales-document matching queue under Reconciliation, Sales — My E-Invoice Admin Applet — 7. Incoming e-invoices and reconciliation
Nothing — the flag is read once, at the moment each document is finalised — My E-Invoice Admin Applet — 1. Entry gate (trigger processor, at FINAL)
The document never became a validated e-invoice, so there is no LHDN record behind the code — My E-Invoice Admin Applet — Where it fits

This is a self-check. Your answers are marked in your browser and stay there — nothing is sent anywhere, nothing is recorded, and the marking is readable in the page source, so it is not a credential. Open the answer key at any time.

Next: Prove it at month end · Back to the series · Play this as a presentation

Last updated on September 17, 2026

What happens behind the scene when you skip Prove it at month end