If you are comparing e-Invoice software in Malaysia, start with the job you need the software to do. Do you need to issue and transmit e-Invoices, check a document's MyInvois validation status, or organize the underlying transaction evidence so a colleague or auditor can review it later? Those jobs touch the same transaction, but they are not interchangeable.
Malaysia's Inland Revenue Board (IRBM/LHDN) describes two e-Invoice transmission mechanisms: the MyInvois Portal and an API. The portal supports individual creation and a prescribed spreadsheet batch upload. API transmission can be handled through a business's own system or a technology provider. A buying decision should establish which route a proposed product actually supports and what the customer still has to do in MyInvois. Source: IRBM e-Invoice Guideline, section 2.2–2.4.
Issue & transmit
Create and submit e-Invoices to LHDN through the MyInvois Portal or an API integration.
Check validation status
Confirm an official IRBM result — identifier, date and status — for a submitted document.
Organize evidence
Keep the source record, context and review decision connected for later use.
First, identify the missing step
| Your question | Capability to check | Evidence to request from the provider |
|---|---|---|
| How will we issue and submit? | MyInvois Portal workflow or an actual API integration | A demonstration of the relevant submission path, supported document types and responsibility for errors |
| How do we know LHDN validated it? | Retrieval or display of official validation results | The IRBM identifier, validation date and status in the appropriate official workflow; handling for an unvalidated document |
| What supports the business transaction? | Source document retention and review | The receipt or contract, linked explanation, exception history and attributed review decision |
| How will our accountant or auditor use the record? | Export and handoff of available evidence | A retrievable original, any corrections, unresolved questions and the basis for decisions |
An OCR scanner can read fields from an image. That can save preparation time, but a correctly read amount cannot by itself establish business purpose or settle an auditor's question.
IRBM validation of an e-Invoice is a specific system outcome. Taxpayers must still retain sufficient records and documentation relating to the transaction even when a validated e-Invoice is stored in its database.
Source: IRBM e-Invoice Guideline, section 2.3.7
For the fuller distinction among MyInvois validation, audit evidence and tax deductibility, read GetZenta's existing guide.
Questions to ask an e-Invoice software vendor
- What is the submission mechanism? Is this an issuing system connected through the API, a tool that helps prepare information for the portal, or an internal review tool? Ask to see the exact handoff.
- What happens when a document is returned unvalidated? Can staff see the error, correct the information and follow the actual resubmission path? A local "ready" flag is not LHDN validation.
- Can we retrieve the original source? Keep the supplier document and related support connected to the transaction rather than only a set of extracted fields.
- Can people challenge and correct output? Ask how OCR suggestions, manual corrections, open exceptions, inquiries and reviewer actions are recorded. A client's response need not settle a reviewer question automatically.
- What can move to the accountant or audit team? Request an example of the actual export or handoff. Check whether the provider offers an integration today or only a proposed workflow.
- Who can access the records? Ask about roles, retention, export, security and how a later reviewer can reconstruct a decision.
A transaction example
Imagine a fictional SME buys equipment and receives a validated supplier e-Invoice. The validation result identifies an official document and status. The finance team still needs to connect the purchase to the underlying order, delivery or other relevant support. If an auditor asks why the equipment was bought, the team should be able to find the source, the question, the response and the review decision without relying on somebody's memory of a chat.
The right supporting material depends on the transaction and the engagement. The example does not determine deductibility, the sufficiency of audit evidence or a compliance outcome.
Where GetZenta fits
GetZenta's published focus is the receipt-evidence and review workflow: connecting source records, extracted information, exceptions, follow-up and human decisions for a clearer handoff. See the Audit Evidence page and Auditor Workflow page for that scope.
If your immediate need is to issue and submit e-Invoices to LHDN, assess the MyInvois Portal or a provider that can demonstrate that issuing path. GetZenta's internal evidence or export readiness should not be interpreted as an official MyInvois validation status or an assertion that GetZenta replaces an issuing system. When comparing tools, ask how the issuer's validated transaction and the supporting records will be handed to the person who reviews the expense.