Para 13 – Draft-Bills-Reports – Business Processes for GST – Payment – Report on – Business Processes for GST – Payment – [April 2015] – Para 13 – Resolution of Reconciliation Outcomes (discrepancies noted during the reconciliation process): 104. There would be to and fro data transmission between GSTN, e-FPB of Authorized Banks, banks other than authorized Banks, RBI, Accounting Authorities and Tax Authorities. There is a scope of error occurring at each leg of communication. The process for reconciliation of such errors in each leg of communication is discussed in succeeding paras. First leg of communication of data (CPIN linked to a GSTIN) starts from GSTN to Authorized banks: 105. If the data forwarded by GSTN (CPIN linked to a GSTIN) itself has an error then this error will be reflected in all the later transactions. So significance of accuracy of this data cannot be overemphasized. It would be important for GSTN to maintain a robust system for maintaining data integrity and keep
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
n a bank s response, the discrepancy will get noticed in the real time validation of the response by the GSTN. The response sent by e-FPB of authorized bank (in Mode I & II) / RBI (in Mode III) should be validated with the data sent earlier by GSTN to Authorized bank / RBI. Key elements are CPIN, GSTIN, CIN & Challan amount in case of authorized banks and CPIN, GSTIN, CIN, NEFT/RTGS UTR and Challan amount in case of RBI. This validation between CPIN available with GSTN and CIN received from e-FPB of authorized banks / RBI should be done on real time basis and the discrepancies, if found should be communicated to the concerned banks immediately by GSTN s IT system so as to enable time to the banks for correction, if possible, before communicating the receipts to RBI on T+1 basis. 108. The validation by GSTN may throw up following discrepancies in the transaction being reported (with CIN added by the bank) by e-FPB of authorized bank / RBI: a) without CPIN; b) with incorrect CPIN
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
data is crucial. RBI collates daily luggage files ( thirty nine) received from all the authorized banks, includes payments received directly by it in Mode III, adds RBI Transaction Id for all modes, prepares and sends daily e-scroll (one for each major head for Centre and each State) to GSTN and Accounting Authorities. Reconciliation by GSTN and Accounting Authorities (of the Centre and the States) will be initiated after they receive their respective files (Government of India authorities will receive three files while State Authorities will receive a file each). Errors in this leg of communication would be detected at this stage. Various situations that can be envisaged in this leg are as follows: a) Transaction reported to GSTN by authorized banks but not to RBI (CIN reported to GSTN but not included in luggage file): 111. To prevent/minimize this type of error, the bank s IT system should have a validation that all credits to the Tax accounts for the date value being the previous
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
acity. The steps involved in the correction mechanism in the aforesaid situation are as follows: i) GSTN to report the error to the relevant Accounting Authority (and Tax Authority, if GOI or concerned State so wants) and RBI, if the discrepancy is detected by GSTN; ii) The relevant Accounting Authority to generate a MOE with a UIN and communicate the same to RBI with a copy to concerned authorized bank for resolution (Accounting Authorities of the Centre and States will have to initiate MOE in respect of their respective taxes) (This may be on the basis of discrepancy detected and communicated by GSTN or by the Accounting Authorities themselves); iii) RBI to ascertain from e-FPB of the concerned authorized bank / RBI and get the discrepancy corrected. E-FPB of the concerned Authorized bank / RBI must rectify this discrepancy within a period of two days from the date of receipt of MOE from the Accounting Authority; iv) Rectification by the concerned e- FPB / RBI will be by way of ident
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
In case of payment through internet banking (Mode I), this seems to be an unlikely scenario, as all payments will be processed at the Core Banking Solution (CBS) of the concerned e-FPB of authorized bank and therefore the compiled data that it reports to RBI on T+1 basis will be nothing but the compilation of data (CIN) already reported by e-FPB of authorized bank on real time basis to GSTN. This discrepancy may however arise due to communication failure even after the prescribed rounds of pinging. 113. This discrepancy can arise in other modes of payment (Mode II and III), because the payment cycle is not a single workflow, is spread over a longer period of minimum two days and requires participation of various banking officials even though the entire cycle is supposed to be done on the IT system customized for GST payments. Such a discrepancy will be detected by GSTN when it undertakes a reconciliation of the challan details (CIN) of a day available with it with the e-scroll of the
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
of error, the bank s IT system should have validations/controls mentioned in para 85 above; iii) Only if the CPIN and associated data in the scroll does not match with GSTN s data there will be a need for MOE. That will be type c) error, discussed in the paragraph below. In those cases, the Accounting Authority should create MOE with a UIN and communicate it to RBI with a copy to e-FPB of the concerned authorized bank. (The Accounting Authorities will identify the concerned bank on the basis of bank code contained in the CIN reported against the successful CPIN in the e-scroll received from RBI). c) Transaction reported to RBI but with incorrect details of CIN (CIN level mismatch): 114. This kind of error can be minimized through suitable validations in the bank s IT system. If the error still occurs, it will be noted when the scroll data is processed by GSTN / Accounting Authorities. Even if the error gets noticed earlier as mentioned in para 109 above but remains unresolved till the
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
o wrong government accounts though CIN matches with data in e-scroll received from RBI (major head level): 115. It may so happen that while sending the luggage file to RBI, the e-FPB of the authorized bank / RBI reflects the amount received in a tax head different from the one specified in the challan (major head level) (CPIN). 116. In such a situation, Accounting Authorities will play a crucial role as they are statutorily responsible not only for proper accounting of money but also for its credit into the correct government account. This discrepancy will be ascertained by the Accounting Authorities while carrying out reconciliation between the challan data obtained from GSTN on T+1 basis (detailing major heads) and e-scroll (for each major head separately) received from RBI. Steps involved in the correction mechanism are as follows: i) The relevant Accounting authority would generate MOE with UIN and communicate the same to RBI. Accounting Authorities of the Centre and States will ha
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
and report correction of MOE to GSTN and relevant Tax authority thereby completing the transaction cycle; vii) RBI to take steps to penalize e-FPB. e) CIN neither transmitted to GSTN nor conveyed in luggage file from authorized bank to RBI and therefore not included in e-scroll received from RBI: 117. This scenario will reflect the failure of the system at two ends. In this scenario the taxpayer has properly paid taxes into the government account through authorized / non-authorized banks but the same has neither been reported to GSTN nor to RBI thereby in effect eliminating the transaction from the system itself. So it is crucial that suitable protocol should be developed for dealing with this kind of errors. It has to be kept in mind here that CPIN generated at GSTN has a validity period of only 7 days within which the payment is to be tendered. This error cannot be ascertained on the basis of any reconciliation as there will not be any flow of information from authorized banks / RBI
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
ayment through authorized banks by instruments drawn on another bank in the same city, the process of giving acknowledgement would be in two steps. In case CIN is not reported to GSTN by the e-FPB of the authorized bank, the taxpayer may follow the procedure detailed in sub-para i) above. E-FPB of the authorized bank is now expected to include this receipt in the luggage file for the day for transmission to RBI. iii) In case of OTC payment through banks via NEFT/RTGS, upon successful completion of the transfer at the end of the bank, the taxpayer will get a receipt detailing Unique Transaction Reference (UTR). Taxpayer can thereafter login into GSTN and update the details of UTR provided by the bank for NEFT/RTGS transaction in the challan. GSTN is expected to communicate the UTR to RBI. In case the CIN is not communicated by RBI, GSTN will now take up the matter with RBI (instead of with authorized bank) in the manner detailed in sub para i) above. RBI is now expected to include this
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =
with a copy to the concerned bank as detailed in para 116 above for getting the shortfall amount. 119. In case the amount in the scroll is more than the challan amount for any tax, the bank will have to raise the MOE with the concerned Accounting Authority for the refund. Without approval of the Accounting Authority, the banks should not be allowed to adjust the excess amount against future receipts. Fourth leg of communication of data is between RBI and GSTN & Accounting Authorities: 120. RBI is collating luggage files from e-FPBs of various authorized banks, including amount received by it in Mode III and thereafter generating and transmitting e-scrolls Major head wise to Government of India and SGST (state wise). During collation of the data, an error can creep into e-scroll resulting in missing / additional transaction. Since there is simultaneous flow of information to two different agencies i.e. GSTN and Accounting Authorities, following situations may arise: a) Transaction
= = = = = = = =
Plain text (Extract) only
For full text:-Visit the Source
= = = = = = = =