Report of the Joint Committee on Business Processes for GST- Payment

Report of the Joint Committee on Business Processes for GST- Payment
GST
Dated:- 12-10-2015

INTRODUCTION
During the Empowered Committee meeting held on 10th March, 2014, it was decided that a Joint Committee under the co-convenership of the Additional Secretary (Revenue), Government of India and the Member Secretary, Empowered Committee should be constituted to look into the Report of the Sub-Group-I on Business Processes for GST and make suitable recommendations for Payment and Return to the Empowered Committee. Accordingly, a Joint Committee, in consultation with the Government of India, was constituted on 7th April, 2014 (Annexure-I). The Committee held its deliberations on 28th October, 2014, 12th November, 2014, 25th November, 2014, 22nd December, 2014, 2nd and 3rd February, 2015, 19th and 20th February, 2015 and 16th and 17th April, 2015.
2. The Joint Committee on Business Processes for GST held on 2nd February, 2015, it was decided to constitute a sub-committee

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

Joint Committee was attended by the officers as listed in Annexure III.
4. In modern day taxation regime, every transaction of the tax payer with the tax administration should be transparent, responsive and simple. It has been experience of tax administrations that more the system and procedures are made electronic more is the efficiency of tax administration and greater is the satisfaction of taxpayer. In this context, payment system of GST should also be based on Information Technology which can handle both the receipt and payment processes.
5. The objectives of this report are as under:
a) Highlight key issues in tax collection, collation, remittance and reporting of tax collection into Government account;
b) Need for a uniform system of banking arrangements for collection, remittance and reporting of GST to both Central and State Governments;
c) Proper accounting and bank reconciliation of taxes derived from basic data of payments made by taxpayers to banks, with the requi

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

, anywhere mode of payment of tax;
c) Convenience of making payment online;
d) Logical tax collection data in electronic format;
e) Faster remittance of tax revenue to the Government Account;
f) Paperless transactions;
g) Speedy Accounting and reporting;
h) Electronic reconciliation of all receipts;
i) Simplified procedure for banks;
j) Warehousing of Digital Challan.
8. With the above features in mind the following three modes of payment are proposed:
a) Payment by taxpayers through Internet Banking through authorized banks and through credit card/debit card;
(Section 45 of RBI Act, 1934 permit banks other than RBI to be appointed as agency banks for carrying out government business. Agency banks are permitted to both receive and make payments on behalf of the Government and therefore act as Banker to respective governments. However, authorized banks are only permitted to receive payment of GST on behalf of the Government, and keeping this distinction in view, the

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ld gradually move to internet payment over an indicative time frame.
10.  The Committee recommends that RBI should play the role of an aggregator through its e-Kuber system. Such role will facilitate participation of larger number of banks in GST receipts enhancing convenience for the tax payers and provide single source of information for credit of the receipts to Government accounts and thereby simplifying accounting and reconciliation tasks. In case of any discrepancy found during the reconciliation by the Accounting Authorities, they would directly interact with RBI. Joint CGA suggested that as per the provisions of Section 20 of the RBI Act, 1934 in the proposed scenario, RBI would be the sole banker to the Governments. RBI, on the other hand, has indicated that Section 20 and Section 45 of the RBI Act, 1934 are not mutually exclusive and therefore there would not be any conflict in the role envisaged for the RBI in the proposed model.
11. Each of the above modes is discuss

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

stakeholders will pay a key role in establishing an effective e-payment network in the proposed GST scenario:
a) GSTN (Goods and Service Tax Network);
b) e- FPBs (Electronic Focal Point Branches) of authorized banks;
c) e-Kuber of RBI;
d) Central Accounts Section (CAS) of RBI, Nagpur;
e) e-PAOs (Electronic Pay and account Offices) / e-Treasuries of State Governments;
f) Pr. CCA, CBEC (Principal Chief Controller of Accounts) / Accountant General of the States;
g) Tax authorities of Centre and States.
Process involved in e-payment of GST:
13. Every tax payer who wants to avail the facility of e-payment will access GSTN for generation of the Challan through which payment is to be made. The following methods for creation of draft challan for GST payments are recommended:
a) By Registered tax payer or his authorized person by logging on to GSTN Common Portal where basic details (such as name, address, email, mobile no. and GSTIN) of the tax payer will be auto populated in

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

per the directions of the tax authority using the GSTIN (like the present provision under Service tax). In this method, GSTN would provide for a validation check (like CAPTCHA) so that challan can be created by a person and not by machine.
14. The issue whether challans should have provision for entering jurisdictional location ( e.g. Commissionerate, division and range) was discussed in detail and it was decided that the same will not be mentioned in the challan. Instead, the Tax authorities would send the Taxpayers updated master data to GSTN as well as to Accounting Authorities. The incremental changes in the said master would also be sent on real time basis by the Tax authorities to GSTN and Accounting authorities. As challan would not have a jurisdictional location code, the Accounting Authorities would use the TAXPAYER Master received from Tax authorities for mapping the challans with the Jurisdictional PAOs / tax authorities' offices by having a suitable mapping mechanism.
15.

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ed, it will be frozen and will not be allowed to be modified. The CPIN/challan so generated would be valid for a period of seven days. In case of payment through Mode III, CPINs would remain live with RBI for a period of 30 days. GSTN would purge all unused CPINs on the day immediately after the date on which the validity period is over (i.e. 7 days if Mode I or II is selected and 30 days if Mode III is selected for payment). At the end of each day (EOD), GSTN would send all the CPINs generated on that day to the Accounting authority of the Centre and to those accounting authorities of the states that so desire. The suggested format of the challan is appended at Annexure – IV which is a common format for all three modes of payment. Since the challan would be prepared electronically, chances of errors will be minimal. However to deal with challan correction in exceptional circumstances, a challan correction mechanism, prepared in consultation with the office of Pr. CCA, CBEC is detailed

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

