What Malaysia Requires: E-Invoicing Explained

If you own e-invoicing for a company, or are about to, read this before you configure anything: it is what LHDN is actually asking for and why. This page is the background: who has to comply and from when, what an e-invoice contains, what happens after you send one, which parts of it BigLedger does for you — and which parts stay a person’s job however well the software is set up. Fifteen minutes of reading, and nothing to configure yet.

This page is mostly LHDN’s rules, and the parts of the job that stay a person’s. What BigLedger does about each rule — the company switch it reads instead of your date, where the seller and buyer come from, the jobs between Finalise and Valid, which month a receipt belongs to — is on What BigLedger does about it.

What e-invoicing is

Malaysian e-invoicing is an Inland Revenue Board (LHDN) programme that replaces the paper or PDF invoice as the tax record with a structured digital document, submitted to LHDN and validated by them before it counts. Your customer may still receive a PDF that looks much as it always did — but the version LHDN holds is the one that matters, and it only exists once LHDN has validated it.

Three consequences follow, and they shape everything else in these guides:

• An invoice is not finished when you print it. It is finished when LHDN says Valid.
• The data has to be right before it is sent, because the correction path after validation is narrow and time-limited.
• Someone has to check, every month, that everything got there — which is why the month-end cycle exists.

Who has to comply, and from when

The rollout is phased by annual turnover, so businesses came into scope in waves:

Notice that the fourth row has no floor. The table stops at “up to RM 5 million” and says nothing about a small business at the bottom of it — the floor lives in a separate paragraph, and that paragraph is the one that moved.

The exemption, and the three ways you lose it

Businesses with annual turnover of less than RM 3,000,000 are exempt (e-Invoice Guideline 4.8, §1.6.1(e)).

Then read §1.6.10, because it takes the exemption back from three kinds of business. This paragraph is new in version 4.8 and it is the part most readers will not think to look for. The exemption applies to every category of taxpayer — individuals, partnerships, companies, co-operatives — except where the business:

• has a shareholder that is not a person (a company, say) whose own annual turnover is RM 3,000,000 or more; or
• is a subsidiary of a holding company whose annual turnover is RM 3,000,000 or more; or
• has a related company or joint venture whose annual turnover is RM 3,000,000 or more. (“Related company” here has the meaning given in section 2 of the Promotion of Investments Act 1986.)

Take the running example. If GadgetSphere Distribution Sdn Bhd turned over RM 2 million last year it would look exempt on §1.6.1(e) alone — and it is not, because it sits in a group with GadgetSphere Sdn Bhd. The exemption is for the standalone small business, not for the small company inside a group. If your company has a corporate shareholder, a parent, or a sister company anywhere, work through §1.6.10 before you conclude anything from the RM 3 million figure.

Two neighbouring rules catch people the other way round. Selling to an exempt buyer does not exempt you — §1.6.3 says a supplier to anyone on the §1.6.1 list still issues e-invoices on its own timeline. And exempt does not mean forbidden: §1.5 lets any business join early, whatever its turnover.

Which year’s turnover counts — not this one

§1.5 is specific about this and it surprises people. The turnover that decides your phase is the one in your audited accounts or tax return for financial year 2022 (pro-rated to twelve months if you changed your year end that year). The guideline then says outright that “any changes to the taxpayer’s annual turnover or revenue in subsequent years will not change the taxpayer’s obligations”. So growing past a threshold since 2022 does not pull you in, and a bad year since does not let you out. Once your date is fixed, it is fixed.

If your business started recently

• Began trading between 2023 and 2025, with annual turnover of RM 3,000,000 or more — you came in on 1 July 2026.
• Began trading from 2026 onwards — the guideline’s words are “1 July 2026 or upon the operation commencement date”.
• Began trading from 2026 onwards and expect less than RM 3,000,000 in your first year — you have no date yet. Your obligation starts on 1 January of the second year after the year your turnover first reaches RM 3,000,000. Reach RM 3 million during 2027, and you start on 1 January 2029.

What goes on an e-invoice

LHDN’s own list runs to 55 data fields (e-Invoice Guideline 4.8, Appendix Table 1). Twenty of the 55 carry the marker [Optional] against the field name — e-mail addresses for both parties, billing frequency and period, quantity, unit of measure, discounts, fees, rounding, and the whole payment block. The other 35 are required. In practice they group into five blocks:

• Who is selling — your company’s name, tax number, registration number, industry classification, address and contact number.
• Who is buying — name, tax number, identity document type and value, address and contact number. This block causes most rejections; see Validation Rules & Troubleshooting.
• The document — type, version, issue date and time, currency.
• The lines — item classification code, description, quantity, unit of measure, unit price, tax type and tax amount.
• The money — subtotal, total excluding tax, total including tax, and any discounts or charges.

Four document types cover almost everything you will send: the invoice, the credit note, the debit note and the refund note. A self-billed e-invoice reverses the roles — you issue it as the buyer, typically when your supplier cannot. In BigLedger a purchase document goes to LHDN only when it is marked self-billed; every other purchase document stays out of the pipeline, which is right, because the e-invoice for an ordinary purchase is your supplier’s to issue.

How a document gets to LHDN

There are two routes, and which one you are on changes what you have to do:

The MyInvois portal. You type each invoice into LHDN’s own web portal. Workable at low volume; unworkable for a retailer ringing up thousands of receipts a month. Note that an invoice created this way exists at LHDN but not in BigLedger, so it will not appear in any BigLedger report.

API integration — what BigLedger does. Your documents are submitted straight from BigLedger. You authorise BigLedger as your e-invoice intermediary on the MyInvois portal once, and from then on BigLedger submits on your behalf.

What happens after you submit

