A training organization focusing on Malaysia Indirect Tax Education

SWPC Latest Events

View Full Calendar
No events

SWPC Contact

Mr. Stanley Wong Kah Leong

Block D-3A07 Phileo Damansara 1
No 9 Jalan 16/11 Off Jalan Damansara
46350 Petaling Jaya, Selangor, Malaysia, MYS

Tel: +6012-9819390; +6012-6981938 

URL: https://www.swpc.com.my

Email: [email protected] 

Please send queries to us via email [email protected]. or fill out the Get-In-Touch form at Get In Touch Page.

E-Invoicing Study: Expected Components in Software Development Kit - System Specification

Details
Category: E-Invoicing
Hits: 1108

E-Invoicing Study: Anticipated Components in Software Development Kit - System Specification

This article is trying to highlight the anticipated contents inside Software Development kit before the official document is scheduled to release in December 2023 or any time after the article publication.

Expected Contents in SDK 20231105

The software development kit shall consider of the following sections:

  1. Digital Certificate and Signature 
    1. IRBM announced in the guideline that digital signature is embedded into the e-invoice. Therefore, IRBM shall use Tax Identification Number to create the digital certificate for specific taxpayer as an authentication approach to validate the identity of the taxpayer. The SDK shall indicate a digital signature to be embedded in the e-invoice shall be based on one digital signature or shall use different digital signature that belongs to the same taxpayer for retailing e-invoice.
    2. Digital signature is mandatory to present in the e-invoice. The attached sample shows typical digital signature as Issuer's Digital Signature as mandatory field. However, the length of the digital signature is yet to be finalized. 
  2. Quick Response Code QR Code
    1. QR Code shall include TIN and Seller's Name.
    2. The SDK shall indicate the development on QR Code whether it is based on Base64 string.
    3. The SDK shall indicate the contents of QR code in term of Tag, Length and Value (TLV) 
  3. Provision for Data Dictionary - Helpful in XML schema
    1. The SDK shall provide complete lists of data dictionary as whether it is based on PEPPOL INTERNAITONAL (PINT) or Malaysia specific data field. 
    2. It shall provide UBL XML schema sample to help in the software development and how to fill in from data catalogue published by IRBM.
    3. Provide sample value in each data field and whether validation will be done during validation stage.
    4. Provide indication whether the data field is mandatory or optional as not all e-invoices issued contain Sales Tax, Service Tax or Tourism Tax.
  4. Elaboration on File Storage Path
    1. IRBM provided the file storage in the e-invoice guideline. Therefore, the software development shall dedicate the folders to store the e-invoices generated before sending for validation and after validation.
  5. File Name Convention
    1. The SDK shall indicate the file name for generated e-invoices. The objective is to make sure that no e-invoices with the same file name are sent to IRBM for validation at the same time.
    2. Typical file name convention as below:
      1. TIN 
      2. DATETIME
      3. E-Invoice Code / Number
      4. Example: C22218888888_20240801151308_INV12345.xml

SWPC Search