LHDN Guidelines update 

LHDN releases SDK (Version 1.0) for Malaysia E-invoicing system

With the recently published the e-Invoice Software Development Kit (SDK Version 1.0), businesses like yours now can charter a seamless pathway to integrate for the Malaysia E-invoicing mandate.

Heading - Recent Changes in Malaysian E-Invoicing Guidelines [6th April 2024]

IRBM recently released the updated e-invoicing guidelines on April 6th, 2024, introducing significant changes in the e-invoice generation process and details that need to be submitted for e-invoice generation.

Major Changes Related to the E-Invoice Generation Process

Paragraph Number

Changes

Explanation

Consideration for Clients

1
Real-time vs. Near Real-time Validation
The new guideline states that e-Invoice will enable "near real-time validation."
Businesses need to adjust their expectations and systems regarding the speed of validation.
1.6.8
"Scholarship" removed from exempt transactions
Entities providing scholarships must now issue e-Invoices
Entities need to generate e-invoices to claim expenses for scholarships provided.
2.3.2 & 2.3.3
Terminology changes from "Batch Generation" to "Batch Upload"
Clarification of process using pre-defined Microsoft Excel spreadsheets for bulk upload on MyInvois Portal
Businesses should adhere to the specific spreadsheet format for uploading details of transactions.
2.3.8
Removal of CSV Format Report
CSV report has been removed from the list of reporting & dashboard services of the MyInvois Portal
Users won't be able to download reports in CSV format.
2.4.3
E-Invoice Validation Process Update via API
Clarification of API response content and addition of notification to both Supplier and Buyer upon successful validation.
Suppliers and technology providers should update their systems based on the new API requirements.
2.4.4
Removal of the Notification Procedure in E-invoicing model via API
Taxpayers would receive notification only for successful validation of e-invoice.
Taxpayers need to establish alternative channels for receiving notifications of rejected e-invoice.
2.4.7
CSV & PDF files have been removed from the list of options to retrieve e-invoice data using API integration.
Only XML / JSON, either by one or in a package, and Metadata are allowed now.
Adjust their system to retrieve e-invoice data only in specified format.

Major Changes in the List of Required Fields for E-Invoice

The updated guidelines have modified both the mandatory and optional field requirements, enhancing the robustness and feasibility of the e-invoice creation process.

Fields

Old Version

New Version

Supplier’s e-mail
Mandatory
[Optional]
Buyer’s email
Mandatory
[Optional]
Original e-Invoice Reference Number
Mandatory
[Mandatory, where applicable]
Issuer’s Digital Signature
No details of the DSC were present
Details of Digital Signature is added
Currency Exchange Rate
Where Applicable
Mandatory, where applicable
Total Payable Amount
No clarification
Clarification regarding the exclusion of any amount paid in advance and any rounding adjustment.
Fee / Charge Amount
Charge associated with the product or serviceimposed after tax
The charge associated with the product or service (with or without tax)
Prepayment Amount
Unique identifier assigned to trace prepayment
Includes description specifying the monetary value prepaid by the buyer to fulfil the financial obligation.

These modifications are for the general e-invoicing guidelines. In addition to these changes, there are minor adjustments in illustrations, descriptions, clarifications, and reference numbers. You can download the updated e-invoicing guidelines on the official LHDN website.

Stay updated with all the latest
announcements from LHDN

LHDN Updates

Important Updates to Classification Codes in Software Development Kit (SDK)

August 9th, 2024

The Inland Revenue Board of Malaysia (IRBM) has recently updated the descriptions of several classification codes on the SDK website. These changes are important for accurately classifying goods and services when generating e-invoices.Below is a summary of the impacted classification codes along with their updated descriptions:

Classification code

Earlier description

Updated description

005
Construction materials (as defined in Lembaga Pembangunan Industri Pembinaan Malaysia Act 1994)
Construction materials (as specified under Fourth Schedule of the Lembaga Pembangunan Industri Pembinaan Malaysia Act 1994)
025
Purchase of motor vehicle
Motor vehicle
026
Purchase or subscription of books / journals / magazines / newspapers / other similar publications
Subscription of books / journals / magazines / newspapers / other similar publications
029
Rental or purchase of EV charging facilities
EV charging facilities (Installation, rental, sale / purchase or subscription fees)
032
Self-billed - Foreign income
Foreign income
037
Self-billed - Payment to agents, dealers or distributors
Self-billed - Monetary payment to agents, dealers or distributors
038
Sports equipment, rental / entry fees for sports facilities or registration in sports competition
Sports equipment, rental / entry fees for sports facilities, registration in sports competition or sports training fees imposed by associations / sports clubs / companies registered with the Sports Commissioner or Companies Commission of Malaysia and carrying out sports activities as listed under the Sports Development Act 1997

