E-Invoice Integration for Your Website: Basics
Home  /  Blog

E-Invoice Integration for Your Website: Basics

The Short Answer: E-invoice integration links your website’s orders to LHDN’s MyInvois system, so invoices are validated without anyone retyping them. Not every site needs it. If your business is in scope and your website takes orders or payments, the right route depends on volume: the free MyInvois Portal suits a handful of invoices a month, while a connector or API link pays off once manual entry starts eating staff hours every week.

Many owners first hear about e-invoicing from their accountant, not their web designer. Then the question lands on the website: does the online shop or booking form now need to talk to LHDN? The honest answer is “sometimes”, and the cost of getting it wrong runs both ways. Some businesses pay for an integration they do not need. Others keep keying orders into a portal by hand long after it stopped making sense.

This guide from IZI Digital Marketing explains what e-invoice integration means for a website, which route fits which business, and how to scope the work before you ask for quotes. It is a decision guide, not tax advice, so confirm your own obligations with your tax agent. For how integration work affects a build budget, see our guide to website design price in Malaysia.

Not sure if your website is even in scope?

Tell us how your site takes orders and who your buyers are. We will map where e-invoicing touches your website and where it does not. Check my website’s e-invoice scope

The video below walks through how the MyInvois Portal and the API route work. After it, we turn those two routes into a decision you can make for your own website.

How E-Invoicing Works Through the MyInvois Portal and API

Source video: Watch on YouTube

PART 1 · DIAGNOSE

Does Your Website Need E-Invoice Integration?

IN BRIEFYour website needs e-invoice integration only when two things are true: your business must issue e-invoices, and the website itself creates sales records. A brochure site that collects enquiries does not. An online store or booking site with paid checkout might. Our guide to website cost factors that move a quote shows why integrations change a build’s scope.

E-invoicing is a duty your business carries wherever it sells. The website only matters if it is where the sale happens. Run through these three questions before you brief anyone:

  1. Is your business in scope? Under the LHDN e-Invoice implementation timeline, updated on 30 August 2026, taxpayers with annual turnover below RM3 million are exempt. Your tax agent should confirm where you stand.
  2. Does the website create the sale? Paid checkout, deposits, subscriptions and online bookings all create transactions. Contact forms and WhatsApp buttons do not; the invoice is raised later in your accounting system.
  3. Who are your buyers? Business buyers usually want a full e-invoice in their own name. Walk-in style consumer sales can often be covered by a consolidated e-invoice, which changes how much the website must collect.

If the answer to the first two questions is “no”, you can stop here. Your e-invoicing sits in your accounting software, and your website brief does not need to change.

Bottom Line: Ask where the sale happens before asking for an integration. If it happens off the website, the website is not the problem to solve.

BENCHMARK BRIEFING 1 OF 4

Which Businesses Must Issue E-Invoices in Malaysia, and Since When?

IN BRIEFE-invoicing reached Malaysian businesses in four phases, starting with turnover above RM100 million in August 2024 and reaching turnover up to RM5 million in January 2026. The latest update exempts turnover below RM3 million. If your website takes orders, our guide to e-commerce website development covers the wider build.

The table lists each phase by annual turnover band and start date, as published by LHDN.

Malaysia E-Invoice Rollout by Annual Turnover Band, 2024–2026
Malaysia e-invoice implementation by annual turnover band. Phase 1: turnover above RM100 million, from 1 August 2024. Phase 2: above RM25 million up to RM100 million, from 1 January 2025. Phase 3: above RM5 million up to RM25 million, from 1 July 2025. Phase 4: up to RM5 million, from 1 January 2026. Taxpayers with annual turnover below RM3 million are exempt, per the timeline updated 30 August 2026. Aggregated by IZI Digital Marketing from LHDN.
Phase Annual turnover band Start date
Phase 1 Above RM100 million 1 August 2024
Phase 2 Above RM25 million, up to RM100 million 1 January 2025
Phase 3 Above RM5 million, up to RM25 million 1 July 2025
Phase 4 Up to RM5 million 1 January 2026
Exempt Below RM3 million Per update of 30 August 2026

Aggregated by IZI Digital Marketing from the LHDN e-Invoice Implementation Timeline, checked September 2026. Thresholds have changed more than once; confirm your status with your tax agent.