The taxpayer can choose any of the gateways available on the portal for making the payment. The exact charge should be calculated separately by the gateway service provider. The gateway provider should collect this amount separately over and above the challan amount. The challan amount should be fully credited to respective Government accounts maintained with the authorised bank (acquiring bank for CC/DC payments), while the gateway charges should be retained back by the gateway provider. The Government/GSTN should procure the payment gateway services from the authorised banks (or their SPVs) through an appropriate competitive process to keep the charge rates low. The Committee also deliberated the issue of charge back claims in case of credit card based payment, and felt that the possibility of such claims on payments to the government is minimal and manageable, especially in view of implementation of two-step authentication norm by the banks. In addition, the taxpayer would be requir

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

erify the card details and debit the challan amount and additional gateway charges from the card holder. The Payment Gateway service providers are expected to build their interface with GSTN common portal to capture challan amount breakup in terms of CGST, IGST, Additional Tax and SGST. Along with the interface, associated accounts for CGST, IGST, Additional Tax and state-wise accounts for SGST should be created by the Authorized banks associated with the gateway service providers. The breakup received from GSTN common portal will be used to credit the amounts received under respective accounts created for the purpose. The Committee noted that in respect of credit card payments, presently the acquiring bank is permitted to transfer the amount to the merchant on T+3 basis. Thus there may arise some situations where the taxpayers account has been debited on T+0 basis whereas Government's account in authorised bank would be credited on T+3 basis. It was informed by RBI that this time coul

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

for debiting the total tax amount and authorize the payment. While making the payment, the bank will display the breakup of total amount payable into CGST, IGST, Additional Tax and SGST and seek confirmation from the user. No change in the break up as well as the total amount would be allowed on the Bank's portal. In case the user wants to change the break up or the total amount, he should abort the transaction and go back to GSTN portal from the bank's portal and reinitiate the process.
21. After the successful completion of a transaction, e-FPB of the concerned bank will create a unique Challan Identification Number (CIN) against the CPIN. This will be a unique 17-digit number containing 14-digit CPIN generated by GSTN for a particular challan and unique 3-digit Bank code (MICR based which will be communicated by RBI to GSTN). The incorporation of the date of payment in the CIN may be examined from the IT's perspective. This CIN, as a combination of CPIN and Bank Code, will be repo

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

same. If a response (positive or negative) is not received by GSTN within the stipulated period (few minutes), there would be a feature in GSTN to re-ping the bank system and seek a response against CPIN. There may be a scenario in which the internet banking transaction is successful, but the connection drops before the control comes back to GSTN portal, and the re-ping facility will help in finding the status of such transactions.
23. Upon receipt of confirmation from the bank regarding successful completion of the transaction, GSTN will inform the relevant tax authorities about payment of taxes. A copy of the paid challan (downloadable/printable) with auto-populated CIN, date and time of payment and a statement confirming receipt of the amount by the bank will be provided to the taxpayer by GSTN.
24. Thereafter the tax paid challan (CIN) will be credited to the tax ledger account of the taxpayer. It was discussed and agreed by the Committee that there would be 20 ledger accounts (o

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

aining RBI's scroll number for taxpayer would also be provided;
e) Information to the respective Tax Authorities on real time basis for each successful transaction reported by banks. The communication at this stage may contain a minimal set consisting of GSTIN, CIN (i.e. CPIN + Bank Code), BRN(s), Challan amount, break-up of the amount into CGST, IGST, Additional Tax and SGST and date of payment;
f) At EOD, GSTN will also send the details of CPIN generated for the particular day to the Accounting Authority of the Centre (to facilitate estimation of revenue and fund management) and to such State accounting authorities that may so desire;
g) On T+1 morning, GSTN will generate a consolidated file containing a summary as well as entire details of the challans for which successful transactions were reported by the banks on real time basis for the date value of T=0 (for this purpose, daily transactions would include transactions from 20:01 hrs on previous day to 20:00 hrs in the curren

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

d in the CIN, received by GSTN from Bank on real time basis, is credited in the cash ledger of the taxpayer, GSTN will lock that CIN to prevent its further usage;
k) Purge all unused CPINs after the expiry of seven days in case of Mode I & II / 30 days in case of Mode III;
l) Receive TAXPAYER master as well as updates thereto from the respective Tax Authorities on real time basis.
e- FPBs (ELECTRONIC FOCAL POINT BRANCHES) OF AUTHORIZED BANKS:
26. There would be a single e-FPB for each Authorized bank for the entire country. It will perform the following role:
a) Each e-FPB will open a major head wise (CGST, IGST, Additional Tax and SGST) account of each government (total 39 accounts) to which the remittances received by it would be credited. Currently, the Constitutional Amendment Bill states that the Additional Tax will be collected by Centre and assigned to States. If this arrangement is continued, the e-FPB will maintain one account for Additional Tax for Centre. A Committe

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

