Skip to content
Sales you skip because a platform e-invoices them · presentation 4 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.

Sales you skip because a platform e-invoices them · presentation 4 of 5

Prove it at month end

You can take GadgetSphere's skipped sales through a month-end review without them looking like a failure: read the skipped total before the discrepancy…

Step 1 — Read the skipped bucket before the discrepancy

You will have the correct order of operations.

  • Read that line first, every month, before you look at any gap
Screen capture pending the demo tenant

The Discrepancies Report on the ERP Transaction Summary tab, with the Skip Einvoice Documents line visible among the totals

Step 2 — Expect every skipped sale on the missing list as well

You will stop treating a number as an alarm.

Where this step sits
    flowchart TD
  s1["1. Read the skipped bucket before the…"]
  s2["2. Expect every skipped sale on the…"]
  s3["3. Explain the gap in one sentence…"]
  s4["4. Know which documents the report never…"]
  s5["5. Expect LHDN's own dashboard to disagree…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — Explain the gap in one sentence per bucket

You will have a reconciliation somebody else can check.

What you do
  1. Write the month down as a subtraction
  2. Take off the skipped documents you intended

Step 4 — Know which documents the report never looks at

You will know a blind spot that no tab announces.

What this step names
  1. A document only reaches the books side of this report if it…
  2. Not deleted
  3. Dated inside the range
  4. In the company's own currency

Step 5 — Expect LHDN's own dashboard to disagree, and know why

You will not spend a day chasing a difference that has a one-line cause.

Where this step sits
    flowchart TD
  s1["1. Read the skipped bucket before the…"]
  s2["2. Expect every skipped sale on the…"]
  s3["3. Explain the gap in one sentence…"]
  s4["4. Know which documents the report never…"]
  s5["5. Expect LHDN's own dashboard to disagree…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

NarrationSlide 1 of 6

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.