Free tool · LHDN e-invoice
e-Invoice TIN and field checker
Enter the buyer's TIN, ID, phone and email as they would go on the e-invoice. See which ones LHDN would refuse or mark Invalid, and how to fix each before you submit. Everything runs in your browser; nothing you type is sent anywhere.
What LHDN would see
Enter a TIN to start.
No problems found in what you entered.
To fix: 0 · To check: 0
- Fix The TIN is missing. Every e-invoice needs a TIN for the seller and the buyer. If the buyer has none, use the general TIN that fits them, from the table below.
- Check Remove spaces and hyphens. Enter the TIN in capitals with nothing between the characters. We checked it as .
- Fix Too long for a TIN. LHDN's TIN field holds at most 14 characters. Check you haven't pasted the ID number or two values together.
- Fix Not one of LHDN's four general TINs. They are EI followed by 11 digits: EI00000000010, EI00000000020, EI00000000030 or EI00000000040. Count the zeros.
- Fix Old individual prefix. SG and OG are older prefixes for individuals. LHDN asks individuals to use their TIN with the prefix IG. The buyer can see it in MyTax.
- Check This doesn't look like a TIN. We expect a prefix such as IG (individual) or C (company) and 10 or 11 digits, for example IG12345678901 or C25845632020. LHDN doesn't publish a full format, so treat this as a typo check and confirm the TIN with the buyer.
- Fix A buyer-only general TIN. EI00000000020 and EI00000000040 are for buyers. As the seller, use your own TIN.
- Check Only on a self-billed e-invoice. A general TIN appears on the supplier's side only when the buyer issues a self-billed e-invoice: EI00000000010 for an individual supplier with only a MyKad or MyTentera number, or on a consolidated self-billed e-invoice, and EI00000000030 for a foreign supplier. On your own sales invoice, use your own TIN.
- Fix The general TIN can't go with a BRN. A business buyer has its own TIN: ask for it. LHDN takes the submission, then marks the e-invoice Invalid.
- Fix Wrong general TIN for a passport. For a foreign buyer who gives only a passport number, LHDN's general TIN is EI00000000020. EI00000000010 goes with a MyKad, MyTentera, MyPR or MyKAS number.
- Fix The general TIN needs an ID here. On an ordinary invoice, EI00000000010 must go with the buyer's MyKad or MyTentera number. Without one it is only allowed on a consolidated e-invoice. Ask for the buyer's IC, or leave the sale as a receipt for your month-end consolidated e-invoice if it is RM10,000 or less. LHDN takes the submission, then marks the e-invoice Invalid.
- Check Buyer ID on a consolidated e-invoice. LHDN's layout for a consolidated e-invoice has the buyer ID as NA. If this buyer gave you their IC, they can have an e-invoice of their own instead.
- Fix Wrong general TIN for a local ID. EI00000000020 is for foreign buyers. A buyer with a MyKad, MyTentera, MyPR or MyKAS number takes EI00000000010.
- Check Add the foreign buyer's ID. The ID field is mandatory. Enter the buyer's passport number, or the ID number they gave you.
- Fix EI00000000030 is a supplier's TIN. It is for a foreign supplier on a self-billed e-invoice. For a foreign buyer, use EI00000000020.
- Check Government buyers take BRN "NA". LHDN's FAQ says to enter EI00000000040 with the BRN as NA for government, state and local authorities and statutory bodies. Choose BRN as the ID type and enter NA.
- Fix A consolidated e-invoice uses EI00000000010. On a consolidated e-invoice the buyer is "General Public", with TIN EI00000000010 and ID NA. A buyer who gave you their own TIN should get an e-invoice of their own.
- Check Add the ID that goes with this TIN. A business's registration number is a mandatory field, and LHDN's Validate TIN matches a TIN with its ID. Only an individual may give their TIN alone.
- Fix Write NA, not N/A. LHDN's placeholder for an empty value is NA. "N/A", "-" and "nil" are refused.
- Fix Remove the hyphens. The NRIC field holds 12 characters, so enter the 12 digits only, for example 770625015324.
- Fix Not a 12-digit IC number. MyKad, MyPR and MyKAS numbers are 12 digits, for example 770625015324.
- Fix Too long. LHDN's field for this ID type holds 12 characters at most. Check for spaces or an extra character.
- Fix Too long for a BRN. LHDN's BRN field holds 20 characters at most.
- Check Letters and digits only. Remove spaces, hyphens and other symbols from the ID number.
- Check Use the new 12-digit BRN. Businesses registered with SSM must give the new 12-digit registration number, for example 202001234567, not the old one. Registered with another body? Its number is fine. LHDN has paused BRN validation since 19 July 2024, so this may not be refused today.
- Fix The contact number is missing. It is mandatory for both parties. An individual buyer is expected to give one.
- Check Enter NA. The field can't be empty. On a consolidated e-invoice, LHDN lets you put NA as the buyer's contact number.
- Fix LHDN refuses this placeholder. "N/A" got e-invoices refused with "Enter valid phone number and the minimum length is 8 characters". Enter a real number, or NA on a consolidated e-invoice.
- Check NA is meant for consolidated e-invoices. LHDN's rules provide NA for the general-public buyer on a consolidated e-invoice. Here, ask for a real number.
- Fix Too short. LHDN refuses contact numbers under 8 characters. Include the country and area code, for example +60123456789.
- Fix Too long. LHDN's contact number field holds 20 characters at most. Enter one number only.
- Fix Not a phone number. Use digits and a leading + only. Put extensions and notes somewhere else.
- Check Use the international form. LHDN asks for E.164: a +, the country code, then the number with no spaces and no leading 0. 012-345 6789 becomes +60123456789.
- Fix Leave the email blank instead. Email is optional, but "N/A" and "-" got e-invoices refused with "Enter valid e-mail address".
- Check NA isn't an email address. Email is optional, so leave it blank when the buyer has none.
- Fix Too long. LHDN's email field holds 320 characters at most.
- Fix Not a valid email address. Enter one address, like name@company.com, with no spaces. Leave it blank if you don't have one.
- Check Enter the amount as a number. For example 12500.00. The RM10,000 checks are skipped until then.
- Fix Over RM10,000: take it out of the consolidated e-invoice. Any single sale above RM10,000 needs its own e-invoice with the buyer's details. The rest of the month can stay consolidated.
- Check Over RM10,000 with the general TIN. This sale needs its own e-invoice, which it has. LHDN's guideline lets EI00000000010 go with a Malaysian individual's MyKad number, but where you can, get the buyer's own TIN. Our platform asks for it above RM10,000.
- Check Allowed until 31 December 2027. During the relaxation period, a Phase 4 business may consolidate every sale, including those above RM10,000. From 1 January 2028, a sale like this needs its own e-invoice with the buyer's details.
On a consolidated e-invoice also put the buyer's name as General Public, the address as NA with state code 17, and classification code 004 on every line.
This checks format and LHDN's rules only. It can't tell whether the TIN is registered or belongs to this buyer. The buyer can see their TIN in MyTax, and a system connected to MyInvois can check the TIN and ID pair with LHDN's Validate TIN API.
Format checks, not tax advice. Rules from LHDN's e-Invoice Specific Guideline v4.9 (7 September 2026: section 3.7, section 16.2, Appendices 1, 2 and 4), e-Invoice Guideline v4.8, e-Invoice FAQ (4 September 2026, questions 32 to 36) and the MyInvois SDK's invoice field rules and Validate TIN API. The 8-character phone minimum, the refusal of "N/A", and LHDN marking general-TIN mistakes Invalid after accepting them come from our own submissions to LHDN's test environment in October 2026; the SDK doesn't state them. Checked on 23 October 2026.
Which general TIN to use
When the other party has no TIN, LHDN gives four general TINs. Each fits specific cases, and using the wrong one gets the e-invoice marked Invalid.
| General TIN | Use it for | Goes with |
|---|---|---|
| EI00000000010 | General public. A Malaysian individual who gives only a MyKad or MyTentera number, or a MyPR or MyKAS holder. Also the buyer on a consolidated e-invoice, and the supplier on a consolidated self-billed e-invoice. | The MyKad, MyTentera, MyPR or MyKAS number. On a consolidated e-invoice, ID NA. Never a BRN. |
| EI00000000020 | Foreign buyer. A foreign individual who gives only a passport number, a foreign buyer on an export sale with no Malaysian TIN, or a foreign shipping recipient. | The passport number, where that is all the buyer gives. |
| EI00000000030 | Foreign supplier, on a self-billed e-invoice only. A foreign individual supplier with only a passport, or an import supplier with no Malaysian TIN. | The supplier's passport number, where that is all they give. Never as the buyer. |
| EI00000000040 | Government buyers: the government, state governments and state authorities, government, local and statutory authorities, statutory bodies, and exempt institutions with no TIN. | BRN entered as NA. |
Why LHDN accepts some mistakes, then marks the e-invoice Invalid
LHDN checks an e-invoice in two stages. When you submit, it checks the structure: mandatory fields, lengths and formats. A phone number of "N/A" fails here, and the document is refused straight away.
A document that passes is accepted and then validated against LHDN's own records and rules, including which general TIN may go with which ID. A general TIN beside a BRN, or EI00000000010 on an ordinary invoice with no buyer ID, gets through the first stage and comes back Invalid a moment later.
That second kind is the dangerous one. If your system only reads the submission response, it reports the e-invoice as sent while LHDN holds it as Invalid. Always read the document's final status. Our guide to LHDN validation errors covers what each outcome means.