Invoice — the baseline document the supplier issues to a customer for goods or services.
Type 01 is the default LHDN MyInvois document — what most businesses think of as "the invoice". The supplier issues it to the customer; it carries the line items, taxes, and totals; it submits to MyInvois and returns a UUID once LHDN accepts it. Everything else on this page applies to type 01 unless the spec carves out an exception for one of the other seven codes.
Four common scenarios.
- 01A standard sale of goods or services from your business to a customer.
- 02Recurring subscription billing where each period is a fresh invoice.
- 03Project milestones or progress-billing where each milestone is its own invoice.
- 04Any commercial document that isn't a correction (use 02–04 for those) and isn't self-billed (use 11–14).
What this document type carries that a generic invoice doesn't.
- Supplier party — your TIN, name, address, MSIC code, contact, SST number.
- Customer party — counterparty TIN, name, address, contact details.
- Line items — description, quantity, unit price, tax classification code, tax rate.
- Totals — subtotal, tax amount, total payable, currency, rounding.
Same pipeline as every other type.
Type 01 is the default path through the bridge's UBL 2.1 generator. Drop a CSV row with the required fields filled in, post a JSON object via the REST API, or enter it manually through the dashboard — all three paths land in the same `buildUblInvoiceXml` pipeline and produce identical wire output to LHDN.
Last updated · May 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.