MyInvois Integration: Middleware, Custom Build, or Portal?

Before asking which MyInvois system to buy, ask whether you need one. The LHDN portal is free and fine at low volumes. Middleware earns its keep in the middle. A custom integration pays off when your own systems or volume make manual entry untenable.

We build integrations for a living, and we do not sell a middleware product — which is the reason this comparison can include "you probably do not need to pay anyone" as a real answer.

Do you need to integrate MyInvois at all?

Possibly not. The MyInvois portal is free, and typing invoices into it is perfectly compliant. The question is only ever about volume and where the work lands.

Manual entry stops being sensible somewhere between roughly 20 and 50 invoices a month, in our experience — not because of a rule, but because that is where the person doing it starts making mistakes and the time cost overtakes the software cost. If you issue a handful of invoices a month, the portal is the correct answer and anyone telling you otherwise is selling something.

Two things push you off the portal regardless of volume: invoices that originate in another system (a POS, an e-commerce store, an ERP) where re-typing means keying the same data twice, and any need for near-real-time validation at the point of sale.

What are the three ways to connect to MyInvois?

There are three routes, and they differ in who owns the mapping work rather than in what LHDN receives. LHDN validates the same payload either way.

The distinction that matters commercially: middleware is an ongoing subscription you rent, a custom integration is an asset you own. Neither is automatically right — see white-label versus custom development for the same trade-off in a different setting.

How much does each option cost in Malaysia?

Published figures cluster into fairly clear bands, though every one of them comes from vendor marketing rather than a rate card, so treat them as indicative and current as of July 2026.

Most Malaysian SMEs land between RM5,000 and RM25,000 for middleware or a basic custom integration. The arithmetic worth doing before you sign anything: middleware at RM1,500 a month is RM18,000 a year, which reaches the low end of a custom build inside two years — and at the end of those two years you own nothing.

That comparison flips if your invoice logic is genuinely standard, because then you are renting someone else's maintenance of a moving compliance target, which is a real service and not a rip-off.

When is middleware the wrong choice?

When your data does not fit its assumptions — and this is the section middleware vendors do not write, because the honest answer costs them a sale.

Middleware maps your fields onto LHDN's. That works beautifully when your system looks like the systems it was built for. It goes badly in four situations we see repeatedly:

• Multi-branch POS with per-outlet TINs or SST numbers. Field mapping that assumes one seller entity gets awkward fast.
• Consolidated B2C at scale, where which receipts may be batched depends on transaction values (see below).
• Credit notes, refunds and self-billed invoices, which are separate document types with their own rules and are frequently the weakest part of a middleware implementation.
• A homegrown or heavily customised ERP, where you end up paying to build a custom integration and renting middleware to host it.

If two or more of those describe you, price the custom route properly before subscribing to anything.

What does a custom MyInvois integration actually involve?

More than posting JSON at an endpoint. The work is in the mapping and the signing, not the HTTP call.

Concretely: your data has to be transformed into UBL 2.1 (XML or JSON) covering the 55 data fields IRBM specifies — seller and buyer TINs, SST registration, classification codes, line items, tax breakdowns and totals. Each document is digitally signed with a certificate issued by IRBM, submitted for validation, and the returned validation result has to be stored against your own record. Get the certificate handling wrong and nothing validates; get the field mapping wrong and it validates but says something untrue about your business.

The engineering that actually consumes the budget is the unhappy path — retries when validation fails, reconciliation when your system and MyInvois disagree about what was submitted, and an audit trail you can defend. That is the same class of problem as any custom software that has to stay in step with an external system of record; our AI knowledge base project had the same shape, with a different counterparty.

What breaks after go-live?

The parts nobody demos. Plan for them in the first build rather than discovering them in January.

The RM10,000 rule is the one that surprises people. From 1 January 2026, individual e-invoices are mandatory for transactions above RM10,000, and consolidated invoices are no longer permitted for those amounts (IRBM e-Invoice Guideline). For B2C that means you may batch receipts only when no single sale in the batch crosses the trigger — so your consolidation logic needs a value check, not just a date range. This constrains consolidation independently of the relaxation period, which is a distinction worth getting right.

Beyond that: credit notes and refunds arrive later than you expect and are their own document types; buyers start asking for validated invoices in specific formats; and IRBM's guideline has been revised repeatedly, so whatever you build needs to be cheap to change. Our full MyInvois compliance guide covers who must comply, the phase thresholds and the relaxation window.

We are engineers, not tax or legal advisors. Thresholds, phase dates and field requirements have all been revised more than once — confirm your own position with a licensed tax agent and against the current IRBM guideline before you design around any figure here.

How Firebird AI approaches this

We will tell you if the free portal is enough, because we would rather not build something you do not need. When integration is genuinely warranted, we build it as software you own, against your existing systems, with the reconciliation and audit trail treated as part of the job rather than a later phase.

If you are weighing middleware against a custom build and want an unbiased read on which fits your volume and systems, get a free consultation — including the version where the answer is "keep using the portal for now".