Run the month-end e-invoice cycle · presentation 1 of 5 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Run the month-end e-invoice cycle · presentation 1 of 5

What LHDN expects each month

You can say what must be validated at MyInvois by the 7th, what a consolidated e-invoice is…

What LHDN asks of you

Step 1 — Recognise what an e-invoice is

An e-invoice is the tax record of a sale, in the form the Inland Revenue Board of Malaysia, LHDN, asks for.

Valid

Where LHDN checks it and answers Valid or Invalid

Step 2 — Name the deadline

You can say the one date the whole cycle turns on.

the 7th

And those must be validated by the 7th of the following month

Step 3 — Describe a consolidated e-invoice

You can explain a consolidated e-invoice in one breath.

the 7th

…small set of documents a person can actually check before the 7th

Which sales go which way

Step 4 — Pick out the sales that are consolidated

You can look at a GadgetSphere sale and say whether it will be consolidated.

RM 10,000

A walk-in sale under RM 10,000 where the buyer did not give…

Step 5 — Pick out the sales that go out on their own

You can name the exceptions.

RM 10,000

…or cash bill of RM 10,000 or more must be reported individually

Where a sale waits, and what waiting costs

Step 6 — Know where a sale waits

You can tell a pool that empties itself from one that waits for you.

Screen capture pending the demo tenant

The Individual Pool listing in the My E-Invoice Admin Applet, one row per document that is waiting for you, with the missing fields named in its Validation Error panel

Step 7 — Understand what a late receipt costs you

You know what happens, inside BigLedger, to a sale that misses its month.

72 hours

It has nothing to do with the 72 hours

Step 8 — Know what the rules require, as opposed to what BigLedger does

Everything so far has been BigLedger.

Where this step sits

    flowchart TD
  s1["1. Recognise what an e-invoice is"]
  s2["2. Name the deadline"]
  s3["3. Describe a consolidated e-invoice"]
  s4["4. Pick out the sales that are…"]
  s5["5. Pick out the sales that go…"]
  s6["6. Know where a sale waits"]
  s7["7. Understand what a late receipt costs…"]
  s8["8. Know what the rules require…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  s6 --> s7
  s7 --> s8
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s8 here;

NarrationSlide 1 of 12

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.