To view the complete list of classification codes and their updated descriptions, please refer to the Classification Codes on the SDK.
If you have any questions or require further assistance, feel free to reach out to your key accounts manager.

e-Invoicing Guidelines Version 3.1 Released by IRBM

July 19th, 2024

Dear Customers,The Inland Revenue Board of Malaysia (IRBM) released the e-Invoice Guideline (Version 3.1) on 19 July 2024. The new guideline includes two changes in Appendix 2 – List of Mandatory and Optional Fields Under Annexure to the E-Invoice. These changes apply to fields related to the import and export of goods in Annexure 2:
i. Clarification for “Incoterms”: It is now an optional field.Description: A set of international trade rules defining the responsibilities of buyers and suppliers.
ii. Editorial changes in the “Product Tariff Code (only applicable to goods)”:Description: The Harmonized System code for goods under relevant orders.If you have any questions regarding these updates, please don't hesitate to reach out to your key accounts manager.

Updates in SDK Version 1.0- Integration Updates

June 28, 2024

The Inland Revenue Board of Malaysia (IRBM) has made new additions and changes to the Software Development Kit (SDK) Version 1.0. While mostly technical, these updates will affect the integration of your business systems.
Here are the key updates from the SDK release notes as published June 28, 2024.

1. Updated response to APIs

  • Get Recent Documents API Response: The API now includes additional response fields. These new fields include SupplierTIN (issuer's TIN), SupplierName (supplier company name), SubmissionChannel (channel through which the document was introduced), and more. These additions will provide more detailed information on the documents retrieved. Read more
  • Reject Document API Error Responses: The Reject Document API now has expanded error responses to provide more specific reasons for rejection failures. New error codes include responses for when the rejection time limit has expired; the document is not in a valid state for rejection and other conditions. Read more
  • Get All Document Types API Response: The new output parameters have been added, which will help better categorise and understand document types. The new output parameters include ID (unique identifier), Name, Description of the document type version, and more. Read more

2. Added Type Page and Relevant Samples for v1.1

3. Other Updates to Validations, Documentation and Signature

  • Updates to Signature -
    Enhanced instructions for encoding the hashed property tag using HEX-to-Base64 Encoder in Document Signature Creation.
  • Updated Validations & Documentation -
    i. Aligned API Response and Standard Error Response.
    ii. Updated Document Type examples to specify “v1.1” instead of “v1.0”.
    iii. Removed ‘Continuation Token’ from Search Documents API.
  • Updated Contacts page - Added Helpdesk support line number:  03 - 8682 8000These updates aim to improve the integration between our business system and the MyInvois System, making e-invoice generation smoother. If you have any questions or need further assistance, please feel free to contact our support team.

Important Updates to SDK Version 1.0

June 21, 2024

The Inland Revenue Board of Malaysia (IRBM) has made important amendments to Software Development Kit (SDK) Version 1.0.
‍Below are the key updates outlined in the SDK release notes by IRBM on June 21, 2024.

1. Updated Validations, Documentation and Parameters

  • Shipping Recipient Field has been made Optional: The requirement for Shipping Recipient Field has changed from "Mandatory where Applicable" to "Optional".  The taxpayer can choose to not provide shipping address details separately as part of the e-invoicing payload.
  • SST Registration Number: Suppliers can now enter up to two SST registration numbers, separated by a semicolon or dash. The character limit for SST registration numbers has been increased from 17 to 35 to account for a maximum of 2 SST registration numbers and a semicolon or dash.
  • Addition of Document Version 1.1: Version 1.1 has been added alongside the existing Version 1.0 for all Document Types. Taxpayers can now test digital signature validation after submitting invoices in the Sandbox environment with the latest version. For Sandbox testing of digital signatures, taxpayers should use version 1.1.
  • Updated TIN Parameters: To validate the Tax Identification Number (TIN), any initial zeros following the TIN prefix must be removed. For example, 'C0123456789' should be validated as 'C123456789'.

2. Changes in API, New Additions and Removal

  • Actual APIs Deployed to Sandbox Environment- The following APIs have been updated from Stub to Actual in the Sandbox environment:
    i. Get All Document Types
    ii. Get Document Type
    iii. Reject Documents
    iv. Get Recent Documents
  • The following Sample files are added
    ‍    i. UBL 2.1 Foreign Currency Sample JSON
    ii. UBL 2.1 with Multi Line Item Sample JSON
  • Removed Sample JSON:
    i. UBL 2.1 Foreign currency with Tax exchange Rate sample XML
  • Added Pagination URL Parameter to Get Submission API : Two new query parameters have been added:
    i. pageNo: Number of the page to retrieve (optional).
    ii. pageSize: Number of documents to retrieve per page. The page size cannot exceed this API's system-configured maximum page size (100). (optional)

3. Other Clarifications, Implementations and Updates

  • Added QR Code Generation Guidance:- Taxpayers can generate a QR code (quick response code) from the validation link using any QR code generator.
    i. The validation link follows this format: {envbaseurl}/uuid-of-document/share/longid. Replace {envbaseurl} with the e-Invoice portal Base URL.
    ii. The Get Submission, Get Document or Get Document Detail API can obtain both UUID and long ID as return parameters.
  • Implemented Minification of XML / JSON Documents: XML / JSON documents are now minified within the Submit Document API to comply with prescribed file size rules.
  • Updated Error Handling:  Renamed the title from "Error 404" to "Error 400" and replaced "BadArgument" with "BadRequest". This API now returns HTTP status code 400 (BadRequest) if the TIN or any input parameters do not match the required structure.
  • Clarification on Tax Rate:  The new description of field values distinguishing between fixed tax rates and percentages.

These are the major updates made by IRBM in SDK Version 1.0, as detailed in the release notes. If you have any questions or need further assistance, please feel free to reach out to us

Important Updates to SDK Version 1.0

May 24th, 2024

The Inland Revenue Board of Malaysia rolled out updates to the Software Development Kit (SDK) Version 1.0 on May 24th, 2024. These updates include improved validations and documentation, new additions, and enhancements to digital signature capabilities.
‍Here are details of the updates.

1. Improved Validation and Documentation Updates

Update

Old

New

Extended Character Limit for Contact Numbers
15 characters
20 characters
Clarification on Tax Rate Notes
In Tax Type Percent Note - Tax rate as % value should not be present.
In Tax Type - For a fixed tax rate, the % value should not be present. However, if the tax rate is not fixed, it can also take % value.

2. Updates to Signature

  • Updated Samples and Explanation of Actual Digital Certificate JSON:
    For your reference, here are the links to view sample files incorporating digital signatures:
    i. UBL 2.1 Invoice Sample XML with Signature: Link
    ii. UBL 2.1 Invoice Sample JSON with Signature: Link
  • A list of licensed providers offering digital signature services and certificates is also added. Click Here
  • New Additions
    New Sample XMLs: Included new sample XMLs for Foreign Currency transactions featuring Tax Exchange Rates and Multi-Line-Item support.
    UBL 2.1 with Multi Line Item Sample XML
    UBL 2.1 Foreign Currency with Tax Exchange Rate Sample XML
  • Added the question “ What is the Call Limit for each API? “ in the FAQ section:Answer: The caller should handle the rate-limiting headers that are returned to them by the API and retry the call according to these headers. The header would specify the current number of rate-limited calls and the time the caller should wait before making the next call.
  • Introduced a new page dedicated to Signing Documents in JSON format within the Document Signature Creation section.
  • Added a new tax code 'E' under Tax Types to support cases of tax exemption where applicable. Click Here

2. Other Updates

These highlights represent the overview of the changes and amendments made to the SDK Version 1.0.

Important Updates to SDK Version 1.0

May 10th, 2024

The Inland Revenue Board of Malaysia (IRBM) has made important amendments to Software Development Kit (SDK) Version 1.0.Below are the key changes, as outlined in the SDK release notes by IRBM on May 10, 2024.
Updated Validations & Documentation-

1. Amended descriptions of  following fields providing further clarification of 

  • Fee / Charge Rate: Charge associated with the product or service (be it in the form of percentage (%) or prevailing specified rate) imposed before tax. Please add currencyID attribute to the XML element
  • Fee / Charge Amount: Charge associated with the product or service imposed before tax. Please add currencyID attribute to the XML element.
  • Total Discount Value: Total amount deducted from the original price of the product(s) or service(s). Please add currencyID attribute to the XML element.
  • Invoice Additional Fee Amount: Total additional charge associated with the product(s) or service(s) (be it in the form of % or prevailing specified rate imposed after tax). Please add currencyID attribute to the XML element.

2. Updated available APIs in the sandbox environment.

  • Login as Intermediary System API: Updated from Stub to Actual
  • Validate Taxpayer’s TIN API: Updated from Stub to Actual
  • Submit Documents API: Fully functional sandbox environment now. Previously it was limited to Structure Validator only.
  • Cancel Document API: Updated from Stub to Actual.
  • Get Submission API: Updated from Stub to Actual.
  • Get Document API: Updated from Stub to Actual.
  • Get Document Details API: Updated from Stub to Actual.

3. Updated the cardinality of the following fields.

  • Quantity, Measurement: Maximum one value input is allowed for quantity
  • Reference Number of Customs Form No.1, 9: Multiple inputs are allowed now.
  • SST Registration Number:
    i. Mandatory for SST registrant
    ii. Supplier to input “NA” if supplier is not registered for SST
    iii. Maximum one input is allowed 
  • Tourism Tax Registration Number.
    ‍    i. Mandatory for tourism tax registrant
    ii. Supplier to input “NA” if supplier is not registered for tourism tax
    iii. Maximum one input is allowed 

4. The measurement field now allows up to 3 characters. A new code table has been introduced to represent the measurement field.

5. Refined descriptions for the following fields

  • Tax Type:  Type of taxes that will be applicable (e.g., sales tax, service tax, tourism tax, etc.) 
  • City Name: The common name of the city, town or village, where the Supplier, Buyer and Shipping Recipient address is located.
  • Payment Mode: Chosen mechanism through which funds are transferred from buyer to supplier (e.g., cash, cheque, bank transfer, credit card, debit card, e-Wallet/ Digital Wallet, etc.)
  • Prepayment Time: Time of prepayment received

6. Updates to Digital Signature

  • Removed the Timestamp Authority (TSA) requirement of XAdES for digital signature.
  • Provided clearer guidance on hashing with SHA256 followed by HEX-to-Base64 encoding.
  • Updated sample in SDK with RSA-SHA256.

New Additions

  • List of unit of measurement types allowed as part of the document line information as part of the document submission. Added Measurement Code Table under Codes. 

These highlights represent just the overview of the amendments made to the SDK Version 1.0. .

Recent Changes in Malaysian E-Invoicing Guidelines

Apr 06th, 2024

IRBM recently released the updated e-invoicing guidelines on April 6th, 2024, introducing significant changes in the e-invoice generation process and details that need to be submitted for e-invoice generation.

  • Old Version: E-Invoice Guideline Version 2.2
  • New Version: E-Invoice Guideline Version 2.3

Major Changes Related to the E-Invoice Generation Process

Paragraph Number

Changes

Explanation

Consideration for Clients

1
Real-time vs. Near Real-time Validation
The new guideline states that e-Invoice will enable "near real-time validation."
Businesses need to adjust their expectations and systems regarding the speed of validation.
1.6.8
"Scholarship" removed from exempt transactions
Entities providing scholarships must now issue e-Invoices
Entities need to generate e-invoices to claim expenses for scholarships provided.
2.3.2 & 2.3.3
Terminology changes from "Batch Generation" to "Batch Upload"
Clarification of process using pre-defined Microsoft Excel spreadsheets for bulk upload on MyInvois Portal
Businesses should adhere to the specific spreadsheet format for uploading details of transactions.
2.3.8
Removal of CSV Format Report
CSV report has been removed from the list of reporting & dashboard services of the MyInvois Portal
Users won't be able to download reports in CSV format.
2.4.3
E-Invoice Validation Process Update via API
Clarification of API response content and addition of notification to both Supplier and Buyer upon successful validation.
Suppliers and technology providers should update their systems based on the new API requirements.
2.4.4
Removal of the Notification Procedure in E-invoicing model via API
Taxpayers would receive notification only for successful validation of e-invoice.
Taxpayers need to establish alternative channels for receiving notifications of rejected e-invoice.
2.4.7
CSV & PDF files have been removed from the list of options to retrieve e-invoice data using API integration.
Only XML / JSON, either by one or in a package, and Metadata are allowed now.
Adjust their system to retrieve e-invoice data only in specified format.

Major Changes in the List of Required Fields for E-Invoice

The updated guidelines have modified both the mandatory and optional field requirements, enhancing the robustness and feasibility of the e-invoice creation process.

Fields

Old Version

New Version

Supplier’s e-mail
Mandatory
[Optional]
Buyer’s email
Mandatory
[Optional]
Original e-Invoice Reference Number
Mandatory
[Mandatory, where applicable]
Issuer’s Digital Signature
No details of the DSC were present
Details of Digital Signature is added
Currency Exchange Rate
Where Applicable
Mandatory, where applicable
Total Payable Amount
No clarification
Clarification regarding the exclusion of any amount paid in advance and any rounding adjustment.
Fee / Charge Amount
Charge associated with the product or serviceimposed after tax
The charge associated with the product or service (with or without tax)
Prepayment Amount
Unique identifier assigned to trace prepayment
Includes description specifying the monetary value prepaid by the buyer to fulfil the financial obligation.

These modifications are for the general e-invoicing guidelines. In addition to these changes, there are minor adjustments in illustrations, descriptions, clarifications, and reference numbers. You can download the updated e-invoicing guidelines on the official LHDN website.

LHDN releases SDK (Version 1.0) for Malaysia E-invoicing system

Feb 09th, 2024

1. Decoding the New Software Development Kit's APIs
E-invoice APIsThese APIs streamline e-invoicing workflows, supporting document submission, validation, retrieval, and status tracking.‍

  • Validate Taxpayer’s TIN: This API validates the TIN before the invoice is issued
  • Submit Documents: All the invoices are grouped into submissions, and the API performs the structural validations.
  • Cancel Document:  This API allows the buyer to cancel the document after it was validated within a 72-hour window.
  • Reject Document: If the seller would like to cancel a document after it was validated, he can do so by using this API
  • Get Recent Document: The user can use this API to retrieve up to 10,000 documents based on his predefined filters.
  • Get Submission: This API returns information on documents submitted during a single submission by a taxpayer.
  • Get Document: The user can get full details of an individual document submitted by mentioning the unique associated with the document.
  • Get Document Details: The user can get full details of an individual document including its validation status, in this API.
  • Search Documents: In this API, the user can apply a certain set of filters and get a high-level summary of each retrieved document.

2. Platform APIs
Platform APIs extend functionalities beyond invoicing workflows, enhancing user experience in authentication, access control, and data retrieval.

  • Login as Taxpayer System: Authenticates user systems accessing invoicing details, generating a token valid for one hour for secure access.
  • Login as Intermediary System API: Allows intermediaries like ClearTax to authenticate on behalf of users, refreshing the token every 60 minutes for continuous security.
  • Get All Document Types API: Retrieves a comprehensive list of supported document types and their details, aiding users in understanding system-supported documents.
  • Get Document Type API: Retrieves schema and fields of a specific document type, facilitating accurate document generation and submission.
  • Get Document Type Version API: Retrieves JSON and XML structure of a given document version, ensuring compatibility and compliance.
  • Get Notification API: Retrieves notification history from IRBM, enhancing compliance experience with insights into past notifications and their status.

3. Document Validation Rules
The SDK also provides seven validation rules that govern the content and structure of e-invoices submitted to LHDN's system.

  • Structure Validator
  • Country Signature Validator  
  • Reference Document Validator
  • Duplicate Document Validator
  • Core Fields Validator
  • Taxpayer Validator
  • Code Validator

Recent Changes in Malaysian E-Invoicing Guidelines

Apr 06th, 2024

IRBM recently released the updated e-invoicing guidelines on April 6th, 2024, introducing significant changes in the e-invoice generation process and details that need to be submitted for e-invoice generation.

  • Old Version: E-Invoice Guideline Version 2.2
  • New Version: E-Invoice Guideline Version 2.3

Major Changes Related to the E-Invoice Generation Process

Paragraph Number

Changes

Explanation

Consideration for Clients

1
Real-time vs. Near Real-time Validation
The new guideline states that e-Invoice will enable "near real-time validation."
Businesses need to adjust their expectations and systems regarding the speed of validation.
1.6.8
"Scholarship" removed from exempt transactions
Entities providing scholarships must now issue e-Invoices
Entities need to generate e-invoices to claim expenses for scholarships provided.
2.3.2 & 2.3.3
Terminology changes from "Batch Generation" to "Batch Upload"
Clarification of process using pre-defined Microsoft Excel spreadsheets for bulk upload on MyInvois Portal
Businesses should adhere to the specific spreadsheet format for uploading details of transactions.
2.3.8
Removal of CSV Format Report
CSV report has been removed from the list of reporting & dashboard services of the MyInvois Portal
Users won't be able to download reports in CSV format.
2.4.3
E-Invoice Validation Process Update via API
Clarification of API response content and addition of notification to both Supplier and Buyer upon successful validation.
Suppliers and technology providers should update their systems based on the new API requirements.
2.4.4
Removal of the Notification Procedure in E-invoicing model via API
Taxpayers would receive notification only for successful validation of e-invoice.
Taxpayers need to establish alternative channels for receiving notifications of rejected e-invoice.
2.4.7
CSV & PDF files have been removed from the list of options to retrieve e-invoice data using API integration.
Only XML / JSON, either by one or in a package, and Metadata are allowed now.
Adjust their system to retrieve e-invoice data only in specified format.

Major Changes in the List of Required Fields for E-Invoice

The updated guidelines have modified both the mandatory and optional field requirements, enhancing the robustness and feasibility of the e-invoice creation process.

Fields

Old Version

New Version

Supplier’s e-mail
Mandatory
[Optional]
Buyer’s email
Mandatory
[Optional]
Original e-Invoice Reference Number
Mandatory
[Mandatory, where applicable]
Issuer’s Digital Signature
No details of the DSC were present
Details of Digital Signature is added
Currency Exchange Rate
Where Applicable
Mandatory, where applicable
Total Payable Amount
No clarification
Clarification regarding the exclusion of any amount paid in advance and any rounding adjustment.
Fee / Charge Amount
Charge associated with the product or service imposed after tax
The charge associated with the product or service (with or without tax)
Prepayment Amount
Unique identifier assigned to trace prepayment
Includes description specifying the monetary value prepaid by the buyer to fulfil the financial obligation.

These modifications are for the general e-invoicing guidelines. In addition to these changes, there are minor adjustments in illustrations, descriptions, clarifications, and reference numbers. You can download the updated e-invoicing guidelines on the official LHDN website.

The information provided above is based on the interpretation of LHDN's e-invoicing guideline updates by the ClearTax team. For further details, please contact your account manager.‍

Important Updates to SDK Version 1.0

10th May 2024

Dear Customers,The Inland Revenue Board of Malaysia (IRBM) has made important amendments to Software Development Kit (SDK) Version 1.0.Below are the key changes, as outlined in the SDK release notes by IRBM on May 10, 2024.
‍Updated Validations & Documentation

1. Amended descriptions of  following fields providing further clarification of 

  • Fee / Charge Rate: Charge associated with the product or service (be it in the form of percentage (%) or prevailing specified rate) imposed before tax. Please add currencyID attribute to the XML element
  • Fee / Charge Amount: Charge associated with the product or service imposed before tax. Please add currencyID attribute to the XML element.
  • Total Discount Value: Total amount deducted from the original price of the product(s) or service(s). Please add currencyID attribute to the XML element.
  • Invoice Additional Fee Amount: Total additional charge associated with the product(s) or service(s) (be it in the form of % or prevailing specified rate imposed after tax). Please add currencyID attribute to the XML element.

2. Updated available APIs in the sandbox environment.

  • ‍Login as Intermediary System API: Updated from Stub to Actual
  • Validate Taxpayer’s TIN API: Updated from Stub to Actual
  • Submit Documents API: Fully functional sandbox environment now. Previously it was limited to Structure Validator only.
  • Cancel Document API: Updated from Stub to Actual.
  • Get Submission API: Updated from Stub to Actual.
  • Get Document API: Updated from Stub to Actual.
  • Get Document Details API: Updated from Stub to Actual.

3. Updated the cardinality of the following fields.

  • Quantity, Measurement: Maximum one value input is allowed for quantity
  • Reference Number of Customs Form No.1, 9: Multiple inputs are allowed now.
  • SST Registration Number
    i. Mandatory for SST registrant
    ii. Supplier to input “NA” if supplier is not registered for SST
    iii. Maximum one input is allowed
  • Tourism Tax Registration Number.
    i. Mandatory for tourism tax registrant
    ii. Supplier to input “NA” if supplier is not registered for tourism tax
    iii. Maximum one input is allowed

4. The measurement field now allows up to 3 characters. A new code table has been introduced to represent the measurement field.
‍
5. Refined descriptions for the following fields

  • Tax Type:  Type of taxes that will be applicable (e.g., sales tax, service tax, tourism tax, etc.) 
  • City Name: The common name of the city, town or village, where the Supplier, Buyer and Shipping Recipient address is located.
  • Payment Mode: Chosen mechanism through which funds are transferred from buyer to supplier (e.g., cash, cheque, bank transfer, credit card, debit card, e-Wallet/ Digital Wallet, etc.)
  • Prepayment Time: Time of prepayment received

Updates to Digital Signature

  • Removed the Timestamp Authority (TSA) requirement of XAdES for digital signature.
  • Provided clearer guidance on hashing with SHA256 followed by HEX-to-Base64 encoding.
  • Updated sample in SDK with RSA-SHA256.

New Additions

  • List of unit of measurement types allowed as part of the document line information as part of the document submission. Added Measurement Code Table under Codes. 

These highlights represent just the overview of the amendments made to the SDK Version 1.0. 

Thank you for your attention to these updates. If  you have any questions or require further assistance, please don't hesitate to reach out to your key accounts manager

[LHDN E-invoicing] Important Updates to SDK Version 1.0

May 24th, 2024

The Inland Revenue Board of Malaysia rolled out updates to the Software Development Kit (SDK) Version 1.0 on May 24th, 2024. These updates include improved validations and documentation, new additions, and enhancements to digital signature capabilities.
‍Here are details of the updates.

1. Improved Validation and Documentation Updates

Update

Old

New

Extended Character Limit for Contact Numbers
15 characters
20 characters
Clarification on Tax Rate Notes
In Tax Type Percent Note - Tax rate as % value should not be present.
In Tax Type - For a fixed tax rate, the % value should not be present. However, if the tax rate is not fixed, it can also take % value.

2. Updates to Signature

  • Updated Samples and Explanation of Actual Digital Certificate JSON:
    For your reference, here are the links to view sample files incorporating digital signatures:
    i. UBL 2.1 Invoice Sample XML with Signature: Link
    ii. UBL 2.1 Invoice Sample JSON with Signature: Link
  • A list of licensed providers offering digital signature services and certificates is also added. Click Here
  • New Additions
    New Sample XMLs: Included new sample XMLs for Foreign Currency transactions featuring Tax Exchange Rates and Multi-Line-Item support.
    UBL 2.1 with Multi Line Item Sample XML
    UBL 2.1 Foreign Currency with Tax Exchange Rate Sample XML
  • Added the question “ What is the Call Limit for each API? “ in the FAQ section:Answer: The caller should handle the rate-limiting headers that are returned to them by the API and retry the call according to these headers. The header would specify the current number of rate-limited calls and the time the caller should wait before making the next call.
  • Introduced a new page dedicated to Signing Documents in JSON format within the Document Signature Creation section.
  • Added a new tax code 'E' under Tax Types to support cases of tax exemption where applicable. Click Here

2. Other Updates

These highlights represent the overview of the changes and amendments made to the SDK Version 1.0.
If you have any questions regarding these updates, please don't hesitate to reach out to your key accounts manager.

Important Updates to SDK Version 1.0

June 21, 2024

The Inland Revenue Board of Malaysia (IRBM) has made important amendments to Software Development Kit (SDK) Version 1.0.
‍Below are the key updates outlined in the SDK release notes by IRBM on June 21, 2024.

1. Updated Validations, Documentation and Parameters

  • Shipping Recipient Field has been made Optional: The requirement for Shipping Recipient Field has changed from "Mandatory where Applicable" to "Optional".  The taxpayer can choose to not provide shipping address details separately as part of the e-invoicing payload.
  • SST Registration Number: Suppliers can now enter up to two SST registration numbers, separated by a semicolon or dash. The character limit for SST registration numbers has been increased from 17 to 35 to account for a maximum of 2 SST registration numbers and a semicolon or dash.
  • Addition of Document Version 1.1: Version 1.1 has been added alongside the existing Version 1.0 for all Document Types. Taxpayers can now test digital signature validation after submitting invoices in the Sandbox environment with the latest version. For Sandbox testing of digital signatures, taxpayers should use version 1.1.
  • Updated TIN Parameters: To validate the Tax Identification Number (TIN), any initial zeros following the TIN prefix must be removed. For example, 'C0123456789' should be validated as 'C123456789'.

2. Changes in API, New Additions and Removal

  • Actual APIs Deployed to Sandbox Environment- The following APIs have been updated from Stub to Actual in the Sandbox environment:
    i. Get All Document Types
    ii. Get Document Type
    iii. Reject Documents
    iv. Get Recent Documents
  • The following Sample files are added
    ‍    i. UBL 2.1 Foreign Currency Sample JSON
    ii. UBL 2.1 with Multi Line Item Sample JSON
  • Removed Sample JSON:
    i. UBL 2.1 Foreign currency with Tax exchange Rate sample XML
  • Added Pagination URL Parameter to Get Submission API : Two new query parameters have been added:
    i. pageNo: Number of the page to retrieve (optional).
    ii. pageSize: Number of documents to retrieve per page. The page size cannot exceed this API's system-configured maximum page size (100). (optional)

3. Other Clarifications, Implementations and Updates

  • Added QR Code Generation Guidance:- Taxpayers can generate a QR code (quick response code) from the validation link using any QR code generator.
    i. The validation link follows this format: {envbaseurl}/uuid-of-document/share/longid. Replace {envbaseurl} with the e-Invoice portal Base URL.
    ii. The Get Submission, Get Document or Get Document Detail API can obtain both UUID and long ID as return parameters.
  • Implemented Minification of XML / JSON Documents: XML / JSON documents are now minified within the Submit Document API to comply with prescribed file size rules.
  • Updated Error Handling:  Renamed the title from "Error 404" to "Error 400" and replaced "BadArgument" with "BadRequest". This API now returns HTTP status code 400 (BadRequest) if the TIN or any input parameters do not match the required structure.
  • Clarification on Tax Rate:  The new description of field values distinguishing between fixed tax rates and percentages.

These are the major updates made by IRBM in SDK Version 1.0, as detailed in the release notes. If you have any questions or need further assistance, please feel free to contact your key accounts manager.

Updates in SDK Version 1.0 -Integration Updates

June 28, 2024

The Inland Revenue Board of Malaysia (IRBM) has made new additions and changes to the Software Development Kit (SDK) Version 1.0. While mostly technical, these updates will affect the integration of your business systems.
Here are the key updates from the SDK release notes as published June 28, 2024.
New Additions and Updates Response

1. Updated response to APIs

  • Get Recent Documents API Response: The API now includes additional response fields. These new fields include SupplierTIN (issuer's TIN), SupplierName (supplier company name), SubmissionChannel (channel through which the document was introduced), and more. These additions will provide more detailed information on the documents retrieved. Read more
  • Reject Document API Error Responses: The Reject Document API now has expanded error responses to provide more specific reasons for rejection failures. New error codes include responses for when the rejection time limit has expired; the document is not in a valid state for rejection and other conditions. Read more
  • Get All Document Types API Response: The new output parameters have been added, which will help better categorise and understand document types. The new output parameters include ID (unique identifier), Name, Description of the document type version, and more. Read more

2. Added Type Page and Relevant Samples for v1.1

3. Added Signature Page and Relevant Samples for v1.1

Other Updates to Validations, Documentation and Signature

  • Updates to Signature -
    Enhanced instructions for encoding the hashed property tag using HEX-to-Base64 Encoder in Document Signature Creation.
  • Updated Validations & Documentation -
    i. Aligned API Response and Standard Error Response.
    ii. Updated Document Type examples to specify “v1.1” instead of “v1.0”.
    iii. Removed ‘Continuation Token’ from Search Documents API.
  • Updated Contacts page - Added Helpdesk support line number:  03 - 8682 8000These updates aim to improve the integration between our business system and the MyInvois System, making e-invoice generation smoother. If you have any questions or need further assistance, please feel free to contact our support team.
✕
Know more

Please fill in your details and our representative will get in touch with you shortly

Thank you for the response.
Our representative will get in touch with you shortly.
Oops! Something went wrong while submitting the form.
A PRODUCT BY DEFMACRO SOFTWARE SDN BHD
LegalPrivacy Policy
Level 6, Menara The Stride, BBCC, Jln Pudu, Bukit Bintang, 55100 Kuala Lumpur Malaysia
Follow us