Guide
e-Invoice for online stores in Malaysia.
Selling to consumers changes the problem. The hard part is rarely the submission itself. It is that a B2C order flow was never built to collect what a validated invoice asks for. Here is what actually bites, and the usual way through it.
Part of the Malaysia e-Invoice guide.
A business selling to other businesses usually already has its buyers' tax details on file. An online store selling to the public almost never does, and that gap is where most of the work sits. Four things tend to surface in order.
1. The buyer details you never collected
A consumer checkout is built to take payment with as little friction as possible, so it rarely captures a tax identification number or a full registered address. A validated invoice can ask for exactly those. A B2C flow that was fine for years suddenly has mandatory fields with nowhere to source the data.
Chasing every customer for a tax number is not the answer, and it is not the expected one. For consumer sales the usual route is a consolidated submission rather than an individual invoice per order. What a consolidated submission must contain, and how often it is filed, is exactly the kind of detail to confirm with a tax agent rather than a web page, but the shape of the answer is: capture the minimum at checkout, and consolidate the rest.
2. Your catalogue has no tax classification
Submissions expect a classification code on each line. A catalogue built for a storefront has almost never carried one, because it never needed to. Before a single invoice can go out cleanly, every product needs a code against it. On a large catalogue that is a data exercise in its own right, and it is better done once, deliberately, than patched per order.
3. Refunds are their own document
A refund is not an edited invoice. It is a separate document type that references the original, and a store that models a refund as a status change on the order has nowhere to put it. If you take returns, the way refunds are recorded has to be sorted out at the same time as invoicing, not after.
4. A customer can still ask for a proper invoice
Even where day-to-day sales are consolidated, a buyer can later ask for an individual validated e-Invoice, for a claim or their own records. Your flow needs to be able to produce one on request rather than only in bulk at month end.
What this means for the build
Put together, the work for an online store is less about the LHDN connection and more about the shop:
- Capture the minimum a validated invoice needs at checkout, without adding friction that costs you the sale
- Classify the catalogue once, with a code on every product
- Model refunds and credit notes as documents, not order statuses
- Be able to issue an individual validated invoice on request, not only a consolidated batch
None of that requires the biggest possible system. It requires the shop you already run to hold a few things it never had to. If you want to see which connection route fits once the shop is ready, there is a step-by-step guide to choosing a route.
Thresholds, dates and penalties for this topic live on the main guide and were last checked on 31 July 2026. Confirm consolidated submission rules and your own position with a tax agent.
Run an online store and unsure where to start?
Tell us what platform your store runs on and how returns work today. We will tell you what has to change before e-Invoice fits, and what can be left alone.