Home Acts & Rules GST Draft-Bills-Reports Report on - Business Processes for GST - Payment - [April 2015] This
Forgot password New User/ Regiser ⇒ Register to get Live Demo
Para 4 - PAYMENT THROUGH NEFT/RTGS FROM ANY BANK (INCLUDING OTHER THAN AUTHORIZED BANKS) - Report on - Business Processes for GST - Payment - [April 2015]Extract III. PAYMENT THROUGH NEFT/RTGS FROM ANY BANK (INCLUDING OTHER THAN AUTHORIZED BANKS) : 53. The third mode of payment envisaged under the GST regime is OTC payment through all banks including other than authorized banks, i.e., a bank where a tax payer may have account but that bank may not be authorized by the Government to accept GST receipts. The payment through this mode will strictly be a matter of normal banking service of NEFT / RTGS provided by that bank to its customer. The chances of error in this mode are similar to that of any remittance done through NEFT / RTGS. However, care needs to be taken to ensure that CPIN number is correctly mentioned in NEFT / RTGS message. The Committee recommends that this mode being a new mode of remittance should be scaled up gradually starting with a pilot run by RBI. It was informed by RBI that a detailed process flow could be worked out with specific provisions for validations. RBI further informed that this concept was being tested in Karnataka and this experience would be further used for developing this mode of payment. NEFT / RTGS mandate would have the same validity period of seven days as the CPIN and the date upto which it would remain valid would be printed on it. The Committee observed that in this mode of payment, it would not be possible to automatically ensure that a CPIN was not used beyond its validity period of 7 days. It was decided that CPIN once generated and intimated by GSTN to RBI in this mode though will have a validity period of 7 days but would remain live with RBI for a period of 30 days. In case the payment is received after the expiry of the said 30 days, RBI would return the amount to the remitter bank. Beside this, it was also decided that there should be a provision in the GST law whereby any taxpayer using this mode beyond the validity period (seven days) of the CPIN more than two times would be barred by GSTN from availing this mode of payment. 54. Although the process under this mode will be more or less similar to the OTC payment discussed earlier in paras 32-52 above, but due to involvement of a new stakeholder i.e. a non-authorized bank, certain modifications are required for this process. This process will be beneficial for those taxpayers who do not have a bank account in any of the authorized banks or find such bank to be far away for OTC payment or want to make the payment directly from their account in their own bank only. In this mode, only payment through National Electronic Funds Transfer (NEFT) / Real Time Gross Settlement (RTGS) is to be allowed as other payment instruments would require the Central and the State Governments to create accounts with non-authorized banks also which will not be desirable. Process involved in payment through NEFT / RTGS from any Bank (including other than authorised banks): 55. Every tax payer who wants to avail the facility of payment through NEFT/RTGS mode will access GSTN for generation of a challan through which payment is to be made. 56. Upon creation of the draft challan, the taxpayer will fill in the details of the taxes that are to be paid. As agreed by the RBI representative, RBI would itself be the recipient of the amount transferred through NEFT / RTGS, thus eliminating the need for a link-up first with an authorized branch to receive the payment and thereafter its transfer to the RBI. RBI would thus perform the role of Authorized bank and that of e-FPB in this mode of payment. In this view, the name of the authorized bank will be auto populated as RBI. As a part of the challan preparation, a tax payer will have to choose the mode of payment as NEFT / RTGS from any bank. The challan so generated will have a Unique Common Portal Identification Number (CPIN), assigned only when the challan is finally generated. The generated Challan will have a NEFT / RTGS mandate associated with it. This mandate will contain NEFT / RTGS pooling bank account details (i.e. of RBI) along with IFSC for receiving money. After the challan is generated, it will be frozen and will not be allowed to be modified. The CPIN so generated would be valid for a period of seven days within which payment is to be tendered but would remain live with RBI for a period of 30 days. NEFT/RTGS mandate would have the validity period of CPIN printed on it. As mentioned above, there shall be a provision in the GST Law whereby any taxpayer using challan under this mode beyond the validity period of seven days of the CPIN more than two times would be barred from availing this facility by GSTN. 57. Upon successful saving of the challan details, the challan will be available on the dashboard of the taxpayer in downloadable / printable form. So the taxpayer can either download the challan form or print it offline or can print the challan directly from GSTN. 58. Besides the generation of challan, GSTN will also generate NEFT / RTGS mandate form in prescribed format. The CPIN generated at the portal shall be incorporated in NEFT/RTGS mandate form in Account Name field. RBI would provide for suitable validations for this field. The Sender to Receiver field shall carry the entry GST Payment . In case of NEFT / RTGS payments, there shall also be a disclaimer on the challan copy and the mandate form that the payment through NEFT / RTGS is a transaction between the tax payer and his bank and the payment will be deemed to be received by the government only when the amount is credited to the designated account in RBI. The payments in this mode would be permitted only against cheques and no cash payments would be permitted to initiate NEFT / RTGS transaction for the reasons mentioned in Para 67 below. 59. The following details will be available in the NEFT / RTGS mandate form: a) Beneficiary IFSC : IFSC of RBI hosting the NEFT / RTGS account for GST; b) Beneficiary Account Number : Account Number of RBI s pooled account for GST; c) Account Name : CPIN of relevant challan (suitable validation to be provided by RBI); d) Total Amount; e) Sender to Receiver Remarks: GST Payment. The form will have a provision to write the NEFT/RTGS charges manually and then record the total amount to be collected by the bank (sum of challan amount and charges). The entire NEFT/RTGS form will be auto-populated except the part relating to the charges. 60. Thereafter taxpayer can print a copy of NEFT / RTGS mandate form and approach his bank branch (any bank) for payment of taxes (within a period of seven days of the generation of CPIN, so that when the amount is received by RBI, the CPIN is still valid.) The payments in this mode would be permitted only against cheques and no cash payments would be permitted to initiate NEFT / RTGS transaction. NEFT/RTGS mandate would have validity period of CPIN printed on it. As already mentioned above, there should be a provision in GST law whereby any taxpayer using this mode beyond the validity period (seven days) of the CPIN more than twice would be barred from availing this facility by GSTN. 61. GSTN will inform RBI on real time basis the following details: a) CPIN; b) GSTIN; c) Challan Amount; d) Break Up of the Amount into CGST, IGST, Additional Tax and SGST; e) State/UT Government to which SGST remittance pertains. 62. The accepting bank should add its charges for doing NEFT / RTGS remittance and collect gross amount from the customer. The amount indicated as GST amount for remittance should be transferred by the remitter bank to the designated account of the government in RBI. For the proper identification of the transaction, there should be a Unique Transaction Reference (UTR) that should be conveyed along with file details to RBI. The remitter bank must also mention the CPIN in the NEFT/RTGS mandate as part of the Account Name. The Remarks field shall mention GST Payment . 63. Upon successful completion of the transfer at the end of the remitter bank, the remitter will get a receipt detailing Unique Transaction Reference (UTR). Taxpayer should thereafter login back to GSTN portal and update the challan details with Unique Transaction Reference (UTR) provided by the remitter bank for NEFT / RTGS transaction. An alternate SMS based facility for such updating by the tax payer (instead of internet based) may be established by GSTN to facilitate those taxpayers who do not have an internet access. On receipt of the transaction number, GSTN will communicate this Unique Transaction Reference (UTR) (for the corresponding CPIN) also to RBI on real time basis. 64. Once the RBI receives the payment in its account with NEFT/RTGS message, it will link up the payment with the CPIN earlier received from GSTN and report the transaction to GSTN on real time basis through an electronic string which will contain the following details: a) CIN (CPIN and Bank Code of RBI); b) GSTIN; c) Challan Amount; d) BRN of RBI; e) Unique Transaction Reference (UTR); f) Time of Payment; g) Date of Payment. 65. Upon receipt of the electronic string regarding successful completion of the transaction by GSTN, the tax paid challan will be credited to the cash ledger of the taxpayer. The GSTN will thereafter lock the CIN so that it cannot be used again. 66. As recommended in para 58 above, the Mode III may be implemented with arrangement of CPIN being mentioned as the Account Name in NEFT/RTGS message. RBI will provide for a suitable validation for this field. In such arrangement, the chances of error will be only marginal as the remitter banks take care to mention the account name correctly in any NEFT/RTGS message. In case of error, NEFT/RTGS unique transaction number (UTR) intimated by the tax payer can be used as a secondary identifier. The primary matching by RBI should be with reference to CPIN only, i.e., CPIN as contained in NEFT/RTGS message and CPIN data provided by GSTN. On successful matching, the GST pooled account should be debited and the respective 39 tax accounts (CGST, IGST, Additional Tax and SGST) should be credited simultaneously as per the challan details with generation of CIN and BRNs. At this stage, the transaction should be treated as successful and CIN and BRNs should be communicated to GSTN by RBI. 67. As stated in para 15 above, though the CPIN is valid for a period of 7 days, the same would remain live with RBI for a period of 30 days. Thus RBI can accept the payment during the said period of 30 days. In case payment is received after the expiry of 30 days, RBI would refund the said amount to the remitter bank. Keeping in view this requirement, it has been recommended, as mentioned above, that payments in cash would not be accepted for initiating NEFT / RTGS transaction. 68. The Committee deliberated the need for a pooled GST account. Based on inputs provided by RBI, a receiving account is necessary for NEFT/RTGS process. Therefore, a pooled GST account as an operational necessity will have to be opened in RBI. This account may be opened in the name of the Accounting Authority of the Government of India solely for the operational reasons as a transit account. There should be a validation in RBI system that no funds pertaining to the transactions with date value T=0 are left in this account when the scroll is prepared on T+1. 69. If the matching based on CPIN does not succeed, the role of UTR as secondary matching identifier becomes important. However, it is possible that RBI may receive NEFT/RTGS message even before the tax payer updates his challan with UTR number and GSTN informs RBI on real time basis. In case of failure of CPIN based matching and UTR not being available, the funds will remain in the pooled account till the UTR is received or scroll is prepared, whichever is earlier. Such credit in the pooled account should be with a CPIN mis-match flag that a secondary level matching needs to be carried out before scroll is generated on T+1 basis. Once UTR is provided by GSTN, the secondary matching of all such transactions remaining in the pooled account should be carried out. If a transaction can now be linked to the correct challan, the respective Tax accounts should be credited with generation of CIN and BRNs. There should be a validation in RBI system that all the transactions with CPIN mis-match and date value T=0 in the pooled account are subjected to secondary level matching before generation of scroll for all taxes. 70. If the matching based on CPIN and UTR NEFT / RTGS transaction number UTR both fails, the entire receipt should be credited to CGST account with a CPIN mis-match flag so that the Accounting Authorities of Government of India can account such amount under a separate suspense sub-head (possibly receipts awaiting transfer i.e. RAT). 71. In all such cases of CGST credits with CPIN mis-match , the tax payer will not get a confirmation SMS from GSTN and his ledger will not reflect the payment. He can be expected to provide UTR at this stage. Once the UTR becomes available, GSTN should carry out the matching with CPIN, and communicate following details to the Accounting Authorities of Government of India and concerned State Government. a) RBI scroll number and date which carried the credit (CGST scroll); b) BRN; c) CIN (of credit to CGST account with CPIN mis-match flag); d) Challan amount; e) Breakup of total amount in CGST, IGST, Additional Tax and SGST; f) Name of State Government to whom SGST pertains. 72. Based on the communication from GSTN, CGST Accounting Authorities shall take steps for clearing the suspense sub-head by transferring the credit to CGST, IGST and Additional Tax accounting heads, and for carrying out inter-government transfer to the concerned State Government. 73. The reconciliation between e-Scroll sent by RBI on T+1 and the transaction details available with GSTN (provided earlier by RBI) will be performed using CIN and Unique Transaction Reference (UTR). Role to be played by each stakeholder: 74. As for the role played by each stakeholder in this mode of payment, it will be same as for their role in OTC payments through authorized banks. The role of Branch of remitter bank that transfers the funds to RBI and the additional role of RBI performing the functions akin to authorized banks is discussed below. Branch of remitter bank: 75. The branch of the remitter bank would perform the following functions: a) Remitter bank is required to ensure that the correct CPIN is entered in the NEFT / RTGS message and also inform UTR to the taxpayer; b) Transfer the amount indicated in the NEFT / RTGS message [which includes Unique Transaction Reference (UTR)] to RBI. RBI performing functions akin to authorized banks: 76. RBI s role for the Mode III will be akin to that of authorised banks for other modes, i.e, RBI will be the bank which will receive the funds directly from a taxpayer s account in a pooled account. It should be possible to have a suitable IT system which will carry out CPIN or UTR based matching (as detailed in para 66 above) for each NEFT/RTGS receipt and credit the remittance to a specially created pooled GST account and thereafter transfer it to the respective tax accounts of each government. 77. Once the remittances are received by RBI, it will perform the following functions: a) RBI will receive and validate the NEFT/RTGS transaction against the Challan details received by it; b) RBI would communicate the receipt of payment (CIN) to GSTN on real time basis; c) On first day of every month, RBI as e-FPB will provide Datewise Monthly Statements (DMS) for each tax and government separately to the concerned wing of RBI for the preceding month with following details: i) Name of Tax; ii) Government Name; iii) Date wise number of successful transactions and total credit reported to RBI; and iv) List of discrepancies remaining unresolved at the end of the report month (MOE UIN, CIN, BRN, Amount, Nature of discrepancy). These statements will be simultaneously communicated to accounting authorities of the Centre and the respective States in case their accounting authorities so desire. d) RBI will also be responsible for incorporating these payment details in their daily master scroll generated by them as an aggregator for amounts received through Mode I and II.
|