E-Invoicing (MyInvois / LHDN)
Malaysia e-invoicing compliance — integrate with LHDN MyInvois, no disruption to your workflow.
E-invoicing solutions for Malaysia's LHDN MyInvois mandate. We integrate e-invoice generation and submission directly into your existing systems, so you stay compliant without changing how you work.
Best for: Malaysian businesses meeting the e-invoicing mandate.
What you get
Who needs a custom MyInvois integration?
A custom integration is for Malaysian businesses that need LHDN e-invoicing to work with an existing e-commerce platform, ERP, POS, or internal system. It is especially relevant when invoice data already moves through several systems and manual re-entry would create another operational step.
Can MyInvois connect to the systems we already use?
Yes, where the required system access and data are available. We map where a sale or invoice originates, which fields each system holds, how records are identified, and where the validated invoice needs to return before designing the integration layer.
Does MyInvois compliance require an MDEC-accredited provider?
Not for the integration work itself — but accreditation is required if the business also needs Peppol delivery. Complying with the LHDN MyInvois mandate means submitting valid documents to MyInvois, either through the MyInvois Portal or through the MyInvois API, and LHDN publishes an SDK and a sandbox for the API route. Integrating a system you already run with that API is the work, and it does not require any accreditation. MDEC is Malaysia's Peppol Authority, and its accreditation covers Peppol Access Point and Peppol Service Provider work — exchanging documents over the Peppol network. So the question worth settling early is whether you need MyInvois clearance only, or Peppol delivery as well because a trading partner requires it. Where Peppol delivery is required, that part has to go through an MDEC-accredited provider, and it is a separate requirement from clearing the document with MyInvois. DayDreamer's part is the integration: building e-invoice generation and submission into the systems you already run, as we did for HOOGA.
What does the e-invoice flow handle?
The flow can prepare invoice data, submit it to LHDN MyInvois, receive the validation status, and keep the relevant reference with the business record. Exact handling for rejections, cancellations, or other exceptions is defined around the systems and process in scope.
Will e-invoicing disrupt the existing checkout or workflow?
It does not have to. For HOOGA, DayDreamer connected the online store, LHDN, and the internal system behind the existing order flow, so customers continued to shop as before while e-invoicing happened as part of the order.
How are access and operational controls handled?
We scope the credentials, permissions, invoice data, logs, and exception handling the integration requires. Responsibilities for reviewing rejected submissions and maintaining source data are agreed with the business before the production flow is launched.
Who owns the integration code, and who maintains it when MyInvois changes?
Ownership of the integration code, the invoice data, and the accounts and configuration it runs on is set out explicitly in the project agreement before development starts. The agreement should distinguish your business and invoice data, the newly written integration code, any pre-existing or third-party components and their licences, the credentials and accounts used to submit to LHDN MyInvois, and the deployment configuration. Maintenance is agreed in the same place: who is responsible for keeping the flow working when the MyInvois specification or one of your own systems changes, and what handover or ongoing support covers, so the operating model is not left ambiguous.
How do you handle PDPA, hosting, and data residency for e-invoice data?
We treat PDPA, hosting region, and data residency as architecture requirements for the e-invoicing flow, not blanket marketing claims. Invoice records can carry customer and business personal data, so during scoping we map which fields the integration processes, which systems and services they pass through, what is stored or logged, and how long it is kept. Any requirement to host in Malaysia or another named region must be stated before the architecture is agreed, so the provider, region, retention, and the client's own legal-review responsibilities can be written into the project scope.
What determines delivery and commercials?
They depend on the number of systems, available APIs, invoice types, data readiness, exception paths, and testing required. We assess those dependencies first and provide a fixed proposal for the integration and delivery stages that are actually needed.
How we work
Daydream
We scope your idea and define what 'good' looks like.
Design
We shape the experience and architecture before writing code.
Build
We engineer AI-native software with intelligence woven in.
Ship
We launch on scalable cloud, then measure and refine.
Proof
Frequently asked questions
Can DayDreamer connect LHDN MyInvois to our e-commerce or internal system?+
Yes. For HOOGA we connected its WooCommerce store, LHDN's e-invoicing system, and its internal system so an online order could be submitted for validation and recorded internally in one flow.
Do we need to replace our existing platform to implement e-invoicing?+
Not necessarily. We can build an integration layer around systems that already work, provided they expose the access and invoice data the flow needs. HOOGA kept its existing checkout and internal system.
Can the integration handle rejected or incomplete submissions?+
Exception handling is designed as part of the integration. We define how statuses return, what is logged, and which cases need a person to correct source data or review the submission before it is sent again.
Related services
Have something you want to build?
Tell us about it and we'll come back with a clear, fixed plan for a fully custom build.