Whose sale is it to report? — 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 some of what GadgetSphere sells is reported to the Inland Revenue Board by somebody else — a marketplace that issues the e-invoice for the order, a partner who bills the customer directly — and you need BigLedger to leave those sales alone without losing them. About ten minutes. The mechanism is one flag, and almost everything worth knowing about it is where it lives and when it is read.

Step 1 — Name the case this lesson exists for

After this step you will know when skipping is the right answer rather than a shortcut. There is a class of sale that is real revenue in your books and is not yours to report as an e-invoice, because another party reports it. If you report it too, the same sale reaches LHDN twice, from two suppliers, and untangling that afterwards means cancellations inside a seventy-two-hour window or credit notes. So the decision is not about tidiness. It is about not creating a second tax record for one transaction, and BigLedger gives you exactly one control for it.

Reference: E-Invoice Pools & Submission Routing — Frequently asked questions

Step 2 — Meet the flag that says “not mine to report”

After this step you will recognise Skip E-Invoice wherever it appears. It is a single true-or-false flag meaning this document does not enter e-invoicing at all. Not held back, not queued, not waiting for buyer details — excluded. You will meet it as a button on a pool row in the admin applet, where it removes a document from the pipeline after the fact, and as a tick box on master records, where it keeps documents out before they ever start. Those two are the same underlying flag and they behave identically once set. What differs is how much you accidentally catch with them.

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

Step 3 — Learn that it lives in three places, not one

After this step you will know why a document you never touched came out skipped. The flag exists on the document itself, on the branch the document was raised in, and on the customer it was raised for. A document is excluded if any one of the three says so. That is deliberate and it is what makes the feature useful: a marketplace fulfilment branch can be set once and every order through it is excluded, and a partner who bills your customers directly can be set once on their customer record. It also means two settings you did not make can decide your document.

Reference: Organization — Branch Details, Pick Pack, Extension and Marketplace

Step 4 — Know the exact moment it is decided

After this step you will stop expecting the flag to work retrospectively. The three are read together at the moment a document is finalised, and the answer is written onto the document. That is also the moment the e-invoice entry gate runs: it proceeds only if the company is enabled for e-invoicing, the document type is one e-invoicing covers, this flag is false, and no active queue row already exists for it. Fail any of those and the event is consumed. Nothing is written — no queue row, no pool row, and no error anywhere for you to find later.

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

Step 5 — Know what it does not change

After this step you will be able to answer the nervous question this always prompts. Skipping changes nothing about the sale. The revenue is booked, the stock moved, the moving average shifted, the cash or the receivable is exactly where it was, the tax on the document is unchanged and the customer’s statement is unaffected. The only columns the e-invoice applet ever writes on your document are this flag and the e-invoice reference fields. It reports your documents; it never posts them. A skipped sale is a normal sale that LHDN will hear about from somebody else.

Reference: My E-Invoice Admin Applet — 9. What this applet writes

How the steps fit together

    flowchart TD
  s1["Step 1 — Name the case this lesson exists for"]
  s2["Step 2 — Meet the flag that says 'not mine to report'"]
  s3["Step 3 — Learn that it lives in three places, not one"]
  s4["Step 4 — Know the exact moment it is decided"]
  s5["Step 5 — Know what it does not change"]
  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: Pick the level, and know what it costs · Back to the series · Play this as a presentation