MyInvois rejected your e-Invoice? Check this one thing first
You would expect a rejection to come from something complex. A missing field. A wrong classification code. A format error deep in the system.
The common cause is small
In the submissions that we support, the most common cause is much smaller. It is an old or incorrect Tax Identification Number (TIN) in a customer or supplier record. Somebody saved the number years ago. Nobody updated it since.
MyInvois checks each TIN when it validates an e-Invoice. A TIN that does not match the buyer fails the validation. The e-Invoice is rejected. The cause is not fraud. The cause is not a technical fault. The cause is a record that was correct once and is now stale.
Why this matters now
This kind of data error has always existed. Under the old system, an invoice with an old TIN still went out. Nobody checked it. Under e-Invoice, the same error now has a consequence. The document does not validate. The sale is not recorded with LHDN. Your team spends time on a correction instead of on the next sale.
What to do
Ask one question: when did somebody last check the TIN records for your customers and suppliers? “Entered once and never checked” is the usual answer. A short data check before the next batch of e-Invoices removes most rejections before they happen. MyInvois also has a TIN search that confirms a number against a name.
Do you want your records checked properly? Talk to us. Data clean-up is the first step in the Finance & Compliance Starter Kit, before the plugin goes live.
Sources: LHDN e-Invoice Guideline v4.8, Section 2.3.3 (validation) and Appendix 1 (mandatory fields); Ooroboros e-Invoice support records.
This is Part 5 of 8 in the e-Invoice series. Start with Part 1: The e-Invoice threshold changed. Ten rules that many Malaysian businesses still miss. Previous: Part 4: Relaxation period does not mean do nothing. Next: Part 6: Credit notes and debit notes need e-Invoices too.
This article is general information, not tax advice.