the file, it may be broken up into different parts with each part being numbered uniquely and also mentioning the total number of parts of that file;
d) In the morning of each day (T+1), each e-FPB will also forward the daily luggage file mentioned above to accounting authorities of the Centre and the respective State, in case their accounting authorities so desire, so that they can independently monitor delayed remittances, if any, from the banks to the Government account in RBI;
e) On the first day of every month, e-FPB will provide Datewise Monthly Statements (DMS) for each tax and government separately to RBI for the preceding month with following details:
i) Name of Tax;
ii) Government Name;
iii) Datewise 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 the res

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

uthority of Centre (e-PAO) / each State (e-Treasury) and GSTN simultaneously. Daily Major head account-wise scroll from RBI will consist of following information:-
(i) Merchant Code given to GSTN;
(ii) Scroll Number and Date;
(iii) Name of Government to which the scroll pertains;
(iv) CIN;
(v) GSTIN;
(vi) BRN;
(vii) RBI Transaction Number;
(viii) Mode of payment;
(ix) Tax amount;
(x) Control parameters like total transaction, Total Amount in the scroll, etc.
c) If any discrepancy is reported by Accounting Authority or GSTN, it would carry out the correction mechanism with the authorized bank and thereafter report the corrected data to respective Accounting Authority and GSTN.
d) RBI will consolidate Datewise Monthly Statements (DMS) received from the banks for each tax and government, validate the consolidated statements (39) with reference to its own data of e-scrolls reported during the report month, have a systemic review of unresolved discrepancies and communi

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

hi itself. The State governments will need to establish their e-PAOs / e-Treasuries (proposed Central Accounting Unit in the RBI Report of 2014). The following functions will be performed by e-PAOs/e-Treasuries:
a) At EOD, the Central Accounting Authority and those State accounting authorities that so desire will receive details of CPIN generated by GSTN for the particular day. (Centre's accounting authorities require this to facilitate estimation of revenue and fund management);
b) Each morning (T+1), e-PAOs / e-Treasuries will receive from GSTN a consolidated file of entire details of the challans (including CIN) for which successful transactions were reported by the banks to GSTN on real time basis for the previous day;
c) Each morning (T+1), e-PAOs for CGST, IGST & Additional Tax and e-Treasuries of the State Government will get consolidated transaction level digitally signed daily e-scrolls from RBI (along with all the challan details) pertaining to the successful transactio

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

able mapping mechanism. This is a requirement of the Government of India for determining revenue from each formation. States may also follow a similar procedure, if they so desire;
h) They will also provide CIN wise payment / challan details to the respective Tax Authorities daily or periodically as per requirements / norms of their governments for departmental reconciliation and for updating Tax Authorities database that the tax amount has been accounted in the government's books. Accounting Authorities should provide their accounting reference number (in Government of India, CIN is used for this purpose; some State Governments seem to be generating their own accounting reference number) for each challan accounted by them along with the tax amount as per the credit accounted by them to the jurisdictional Tax Authorities for reconciling their records.
i) They will provide verified Datewise Monthly Statement (DMS) to Pr. CCA, CBEC (Principal Chief Controller of Accounts) and Account

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

rized banks might be asked as to whether they would be able to scroll these OTC payments through e-FPBs. This was discussed and RBI's representative assured that the scrolling by e-FPBs of OTC payments in one scroll would be ensured. The authorized banks will be required to establish / upgrade their IT software for accepting GST receipts.
33. The following stakeholders will play a key role in establishing an effective OTC payment system in the proposed GST scenario:
a) GSTN;
b) Branches of Authorized Banks;
c) e-FPBs of Authorized banks;
d) e-Kuber of RBI;
e) e- PAOs of Centre / e-Treasuries of State Governments;
f) Pr. CCA, CBEC / Accountant General of the States;
g) Tax authorities of Centre and States.
Process involved in Over the Counter payment of GST through authorized banks:
34. Every tax payer who wants to avail the facility of OTC payment (only for paying tax upto Rs. 10,000/- per challan), will access GSTN for generation of a challan through which payment is

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

of taxes. The challan so generated will have a Unique Common Portal Identification Number (CPIN), assigned only when the challan is finally generated, that will help the portal and other authorities in identifying the challan. After the challan is generated, it will be frozen and will not be allowed to be modified. The CPIN / challan so generated would be valid for a period of seven days within which payment is to be tendered. GSTN will inform the challan details including validity period to the CBS (Core Banking System) of the selected bank on a real time basis.
36. 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 and print it offline or can print the challan directly from GSTN. If the payment is made by cheque or DD, the challan itself would have a disclaimer that the payment is subject to realization of cheque or DD.
37. Thereafter taxpa

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

