Connecting AutoCount, SQL and QNE to MyInvois without replacing them

If you run AutoCount, SQL Account or QNE, you have probably been told you need to "upgrade for e-invoicing". In most cases that is not true. What you need is a working connection between the system you already use and LHDN MyInvois.

What the mandate actually requires

E-invoicing is a legal requirement, not a software preference. Invoices must be submitted to MyInvois for real-time validation, and each one carries 55 required data fields and a digital signature issued by LHDN.

Two dates matter for most SMEs. From 1 January 2026, individual e-invoices became mandatory for transactions above RM10,000, which means consolidated invoices no longer cover those. Businesses in the RM1 million to RM5 million turnover band fall under Phase 4, where mandatory compliance began January 2026 with a relaxation period running to the end of 2027.

Three ways to submit

• MyInvois Portal. Free, manual, fine at low volume. Someone keys in each invoice.
• Integrated accounting software. AutoCount, SQL, QNE, Million and Xero all have MyInvois modules. Best fit for most SMEs.
• Direct API or PEPPOL. For high volume or custom ERP. Needs developer resource or a certified provider.

The second option is where most Malaysian businesses land, and it is also where most of them get stuck.

Where it actually breaks

Activating the MyInvois module is the easy part. The problems show up in the data around it.

• Customer and supplier records are missing TIN numbers and SST registration numbers.
• Inventory items have no MSIC classification codes.
• Sales happen in a POS or an order system that never talks to the accounting software, so invoices get keyed twice.
• Rejections come back and nobody has a process for the 72 hour correction window.

That last one catches people. A rejected invoice is not a filed invoice. If nobody is watching the rejection queue, you can be non compliant without knowing it.

What middleware does

Middleware sits between the systems you already run and MyInvois. It pulls the invoice data, fills the gaps, submits, catches the response, and writes the validated status back. Nobody re-keys anything.

In practice this is the same problem as any other integration work. Your order system, your accounting software and LHDN each hold part of the picture, and someone in your team is currently the bridge between them. That is the part worth automating.

This is the disconnected systems problem in a nutshell.

A sensible sequence

• Confirm your phase using audited turnover, not an estimate.
• Register the company on MyInvois through MyTax and generate API credentials if you are going the software route.
• Clean master data first. TINs, SST numbers, MSIC codes. This is the slow part and it cannot be skipped.
• Run parallel for about 30 days. Issue both the old document and the e-invoice, and reconcile rejections.
• Switch over, then review the rejection queue weekly.

The honest summary

You do not need new accounting software. You need your existing systems to talk to each other and to LHDN without a person in the middle. Most of the cost and most of the delay sits in data cleanup, not in the technology.

Confirm anything time sensitive directly with LHDN, since thresholds and relaxation windows have already changed more than once.