# TRSuite 26.02 - CRS Malaysia *Source: TRSuite_26.02_UsersGuide_Module_CRS_MY.docx - TRSuite 26.02, published September 2026. Generated with word/tools/docx_to_md.py.* TAX REPORTING SUITE CRS ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image1.png) Malaysia VERSION 26.02 USERS’S MANUAL Published: Sep 2026 For the latest information and to leave feedback, please visit BRIFS GmbH at [http://www.section11.ch](http://www.section11.ch) or [https://www.trsuite.ch](https://www.trsuite.ch) The information in this document and any document referenced herein is provided for informational purposes only, is provided AS IS AND WITH ALL FAULTS and cannot be understood as substituting for customized service and information that might be developed by BRIFS GmbH for a particular user based upon that user’s particular environment. RELIANCE UPON THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN IS AT THE USER’S OWN RISK. © 2026 BRIFS GmbH. All rights reserved. Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. BRIFS GMBH PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION CONTAINED IN THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN. BRIFS GmbH provides no warranty and makes no representation that the information provided in this document or any document referenced herein is suitable or appropriate for any situation, and BRIFS GmbH cannot be held liable for any claim or damage of any kind that users of this document or any document referenced herein may suffer. Your retention of and/or use of this document and/or any document referenced herein constitutes your acceptance of these terms and conditions. If you do not accept these terms and conditions, BRIFS GmbH does not provide you with any right to use any part of this document or any document referenced herein. Complying with the applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without the express written permission of BRIFS GmbH. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. ## Revision History | **Version** | **Doc Version** | **Revision Date** | **Description** | | --- | --- | --- | --- | | 1803 | Rev 0 | 10.04.2018 | GA Release MY | | 1807 | Rev 1 | 31.07.2018 | Minor fixes, adaptions to data preparation guide | | 1812 | Rev 2 | 17.12.2018 | Minor fixes | | 1902 | Rev 3 | 12.02.2019 | No changes | | 1911 | Rev 4 | 07.11.2019 | Minor fixes, stability improvements | | 20.01 | Rev 5 | 20.01.2020 | [https://www.easycrs.ch/index.php/8-trsuite/12-trsuite-release-notes-version-20-01](https://www.easycrs.ch/index.php/8-trsuite/12-trsuite-release-notes-version-20-01) | | 20.02 | Rev 6 | 24.02.2020 | [https://www.easycrs.ch/index.php/8-trsuite/13-trsuite-release-notes-version-20-02](https://www.easycrs.ch/index.php/8-trsuite/13-trsuite-release-notes-version-20-02) | | 20.11 | Rev 7 | 24.11.2020 | https://www.easycrs.ch/index.php/8-trsuite/17-trsuite-release-notes-version-20-11 | | 21.01 | Rev 8 | 01.02.2021 | https://www.easycrs.ch/index.php/8-trsuite/18-trsuite-release-notes-version-21-01 | | 26.02 | Rev 9 | 06.09.2026 | https://www.trsuite.ch/trsuite/ReleaseNotes/RELEASE_NOTES_26.02.en.html | ## The Main Window The Main window is the launch point for the entire application. You can select the licensed module in the modules button bar and perform the module specific tasks within main area of the module. Each module comes with its own module menu and detail area. Modules Button Bar – shows all available modules of the software.Modules Button Bar – shows all available modules of the software. Module Menu – module specific menu optionsModule Menu – module specific menu options Menu optionsMenu options Module Details Area – includes general information and details for the selected moduleModule Details Area – includes general information and details for the selected moduleModule Main Area – the main working area of a module, where all module specific tasks can be executedModule Main Area – the main working area of a module, where all module specific tasks can be executed ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image2.png) ## CRS MY: Module Overview This guide provides information about the MY specific extension of the CRS module of the TRSuite software package. It describes processes and procedures for generating transmission files to MY gateway. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image3.png) This document may describe features and capabilities that requires a separate license and are not covered by the standard license. For information about licensing please contact support@section11.ch The CRS module includes the following: - General Info Tab - Reporting FIs Tab - Account Holder List - XML- / Excel-Import - XML-Export - Configuration The functions are described in the CRS User Guide. The CRS MY module covers the following extension - Malaysia Tab The screenshots throughout the USER’s MANUAL are produced on Windows 11 using the Windows Look and Feel. ### Reference In addition to this Users Guide, the following online resources may be useful: - LHDN CRS Guideline: [https://www.hasil.gov.my/en/antarabangsa/automatic-exchange-of-information-aeoi/common-reporting-standard-crs/](https://www.hasil.gov.my/en/antarabangsa/automatic-exchange-of-information-aeoi/common-reporting-standard-crs/) - IRBM Public Key: [https://www.hasil.gov.my/en/antarabangsa/irbm-public-key/](https://www.hasil.gov.my/en/antarabangsa/irbm-public-key/) - OECD AEOI portal [http://www.oecd.org/tax/automatic-exchange/common-reporting-standard/](http://www.oecd.org/tax/automatic-exchange/common-reporting-standard/) - The Common Reporting Standard [http://www.oecd.org/ctp/exchange-of-tax-information/standard-for-automatic-exchange-of-financial-account-information-for-tax-matters-9789264216525-en.htm](http://www.oecd.org/ctp/exchange-of-tax-information/standard-for-automatic-exchange-of-financial-account-information-for-tax-matters-9789264216525-en.htm) - The CRS XML Schema User Guide [http://www.oecd.org/tax/automatic-exchange/common-reporting-standard/schema-and-user-guide/#d.en.345315](http://www.oecd.org/tax/automatic-exchange/common-reporting-standard/schema-and-user-guide/#d.en.345315) ### CRS Malaysia The following information is used to generate a CRS OECD 3.0 XML compliant document. Before filing an OECD CRS Report, please ensure that you are familiar with your country specific Guidance Notes. The Inland Revenue Board Of Malaysia (IRBM) defines a guideline for data preparation of CRS files similar to the FATCA IDES process. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image4.png) Before you begin, you must have a valid certificate from an IRBM approved certificate authority. #### Configuration The configuration section allows the user to enter all required information needed to generate a valid transmission archive. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image5.png) - Your public key certificate uploaded to HiDEF - The path to your private key PEM or PFX/P12 file (NEVER share this file!) used to generate the CSR/certificate. - Optional: Password for your PEM/PFX/P12 file. Typically, SSL-Server private keys do not use passwords, still it is supported - Path to the IRBM public key certificate can be downloaded from IRBM website. - Your MyCRSID: The ID is a unique 8 character-length number that identifies the transmission. This ID will be included in both HiDEF system alerts and notifications generated by the IRBM. - The current configuration can be saved and is loaded automatically the next time you start TRSuite. Checking the configuration requires the working directory to be set. During the validation a piece of information is en-/decrypted to verify the configured private and public key matches. TRSuites creates a sender metadata file to ensure that IRBM accurately process CRS XML files and notifications. Notifications are sent by the IRBM to an FI and state whether the file is processed correctly or contained errors. In the Sender Meta Data section provide the required data elements: ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image6.png) - The Sender Country Code element identifies the jurisdiction of the Sending Competent Authority. Only a value MY is currently allowed. - The Receiver Country Code element indicates the jurisdiction of the Receiving Competent Authority. Only a value MY is currently allowed. - The Sender File ID element is a free text field to capture the file name or ID created by the Sending Financial Institution. The element helps both the Sending FI’s and Receiving IRBM Authority to track and monitor a specific message. - The agreed format is: CRS\_ MY+MyCRSID +Date +SEQNO - MyCRSID – will be given upon registration of MYFI with HiDEF - Date format – YYYYMMDD - SEQNO – 4 digits character (0000 – 9999) - The Tax Year element specifying the tax year to which the file relates. - The File Revision Indicator element is a Boolean field to indicate if the file is a revised message. - The Orginial CTS Transmission ID element is a free text field to reference the unique original HiDEF transmission ID. The identifier helps both the FI’s and IRBM to track and monitor messages. HiDEF Transmission ID referencing an update to an earlier transmission - Optional – Use only after IRBM request - The Sender Contact eMail Address element is a free text field to identify the email address of the Financial Institution. #### Create a CRS Data Packet A file that is transmitted through HiDEF is known as a CRS data packet or data packet. The data packet is an archive in .ZIP file format. HiDEF only supports data packets in a .ZIP file format with a .zip file extension. The files are case sensitive and any variation in the file name or format will cause the transmission to fail. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image7.png) The Generate Upload File section let the user select the XML file (Payload Path) to be processed ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image8.png) All generated files will be written to the following folder structure within the selected output directory. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image9.png) The processed XML file is either copied to the processed folder, if the transmission archive was successfully generated or to the failed folder if the file could not be processed properly. The generated transmission archive is moved to the upload folder (2). The temp folder (1) contains all artifacts generated during the processing. All temporary output is stored in a new folder created within the working directory temp folder. The naming schema for the new folder is simply the UTC-timestamp as used for naming the transmission archive. Files contained in a transmission archive or data packet: - MyCRSID_CRS_Metadata.xml - MyCRSID_CRS_Key - MyCRSID_CRS_Payload The file naming convention of data packet is composed of a Coordinated Universal Time (UTC) timestamp and the MyCRSID of the sender as: MyCRSID_RPTYR_CRS_UTC.zip Following steps are executed during the creation process: ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image10.png) - Validation of the payload xml file against the OECD CRS schema. The version is selected with the drop-down menu: "OECD XML 3.0" (default) or "2.0"; version 1.0 has been withdrawn and is no longer offered. - Signing the payload xml with the FI’s private key - Compressing the signed payload xml - Encrypting the compressed payload file with a one-time AES-256 key - Encrypting the AES key with the IRBM public key - (Optional) Encrypting the AES key with the HCTA public key - Creating the sender metadata file with a current timestamp - Creating the transmission archive and write all output to the working directory If the process step executes without errors a success symbol is displayed next to the step label. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image11.png) If the step fails, a warning symbol is shown. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image12.png) More information about the result is displayed in the status area below the process steps. In case of an error, a localized error message is displayed within a notification dialog. The language of the message depends on your OS settings. For instance, if you use a German version of Windows the message is display in German. ![](media/TRSuite_26.02_UsersGuide_Module_CRS_MY/image13.png) A more detailed (but technical) error message is written to the log file. ## Appendix ### Export control information This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information. TRSuite uses the Java Cryptography Architecture (JCA) and the Bouncy Castle libraries for handling de-/encryption.