Notice how often the lower thresholds moved. Plan your website around your own confirmed status, not around a headline you read last year. A business near the RM3 million line should build so that e-invoicing can be switched on later without a rebuild.

Bottom Line: Check the current LHDN timeline before you brief a developer. Rules that changed twice can change again.

PART 2 · DIAGNOSE

What Does E-Invoice Integration Actually Involve?

IN BRIEFE-invoice integration means order data travels from your website to MyInvois, gets validated, and comes back with a reference your customer can check. Most of the work sits in data mapping and testing, with very little design. Our guide to website hidden costs explains why integration lines are often missing from first quotes.

LHDN offers two ways to send e-invoices, as set out in its overview of the e-Invoice model: the free MyInvois Portal, and an API that connects your own system directly. LHDN notes the API needs upfront investment and suits businesses with large transaction volumes. For a website, an integrated flow usually runs like this:

  1. Capture the order. The checkout records what was sold, the price, the tax treatment and, for business buyers, their details.
  2. Build the invoice data. The site, or the accounting system behind it, turns the order into LHDN’s required e-invoice format.
  3. Submit for validation. The data goes to MyInvois through the API or a connector, and LHDN checks it.
  4. Return the proof. A validated e-invoice carries a unique reference and QR code that the buyer can use to verify it.
  5. Handle changes. Refunds, cancellations and corrections follow the rules in LHDN’s e-Invoice guidelines, including a short 72-hour window for cancelling or rejecting a validated invoice.

Step five is where cheap builds fall apart. A refund that works in your store but never reaches MyInvois leaves your records and LHDN’s out of step, and someone has to fix it by hand.

Bottom Line: Judge an integration by how it handles refunds and corrections, not by how neatly it sends a normal sale.

BENCHMARK BRIEFING 2 OF 4

How Do the Main Website E-Invoice Routes Compare?

IN BRIEFWebsites reach MyInvois by one of four routes: manual portal entry, an accounting-software connector, a store plugin or middleware service, or a direct API build. Each trades set-up effort against weekly effort. Your store platform narrows the choice, as our comparison of Shopify vs WooCommerce explains.

The ratings below compare the four routes on set-up effort, ongoing effort and volume fit.

Illustrative Comparison of Website E-Invoice Integration Routes
Illustrative comparison of four website e-invoice integration routes. Manual MyInvois Portal entry: very low set-up effort, high ongoing effort, fits a handful of invoices a month. Accounting-software connector: low set-up effort, low ongoing effort, fits businesses whose store already syncs to accounting software. Store plugin or middleware service: medium set-up effort, low ongoing effort, fits standard online stores. Direct API build: high set-up effort, lowest ongoing effort, fits high volumes or custom systems. Illustrative model by IZI Digital Marketing.
Route Set-up effort Ongoing effort Best fit
Manual MyInvois Portal Very low High A handful of invoices a month
Accounting-software connector Low Low Store already syncs orders to accounts
Store plugin or middleware Medium Low Standard online stores
Direct API build High Lowest High volumes or custom systems

Illustrative model by IZI Digital Marketing, built on LHDN’s description of the Portal and API transmission options and typical Malaysian website set-ups in 2026. Relative ratings, not measured results.

The highlighted route is often missed. If your store already sends orders to accounting software, and that software handles e-invoicing, the website may need only a clean sync rather than its own integration.

Bottom Line: Check what your accounting software already does before paying anyone to build a second path to LHDN.

PART 3 · DESIGN

MyInvois Portal, Plugin or API: Which Route Fits Your Website?

IN BRIEFChoose the MyInvois Portal when online sales are few, a connector when your accounting software already handles e-invoicing, a plugin for a standard store, and an API build only when volume or custom systems demand it. Plugins add upkeep, as our guide to e-commerce plugins worth paying for explains.

The right route depends less on the size of your business and more on how many website sales need an individual e-invoice each month. Find your situation below:

DECISION BOX · WHICH E-INVOICE ROUTE SHOULD YOUR WEBSITE USE?

Your situation Better fit Why
Website only collects enquiries No website integration Invoices are raised in accounting software after the sale
A few online B2B orders a month MyInvois Portal Free and quick; manual work stays small
Store syncs orders to e-invoice-ready accounts Accounting connector The accounts system does the LHDN work already
Standard online store, steady daily orders Store plugin or middleware Automates volume without custom code
Custom platform, portal or very high volume Direct API build Only a direct link fits non-standard data flows