as per details in challan (CPIN Data)]. However RBI representatives observed that since there would be real-time sharing of data between GSTN and Agency Banks, the details would be available to the bank official before submission of the challan by the customer. In such a situation, GSTN would have already shared the break-up of the total amount to the bank and the bank needs to credit the same in the appropriate head. The internal Accounting mechanism of bank may be left to the bank to design, as the requirement here is the proper booking and reporting of the transaction which banks would have to ensure. It was decided that those banks need not operate a GST pool account which can credit the amount in the respective tax accounts 'on the fly'.
38. There should be a linkage between the GSTN and the Core Banking System (CBS) of the authorized banks whereby the details of challan are shared with the Authorized bank selected by the tax payer on real time basis so that they can be stored in

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ot be allowed to accept OTC payments. The minimum requirements to be met by the banks for being authorized to accept GST receipts for all modes including OTC mode are detailed in para 85 below.
40. The cashier / teller will verify the details of challan, payment instrument and amount provided by the taxpayer with those displayed in his system and should accept the receipt only when no discrepancy is found. If the challan has crossed its validity period of seven days, the bank's system itself should bar acceptance of the payment. In any case, the challan would also not be available in the GSTN and consequently in the bank's system because it would have been purged from the System by GSTN upon the expiry of the 7 day validity period.
41. The tax payer may make payment by cash or instruments drawn on the same bank or on some other bank in the same city. In case of cash payments or same bank instruments, the payment would be realized immediately and a transaction number (BTR/BRN) and CIN

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

p and a stamp to the effect that the acknowledgment by the bank is subject to realization of the cheque / DD. The tax-payer need not visit the bank again to get CIN as the same will be communicated to him from GSTN as per the process detailed in para 47 & 48 below. However, if he does not receive any communication from GSTN within 3 days, he should visit the bank to ascertain the status of his payment.
44. Where the instrument is drawn on another bank, there should be a validation in the bank's system to prevent out station cheques (except those payable at par across cities), and to also prevent deduction of commission charges for instruments drawn on another bank in the same city.
45. The Authorized Bank would send the instrument for collection and the transaction would be treated as complete and successful only after the actual receipt of the amount by the said bank.
46. The bank will inform GSTN on real time basis in two stages. First when an instrument is given OTC. At this stag

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

n para 46 above with three additional details:
a) CIN;
b) Date of Realization of Cheque;
c) Time of realization of cheque;
d) Bank Transaction Number (BRN/BTN).
On receipt of the second message, GSTN would send a SMS to the tax payer, in addition to updating the status of the payment on its portal.
48. This 2 stage intimation by authorized banks is recommended for the following reasons:
a) Keep a watch on delays on the part of authorized banks in realization;
b) Maintaining a system based control as all branches of authorized banks will be allowed for OTC.
49. On receipt of the real time information for a successful transaction as per para 41 above (cash, cheque on same bank or DD) or receipt of the second message from Bank as per para 47 above (cheque drawn on another bank), the tax paid challan will be credited to the tax ledger account of the taxpayer. If the OTC payment was subject to realization (para 46), the initial status on the dashboard will state so. If the ch

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ystem as and when the response is received. Such recording should be system based rather than manual and include realization or dishonouring of the cheque, as the case may be, so that the IT software can take up further action including intimation to GSTN on real time basis;
d) Credit the realized amount into either GST pool account, if so, maintained by the authorized bank (in its e-FPB) and thereafter transfer the said amount into the individual tax head accounts as indicated in the challan (all Authorized banks must develop a suitable GST software for this purpose) or to credit the amount directly to the respective government's account (39 accounts).
e) In case the instrument is dishonoured, the presenting bank should inform GSTN.
52. It is to be noted that banks will have to develop a mechanism/IT application where all these amounts tendered at individual branches of an authorized bank are only handled through the e-FPB of that authorized bank. This is because the tax accounts

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

re 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 afte

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

uire 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 choo

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ls, 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 i

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

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

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

essage, 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

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

s 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 an

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

orities 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

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

nique 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

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ide for this mode i.e. payment across departmental counters. It was also stated that taxpayers have been provided various other modes to facilitate anytime, anywhere payment and this mode would be retrograde especially when e-payment is being declared as the preferred mode of payment. However, the departmental officers will accept the deposit of taxes during the course of enforcement and anti-evasion investigations including by flying squads, etc. While doing so, if the concerned person is not already registered, the departmental officer will create a temporary GSTIN on the GSTN common portal. For this purpose, GSTN will provide a separate module and a GSTIN series for giving temporary GSTIN. The officer will collect the amount in respect of all types of taxes payable by him in cash/cheque/DD from the said person, issue a temporary receipt to him, generate the challan from GSTN, fill up the challan (at a later stage, if not possible at that time) and remit the amount using Mode2. GSTN

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