1. Submission. BigLedger sends the e-invoice to LHDN. Your document status becomes Submitted.
2. Validation. LHDN checks it and returns Valid or Invalid, along with a unique identifier for the validated document.
3. Sharing. The validated e-invoice — with its QR code — is what you give the buyer. BigLedger can e-mail it to the buyer for you once LHDN says Valid, when the company’s Send Email To Buyer switch is on (Organisation Applet, E-Invoice tab). Whether it leaves at once or waits for a scheduled e-mail processor depends on how your tenant is set up, so confirm the first one arrived rather than assume it.
4. The 72-hour window. From validation, the supplier has 72 hours to cancel the e-invoice, and the buyer has 72 hours to reject it. After that neither is possible, and the only correction is a credit, debit or refund note — LHDN’s rule, e-Invoice Guideline 4.8 §2.3.6 (which version we cite). See Cancelling and Correcting a Validated E-Invoice.

Consolidated e-invoices, and why retailers care

You do not issue an individual e-invoice for every walk-in sale. Receipts where the buyer did not give their details are reported together in a consolidated e-invoice — one document, the buyer recorded as General Public, due at LHDN by the 7th of the following month (e-Invoice Specific Guideline 4.9, §3.6.2: within seven calendar days after the month end).

For a 22-branch electronics retailer like GadgetSphere Sdn Bhd ringing up around 38,000 counter receipts a month, that is the difference between a few hundred consolidated e-invoices somebody can actually check before the 7th and 38,000 individual ones that nobody can.

The large sale

The one line to plan around is the large sale. LHDN bars consolidation for any single transaction with a value exceeding RM 10,000, in every industry, from 1 January 2026 — e-Invoice Specific Guideline 4.9, §3.7.2, Table 3.6 row 7. Such a sale needs an individual e-invoice with the buyer’s real identity, which in practice means asking for it at the counter, because chasing it a week later rarely works. A taxpayer still inside LHDN’s interim relaxation period (turnover up to RM 5 million, until 31 December 2027) may consolidate even these sales; BigLedger implements none of that relief (LHDN guideline versions).

For a sales invoice or cash bill marked Consolidated, BigLedger applies its own line one sen lower, at RM 10,000 and above: The large sale, one sen lower.

Who does what

The software sends, polls and consolidates. These parts of the job are still people’s, with or without it:

• The owner of the figures, with your tax agent — decides each company’s date and exemption once, in writing, and sets E-Invoice Status to match. BigLedger holds no date to check it against.
• Whoever serves at the counter — asks for the buyer’s details on any sale of RM 10,000 or more, before the customer leaves. A diverted sale waits in the Individual Pool until someone completes it.
• Whoever runs My E-Invoice Admin — works the pools daily, owns every Invalid row, and decides inside the 72 hours whether a wrong e-invoice is cancelled or corrected by a note.
• Whoever closes the month — confirms by the 7th that last month’s Batch Pool is empty and its consolidated e-invoices are Valid.
• Whoever voids a cash bill — tells the person who runs My E-Invoice Admin the same day. The check meant to stop a void once the bill’s e-invoice has been submitted does not fire today (a known issue, reported to engineering), so a voided bill can leave LHDN holding a sale your books no longer have.

Common mistakes

1. “I finalised the invoice and nothing was submitted to LHDN.” Usually it is in a pool, with the missing field written on the row; fix the field and use Save and Resubmit. If it is in no pool and not on To IRB E-Invoice either, check the company’s E-Invoice Status and the branch’s and customer’s Skip E-Invoice setting — a document that failed the entry test leaves no trace.
2. Every document from one company is parked, all naming the same Supplier field. The seller block is read from the company record when each document is checked. Correct the company record, then resubmit the parked rows from their pool (where the seller and buyer come from).
3. The cancellation was refused although the button was lit. The button used your computer’s clock; the refusal used BigLedger’s count from LHDN’s validation time. Past 72 hours the route is a credit, debit or refund note (where the 72 hours come from).
4. A RM 10,000.00 sale is missing from the consolidated e-invoice. It was diverted to the Individual Pool on purpose. Complete the buyer and send it individually before the 7th.
5. Consolidated e-invoices for last month are still being built on the 7th. The default batch is too small for your volume. Consolidate the rest by hand from the Batch Pool, and ask support to resize the clock before next month (the arithmetic).
6. Disable Consolidated Submission is on, and receipts were consolidated anyway. The switch governs the drop-down, not the month-end run. If no receipt may be consolidated, last month’s receipts have to be cleared out of the Batch Pool before the 1st (what the switch does not govern).
7. An invoice keyed straight into the MyInvois portal is missing from every BigLedger report. It was never in BigLedger. Choose one route per company and keep to it.

What success looks like

Five checks, about ten minutes, run them at the start and again after your first month-end:

1. Each company you decided is in scope reads ENABLED on the Organisation Applet’s E-Invoice tab, and each one you decided is exempt does not — and the decision is written down somewhere other than this screen.
2. Today’s ordinary sales reach LHDN. On To IRB E-Invoice, a sale finalised this morning reads Valid with an LHDN identifier and a QR code. If it still reads Submitted after an hour, press Refresh.
3. The pools are worked. Neither the Individual Pool nor the Single General Pool holds a row older than a week.
4. The month closed. By the 7th, the Batch Pool holds nothing dated last month, the Consolidated Submission screen is empty, and last month’s consolidated e-invoices on To IRB E-Invoice read Valid, dated the last day of the month.
5. The buyer got it. For one Valid individual e-invoice, the buyer confirms the e-mail arrived — or you know that your company’s Send Email To Buyer switch is off and somebody sends it by hand.

Where to go next