Verdict: Start with the lightest route that covers your volume. Move up a route only when manual work or errors start costing more than the next step would.

Consultant’s Note: The most expensive mistake we see is running two routes at once: a website plugin and an accounting system both sending the same sale to MyInvois. Before you approve any build, write down which single system owns e-invoicing, and make every other system feed it.
Bottom Line: Pick one system to own e-invoicing. The website’s job is to feed it clean data, not to compete with it.

BENCHMARK BRIEFING 3 OF 4

Where Does the Effort in an E-Invoice Integration Go?

IN BRIEFIn our model, set-up and data mapping take the largest share of a plugin project, while testing and edge cases dominate a direct API build. Checkout changes stay small in both. That split explains why integration quotes vary so widely, as our guide on what a bigger web design budget actually buys shows.

Each bar splits project hours into set-up and data mapping, checkout and form changes, and testing and edge cases.

Illustrative Split of Project Hours by E-Invoice Integration Route
Illustrative split of project hours by website e-invoice integration route. Accounting-software connector: 60 percent set-up and data mapping, 10 percent checkout and form changes, 30 percent testing and edge cases. Store plugin or middleware: 50 percent, 20 percent, 30 percent. Direct API build: 40 percent, 15 percent, 45 percent. Illustrative model by IZI Digital Marketing.
Route Set-up and mapping / checkout changes / testing and edge cases
Accounting connector

60% / 10% / 30%

Store plugin or middleware

50% / 20% / 30%

Direct API build

40% / 15% / 45%

Illustrative model by IZI Digital Marketing, built on typical Malaysian website integration scopes in 2026. Colour order: set-up and data mapping (rust), checkout and form changes (slate), testing and edge cases (grey). Shares of total project hours; planning assumptions, not measured results.

Testing takes so much of an API build because every refund, discount, shipping fee and cancellation needs its own path to MyInvois. A quote that shows almost no testing time is a quote that expects you to find the bugs.

Bottom Line: Ask how many hours an integration quote gives to testing. For an API build, it should be close to half.

Holding an integration quote you cannot read?

Send it over. We will point out which route it assumes and what testing it leaves out. Review my integration quote

PART 4 · DEPLOY

What Should Your Website Collect at Checkout for E-Invoicing?

IN BRIEFYour checkout should let business buyers request an e-invoice and give their tax details, without forcing every consumer through extra fields. An optional “I need an e-invoice” tick box keeps checkout short. Collecting tax IDs is personal data, so read our guide to PDPA website compliance first.

Good e-invoice checkouts ask only the buyers who need an e-invoice for extra details. Build these pieces into the brief:

  • An optional e-invoice request. A tick box that reveals extra fields only for buyers who want an e-invoice in their own name. Everyone else checks out as normal.
  • The buyer’s tax details. Typically the buyer’s tax identification number, registration or identity number, SST number where relevant, address and contact details, as listed in LHDN’s e-Invoice guidelines.
  • A way to request one after purchase. Some buyers only remember after paying. A link in the order email saves your team a stream of WhatsApp requests.
  • Clear privacy wording. Say why you collect tax details and how you store them, in line with your privacy notice.
  • Payment data that matches. Your gateway’s records must agree with the invoice amount; our guide to payment gateways for Malaysian stores covers what each one reports.

Sales where the buyer does not ask for an e-invoice can usually be grouped into a consolidated e-invoice each month under LHDN’s rules. That keeps consumer checkout fast while business buyers still get what their own accounts team needs.

Bottom Line: Make e-invoice fields optional and conditional. A longer checkout for every buyer costs sales you will never see.

BENCHMARK BRIEFING 4 OF 4

When Does Manual MyInvois Entry Stop Making Sense?

IN BRIEFIn our model, keying individual e-invoices into the MyInvois Portal takes about 2.5 hours a month at 50 invoices, but about 50 hours at 1,000. Past roughly 200 a month, manual entry becomes a part-time job. That running cost belongs in your yearly budget, as our guide to the cost of running a website explains.

Each bar shows staff hours a month spent keying individual e-invoices by hand, assuming about three minutes per invoice.

