The question the Discrepancies Report can answer, and the one it cannot — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This presentation is for whoever runs the books for a group — GadgetSphere’s three companies in one tenant — and has been told to “run the discrepancies report” at month end without being told what it proves. In about nine minutes you will know what the screen compares, when it read the numbers it shows you, and the one question it cannot answer on its own.

Step 1 — Start with the question the screen actually answers

After this step you will stop reading the report as a statement from the tax authority. The Discrepancies Report compares two things that both live inside BigLedger: the documents you finalised in a period, and the e-invoice records BigLedger created for them. It never asks LHDN anything. So the question it answers is “does every document I finalised have an e-invoice record?” — and that is a narrower question than “did everything reach LHDN”. A record can exist and still be sitting in a queue, still be waiting for LHDN’s answer, or have been rejected. Keep the two questions apart from the first minute, because the rest of this series is about the gap between them, and the report’s own labels will not hold it open for you.

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

Step 2 — Understand that Create takes a photograph

After this step you will know why the figures never change under you. Create asks for one company and a start and end day, writes a report header marked processing, and then builds the whole report inside that same call — so by the time the listing refreshes, the row already reads processed, or failed. Nothing ever recomputes it. If you fix a stuck receipt on the third and open the report you created on the second, it still shows the receipt missing; you create a new report and read that one. Two consequences follow. A row that stays at processing is dead — no job will ever finish it — so delete it and create again. And a failed row keeps its reason in a place no screen shows, so failed means “try again, and if it fails twice, raise it”.

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

Step 3 — Read the four tabs as two ledgers and a difference

After this step each tab will have a job. Main is the header: which company, which days, what state. The ERP Transaction Summary is your side of the ledger — the finalised documents, totalled by type, with a separate line for documents you marked Skip E-Invoice. The IRB Audit Summary is the e-invoice side — the records BigLedger holds for the period, totalled by document type, with a cancelled figure beside each. Document versus E-Invoice Discrepancy is the difference, in both directions: documents with no record, and records with no document. Every line on the last tab opens into the documents behind it, and that list is the one frozen when you pressed Create, even though the documents themselves open live.

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

Step 4 — Create one per company, after the environment check

After this step you will know how many reports a group needs and what comes before them. The report is a company-level fact: the company is mandatory, and a report cannot span two. GadgetSphere therefore creates three each month — retail, online, distribution — from the same screen, because the admin applet is one screen over the whole tenant. Before any of the three, read each company’s LHDN environment and e-invoice status on its company record. A company left pointing at the sandbox produces a report that balances perfectly against records LHDN’s production system has never seen, and the report has no way to tell you that. Environment first, then three reports, in that order every month.

Reference: My E-Invoice Admin Applet — Which level each e-invoice fact lives on — tenant, company, branch

Step 5 — Do not wait for the e-mail

After this step nobody in your team will be waiting for a message that does not come. The platform contains a second job that would, once a month, build last month’s report for every enabled company and e-mail a notice to an address in the application settings. That job cannot be put on a timetable — its code is missing from the list the scheduler is allowed to run — and across every production tenant it has never run once: not one report was created by the account it would sign as, and no tenant holds the e-mail setting. So the report exists only when a person presses Create. Put it in the month-end checklist between the first and the seventh, while a wrong consolidated e-invoice can still be cancelled, and treat it as a screen you visit.

Reference: Reports — The monthly rhythm these reports support

Step 6 — Prove it on your own screen in thirty seconds

After this step you will have created a report and read a clean one. Open Monthly Report, Discrepancies Report, Create. Choose the retail company; the dates default to the current month, so set them to the first and last day of last month, and press Create. Come back to the listing: the row is already processed. Open it and go straight to the last tab. A closed month reads zero in both directions, or every non-zero line is one you can name — the four corporate invoices still waiting for a tax number, the twenty voided receipts you skipped. If you can name every line, the report is working. Whether the month has also reached LHDN is the question the next three presentations answer.

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

How the steps fit together

    flowchart TD
  s1["Step 1 — Start with the question the screen actually answers"]
  s2["Step 2 — Understand that Create takes a photograph"]
  s3["Step 3 — Read the four tabs as two ledgers and a difference"]
  s4["Step 4 — Create one per company, after the environment check"]
  s5["Step 5 — Do not wait for the e-mail"]
  s6["Step 6 — Prove it on your own screen in thirty seconds"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

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: Where every number on the report comes from, and when it was read · Back to the series · Play this as a presentation