Update: | Compliance Alert – IRBM’s optimization of MyInvois API Usage |
Date: | 2024-10-15 |
The Inland Revenue Board of Malaysia (IRBM) addressed certain practices for optimising API usage that can lead to better performance and system stability.
- Token Management for Login as Taxpayer API
- The system token remains valid for 60 minutes. IRBM recommends utilising this token for subsequent API operations within its validity period rather than generating a new one for each request. Excessive token requests may prompt the system to impose request limits.
- Batch Processing for Submit Documents API
- The ERP system allows submitting documents in batches, accommodating up to 100 documents per batch, with a combined size limit of 5 MB and a maximum of 300 KB per document. For enhanced efficiency, batch submissions are recommended over single submissions.
- Avoid repeated submissions of the same document without considering the results from the initial submission API. The API provides immediate processing results, which should be reviewed before any resubmission.
- Monitoring Submissions with Get Submission API
- To check the status of submissions and documents, use the Get Submission API with a recommended polling interval of 3-5 seconds. Frequent requests for the same submission may lead to system throttling.
- Retrieving Document Details with Get Document Details API
- The Get Document Details API should be used exclusively to obtain error information or exceptions for invalid documents. For status updates, the Get Submission API should be utilised, maintaining the 3-5 seconds polling frequency to prevent system throttling.
- Usage of Get Recent Documents API
- The Get Recent Document API is designed to assist with troubleshooting issues and not for reconciliation between the taxpayer’s ERP and MyInvois systems. Excessive use of this API for purposes other than troubleshooting may result in system throttling.
- Appropriate use of Search Documents API
- The Search Documents API is designed to assist with manual auditing and troubleshooting. It should not be used for ERP system reconciliation with the MyInvois system. Excessive use of this API may result in system throttling.
- Validating TIN with Validate TIN API
- The Validate TIN API should be utilised to validate the Buyer's TIN before document submission. IRBM recommends caching the validation results to minimise API calls. Frequent, unnecessary requests may be considered malicious activity and are subject to system throttling.
- IRBM recommends validating the Buyer's TIN when setting up the Buyer entity in the taxpayer’s ERP system and recording the validation status to avoid repeated API calls.
- It should be refrained from invoking this API before each document submission to prevent potential flagging and throttling.
Taxpayers may review the recommended integration practices at MyInvois Integration Practices to ensure that the ERP integration aligns with optimal standards.