What happens behind the scene when you skip — 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 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 submission pipeline never knew about it.

Reference: My E-Invoice Admin Applet — 1. Entry gate (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 nothing schedules it for you, so unless somebody at BigLedger has scheduled it on your tenant 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 that is easy to miss. Skipping a sales document does not leave it with no record anywhere. A second job runs off the same finalisation — not a schedule, provided your tenant subscribes it — and checks 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 already skipped. Every one of those is written into the sales-document matching queue, under Reconciliation, Sales in the admin applet, and that list builds itself. Two things it will not hold: a sale you skip later from a pool row, because that job runs only at finalising; and anything at all if the job is not subscribed, so an empty list while you know you have skipped sales is a question for support.

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 mistake this feature invites. 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 that hangs off validation never happens for it. 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 to print, and a portal search finds nothing to request against, because the portal looks only in the pools and the e-invoice records. One thing does not stop, and it is the surprise: Peppol. Its waiting queue is filled at finalising from the company’s own Peppol switch without asking about e-invoicing, so in a company with Peppol on, a skipped sale can still be queued for Peppol delivery. The rest is correct, and all of it will be reported to you as a fault.

Reference: My Peppol Admin Applet — The two routes into the Waiting Queue

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.

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