Malaysia E-Invoice Data Requirements Every Business Must Know

Honestly, most businesses do not realise just how detailed the Malaysia e-invoice data requirements are until their first invoice gets rejected. And that is a frustrating way to learn. LHDN has built the MyInvois system around very specific data standards — and the portal does not give second chances when something is missing or wrong. One absent field, one mismatched identifier, and the whole document bounces back.

So before that happens to you, here is a proper walkthrough of every element covered in this guide — what goes where, why it matters, and where the real traps are. Whether your team is mid-implementation or just starting to plan, this covers the ground you need.

Mandatory Fields in an LHDN E-Invoice

There is no flexibility here. Every single e-invoice that goes through the MyInvois portal must carry a fixed set of fields — all of them, every time. The LHDN invoice data fields list was put together to give LHDN a complete, consistent picture of every transaction passing through the system. Skip one, and the portal will not process it.

These are the fields that must appear on every valid e-invoice:

Invoice version number
UUID — the unique identifier MyInvois assigns after a successful submission
Date and time the invoice was issued
Invoice type code (01 for a standard invoice, 02 for a credit note, and others as applicable)
Currency code — MYR for Malaysian Ringgit, or the relevant foreign currency code
Full supplier details: legal name, TIN, registered address, contact information
Full buyer details: name, TIN, address, and applicable registration numbers
Line items — each with a description, quantity, unit price, and subtotal
Tax type, tax rate, and tax amount broken down per line item
Total before tax, total tax, and the final payable amount
LHDN validation stamp from MyInvois confirming successful acceptance

Your invoicing software or ERP needs to be generating all of these automatically — not filled in manually before submission. If your current setup cannot do that reliably, that is the first thing worth fixing.

Supplier and Buyer Information Requirements

This section catches out more businesses than any other part of the Malaysia e-invoice data requirements. On the surface it seems simple — your details, their details. In practice, LHDN wants very specific information, formatted in a very particular way. Anything less and the submission fails.

What the supplier must include on every invoice:

Full legal business name — exactly as it appears in SSM registration, no shortcuts
Tax Identification Number (TIN) issued by LHDN
Business Registration Number (BRN) or MyInvois Registration Number
SST registration number, if applicable
Complete registered business address — postcode, state, and country all required
A working contact number and email address
MSIC code (Malaysia Standard Industrial Classification)
A short description of the business activity

What must be captured for the buyer:

Full name of the buyer — individual or registered entity
TIN or IC number for individual buyers
BRN or passport number where it applies
SST number if the buyer is registered
Full address
Contact number and email

A quick note on B2C transactions — below certain value thresholds, you can get away with simplified buyer information. But for anything B2B or B2G, that option disappears entirely. The e invoice structure Malaysia has established for business transactions demands the full picture, and the Malaysia invoicing standards back that up without any grey area.

Product and Tax Information in E-Invoices

Here is where the data gets genuinely detailed. Under the digital tax invoice Malaysia framework, every product or service on an invoice carries its own data set. You cannot consolidate everything into a single line with a lump-sum tax figure at the bottom — that is not how this works.

Per line item, you need to provide:

An LHDN classification code specific to that product or service
A clear, readable description of what was supplied
Unit price before tax
Quantity and the unit of measurement
Any discount applied to that line
Subtotal before tax for the line
Tax category — SST, import GST, or exempt as appropriate
The tax rate applied
The tax amount calculated for that individual line

The Malaysian invoice data format is deliberate about this line-level breakdown. It is not just administrative complexity for its own sake — it gives LHDN the ability to cross-check each invoice against your SST return filings, line by line if needed.

And here is something that trips people up regularly: if you supply exempt or zero-rated goods, the tax fields on each line still need to be filled in — with the correct exemption code. Blank tax fields on exempt lines are read as errors, not as intentional omissions. That misunderstanding is baked into a lot of the rejections we see under the LHDN invoice data fields setup, and it is one of the more avoidable pitfalls the digital tax invoice Malaysia system continues to surface across industries.

Invoice Number and Document Structure

Structure is as important as content in this system. The Malaysia e-invoice data requirements specify a dual-identifier approach — your own internal invoice number alongside the UUID that MyInvois generates post-validation. These identifiers do different jobs, and both are compulsory. The malaysia invoice data format does not allow you to rely on one without the other.

Structural requirements for a compliant e-invoice:

Your internal invoice reference number — must be unique within your own system
Invoice type code — the correct code for standard invoices, credit notes, debit notes, refund notes, or self-billed invoices
Original invoice UUID — mandatory when raising a credit note, debit note, or refund against an existing invoice
Currency code plus exchange rate for any foreign currency transactions
Payment terms and mode of payment
Delivery details where physical goods are being shipped
Prepayment or deposit reference, where a partial payment was made upfront
Digital signature and MyInvois validation stamp

