What happens when LHDN changes the requirements?

The field schema is versioned and configuration-driven. A guidance revision is a configuration change, not a redeployment — which is why we do not hardcode the field set.

Do you handle credit notes, debit notes and self-billed invoices?

Yes. Standard invoices, self-billed invoices, credit notes, debit notes, refund notes and consolidated invoices are all supported.

How does B2C consolidation work in practice?

Consumer sales are aggregated into monthly consolidated invoices according to rules you configure per entity. Transactions at or above RM10,000 are automatically excluded and issued as individual e-invoices, as the rules require.

Do we have to replace our accounting system?

No. The Gateway reads from the system you already run — through its API or a read-only database view — and submits on its behalf. Your team keeps raising invoices exactly as they do today.

Our system isn't on your list. Can you still connect to it?

Usually. Anything that exposes a REST API or allows a read-only database view can be connected. That work is scoped in discovery so you know what is involved before committing.

What happens to a submission that fails?

It lands in the error queue with the LHDN error translated into plain English and the offending field identified. Transient failures retry automatically; anything needing a decision waits for a human.

Where is our data stored?

In the region you choose — Malaysia, Singapore or Australia — set at tenant level. There is no cross-region data movement.

Can our own team change the field mappings?

Yes. Mappings, validation rules and consolidation rules are all editable in the admin UI. If only we could configure it, you would own a support dependency forever.

Compliance

MyInvois ComplianceWithout Replacing Your System

Submit LHDN-compliant e-invoices at volume from SQL Accounting, AutoCount, QNE or a custom ERP — with TIN validation, B2C consolidation, and an error queue that tells you what actually went wrong.

Request a demo See how it works

Counted, not claimed

MyInvois fields mapped

Document types supported

Accounting systems, plus custom ERP

Certified against the LHDN sandbox before any go-live

CHALLENGE & APPROACH

The problem, and how we solve it

The Challenge

The grace period ends 31 December 2027, and most accounting systems emit only part of what LHDN asks for. Teams end up filling the gap by hand — re-keying invoices into the MyInvois portal, chasing missing tax numbers, and re-submitting rejections they cannot interpret.

Rejected submissions returning error codes nobody in the business can translate
A customer master full of missing, malformed or unvalidated TIN and SST numbers
B2C sales volume that cannot realistically be invoiced one transaction at a time
No audit trail in a form an LHDN inspection would accept

Our Approach

The Gateway sits between your system of record and MyInvois. It maps your fields to the required schema, validates before submission rather than after rejection, consolidates B2C sales to the rules you set, submits, retries what fails, and keeps the audit trail. Your accounting system stays exactly where it is.

Why This Product

Keeps your existing system — this is a gateway, not a migration
Validates before submission, so rejections are caught while they are still cheap to fix
LHDN errors translated into plain English with the field that caused them
Field schema is versioned — a guidance revision is a config change, not a redeployment
Audit trail export built for inspection, not reconstructed after the fact

Who It's For

Finance teams facing the mandate with an accounting system that only partly supports it
High-volume B2C sellers who need consolidated invoicing to be workable
Businesses running SQL Accounting, AutoCount, QNE or Million
Multi-entity groups submitting under more than one TIN
Anyone who has tried the MyInvois portal manually and done the arithmetic

KEY FEATURES

What e-Invoice Compliance Gateway does

Field mapper

Maps your source fields to all 55 MyInvois fields
Configurable per client, per document type
Versioned schema — revisions land as configuration

TIN validation & taxpayer lookup

Validates tax numbers before submission, not after rejection
Taxpayer lookup against the LHDN register
Flags mismatches against your customer master

Master data cleanup

Audits customer TIN, SST and business registration numbers
Bulk fix UI for correcting records in batches
Run before go-live so the first submission is not the discovery

B2C consolidation engine

Aggregates consumer sales into monthly consolidated invoices
Consolidation rules configurable per entity
Scheduled to your submission window

RM10,000 rule handler

