How do Malaysian enterprises integrate their ERP with the LHDN MyInvois API?
Malaysian large enterprises must integrate their ERP systems with the LHDN MyInvois API for high-volume automated invoice clearance. Integration options include direct LHDN REST API connectivity, middleware-based integration via certified technology providers, or Peppol-based routing through registered network participants. The integration must handle invoice submission, UIN retrieval, error processing, and 72-hour window management.
What are the integration architecture options for ERP-to-LHDN connectivity?
Three integration architecture patterns are available: (1) Direct API Integration: the ERP or billing system calls the LHDN REST API directly, handling authentication, XML formatting, UIN retrieval, and error processing internally. This requires in-house development or a certified LHDN API connector from the ERP vendor; (2) Middleware Integration: a certified third-party middleware platform (e.g., a specialized e-invoicing hub) sits between the ERP and LHDN, handling format conversion, API connectivity, and error management. This reduces ERP customization but introduces a dependency on the middleware vendor; (3) Peppol Provider Integration: businesses route through a registered Peppol technology provider that connects to LHDN via approved Peppol pathways. This option aligns with the broader Peppol ecosystem but requires both the ERP and the Peppol provider to support LHDN's API protocol.
- Document current ERP billing architecture and available API extension points
- Evaluate direct LHDN API connector availability from ERP vendor (SAP, Oracle, etc.)
- Assess middleware vendors with LHDN-certified connectors
- Review Peppol-based routing option through registered providers
- Define error handling workflow for LHDN validation failures
- Plan UIN storage and association with ERP invoice records
- Implement 72-hour window alerting for pending cancellation/rejection decisions
What testing is required before going live with LHDN API integration?
LHDN provides a sandbox testing environment for API integration testing. Pre-production testing should cover: valid invoice submission and UIN retrieval; mandatory field validation error scenarios; cancellation and rejection workflows within the 72-hour window; credit note and debit note submission; self-billed invoice submission for foreign supplier scenarios; and high-volume load testing to verify the integration can handle peak invoice volumes without timing out or losing transactions.
Frequently Asked Questions
- What XML schema must be used for LHDN API submissions?
- LHDN's e-Invoice Guidelines (version 4.6 as of the latest update) specify the accepted XML schema for API submissions. The schema defines mandatory fields, data types, and business validation rules. LHDN's developer documentation and sandbox environment provide schema files and sample documents for testing. The schema is updated periodically, and businesses must ensure their integration is updated to reflect current schema requirements.
- How should the ERP store and reference LHDN UINs?
- The UIN returned by LHDN after successful invoice validation should be stored in the ERP against the corresponding invoice record as an additional reference field. This ensures that: (1) the UIN can be included in the printed or digital invoice sent to the buyer; (2) future cancellations or adjustments can reference the correct UIN; and (3) audit queries from LHDN can be resolved by cross-referencing ERP invoice records with UIN values.
Related Concepts
- What is the difference between the LHDN API and the MyInvois Portal for e-invoice submission?
- What is Malaysia's LHDN 72-hour e-invoice cancellation and rejection window?
- What are the LHDN Unique Identification Number (UIN) and cryptographic QR code?
- What are Malaysia's self-billing e-invoice requirements for foreign supplier transactions?
- What is Section 134A of the Income Tax Act 1967 and how does it underpin Malaysian e-invoicing?