MyInvois API integration, from your ERP to LHDN.
Invoices are issued as usual. Submission, statuses and rejections are handled in the background.
A MyInvois API integration pulls invoices from AutoCount or your ERP, checks the fields MyInvois expects, submits them through the e-invoice API and writes their statuses back. Rejections and missing buyer details go to the person who can fix them.
- Connected to AutoCount or your ERP
- Checked before submission
- Rejections to your team
No upfront consultation fee. Free discovery and a free tailored proposal.
42 sales invoices pulled from AutoCountDone- Required fields and tax codes checked42 passed
- Buyer TINs validated1 missing
- 41 invoices submitted through the APIDone
- Statuses returned and written backValidating
Every invoice now makes a second trip, to LHDN.
For businesses in scope, invoices have to be submitted to MyInvois and validated. Done by hand, that means exporting, uploading to the portal, reading each result and chasing missing buyer details, one invoice at a time.
Before: the portal, by hand
- Export invoices from the accounting system
- Upload them to the MyInvois portal
- Check each validation result
- Chase sales for missing buyer TINs
- Copy validation links back to invoices
After: the e-invoice integration
- Invoices picked up as they are issued
- Required fields and buyer TIN checked
- Submitted to MyInvois through the API
- Rejected or incomplete invoices fixed by staffYour team
- Status and validation link written back
Finance only touches the invoices that need a fix. The rest are submitted and recorded without anyone opening the portal.
From invoice issued to validated.
What a MyInvois e-invoice integration does after an invoice is issued, and roughly when. The clock times are illustrative; submission rules and timeframes are set by LHDN and change, so we build to the current guideline.
- 09:00Invoice issued
Sales admin issues the invoice in AutoCount or your ERP, exactly as today.
Your team - 09:02Checked and submitted
Required fields, tax codes and the buyer TIN are checked, then the invoice is submitted through the e-invoice API.
Automated - 09:03LHDN returns a status
Valid or invalid, with the reason. The validation link and ID are written back to the invoice.
Automated - 09:05Rejections routed
Invalid invoices go to whoever can fix them: sales admin for buyer details, finance for tax codes.
Your team - Same dayFixed and resubmitted
The corrected invoice goes through the same checks and is submitted again.
Automated - WindowCancellations and corrections
Cancelled only within LHDN's cancellation window, otherwise corrected by credit or debit note. Check the current guideline.
Your team
E-invoice requirements are set by LHDN and change over time. We build the integration; how the rules apply to your business is for you and your tax adviser to confirm.
The integration submits. Your team fixes what's rejected.
Routine submissions run in the background. Decisions about customers, tax treatment and corrections stay with the people accountable for them.
- Picking up invoices, credit and debit notes as issued
- Checking required fields and tax codes
- Validating buyer TINs before submission
- Submitting through the MyInvois API
- Writing statuses and validation links back
- Missing or wrong buyer details
- Invoices LHDN marks invalid
- Cancellations and corrections
- Consolidated and self-billed invoice decisions
- How the rules apply, with your tax adviser
E-invoice status, todayExampleRejected invoices reach a person, with LHDN's reason attached.
- Guesses a buyer's TIN or tax details
- Cancels a validated invoice on its own
- Decides how LHDN rules apply to you
From your books to the LHDN MyInvois API and back.
Invoices keep being issued where they are today. The integration sits between your system and MyInvois and records every submission and response.
AutoCountERPPOS or online store
GmailStatus reportMyInvois requirements and AutoCount's e-invoice features change over time, so we confirm the current API, credentials and your software version during discovery.
AutoCount & e-invoice automation →What businesses report after moving to e-invoicing.
A published result from a company that automated its e-invoicing, and the scale of MyInvois in Malaysia today.
A Singapore logistics company after moving to e-invoicing.
The same company, for some of its documents.
LHDN reports over 1 billion e-invoice transactions and more than 200,000 taxpayers on MyInvois (February 2026).
- Invoices submitted without a person
- First-time validation rate
- Time from issue to validated
- Rejections by reason
- Open rejections at month-end
What shapes an e-invoice API integration.
Every business issues invoices from a different mix of systems. These factors shape the integration and the effort involved.
- Source systems
- AutoCount, another ERP, POS or online store, and their versions.
- Document types
- Invoices, credit and debit notes, refunds and self-billed documents.
- Volume and timing
- Invoices per day, peaks and consolidated B2C submissions.
- Buyer data
- How complete customer TINs and registration details are today.
- Credentials
- API access, digital certificate and any intermediary set-up.
- Your tax adviser
- How they read LHDN's guideline for your business and documents.
MyInvois API integration questions.
Straight answers about scope, data, ownership and support. Can’t find yours? Ask us directly below.
What is a MyInvois API integration?
It is a connection between the system you invoice from and LHDN's MyInvois, so invoices are submitted by API instead of uploaded by hand. Each invoice is checked for required fields, tax codes and the buyer TIN, then submitted, and its status and validation link are written back. Invoices that fail go to the person who can fix them.
Does an e-invoice integration make us compliant?
It handles submission, but compliance stays with your business. LHDN sets the e-invoice requirements and changes them over time, so we build to the current guideline. How the rules apply to your documents, such as consolidated or self-billed invoices, is for you and your tax adviser to confirm.
Does it work with AutoCount or our ERP?
Yes, depending on your AutoCount version and modules. If AutoCount already submits your e-invoices, we can add pre-submission checks, rejection routing and status reporting around it. Other ERPs, POS systems and online stores connect through their API or a regular export, and we confirm your software version during discovery.
What do we need to use the LHDN MyInvois API?
API credentials for MyInvois and, depending on your set-up, a digital certificate or an intermediary. We check which applies to your business, help you put access in place and test submissions in LHDN's sandbox environment before going live, so your first real invoices are not the test.
What happens when LHDN rejects an invoice?
It goes to the person who can fix it, with LHDN's reason attached. Missing buyer details go to sales admin and tax code problems to finance, then the corrected invoice is checked again and resubmitted. Cancellation is possible only within LHDN's cancellation window; after that, a credit or debit note is prepared for your approval.
How is this different from off-the-shelf e-invoice software?
It fits around the systems you already invoice from rather than replacing them. Some e-invoice software in Malaysia asks you to issue invoices inside its own tool, and uploading through the portal by hand means checking each result yourself. This keeps invoicing in AutoCount or your ERP and adds checks, routing and reporting around submission.
How are buyer TINs and personal details protected?
Buyer TINs are checked before submission using LHDN's validation where available, and missing or invalid ones go to sales admin rather than being guessed. Buyer details are handled under PDPA, access is limited to staff who need it, and API credentials are stored securely. Every submission and response is logged.
What does it cost, and how long does it take?
It depends on your source systems, the document types you issue and your invoice volume, so it is quoted privately after a free discovery session. Timelines follow the same factors and how quickly API access is in place. We start with one system and document type, usually sales invoices, then add credit notes, debit notes and other sources.
More showcases you might like.
Other workflows we have mapped, starting with the ones closest to this one.
Finance & Accounting
Bank reconciliation automation for AutoCount and Xero
Bank lines matched to invoices and ledger entries by your rules, with exceptions queued for finance to approve.
See the workflow →
Accounting Firms
Client portal for accounting firms on WhatsApp
Checklists and reminders on WhatsApp, files filed by client and period, missing items handed to staff.
See the workflow →
Field Services
Field service management software: job sheet to invoice
Completed job sheets, photos and sign-off become a draft invoice the same day, with extras approved by a supervisor.
See the workflow →
E-Commerce
AI product photography for e-commerce
A few product photos in, a consistent set of store, marketplace and banner images out, approved before publishing.
See the workflow →
Marketing Agencies
Marketing dashboard and automated client reporting
Ad and analytics data pulled on schedule, KPIs and anomalies ready, and a draft report for the account manager.
See the workflow →
Healthcare
Clinic appointment system on WhatsApp and phone
Patients book, reschedule and get reminders, after hours too, while clinical questions go straight to staff.
See the workflow →Map your e-invoice process.
Tell us where your invoices are issued and how you submit to MyInvois today. We'll show you what the integration would handle and where your team stays in control. No obligation.