naccurate reporting and delayed settlement of taxes is already in place in the case of Direct Taxes and the same may be put in place in GST regime. It is further recommended that a framework of desired features and validations at Banks for collection of taxes under GST regime should be devised by RBI in consultation with the Accounting Authorities. Any bank found not having built capabilities to adhere to the framework, should not be allowed to collect GST receipts. Due care should be taken so that discontinuities arising from manual interventions in the banks' internal processes are removed. The Committee also recommends that, over a long term, Accounting Authority should develop a service quality rating for the participating banks based on identified transparent and quantifiable parameters.
BANKING ARRANGEMENTS UNDER GST:
80. At present Central Government and each State Finance Department prescribes banking arrangements for collection of government taxes. At present, Central and S

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ervention for data entry, funds flow and exchange of data.
83. It is also noted that a participating bank in the current context has limited mandate for tax receipts as compared to that of an authorized bank. The mandate of participating banks, though essentially agents of RBI, is limited to acceptance of tax receipts through internet banking mode only. Whereas, authorized banks have a broader mandate of accepting government receipts through both internet banking mode and physical mode (OTC) of Cash, DD and Cheques, in addition to mandate of making government payments. In order to give a broader choice to the tax payers, and hence to enhance ease of doing business, it is recommended that the participating banks can also be allowed to accept GST receipts through OTC mode envisaged in this report.
84. Out of the superset of existing authorized banks and participating banks only those banks should be authorized to accept GST receipts who meet the minimum requirements suggested below. Th

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

T system should have the ability to receive challan data and to communicate successful remittances on real time basis to GSTN portal for both modes.
h) The collation of data and reporting to GSTN portal and to RBI should be system based and not require manual operations.
i) The standards of communication prescribed by RBI (ISO 20022) should be followed.
j) There should be an upfront (before being authorized) as well as periodic audit of the IT system and the centralized application for handling GST receipts. The system audit should cover operational, technical and security aspects as per terms of reference and periodicity set by GSTN in consultation with Accounting Authorities.
k) One branch of the concerned authorized bank in the entire country should be established / designated as the e-FPB (Electronic Focal Point Branches) to handle all backend operations of GST receipts including operation of 39 tax accounts, data collation, reporting and reconciliation with RBI / GSTN / Ac

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

SGST account for each State / UT Government), a common pooled account for cheque/Draft and CC/DC payments should be set up and operated by e-FPB ( but not required by those banks who can credit the amount 'on the fly').
q) As a part of the daily consolidated but transaction level report of successful receipts in each government account to RBI, there should be an assurance that all transactions credited to respective CGST, IGST, Additional Tax and SGST Accounts are being reported to RBI and no balances are left in these accounts meant for cheque realization. RBI will need to build a similar assurance for NEFT/RTGS remittances.
r) Suitable validations prescribed by GST Law should be inbuilt in the IT system / GST application. Some of such validations will pertain to non-acceptance of outstation cheques and non-deduction of cheque collection charges for OTC receipts, and mark up and collection of CC/DC charges (to be agreed) from tax payers.
86. It was agreed that the minimum standar

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ds, wherever required, to account for various taxes.
90. There is a need to standardize these accounting codes for all items covered under GST regime among all the States and UTs, since settlement of IGST would be based on centralized reporting. SGST will be accounted for by the States and credited to individual State Treasuries, through the existing system followed in each State. SGST will not be reflected in accounts of the Central Government.
91. There may be cases of mis-classification and erroneous scrolling under Major Heads of accounts which may lead to less or excess revenue settlements between the Centre and State(s). To deal with such transactions, detailed accounting procedures should be designed. It is recognized that it is IT system issue, and not an accounting issue. The debit from tax-payers account should result in auto-credit to respective accounts of Government of India and the concerned State Government. Except in case of remittance through any authorized bank incl

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

id amount along with related bifurcations of nature of tax liability, such as, Interest, Penalty, Fees, other charges, etc. Presently, the Tax Payment Challan information forms the basis of accounting and reconciliation between the banks, RBI, Tax authorities and Accounting authorities of the Centre/States/UTs. A list of sample tax accounting codes under GST is proposed in the table below:-
S. No.
Type of Tax Liability
Sample Accounting Code
1
CGST – Tax
00010001
2
CGST – Interest
00010002
3
CGST – Penalty
00010003
4
CGST – Fees
00010004
5
CGST – Other
00010005
6
IGST – Tax
00020001
7
IGST – Interest
00020002
8
IGST – Penalty
00020003
9
IGST – Fees
00020004
10
IGST – Other
00020005
11
SGST- Tax
00030001
12
SGST – Interest
00030002
13
SGST – Penalty
00030003
14
SGST – Fees
00030004
15
SGST – Other
00030005
16
Additional Tax – Tax
00040001
17
Additional Tax – Interest
00040002
18
Additional Tax – Penalty
00040003
19
Additional

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

l process discontinuities in banks, RBI and common portal should eliminate/reduce possibilities of errors. However, there may still be reconciliation challenges arising due to errors encountered during the stabilization phase of the IT systems of the stakeholders and their mutual functional integration. Even in the post stabilization phase, some errors may be seen due to problems external to the IT systems, e.g., in the public network used for sharing the data. A process and standard operating procedure for handling the errors, if they arise, will have to be established, as multiple agencies would be handling funds and related information pertaining to different governments.
98. The proposed GST payment process envisages a paradigm shift from the processes and validations currently being used for payment of taxes to the Government. This shift is aimed at establishing a convenient, consistent and efficient payment process for the tax payers as well as for the 37 governments simultaneou

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

