- Loading...
DocRefID Naming Convention
'MY'+MyCRSID +Date +'F' or 'A'+SEQNO
MY – code 'MY'
MyCRS ID – will be given upon registration of MYFI with Hasil International Data Exchange Facility (HiDEF)
Date format – YYYYMMDD
'F' for Financial Institution or 'A' for Account Reports
SEQNO – 4 digits character (0000 – 9999)
MessageRefID Naming Convention
'MY'+MyCRSID +Date +SEQNO
MY – code 'MY'
MyCRS ID – will be given upon registration of MYFI with HiDEF
Date format – YYYYMMDD
SEQNO – 4 digits character (0000 – 9999)
Prompt pre-fills FI’s ID/IN# but can be overridden. This ID # is 8 characters in length.
XML:
NOTE: Please take into the consideration the number sequencing limitation is defined at 9,999. Alternatively, you can do 1 of the following:
- Schedule your XML generations to 9,999 per day until you have created all needed files for submission.
- Post date your computer's clock 1 day ahead between each XML batch.
- If you wish to generate them within the same day, additional configuration to the software (listed below) are needed.
- Update the INI configuration file by adding the lines below. The INI is located by default in C:\1099 Pro\ProCRSTXX\MagCRS.ini. If the file does not exist, please create the file and notepad and name it MagCRS.ini in this location. You can also download this file here: MagCRS.ini
[MY]
MSIDFmt = "{rcc}{cin}{timestamp:yyyyMMdd}{serial:D4}"
FIIDFmt = "{rcc}{cin}{timestamp:yyyyMMdd}F{serial:F:D4}"
ARIDFmt = "{rcc}{cin}{timestamp:yyyyMMdd}A{counter:A:D4}" - Set the XML output to a lower limit through Security and Administration found under the File drop down menu.
- This will batch the files within a session to assign unique ID's for the MessageRefID and the ReportingFI DocRefID across the batched XML's created.
- Update the INI configuration file by adding the lines below. The INI is located by default in C:\1099 Pro\ProCRSTXX\MagCRS.ini. If the file does not exist, please create the file and notepad and name it MagCRS.ini in this location. You can also download this file here: MagCRS.ini
Encrypted Packager
Per their requirements The FI must also:
- digitally sign the XML file
- encrypt the CRS XML file with AES-256 key
- encrypt with IRBM public key
- create sender metadata
- create transmission file in a zip file
Packager notes:
Step 2 you will need to provide your own digital cert/private key file (and passphrase if required).
Step 3 you can leave blank since we embedded the MY production public key.
http://www.hasil.gov.my/bt_goindex.php?bt_kump=6&bt_skum=2&bt_posi=1&bt_unit=2&bt_sequ=1
http://lampiran1.hasil.gov.my/pdf/pdfam/CRS_Data_Preparation_Guide.pdf