Illustrative Monthly Staff Hours for Manual MyInvois Portal Entry by Invoice Volume
Illustrative monthly staff hours for manual MyInvois Portal entry by number of individual e-invoices per month, at about three minutes per invoice. 50 invoices: 2.5 hours. 200 invoices: 10 hours. 500 invoices: 25 hours. 1,000 invoices: 50 hours. Illustrative model by IZI Digital Marketing.
Individual e-invoices a month Staff hours a month
50

2.5

200

10

500

25

1,000

50

Illustrative model by IZI Digital Marketing, assuming about three minutes to key and check one individual e-invoice in the MyInvois Portal, excluding corrections and consolidated monthly e-invoices. Bar widths are scaled to the highest value. Planning assumptions, not measured results.

The highlighted row is a useful trigger. At around 200 individual e-invoices a month, manual entry takes more than a full working day. Compare that recurring cost, plus the risk of typing errors, against a one-off integration project and its yearly upkeep.

Bottom Line: Count your individual e-invoices for one month. The number tells you more than any vendor’s pitch.

PART 5 · DRIVE

How Do You Scope E-Invoice Integration Before Asking for Quotes?

IN BRIEFScope e-invoice integration by writing down your platform, monthly invoice volume, which system owns e-invoicing, and how refunds are handled, before any developer quotes. A written brief makes quotes comparable. Our guide to writing a digital marketing RFP shows how to structure one.

Put these items in your brief so every provider quotes the same job:

  1. Platform and plugins. Name your store platform, its version and the accounting software it connects to.
  2. Volume. State your monthly count of individual e-invoices and consolidated sales, from the exercise above.
  3. System of record. Say which single system will submit to MyInvois.
  4. Edge cases. List refunds, partial refunds, discounts, deposits and shipping charges that must be handled.
  5. Testing and support. Ask for LHDN sandbox testing before go-live and a named contact for fixes when LHDN updates its rules.

Campaign sites deserve a mention too. If you plan a short-term promotion site that takes payments, ask early whether it must feed the same e-invoice flow; our guide on whether you need a microsite covers that trade-off. Ongoing checks belong in your website maintenance plan, and our e-commerce website page explains how store builds handle integrations.

Bottom Line: A clear integration brief is the cheapest part of the project, and it protects every ringgit that follows.

THE VERDICT

Integrate When the Numbers Say So

E-invoice integration is worth doing when your business is in scope, your website creates the sale, and manual entry has become real work. For most businesses, the decision comes down to five moves:

  1. Confirm your status against the latest LHDN timeline.
  2. Check where the sale happens before touching the website.
  3. Pick one system to own e-invoicing.
  4. Count individual e-invoices to choose the route.
  5. Brief in writing, including refunds and testing.

To see how integration work fits into a wider build budget, read our guide to website design price in Malaysia, or our website design page.

FAQ

Frequently Asked Questions

1. What is e-invoice integration for a website?

It is a link that sends your website’s sales data to LHDN’s MyInvois system for validation. It depends on your set-up: some websites send data directly, others go through accounting software, but both remove the need to retype orders.

2. Does every business website need e-invoice integration?

No. It depends on whether your business is in scope and whether the website itself creates sales. A site that only collects enquiries usually needs no integration, because invoices are raised elsewhere.

3. Is the MyInvois Portal enough for a small online store?

Often, yes. It depends on how many buyers ask for individual e-invoices, but a store issuing a few dozen a month can usually key them into the free portal without much strain.

4. When should I pay for an API integration?

Only when volume or a custom system makes lighter routes impractical. It depends on your platform, but most standard stores are better served by a connector or plugin first.

5. Do consumers need to give tax details at checkout?

Usually not. It depends on whether they want an e-invoice in their own name; sales without a request can generally be grouped into a consolidated e-invoice under LHDN’s rules.

6. Can a refund break my e-invoice records?

Yes, if the integration ignores it. It depends on how refunds are built, so ask any provider to show how cancellations, credit notes and partial refunds reach MyInvois.

7. Who should I ask first, my web designer or my tax agent?

Your tax agent. It depends on your turnover and business structure, which your agent can confirm; your web designer then decides how the website supports those rules without slowing checkout.

Want a clear plan for e-invoicing on your website?

Book a free Blueprint consultation. We will look at how your website takes orders, show which e-invoice route fits your volume, and help you write a brief that developers can quote fairly.

Book my free consultation

Have a campaign in mind? Let's talk.