Cause: This error message appears when the authorizer rejects a payment in the bank portal but does not enter the reason for rejection.

Solution: In the e-Payments report, mark the transactions as not applicable and make the necessary changes for the transactions. Reset the status of the transactions and send them to the bank again. Next time when you need to reject a transaction, provide a reason in the bank portal to avoid getting the error message.

Cause: This error appears either because the bank server is not responding or the connection to the bank server is timed out.

Solution: Re-send payment instructions to the bank after some time.

Cause: This error occurs when the bank server is not responding.

Solution: Try to re-send the payment instructions after some time.

Cause: This error occurs when the platform cannot parse the request sent from Tally Client.

Solution: Contact Tally Solutions.

Cause: This error occurs when the necessary capsule files are unavailable while a user tries to send payment instructions to the bank.

Solution: Contact Tally Solutions.

Cause: This error occurs if the capsule files are corrupted in the Tally folder or in TSS, when a user sends payment instructions to the bank.

Solution: Contact Tally Solutions.

Cause: This error occurs when the required values cannot be appended to the metadata (xml) sent by the Application layer due to internal technical issues.

Solution: Contact Tally Solutions.

Cause: These error codes appear when there is no internet connectivity on your system, and the Tally.NET Server is down.

Solution: Go to Control Panel and ensure that your LAN connection is enabled. Check if your LAN cable is connected to both your computer and the network wall socket. After you have resolved the network issue, you can re-send the payment instructions to the bank. If this problem persists despite having internet connectivity, contact Tally Solutions.

Cause: This error occurs when the status ofthe license is changed to inactive mode (after the threshold limit assigned from back-end) due to non-availability of internet connection on the computer where the gateway server is installed. For example, if the offline limit for alicense is set to 30 days, and the computer is not connected to the Internet for more than 30 days, then the license status changes to inactive mode.

Solution: On the computer where the gateway server is installed, go to Control Panel and ensure that your LAN connection is enabled. Check if your LAN cable is connected to both your computer and the network wall socket. After you have resolved the network issue, you can resend the payment instructions to the bank. If this problem persists despite having internet connectivity, contact Tally Solutions.

Cause: This error occurs due to an internal technical error.

Solution: Contact Tally Solutions.

Cause: This error occurs when the sender account number is invalid for the transaction that you have sent to the bank.

Solution: Alter the bank ledger to provide a valid account number from where the payment will be made, reset the transaction status, and then send the transaction to the bank.

Cause: This error occurs when the TSS ID that you have used for sending transactions to your bank is not registered with the bank.

Solution: Contact your bank for registering your TSS ID. After your ID is registered with the bank, log in to your company again and send transactions to the bank.

Cause: This error occurs due to an internal technical error.

Solution: Contact Tally Solutions.

Cause: The account number specified in the DBS bank ledger may be incorrect or the account number is not register with the bank for using e-payment services.

Solution: Check/alter the account number specified in DBS Bank ledger.

• Go to Gateway of Tally > Accounts Info. > Ledgers > Alter.
• Select DBS Bank ledger and check/alter the account number.
• Press Ctrl+A to save.

Alternatively, if the account number is correct, contact DBS bank for registering the account number for using e-payment services.

Cause: This error occurs due to an internal technical error.

Solution: Contact Tally Solutions.

Cause: This message appears when the user has sent the payment instructions from the Tally.NET login ID which is not registered with DBS bank.

Solution:

• Log in to the company with the Tally.Net ID which is register with DBS bank for sending the payment instructions.
• If the Tally.Net ID is not registered, then contact DBS bank to register and send the payment instructions.

Cause: This error occurs when the response received from the bank is invalid for the transactions sent to the bank.

Solution: Log in to the bank portal to view the status of the transaction. Once you find the transaction status with the instruction ID details, reconcile the transaction manually in TallyPrime.

Cause: This error occurs when one or more of the mandatory details of the sender is missing or invalid. For example, the sender’s bank account number may be missing or in an invalid format.

Solution: In the bank ledger, provide a valid account number and re-send the payment instructions to the bank. If the problem still persists, contact Tally Solutions.

Cause: After migrating the data, if you click Send to Bank to send payment instructions to the bank, without specifying the Account holders name in the bank ledger, this error occurs. This error generally occurs for users who were not using e-Payments in the previous release.

Solution: You need to specify the Account holders name in the bank ledger and then send the payment instructions to the bank.