Business · E-invoicing

E-invoicing is an integration project. Treat it like one

LHDN's e-invoice rollout has reached smaller businesses in phases, with revised dates and thresholds along the way. The compliance deadline is the visible part. The work is connecting the systems where your sales actually happen.

Pikabyte Engineering 4 min read

RM5M

the revenue band below which LHDN deferred mandatory e-invoicing to 1 January 2026

Malaysia’s e-invoicing mandate has rolled out by revenue band since August 2024, starting with the largest taxpayers. In June 2025 the Inland Revenue Board revised the schedule for smaller businesses: implementation for taxpayers with annual revenue below RM5 million was deferred to 1 January 2026, and it announced an exemption for the smallest taxpayers, then set at annual revenue below RM500,000.

Dates, thresholds and relaxation periods have been adjusted more than once since the programme began. Check the Inland Revenue Board’s own implementation timeline for your current position before you plan anything. It is linked at the end.

What has not changed is the nature of the job. E-invoicing is not a form you fill in. It is a requirement that every sale your business makes ends up as a validated, structured record with the tax authority. If your sales happen in more than one place, that is an integration project.

Where the work actually is

A business rarely has one source of invoices. It has an accounting package, and then:

  • an operations system where jobs or orders are completed
  • a point of sale
  • an online store or marketplace
  • a spreadsheet someone raises quotations and invoices from
  • invoices typed by hand for the unusual cases

The accounting software vendor will handle submission from the accounting package. The question is how everything else gets into the accounting package, completely and correctly, without someone typing it twice.

That re-keying step is where invoices go missing, amounts differ and customer details do not match. Under e-invoicing those are no longer internal annoyances. They are rejected submissions.

Connect the source system to accounting

The fix is to make the system where the work is done create the invoice.

We did this for a law firm running banking litigation. Billing events occur inside the litigation platform: a stage completed, a document filed. The platform creates the invoice in the firm’s SQL Accounting system through its API, directly from the matter record. Nobody copies figures across. The invoice has the right client, matter and amount because it is generated from the same record the work was done on.

The same approach applies to a distributor’s order system, a clinic’s billing or a manufacturer’s delivery orders. Whatever event means “we are owed money” should raise the invoice automatically.

Five things that go wrong

1. Customer master data. E-invoices need accurate buyer details, including tax identification numbers. Most customer lists were never built for that. Clean it before go-live, and capture the fields at onboarding from now on.

2. Consolidated versus individual invoices. Retail sales to consumers who do not request an e-invoice can generally be consolidated. Business customers will ask for their own. Your systems need to handle both, and to issue an individual e-invoice after the fact when asked.

3. Credit notes and corrections. Once validated, and past the short cancellation window, an e-invoice is not edited. It is corrected with a further document such as a credit note. Operational systems that let staff silently change a past invoice need to change.

4. Failure handling. Submissions will sometimes be rejected or the service will be unavailable. There must be a visible queue of what did not go through, with reasons, and someone responsible for clearing it.

5. The manual exceptions. The invoice typed in Word for a one-off job is the one that gets forgotten. Route every invoice through one system, without exception.

Where AI helps, and where it does not

Helps: reading supplier invoices into your system, matching them to purchase orders, and filling gaps in customer data from documents you already hold. These are reading tasks, with a person confirming.

Does not help: the submission itself. That is structured data to a defined specification. It should be deterministic code, tested, with every submission logged.

An order of work

  1. List every place an invoice or receipt is created.
  2. Decide the single system of record for invoices, usually the accounting package.
  3. Connect each source to it so invoices are created automatically.
  4. Clean customer and product master data.
  5. Build the exception queue and assign an owner.
  6. Run in parallel for a month before relying on it.

Done this way, e-invoicing compliance is a side effect of something worth having anyway: every sale recorded once, correctly, at the moment it happens.

Sources

This article is general information and is not tax advice.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.