The original UUID linkage on credit notes is something businesses keep missing — especially in the early months of implementation. Without it, LHDN cannot connect the correction to the original validated document. The e-invoice structure Malaysia operates on is built on that audit chain, and a credit note that floats without a valid reference will not be accepted.

Data Accuracy and Compliance Rules

Clearing technical validation is not the finish line. An invoice can pass every structural check and still fall foul of the Malaysia e-invoice data requirements if the underlying data is wrong. LHDN is unambiguous about this — accuracy is the issuing party’s responsibility, not something the system will compensate for. Businesses that treat the Malaysia e-invoice data requirements as a checklist to pass rather than a standard to maintain are the ones that keep running into avoidable problems.

The accuracy rules your team needs to operate by:

TINs must be checked against LHDN’s live system before submission — an unverified TIN fails on the spot
Business names must match SSM records exactly — trade names or shortened versions are not accepted unless formally registered as such
Tax figures must be mathematically correct at every level — rounding errors at the totals stage will get the invoice rejected
Invoice dates must reflect the actual date of supply, not the day the data was entered
Currency codes must follow ISO 4217 — no informal abbreviations allowed
Every monetary figure must be shown to two decimal places
Issued invoices are locked after validation — any correction goes through a credit note or debit note, never a direct edit

Under the Malaysia invoicing standards, records need to be kept for seven years — and that means your own independent copies, not just relying on what LHDN stores on MyInvois. Supporting documents fall under the same retention obligation. Build that habit early and it will save you a lot of trouble down the road.

Common Mistakes in Invoice Data

Even well-prepared businesses encounter rejections. The same errors tend to come up again and again, across industries and company sizes. Knowing what they are ahead of time is genuinely useful — these are the real-world stumbling blocks within the Malaysia e-invoice data requirements that show up most often.

They serve different purposes and live in different fields. Putting the SST registration number where the TIN should go — or vice versa — is one of the most repeated errors in early submissions.

Empty classification codes on product lines: Every line item needs an LHDN classification code. There is no generic fallback — using a placeholder or leaving it blank will not get through validation.

Thin buyer details on B2B invoices: Some teams assume simplified buyer info works for all invoice types. It does not. LHDN’s requirements mandate full buyer party details on every B2B transaction — no trimming.

Wrong type codes on credit notes: A credit note without type code 02, or without the original UUID referenced, will be rejected. This is a consistent problem, particularly in businesses issuing their first round of adjustment documents.

Timestamps in the wrong timezone: The submission system requires Malaysia Standard Time (UTC+8). ERP systems set to other regions will push out timestamps that do not align, and those invoices will not pass.

Tax totals that do not add up: If your line-level tax figures do not sum correctly to the total tax field, the invoice gets kicked back. Pre-submission validation through your system or via MyInvois sandbox testing is the most reliable way to catch this before it becomes a problem — and it is a step every business operating under the Malaysia e-invoice data requirements should treat as non-negotiable.

Conclusion

Working through LHDN’s e-invoicing rules is not something you do once and forget. The detail involved — from line-level tax codes to exact party identifiers to document linkage on credit notes — means there are genuine points of failure at every stage. And the system is not lenient about any of them.

What actually reduces rejections is not just knowing the rules — it is having your internal processes set up so that the right data flows into every field without anyone having to think about it at the point of submission. Good system configuration, well-trained staff, and regular pre-submission testing against the MyInvois sandbox environment will take you further than any checklist. That is the environment LHDN’s digital invoicing framework operates in — one that rewards preparation and penalises shortcuts.

LHDN is expanding the mandate progressively, and businesses that sort out their data fundamentals now will be far better placed than those scrambling to catch up. Keep this as a working reference, revisit the official documentation regularly, and treat every part of the compliance structure LHDN has established with the same level of care — because none of it is optional.

FAQ: Malaysia E-Invoice Data Rules

Q1: What happens when I submit an invoice with a missing field?

Instant rejection by MyInvois. Correct the data and resubmit fresh.

Q2: Can a validated e-invoice be edited after LHDN stamps it?

Never. Raise a credit note or debit note instead — direct edits are not permitted.

Q3: Do I need full buyer details on every single invoice?

Always for B2B and B2G. Low-value B2C transactions allow a simplified version.

Q4: What is the UUID and where does it come from?

MyInvois generates it after validation — it is your official proof of accepted submission.

Q5: How long must I keep my e-invoice records?

Seven years, with your own independent copies — not just LHDN’s stored versions.

Source by:

Image by Freepik