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 e-invoiced to the Inland Revenue Board (LHDN) 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. Skip E-Invoice is for a sale that is real revenue in your books but must not be e-invoiced by you, because somebody else issues the e-invoice for it instead. Whether a particular marketplace or partner really does that for your orders is a fact to get from them, and to confirm with whoever handles your tax, before you set anything — this lesson cannot settle it for you. The reason it matters: if you both issue one, two e-invoices exist for one sale, and one of them has to be cancelled or reversed with a credit note. BigLedger gives you exactly one control for it.
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. Both set the same flag on the document, with one difference you will meet in lesson three: a flag that is already true when the document is finalised also puts it on a register of skipped sales, and a pool-row skip, which comes after finalising, does not. What differs most 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 gate consumes the event. It writes no queue row, no pool row, and no error anywhere for you to find later.
Reference: My E-Invoice Admin Applet — 1. Entry gate (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.
Answer key
- Because the same sale would become two tax records, and unpicking that needs a cancellation or a credit note — E-Invoice Pools: What You Can Do in Each Pool, and the Questions That Come Up Most — Frequently asked questions
- On the document, on the branch and on the customer — any one of the three excludes it — Organization — Branch Details, Pick Pack, Extension and Marketplace
- At the moment the document is finalised, and the answer is written onto the document — My E-Invoice Admin Applet — 1. Entry gate (at FINAL)
- Nothing — the ledger, the stock, the costing and the receivable are untouched — My E-Invoice Admin Applet — 9. What this applet writes
Next: Pick the level, and know what it costs · Back to the series · Play this as a presentation