Skip to content
Learn
Presentations P-00000 to P-00999
Which LHDN your new company is actually talking to

Which LHDN your new company is actually talking to

Set up MyInvois and Peppol for a new company · presentation 1 of 4 · 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.

Set up MyInvois and Peppol for a new company · presentation 1 of 4

Which LHDN your new company is actually talking to

You can say which of LHDN's two systems a company's e-invoices are going to, why a blank field sends them to the wrong one…

The field nobody mentions

Step 1 — Find the field that decides the destination

You will know where the decision is made.

Screen capture pending the demo tenant

The company E-Invoice tab with the LHDN Environment drop-down showing sandbox and production

Step 2 — Understand what a blank field means

You will treat an empty drop-down as a decision rather than an absence.

Where this step sits
    flowchart TD
  s1["1. Find the field that decides the…"]
  s2["2. Understand what a blank field means"]
  s3["3. See why the mistake survives your…"]
  s4["4. Learn how the token is made…"]
  s5["5. Tell the two failure messages apart"]
  s6["6. Put the environment before the switch"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — See why the mistake survives your own checks

You will know why this one is worth being careful about rather than merely correct about.

Valid

Your e-invoice goes to Valid

Who LHDN thinks is sending

Step 4 — Learn how the token is made, and why the TIN matters more than you thought

The intermediary arrangement will stop being a black box.

Where this step sits
    flowchart TD
  s1["1. Find the field that decides the…"]
  s2["2. Understand what a blank field means"]
  s3["3. See why the mistake survives your…"]
  s4["4. Learn how the token is made…"]
  s5["5. Tell the two failure messages apart"]
  s6["6. Put the environment before the switch"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Tell the two failure messages apart

You will save a day of the wrong diagnosis.

Where this step sits
    flowchart TD
  s1["1. Find the field that decides the…"]
  s2["2. Understand what a blank field means"]
  s3["3. See why the mistake survives your…"]
  s4["4. Learn how the token is made…"]
  s5["5. Tell the two failure messages apart"]
  s6["6. Put the environment before the switch"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

The order that saves the rework

Step 6 — Put the environment before the switch

You have a rule that costs nothing and prevents a re-submission.

  • Set the LHDN Environment to production, save…

Valid

…confirm it says production before you congratulate yourself on a Valid e-invoice

NarrationSlide 1 of 10

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.

Last updated on
Voiding a foreign-currency document, and reading the residue it leaves — transcriptWhich LHDN your new company is actually talking to — transcript