Malaysia EInvoice

April 24, 2024

Questions:

We are struggling to fulfill the EInvoice implementation mandate from Malaysian government, which is on 1st August 2024 (3 months from now). We wish to implement a direct integration from the company system to the government system through API (EInvoice submission and retrieval). After studying the guidance from the government on Digital Signature at …

https://sdk.myinvois.hasil.gov.my/signature/
https://sdk.myinvois.hasil.gov.my/signature-creation/
https://sdk.myinvois.hasil.gov.my/files/one-doc-signed.xml

Our developer team has limited knowledge and experience on fulfilling the digital signing with all the required standards stated in the guides. Thus, I am looking for another solution in order to achieve our objective concerning the digital signing and I found your website at https://www.example-code.com/vbnet/xades_malaysia_eInvoice.asp which has provided an excellent sample that looks fit to solve our current problem.

I would like to get some additional information:

1) What kind of support can I get from you should there be any changes from Malaysian government on the structure or standard used?

Chilkat has been in business for over 20 years, and it is normal over the span of years for protocols and formats to evolve over time. Chilkat has always done its best to keep up to date to satisfy the needs of its customers, and will continue to do so.

2) Will I get close support from you?

Support is by email, and most responses are same business day. Timezone differences can cause delays.

3) Do you have any Malaysian customers who are using your class library for the Malaysian EInvoice?

Yes. Chilkat has been helping Malaysian customers to better understand how to implement solutions. The general process is that Chilkat updates and improves examples and documentation based on knowledge gained from supporting customers.

4) Can I digitally sign both XML and JSON content with your product?

You can sign XML content. As far as I know there is no JSON equivalent standard to XMLDsig ( https://www.w3.org/TR/xmldsig-core2/ )

5) Does the class library support UBL 2.1 (XML and JSON)? If It does, will It be a problem if the UBL standard changes to greater version than 2.1? If It does not, can you recommend one?

The Chilkat XML and JSON API’s are general and capable of supporting any XML or JSON. For example, you can copy/paste XML or JSON into Chilkat’s online tools at the following URLs to generate code that either produces the given XML/JSON, or parses the given XML/JSON.

6) Besides certificate with .pfx extension, what are the other extensions can be supported in your class library?

Certificates and private keys can be loaded from most file formats, including PFX (.pfx/.p12), PEM, DER, base64, etc. It is also possible to load certificates/private keys from HSM (smart cards or tokens), or even use from Cloud HSM. It is also possible to load certs and keys installed on Windows from the registry-based certificate stores.

7) Do you have any advice that I should look into for the EInvoice implementation?

The example at https://www.example-code.com/vbnet/xades_malaysia_eInvoice.asp is currently the only advice and example from Chilkat. As more experience is gained from supporting customers, the example can be improved or perhaps additional examples will be added.

admin