This is an overview of the e-Invoice workflow from the point a sale is made or transaction undertaken, and an e-Invoice is issued by the supplier via MyInvois Portal or API, up to the point of storing cleared e-Invoices on LHDNM’s database for taxpayers to view their respective historical e-Invoices.

The focus of our solutioning is the e-Invoice model via API.

API allows taxpayers to submit e-Invoices directly to LHDNM. Taxpayers would need to configure the API integration by setting up call-backs (specific taxpayers system addresses) and log into the available LHDNM APIs via the Digital Certificate issued by LHDNM (authentication mechanisms).

The e-Invoice structure has been specifically designed to cater to B2B, B2G and B2C transactions to ease e-Invoice procedures for businesses and individual taxpayers. The following formats will be available for transmission of e-Invoice data:

The first is Extensible Markup Language (XML): XML is defined as a simple text-based format for representing structured information. It is one of the most widely used formats for sharing field structured information today. The syntax rules for XML are strict. It will not process files that contain errors and error messages will be sent to inform that rectification is required. Almost all XML documents can be processed reliably by computer software.

The second is JavaScript Object Notation (JSON): JSON is a lightweight text-based data interchange format that is simpler to read and write as compared to XML. Though it is derived from a subset of JavaScript, it is language independent. Therefore, the code for generating and parsing JSON data can be written in any other programming language.