Skip to content

Free reference · LHDN e-invoice

MyInvois error codes, explained

What LHDN's rejection codes and messages mean, why your e-invoice got one, and how to fix it. Every entry comes from a response LHDN actually sent to our e-invoice platform, not from guesswork. Type the code or a few words of the message to jump to it.

ERR237Marked Invalid

Business buyer given the general public TIN

Buyer's details cannot be general TIN (010) for issuance of individual e-Invoice

Why
The buyer's ID is a business registration number (BRN), but the TIN is the general public TIN EI00000000010. That general TIN is for individuals and consolidated e-invoices, never for a company.
Fix
Ask the buyer company for its own TIN and resubmit. A Malaysian company's TIN starts with C (for example C21984536000). LHDN reports this under "Step05 - Invalid Taxpayer Profile Validator".

ERR222Marked Invalid

General TIN with the wrong kind of ID

Why
EI00000000010 on an individual e-invoice must go with a Malaysian individual's MyKad (IC) or MyTentera (army) number. Here it went with another kind of ID.
Fix
Enter the buyer's own TIN, or their IC number with the general TIN. A foreign individual with only a passport takes EI00000000020 instead. Check the TIN and ID pair →

ERR228Marked Invalid

General TIN on an ordinary invoice with no buyer ID

Why
The general TIN appears with no buyer ID (or "NA") on an invoice that is not a consolidated e-invoice. LHDN only accepts that pairing on a consolidated e-invoice.
Fix
Add the buyer's IC number, or use the buyer's own TIN. If this is a walk-in sale, leave it out of individual e-invoicing and file it in your month-end consolidated e-invoice instead.

ERR236Marked Invalid

Looks like a consolidated e-invoice, but isn't laid out as one

Why
The buyer is the general public (EI00000000010 with ID "NA"), which LHDN reads as a consolidated e-invoice, but not every line carries classification code 004.
Fix
On a consolidated e-invoice, every line uses classification 004, the buyer is "General Public" with TIN EI00000000010 and ID "NA". If it is really a single sale, give the buyer's details instead. How consolidation works →

No codeRefused

Seller TIN doesn't match the account that submitted

Authenticated TIN and document's TIN is not matching

Why
The seller's TIN on the e-invoice is not the taxpayer whose MyInvois credentials sent it. Common after copying an invoice template from another company, or when a system submits for a client it is not authorised for.
Fix
Make the seller TIN match the account you submit with. For a sole proprietor, the ID is the owner's own IC number. If someone submits on your behalf, authorise them as your intermediary in MyInvois first.

No codeRefused

Email address refused

Enter valid e-mail address - BUYER

Why
The email field holds a placeholder such as "N/A" or "-", or more than one address. LHDN checks the format even though email is optional.
Fix
Enter one valid address, or leave the field empty when the buyer has none. Empty is accepted; "N/A" is not.

No codeRefused

Contact number refused

Why
The contact number is mandatory and LHDN refuses one shorter than 8 characters. Placeholders such as "N/A" and "-" fail that check.
Fix
Write the number with the country code, such as +60123456789. On a consolidated e-invoice, where the buyer is the general public, LHDN's own placeholder is "NA", without the slash.

DuplicateSubmissionNothing to resend

LHDN already has this submission

Why
The same document was sent again, usually because the first attempt timed out and the system retried without checking.
Fix
Don't resend. Look the document up in MyInvois (or with the API's document search) and record the e-invoice LHDN already holds. Sending it a third time won't change the answer.

Codes and messages LHDN returned to submissions from our e-invoice platform in LHDN's test (preprod) environment in October 2026, with the cause we confirmed for each. The MyInvois SDK documents the API and the fields, but not these codes. Where LHDN's exact wording is on record it is shown in the grey box; otherwise the description is ours. Not tax advice. Checked on 19 November 2026.

Refused now, or marked Invalid later

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" or an email of "-" fails there, and the document is refused straight away.

A document that passes is accepted, then validated against LHDN's own records and rules a moment later. The four ERR codes above come from that second stage: the submission looked successful, and the e-invoice came back Invalid.

That second kind is the one that causes trouble. A system that only reads the submission response reports the e-invoice as sent while LHDN holds it as Invalid. Always read each document's final status. For the wider picture of rejections, see our guide to LHDN validation errors.

Common questions

What does ERR237 mean in MyInvois?
LHDN's message is "Buyer's details cannot be general TIN (010) for issuance of individual e-Invoice". The buyer has a business registration number, but the e-invoice gives the general public TIN EI00000000010. A business buyer must be invoiced under its own TIN. LHDN accepts the submission first and then marks the e-invoice Invalid, so check the document's final status.
Why did LHDN accept my e-invoice and then mark it Invalid?
LHDN checks in two stages. At submission it checks the structure, such as mandatory fields and formats. A document that passes is accepted and then checked against LHDN's records and rules, including which general TIN may go with which ID. ERR222, ERR228, ERR236 and ERR237 come from that second stage, a moment after the submission was accepted.
Can I resubmit an e-invoice after fixing the error?
Yes. An e-invoice LHDN refused or marked Invalid was never a valid e-invoice, so correct it and submit it again under the same invoice number. Do not resend a document LHDN already accepted as Valid: that is a duplicate. Change a Valid e-invoice by cancelling it within 72 hours, or by issuing a credit or debit note.
Where does LHDN list these error codes?
The MyInvois SDK documents the API and the fields, but not these rejection codes and their causes. This page lists codes and messages LHDN actually returned to submissions from our e-invoice platform in its test environment in October 2026, with the cause we confirmed for each.
Catch them before LHDN does Our e-Invoice platform runs these checks on every invoice before it is sent, explains any rejection in plain words, and resubmits corrected invoices for free. See the e-Invoice platform → Try the live demo, no sign-up → Checking one buyer by hand? Use the TIN and field checker → Have the JSON your system sends? Check the whole document →