Flags transactions at or above the threshold automatically
Forces an individual e-invoice instead of consolidation
Applied at capture, so exceptions do not reach the deadline

Error queue

LHDN errors translated into plain English
Points at the field and record that caused the failure
Automatic retry with a dead-letter queue for what needs a human

Submission dashboard & audit export

Submitted, validated, rejected and pending, per period
QR code and validated-invoice PDF for customer delivery
Full audit trail export for LHDN inspection

On the roadmap — not yet shipped

InvoiceNow (Singapore, Peppol BIS) adapter — same core, different profile
Multi-entity and multi-branch consolidation
Monthly compliance health report, generated automatically

HOW IT WORKS

How it works

Extract from source

Invoices are read from your accounting system, POS or ERP through its API or a read-only database view. Nothing about how your team raises an invoice changes.

Map & validate

Your fields are mapped to the MyInvois schema and checked — TIN validity, required fields, formats, arithmetic. Problems surface here, before LHDN sees them.

Consolidate or split

B2C sales are aggregated into consolidated invoices on your rules; anything at or above RM10,000 is pulled out and forced to an individual e-invoice.

Sign & submit

Documents are digitally signed and submitted to MyInvois within your submission window, with per-tenant rate limits respected.

Poll, retry, archive

Status is polled until validated. Failures are translated and queued for correction. Everything is archived with the audit trail an inspection needs.

INTEGRATIONS

Connects to what you already run

Accounting & ERP

SQL Accounting
AutoCount
QNE
Million
Xero

Built in this order — ask where your system sits in the queue.

Point of sale

POS systems via API or export

Custom systems

REST API
Read-only database view

Running something that isn't listed? Tell us what it is — anything with an API or a read-only database view can usually be connected.

TRUST & CONTROLS

Built for the audit, not just the demo

Versioned field schema

LHDN guidance revises frequently. The schema is versioned and configuration-driven, so a revision is a configuration change rather than a redeployment.

Sandbox certification

Every deployment is certified against the LHDN sandbox before a single live invoice is submitted.

Digital signature handling

PKCS#12 certificate handling with XAdES signing, per entity.

Data residency

Malaysia, Australia or Singapore — set per tenant. No cross-region data movement, ever.

Audit log

Every read and write of your data is logged, exportable, and retained to your policy.

Human approval gate

Nothing writes to your system of record without someone approving it. That is a product rule, not a setting.

PII handling

No personal data in logs. Prompts are redacted before they are stored, and credentials are isolated per tenant.

WHERE IT FITS

Who runs this, and why

Distributors & wholesalers

High invoice volume across many trade customers, with the tax master data to match. Validation and cleanup carry most of the weight here.

Retail & F&B chains

Thousands of consumer transactions a day that only work as consolidated invoices — with the RM10,000 exceptions pulled out automatically.

Manufacturers

Self-billed invoices, credit notes and debit notes alongside standard invoicing, often under more than one entity.

Professional services firms

Lower volume, higher scrutiny. The audit trail export and per-period submission dashboard matter more than throughput.

HOW WE DELIVER

What happens after you get in touch

01
Discovery
A paid diagnostic that maps your systems, takes a real data sample, and captures the baseline metric. Without a baseline measured before go-live, no one can prove what changed afterwards.
02
Configure
Connectors, field mappings, validation rules and templates set up against your systems — configured for how you actually work, not rebuilt from scratch.
03
UAT & parallel run
The system runs alongside your existing process for two to four weeks. You see the delta on your own data before anything is switched over.
04
Handover
Training, a runbook and documentation — plus the admin UI, so your team can change mappings and rules without coming back to us.

Start with a discovery call

We'll come back to you within 48 hours.

Start Your Project

Let's work together,
get started.

Tell us about your project. We'll respond with a tailored proposal within 48 hours — no templates, no salesperson.

No commitment required
Response within 48 hours
Signed NDA on request

Ready to take your business to the next level? Send us a message and see how we can help.