Skip to content
Run the month-end e-invoice cycle · 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.

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

Fix a rejection

You can tell a document BigLedger held back from one LHDN rejected, read the error on either, fix the cause on the customer record…

Whose rejection is it

Step 1 — Tell BigLedger's rejection from LHDN's

You can say, from the status alone, whose check a document failed and therefore what kind of fix it needs.

Invalid

…document that passed BigLedger's check and was sent can come back Invalid

Step 2 — Recognise a failure to send

You will not mistake a transmission failure for a rejection.

  • Open the row in Internal Submission, then Individual Submission, and read the request error

Invalid

An Invalid row is LHDN's

Read the error

Step 3 — Build the Invalid list from the right screen

You have the complete list of last month's rejections in front of you.

  • Go to Internal Submission, then To IRB E-Invoice, filter to last month…
Screen capture pending the demo tenant

Internal Submission → To IRB E-Invoice filtered to last month and sorted on status, with an Invalid row opened to its validation error and the LHDN error code visible

Step 4 — Read a buyer identity error

You can read the two commonest LHDN codes and name the fix.

What this step names
  1. Every e-invoice carries the buyer's tax identification number
  2. Their TIN
  3. Plus an identity document type
  4. Its value

Step 5 — Read the other codes you will meet

You can work one more code properly and you know where the rest are written down.

What you do
  1. Read them there when one turns up, rather than memorising them now

Fix it and prove it

Step 6 — Fix it where it lives

You will fix the record that was actually sent, once, instead of the e-invoice, repeatedly.

  • Fill the block completely or empty every field of it

22 branches

…one bad state or missing city fails all 22 branches at once

Step 7 — Resubmit and watch it to Valid

The document is back at LHDN and you know what proves it.

  • Go back to the row, in the pool or on To IRB E-Invoice…
  • Watch the row to Valid, not Submitted, which only means LHDN is still deciding
Screen capture pending the demo tenant

An Invalid row on To IRB E-Invoice opened on its Account tab, the corrected buyer fields, and the Save and Resubmit button

NarrationSlide 1 of 11

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.