by it from another agency earlier in the work-flow chain, and thereafter pass on the data to the agency next in the chain.
e) RBI will play the role of the aggregator for flow of funds as well as information from the banks.
f) GSTN will have the primary anchor position in the payment process with responsibility for information flow to various agencies whereas RBI will have the primary anchor's role in relation to funds flow, information flow about receipts and correction of discrepancies noticed during reconciliation process.
g) e-Scroll from RBI will be the basis for accounting, reconciliation and other incidental activities to be carried out by the accounting authorities of both Centre and States.
100. In view of these fundamental changes, the key Id for information exchange with banks and RBI should use the unique Id generated by GSTN, i.e., CPIN. Once the payment has been made by the taxpayer and CIN is generated and reported by the recipient bank along with its transaction

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

y out the reconciliation between those scrolls and the consolidated challan files communicated to the Accounting Authorities earlier in the day. The discrepancies should be communicated by GSTN to the Accounting Authorities and RBI simultaneously on the same day. The purpose of this reconciliation is to assist those Accounting Authorities who may not have IT systems to carry out transaction level reconciliation in an automated manner, and to identify systemic and service level issues for taking up with the authorized banks and RBI.
102. The role of GSTN in the reconciliation process should be limited to the above set of activities. GSTN should not be expected to take up MOE process for any error type as that is fairly resource intensive, requires manual appreciation of facts and is time consuming. The transaction level resolution of discrepancies through the Memorandum of Error (MOE) process with RBI and banks should be the responsibility of the respective Accounting Authorities.
Rec

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ies. 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 keeping the data error free by having suitable validations at the time of creation of CPIN. Key elements here are CPIN and GSTIN.
Second leg of communication of data (CIN with embedded CPIN) starts from Authorized banks / RBI to GSTN (T=0):
106. This communication is not meant to be the basis for accounting, but act as an enabler to reduce errors in the overall process and to facilitate fleet-footed monitorin

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

an 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;
c) with challan amount mismatch.
109. In all these cases, the resolution at e-FPB may require manual intervention. The bank may resend the data to GSTN after correction. If the bank is unable to resolve by T+1 reporting time to RBI, the bank should include the transaction in the luggage file with whatever CPIN data it may have for that transaction. It will be type (c) error in the third leg.
T

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

) 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 day should get reported to RBI in the luggage file. This discrepancy will be detected at the stage when GSTN and Accounting Authorities compare the challan data (CIN ) of the day received from authorized banks with the e-scroll of the corresponding date received from RBI on T+1 basis. If GSTN detects such a discrepancy, it will communicate the same to the relevant Accounting Authority and RBI. On

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

orized 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 identifying the missing transaction, putting it in a separate luggage file containing the UIN of the relevant MOE and then transmitting the same to RBI;
v) RBI will send a separate e-scroll relating to MOE to the concerned Accounting Authority containing the missing transaction;
Points at iv) and v) are design issues, which can be decided by GSTN in consultation with RBI. The reporting by

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

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 same day received from RBI on T+1 basis. In such cases, the correction mechanism will involve the following steps:
i) If CPIN and associated data reported in the scrolls received from RBI matches with GSTN's CPIN data, GSTN can forward the entire challan details of that CPIN to the concerned Accounting Authorities with a copy to Tax Authorities. There will not be any need fo

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

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 time of reporting to RBI on T+1 basis, the bank should report the transaction to RBI with whatever CIN data it has received from the e-FPB of authorized bank. The bank should not hold back any balance in the tax accounts beyond the reporting time to RBI in respect of transactions of the previous day. When such unresolved transaction is reported to RBI, it should carry

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

uthorities 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 have to initiate MOE in respect of their respective taxes;
ii) RBI to ascertain from e-FPB of the concerned Authorized bank / RBI (in case of Mode III) and get the discrepancy corrected within a time period of 2 days from the receipt of MOE from the Accounting Authorities;
iii) E- FPB of the concerned Authorized bank / RBI would verify the details in the CIN tra

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

stem 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. The error will be noticed only when the taxpayer on not receiving a credit confirmation SMS from GSTN or not finding the credit in his ledger inform GSTN. Steps involved in correction are:
i) In case of OTC payment through authorized banks in cash or by instruments drawn on the same bank, taxpayer will be provided with an instantaneous acknowledg

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

is 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 receipt in the e-scroll for the day, if NEFT/RTGS remittance was received. If the remittance was not received, RBI will inform GSTN accordingly. In turn, the tax payer will be intimated by GSTN for taking up the matter with his bank (through which NEFT / RTGS was effected by him) for deficiency of service.
f) Sum total of amount for a CIN repo

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

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 reported to GSTN by e-FPB of authorized banks but not by RBI in its e-scroll (CIN level);
b) Transaction reported by RBI in its e-scroll but not by e-FPB of authorized bank / RBI to GSTN (CIN level);
c) Transaction reported by RBI but with incorrect details of CIN (CIN level);
d) Sum total of the amount for CIN reported to RBI is lesse

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

