Welcome to BigLedger Knowledge Center!
6.2 Internal Submission Queue
6.2.1 Internal Submission Queue Overview
Purpose: Manages the submission of transactions to IRB from the posting queue and batch pool.
User Actions:
• Submit transactions manually or wait for automatic submission by the system.
• View reasons for failure by clicking on individual transactions.
Note: Successfully submitted transactions are removed from this queue and stored in the Internal Submission History.
6.2.2 Internal Submission Queue Listing
In the Internal Submission Queue Listing, you can check the status of each transaction:
Not Submitted: Indicates the transaction is still pending.
You can manually submit these transactions or let the system process them automatically.
Once a transaction is successfully submitted:
It will be removed from this queue and transferred to the Internal Submission History, where it will no longer appear in the listing.
6.2.3 Failed Submissions
To investigate a Failed Submission, click on the transaction with this status.
A side menu will appear on the right.
Navigate to the last tab labeled "From LHDN."
This tab shows the response message from LHDN, indicating why the document was rejected.
Review the message to understand the reason for rejection, which usually indicates that the document needs to be updated.
Powered by: Bigledger Sdn Bhd