The CSV column reference: planned mapping the bridge parser accepts.
Note: CSV import is on the roadmap — not live yet. This guide previews the planned column reference so you can prepare your export mapping ahead of time. Today, send invoices with the REST API (Pro plan) or enter them in the dashboard. Below is the full column reference, grouped by purpose, with the LHDN field each column maps to.
The 8 columns every row must carry.
These eight columns are non-negotiable for every document type. Missing any one of them and the parser rejects the row before it ever reaches LHDN.
- Invoice No: your internal invoice number (any string).
- Invoice Type: one of the 8 LHDN codes (01, 02, 03, 04, 11, 12, 13, 14).
- Invoice Date: ISO format (YYYY-MM-DD).
- Currency Code: ISO 4217 (MYR for Ringgit, USD, etc).
- Line No: line item number within the invoice.
- Qty Inv: quantity invoiced for the line.
- Unit Price: price per unit before tax.
- Total Including Tax: the rolled-up tax-inclusive total.
Required for standard invoices (01–04).
Standard supplier-issued invoices need the customer party identified. Self-billed types (11–14) source the customer from the company DB record instead, so these two columns become optional in that case.
- Customer Name: registered business name of the counterparty.
- Customer TIN No: LHDN-issued TIN of the counterparty.
- Customer Address, City, State, Postcode, Country: address fields.
- Customer SST No, BRN: optional but recommended for B2B.
Three extras required for types 11–14.
Self-billed types carry an extra invariant on top of the base eight: the supplier party (who's being paid) must be fully identified, including the MSIC industry classification code that LHDN uses for tax treatment.
- Customer Name (the party being paid): same field name, different role.
- Customer TIN No (the party being paid).
- Customer MSIC Code: 5-digit MSIC, validated against the regex /^\d{5}$/.
Two extras required for types 02, 03, 04, 12, 13, 14.
Every note document (credit, debit, refund; supplier-issued or self-billed) must reference the parent invoice it modifies.
- Original Invoice No: your internal reference to the parent.
- Reference Invoice No: the LHDN UUID of the parent document.
Everything else the parser accepts.
The planned importer will validate numeric and LHDN-specific fields before submission. Exact accepted columns and limits will be published when CSV import ships; they are not product guarantees today.
Last updated · July 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.