State Government (some governments have that practice) should be communicated by the Accounting Authorities to the Tax Department's system for updating the records, which would finally contain following unique Ids for each receipt:
a) CIN;
b) GSTIN;
c) Bank Transaction Number (BRN);
d) RBI Transaction Number;
e) Accounting Entry ID Number/confirmation flag.
The presence of all the above mentioned five fields would constitute the assurance for credit to the government account with RBI, and the reconciliation and accounting in the government books.
Challan Correction Mechanism:
123. In view of the presumptions listed above, the requirement of providing for a challan correction mechanism would be minimal though not completely ruled out. The Committee recommends for providing the correction mechanism in following situations:-
a) ERROR IN GSTIN: This may happen in situations where the payment of tax is being made by either authorized representative such as CA or any other per

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

and tax administration should have no role to play in this matter.
b) ERROR IN MAJOR HEAD: In such a scenario, the bank though has collected the correct amount but has credited the wrong head of tax account. This would impact the transfer of funds to the account of the respective governments as bank has transferred the funds on the basis of the data not detailed in CPIN. Thus bank would be required to withdraw funds from one account and credit the other account(s). It is proposed to permit banks to rectify such error before the end of the day during which the amount has been received by the bank as at the end of the day, the amount would have been credited in respective government accounts and thereafter the same would also have been accounted by Accounting Authorities of the Centre and State. No correction in the challan data is required even in this case. If the error is noted after reporting of the credit on T+1 basis, the normal MOE process should be used.
c) ERROR IN TOTAL AMO

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

