Prove it at month end — 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 you run GadgetSphere’s month-end e-invoice review and your deliberately skipped sales keep appearing on the list of things that went wrong. They are not wrong. The report shows them twice on purpose, in two places that mean different things, and reading them in the right order turns a forty-minute investigation into a two-minute check. About eleven minutes.

Step 1 — Read the skipped bucket before the discrepancy

After this step you will have the correct order of operations. The monthly report has four tabs. The one called the ERP transaction summary is your own books, and it carries a line totalling documents marked Skip E-Invoice. Read that line first, every month, before you look at any gap. It is the answer to “how much did we deliberately not report”, and until you know that number nothing else on the report can be interpreted. If it matches what you expect, the rest of the review is about genuine problems. If it does not, stop there.

Reference: My E-Invoice Admin Applet — 8. Monthly Report → Discrepancies Report

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

After this step you will stop treating a number as an alarm. The discrepancy tab asks a simple question: which finalised documents have no e-invoice record behind them? A skipped document has no e-invoice header and no link row, so it answers yes and appears as missing. The skipped total on the other tab is not subtracted from it. So a month in which you skipped two hundred marketplace orders shows two hundred documents missing from e-invoicing, all of which you meant. Both numbers are correct; they are answering different questions, and only one of them is a problem.

Reference: E-Invoice Submission Mechanics — The discrepancy report: what “missing” means

Step 3 — Explain the gap in one sentence per bucket

After this step you will have a reconciliation somebody else can check. Write the month down as a subtraction. The discrepancy total is your starting figure. Take off the skipped documents you intended. What remains is the real gap, and every ringgit of it belongs to one of a small set of named causes — documents still sitting in a pool, batch rows that failed and will not be swept, sales voided after their e-invoice went out, and documents dropped at the gate. Name each one with its amount. A reconciliation that ends in a single unexplained figure is not finished.

Reference: The Month-End E-Invoice Cycle (1st to 7th) — Step 7: Reconcile, and understand the five reasons a tally does not balance

Step 4 — Know which documents the report never looks at

After this step you will know a blind spot that no tab announces. A document only reaches the books side of this report if it is finalised, not deleted, dated inside the range, and in the company’s own currency. That last condition is the quiet one. GadgetSphere Distribution’s purchases in United States dollars from a Singapore distributor are simply not examined, whatever state their e-invoicing is in. They are neither counted as present nor reported as missing. If your foreign-currency trade matters, it needs a separate check, because this report will never mention it.

Reference: E-Invoice Submission Mechanics — The discrepancy report: what “missing” means

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

After this step you will not spend a day chasing a difference that has a one-line cause. This report compares your documents against BigLedger’s e-invoice records. It does not ask LHDN what it is holding. So anything reported to LHDN by some other route — an invoice keyed straight into the MyInvois portal, or submitted by another system in the group — is invisible here and perfectly visible there. A count on the LHDN dashboard that is higher than this report’s is the signature of exactly that, and the place to look is outside BigLedger.

Reference: My E-Invoice Admin Applet — 8. Monthly Report → Discrepancies Report

How the steps fit together

    flowchart TD
  s1["Step 1 — Read the skipped bucket before the discrepancy"]
  s2["Step 2 — Expect every skipped sale on the missing list as well"]
  s3["Step 3 — Explain the gap in one sentence per bucket"]
  s4["Step 4 — Know which documents the report never looks at"]
  s5["Step 5 — Expect LHDN's own dashboard to disagree, and know why"]
  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: How far the e-commerce reconciliation actually goes · Back to the series · Play this as a presentation