In the GST regime, the existing practice of entry of challan data at the bank branch level will be dispensed with as the challan would be shared on real time basis from the GSTN portal to the CBS of the authorized bank / RBI indicated in the challan.
127. Central Government Accounts (Receipt and Payment) Rules, 1983 provides for submission of Challan in form GAR 7 along with the payments to facilitate the Pay and Accounts Officer to classify the receipts accurately in his accounts. The form will need to be suitably modified for use in the electronic systems envisaged for GST payments. Almost all the information currently required in GAR 7 has been provided in proposed GST challan form. However, as discussed in para 14 above, the jurisdictional location code will not be available in the challan and the same would need to be mapped with the help of the backend system of each tax administration.
(Satish Chandra)
Member Secretary
Empowered Committee of State Finance Ministers
(Rashmi

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ith the following members:
Government of India
(1) Smt. Rashmi Verma, Additional Secretary (Revenue) Co-convener
(2) Shri P.K. Mohanty, Joint Secretary (TRU-I)
(3) Shri M. Vinod Kumar, Joint Secretary (TRU-II)
(4) Shri J.M. Kennedy, Director (TRU-II)
(5) Director/Deputy Secretary holding the charge of State Taxes Section
States Government
(1) Dr. J.B. Ekka, Commissioner of Taxes, Assam
(2) Shri Prashant Goyal, Commissioner, Trade & Taxes, Delhi
(3) Shri H.V. Patel, Commissioner, Commercial Tax, Gujarat
(4) Shri Sudhir Rajpal, Commissioner, Excise & Taxation, Haryana
(5) Shri Kifayat Hussain Rizvi, Commissioner, Commercial Tax, J&K
(6) Shri Ajay Seth, Commissioner, Commercial Tax, Karnataka
(7) Shri Shyam Jagannathan, Commissioner, Commercial Tax, Kerala
(8) Shri Amit Rathore, Commissioner, Commercial Tax, Madhya Pradesh
(9) Dr. Nitin Kareer, Commissioner, Sales Tax, Maharashtra
(10) Shri Abhishek Bhagotia, Commissioner, Commercial Tax, Meghalaya
(11) Shri Manoj Ahuja

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

./A.O., Empowered Committee of State Finance Ministers
 
Annexure-II
EMPOWERED COMMITTEE OF STATE FINANCE MINISTERS
DELHI SECRETARIAT, IP ESTATE, NEW DELHI – 110002
Tel. No. 2339 2431, Fax: 2339 2432 e-mail: vatcouncil@yahoo.com, vatcouncil@gmail.com
No.15/45/EC/GST/2015/20
Date: 3rd February, 2015
SUB-COMMITTEE ON PAYMENT PROCESSES UNDER GST
During the meeting of the Joint Committee on Business Processes for GST held on 2nd February, 2015, it was decided that a Sub-Committee should be constituted to consider the Report of the Committee for Finalizing Payment Processes under GST and to give its recommendations for the consideration of the Joint Committee on Business Process for GST. Accordingly, a Sub-Committee consisting of the following officers was constituted:
Government of India
1.
Shri Shashank Priya, Commissioner, GST Cell, CBEC,
Government of India
Co-convener
2.
Shri Upender Gupta, Additional Commissioner, CBEC Government of India
Member
3.
Shri Manish

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

members of the Sub-Committee are requested to kindly make it convenient to attend the meeting of the Sub-Committee. They are also requested to intimate their travel programme to Shri Ritvik Ranjanam Pandey, Commissioner Commercial Tax, Karnataka (Tel: 080-22264495, Fax: 080-22263595 and e-mail: ritvik@gov.in) so that necessary arrangements for their boarding, lodging and transport could be made under intimation to the Empowered Committee.
Sd/-
(Satish Chandra)
Member Secretary
Empowered Committee of
State Finance Ministers
Copy to:
Additional Secretary (Revenue), Government of India with the request to kindly request RBI, Principal Chief Controller of Accounts, CBEC and Controller General of Accounts to nominate suitable officers to attend the meeting in Bangalore and subsequent meeting of the Joint Committee on Business Process for GST, when the Business Process for payment is considered by the Committee.
Copy to: All the members of the Sub-Committee
Copy also to:
Adviser/O

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

ommissioner, Commercial Tax, Gujarat
6. Shri Riddhesh P. Raval, Assistant Commissioner, Commercial Tax, Gujarat
7. Shri Shyamal Misra, Commissioner, Excise & Taxation, Haryana
8. Shri Hanuman Singh, Additional Commissioner, Excise & Taxation, Haryana
9. Shri Zaffar Ahmad Bhat, Commissioner, Commercial Tax, Jammu & Kashmir
10. Dr. Shamim Ahmad, Additional Commissioner, Commercial Taxes, Jammu & Kashmir
11. Shri Ritvik Ranjanam Pandey, Commissioner, Commercial Tax, Karnataka
12. Dr. M.P.Ravi Prasad, Joint Commissioner, Commercial Tax, Karnataka
13. Shri M. Girees Kumar, Commissioner, Commercial Tax, Kerala
14. Shri M.I. Mansur, Assistant Commissioner, Commercial Tax, Kerala
15. Shri Sudip Gupta, Deputy Commissioner, Commercial Tax, Madhya Pradesh
16. Shri Rajiv Jalota, Commissioner, Sales Tax, Maharashtra
17. Shri P. Velrasu, Special Commissioner, Sales Tax, Maharashtra
18. Shri Manoj Ahuja, Commissioner, Commercial Tax, Odisha
19. Shri Sahadev Sahoo, Joint Commissioner, Co

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

yagi, Chief Controller of Accounts, CBEC
2. Alok Kumar Verma, Controller of Accounts, CBEC
CGA
1. Shri Chandan Mishra Dwivedi, Deputy Comptroller and General of Accounts
RBI
1. Shri G. Sreekumar, CGM, RBI
2. Shri Manish Parashar, Deputy GM, RBI
Empowered Committee of State Finance Ministers
1. Shri Satish Chandra, Member Secretary, Empowered Committee
2. Shri Bashir Ahmed, Adviser, Empowered Committee
PWC
1. Shri Kalyan K. Pal, PWC
Annexure V
Issue of charge back in CC/DC Payment
1. Under the charge back claim, a taxpayer after making payment through credit card may seek refund of the money till 60 days of the transaction. Usually such refunds can be sought under three scenarios:
(i) Payment was made fraudulently by someone using the card of others;
(ii) Extra payment was made because of some technical error during payment;
(iii) Some service was not delivered for the payment made.
2. During the past few years, there have been significant changes in the security sy

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

GSTN on real time basis but before the reporting to RBI on T+1 basis, the acquiring bank can refund the amount under real time intimation to GSTN. Thereafter, such double payment should not be reported to RBI.
5. In case the technical error is detected after reporting to RBI on T+1, the acquiring bank should send the claim to GSTN with full details. GSTN should verify its database, and confirm to the bank regarding double payment received against the same CPIN.
6. There should be a validation in GSTN's system that such double payments (para 4 and 5 above) are either not reflected in the tax payer's ledger or the second payment against the same CPIN is barred from utilization. Based on the confirmation from GSTN, the acquiring bank can refund the extra payment.
7. For scenario (iii) arising from claim of non-delivery of service, the acquiring bank should send the claims to GSTN with full details. GSTN can rebut the claim by providing a copy of the Challan (pdf file generated from it

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =

the Government and there was no denial of service) or accept the claim. If the claim is accepted, the process suggested in para 9 below may be followed.
9. In case the charge back is accepted after reporting to RBI (either in case of scenario (ii) or in case of scenario (iii) when GSTN's rebuttal is not accepted) and refund is made by the acquiring bank to the issuing bank, such refund should be reported as a new transaction to RBI. The report to RBI as well as the entry in RBI's scroll should be as a debit entry identified using the original CPIN. On receipt of such information, GSTN should debit the taxpayer's ledger and inform the Tax Authorities who should recover the amount from the said taxpayer.
 
Annexure VI
List of Banks presently authorised in Centre and States
1.
ALLAHABAD BANK
2.
ANDHRA BANK
3.
BANK OF INDIA
4.
BANK OF BARODA
5.
BANK OF MAHARASHTRA
6.
CANARA BANK
7.
CENTRAL BANK OF INDIA
8.
CORPORATION BANK
9.
DENA BANK
10.
INDIAN BANK
11.
IND

= = = = = = = =

Plain text (Extract) only
For full text:-Visit the Source

= = = = = = = =