2015-10-14

REPORT OF THE JOINT COMMITTEE ON BUSINESS PROCESSES FOR GST ON GST PAYMENT PROCESS

Empowered Committee of State Finance Ministers

New Delhi- April, 2015

CONTENTS OF THE REPORT

1. Introduction

2. Payment by taxpayers through internet banking including Credit Card/Debit card

A. Process involved in e-payment of GST

B. Role to be played by each stakeholder

(i) GSTN

(ii) e- FPBs of authorised banks

(iii) e-Kuber (Core Banking System) of RBI

(iv) CAS

(v) e-PAOs of Centre and e-Treasuries of State Governments

(vi) Pr CCA, CBEC & Accountant General of States

3. Over the Counter payments through Authorised banks

A. Process involved in OTC payments

B. Role to be played by each stakeholder

(i) Branch of authorised bank

4 Payment through NEFT / RTGS from any bank (including other than Authorised bank)

A. Process involved in OTC payments

B. Role to be played by each stakeholder

(i) Branch of remitter bank

(ii)RBI performing functions akin to authorized banks

5 Payment across departmental counters

6. Penalty mechanism for erring banks

7. Banking arrangements under GST

8. Accounting System under GST

9. Proposed Accounting System under GST

10. Reconciliation of Receipts

11. Reconciliation by GSTN

12. Reconciliation by Accounting Authorities

13. Resolution of Reconciliation Outcomes (discrepancies noted during the reconciliation process)

First leg of communication of data

Second leg of communication of data

Third leg of communication of data

Fourth leg of communication of data

14. Recording by Tax Authorities

15. Challan Correction Mechanism

16. Challan Format

17. Constitution of Joint Committee on Business Processes (Annexure_I)

18. Constitution of Sub_Committee on Payment Processes under GST (Annexure_II)

19. List of Participants of the meeting held on 16th April, 2015 and 17th April, 2015 (Annexure_III)

20. GST Challan Form (Annexure_IV)

21. Issue of charge back in CC /DC payment (Annexure_V)

22 List of banks presently authorised in Centre & States (Annexure_VI)

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



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 on GST Payment Process. Pursuant to that decision, the Member Secretary, Empowered Committee constituted the Sub-Committee vide his memorandum letter dated 3rd February, 2015 (Annexure-II). Shri V Rajendaran, DG (Government Accounts), CAG, Mrs. Krishna Tyagi, CCA, CBEC, Government of India, Shri Madan Mohan, Jt. CGA, Government of India and Shri G Sreekumar, CGM, RBI were co-opted as members of the Sub-Committee. Shri Ravneet S. Khurana, Deputy Commissioner GST Cell, CBEC also participated in the deliberations of the Sub-Committee. The Sub-Committee met in Bengaluru on 14th and 15th February, 2015 and on 06th and 7th April, 2015. The Sub-Committee also exchanged drafts on emails during the interregnum period. The Sub-Committee submitted its final report on 10th April, 2015.

3. The report of the Sub-Committee was discussed in the meeting of the Joint Committee of Business Processes held in Delhi on 16th and 17th April 2015 and was accepted with certain modifications. The meeting of the 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 required classification of heads of accounts indicated on the Challan;

d) Designing the format of a new Challan for use by the taxpayers paying GST;

e) Developing a detailed accounting procedure common to both Central and State Governments for GST, covering all relevant aspects of payments, accounting and related banking arrangements.

6. It is noted that under GST regime, some taxes and duties may remain outside the purview of GST and will continue to be collected in the manner prescribed under existing accounting procedures/rules/manuals, etc. This means that two types of challans (one for GST and other for non-GST) will be used and accounted for by the respective Pay and Accounts Offices (PAOs)/State AGs.

7. The payment processes under proposed GST regime should have the following features:

a) Electronically generated challan from GSTN Common Portal in all modes of payment and no use of manually prepared challan;

b) Facilitation for the taxpayer by providing hassle free, anytime, 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 expression ‘authorized bank’ is used throughout this Document.)

b) Over the Counter payment (OTC) through authorized banks;

c) Payment through NEFT/RTGS from any bank (including other than authorized banks).

9. Mode of payment described at b) above will be available for payments up to ₹ 10,000/- per challan only. Model GST law may have suitable provisions in relation to this. However, there should not be any IT system constraints for this i.e. the systems should be able to receive payments through all three modes irrespective of the amount. Other means of payment, such as payment by book adjustment as is presently being allowed by Government of India to some departments / State governments or payment by debit to export scrips, while paying tax would not be allowed. It is also noted that all taxpayers under Centre are paying taxes electronically and possibly the same situation exists in some State Tax administrations. It is desirable that under the GST regime, all taxpayers should 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 discussed separately along with the role of stakeholders involved, process of reporting, accounting and reconciliation of data. As already mentioned above, it is envisaged that for each mode of payment, the challan will be generated electronically at the GSTN and no manual challan will be used under any mode of payment.

I. PAYMENT BY TAXPAYERS THROUGH INTERNET BANKING THROUGH AUTHORIZED BANKS AND THROUGH CREDIT CARD/ DEBIT CARD:

12. With increasing spread of internet and electronic communication, this mode has emerged as one of the preferred modes of tax payment for both the taxpayers and administrators. As the name suggests, this mode of payment involves payments by the taxpayers that utilize the electronic network, right from the generation of the challan by the taxpayer to the ultimate reconciliation of the data by the Accounting authorities. Before understanding the process involved in e-payments, it is important to list the stakeholders involved in this mode of payment. The following 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 the challan;

b) By authorized representatives of tax payers by logging on to the GSTN Common Portal whereafter the list of registered taxpayers represented by him will be displayed. He can select any tax payer on whose behalf he proposes to pay GST and challan details for such tax payer will be auto populated;

c) By grant of temporary Registration number by any one Tax authority on GSTN Common Portal which can be used by both the tax authorities for facilitating tax payments on behalf of an unregistered person. Such a situation can arise during enforcement action by a tax authority and this temporary registration can be later converted into a regular registration number (GSTIN) if the tax payer has a regular GST liability to discharge after the enforcement action (detailed procedure described in Para 78 below);

d) By creation of a challan without requirement of USER ID and Password, for enabling payment of GST by a registered or an unregistered person on behalf of a taxpayer as 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. Upon creation of the draft challan, the taxpayer will fill in the details of the taxes that are to be paid. The challan page will have sets of mandatory fields, which the user has to provide. The tax payer will have the option to pay CGST, IGST, Additional Tax and SGST concurrently. The tax payers can partially fill in the challan form and temporarily “save” the challan for completion at a later stage. A saved challan can be “edited” before finalization. After the tax payer has finalized the challan, he will generate the challan, for use of payment of taxes. The remitter will have option of printing the challan for his record. The challan so generated will have a 14-digit (yymm followed by 10-digit) Unique Common Portal Identification Number (CPIN), assigned only when the challan is finally generated, this will help the portal and other authorities in identifying the challan. The CPIN would be a running serial number to be initialized every calendar month. 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. 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 in paras 123 and 124 below.

16. Since there are three modes of payment, the tax payer has to choose the e-payment mode. This mode will also cover payment by Credit/Debit Card which can be used only after log in on the GSTN.

17. Once e-payment mode is selected, options will be shown to taxpayer to choose between Internet Banking and Credit / Debit Cards for making payment. In case Internet Banking mode is selected, a field with drop down box detailing names of various authorized banks, registered with GSTN for Internet Banking, would be displayed. The taxpayer will have option of choosing his preferred bank for Internet Banking. Credit and Debit Cards of all banks shall be accepted. However, the payment gateway services should be obtained by GSTN from the authorised banks or their payment gateway SPVs only. To encourage competition, preferably more than one such gateway should be provided on the GSTN portal, with display of their respective charge rate and service performance level. 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 required to pre-register his credit card, from which the tax payment is intended, with the GSTN system. GSTN may also attempt to put in a system with banks in getting the credit card verified by taking a confirmation from the credit card service provider. The payments using credit cards can therefore be allowed without any monetary limit to facilitate ease of doing business. In the event of such claims, recommended standard operating procedure, prepared in consultation with RBI, is enclosed as Annexure-V.

18. In case of Payment Gateway, the first choice for a taxpayer would be to select the card type to be used for making the payment. Upon choosing the card type, the taxpayer would be displayed available gateway service providers servicing the card type. Once a taxpayer chooses a gateway, the interface of the gateway would be invoked. Alongside, GSTN will forward the same electronic string as was passed for Internet Banking (details in para 19 below). The service provider will capture and verify 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 could be reduced to T+1 basis by suitable negotiations with the payment gateways. It is recommended that suitable negotiations may be carried out by the Accounting authorities and RBI with payment gateways to credit the amount on T+1 basis.

19. In case of payment through Internet Banking, once the taxpayer chooses a particular bank for payment of taxes, GSTN will direct him to the website of the selected bank. Alongside, GSTN will forward an electronic string to the selected bank carrying the following details for each challan on real time basis:

a) GSTIN;

b) CPIN;

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.

GSTN in consultation with banks would decide about the requirement of merchant code as a GSTN identifier.

20. Taxpayer will make the payment using the USER ID and Password provided by the bank to enter into the secured e- banking area of his bank. He will select an account 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 reported by the banks along with its own Unique Bank reference number (BRN). Such CIN is an indicator of successful transaction and will be used as a key field for accounting, reconciliation etc. by taxpayers, accounting authorities and tax authorities. After every successful e-payment transaction, there will be an instantaneous reverse flow of information through an electronic data string from the collecting bank to the GSTN containing the following details:

a) CIN;

b) GSTIN;

c) Bank Reference number (BRN);

[Since there could be maximum of four credits against one debit, banking practice may be ascertained by GSTN. If such transactions (i.e. four credits against one debit require multiple BRNs i.e. one for each credit entry), all BRNs should be reported.]

d) Challan amount;

e) Date of Payment;

f) Time of Payment

22. If the transaction cycle is not completed because of failure of credential verification, there would be no response from the bank to portal informing about the 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 (one for each Major heads i.e. CGST, IGST, Additional Tax & SGST and 4 Minor heads for each Major Head i.e. Interest, Penalty, Fees & Others).

Role to be played by each Stakeholder:

GSTN:

25. In the framework of GST administration, GSTN is envisaged to be a “pass through portal” that works as a common interface between taxpayers, tax authorities, authorized banks, RBI and accounting authorities. So GSTN will play the following role in this mode of payment:

a) Generation of challan along with CPIN;

b) Facilitating e-payments by providing a linkage to Internet Banking interfaces of authorized banks and payment gateways of authorised banks for CC/DC based payments;

c) Receipt of real time data from IT system (e-FPBs) of each authorized bank regarding successful completion of payment transaction by the taxpayer (CIN);

d) Generating receipt containing BRN No. of collecting bank for taxpayer acknowledging receipt of payment by the bank. A further facility of generating receipt containing 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 current day). The file will be sent to the respective accounting authorities. At this stage, the challan data will also include CIN (i.e. CPIN + Bank Code) and BRN reported by the banks. GSTN would generate this file on all working days including the days on which no transaction took place;

h) GSTN will receive 39 consolidated e-scrolls from RBI (one each for CGST, IGST and Additional Tax and one each for SGST for each State/UT Govt, see para 26(a) below) on T+1 basis. The contents of the scrolls are mentioned in para 28 below;

i) On receipt of consolidated transaction level e-scrolls from RBI during latter part of the day, GSTN will carry out preliminary system based reconciliation with reference to the successful transactions already reported real time by the banks and consolidated by GSTN as per step (g) above. GSTN will append the RBI scroll Number on each challan and thereafter forward its reconciliation results to the respective accounting authorities;

j) Once the amount reflected 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 Committee has been constituted by the EC to examine the operational issue of Additional Tax and if it is decided that this tax will be collected by the respective State Government and retained by them, separate accounts for every State will have to maintained for Additional Tax also, on the lines of SGST;

b) Sending real time data regarding successful completion of payment transaction by the taxpayer (CIN);

c) At the end of each day (T+1), each e-FPB will be responsible for preparing daily luggage files Major Head wise (CGST, IGST, Additional Tax and SGST) for each government detailing receipts from all modes of payments on a particular day (including nil payment days) and forwarding it to RBI in the morning. Each luggage file will have a Unique Serial Number which will be a running serial number extending through a financial year which will facilitate identification of missing files. This luggage file number will become part of the electronic file. For operational purposes such as size of 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 respective Accounting Authorities, if they desire so.

27. Each authorised bank should have one or more service branch in each State to serve as GST help desk and to receive queries / e mails to resolve the issues from Taxpayers, Tax Authorities and Accounting Authorities.

e-Kuber (Core Banking System) of RBI:

28. The following functions will be performed by RBI (e-Kuber):

a) RBI will consolidate luggage files received from all authorized banks, debit their accounts and correspondingly credit the CGST, IGST and Additional Tax accounts of Government of India and SGST accounts of each State/UT Government maintained in RBI(39 accounts);

b) RBI would send consolidated, digitally signed e-scrolls, along with all the challan details, for each type of Tax (one each for CGST, IGST and Additional Tax for Government of India, and separate e-scrolls of SGST for each State/UT Governments) per day (including NIL payment day) after including the amount collected by it in Mode – III to Accounting Authority 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 communicate the statements to the respective accounting authorities within 3 days from end of the report month.

Central Accounts Section (CAS) of Reserve Bank of India, Nagpur:

29. CAS, Nagpur reports daily consolidated credits and debits to each Government and Accounting Authorities. Such daily statements cover all receipts and payments for the respective governments including inter-government transactions. GST credits will be one of the items reported by CAS, Nagpur in its daily statements. The scroll number mentioned in para 28 (b) (ii) above should be the credit identifier in the daily statements.

e-PAOs (Electronic Pay and Account Offices ) of Centre and e-Treasuries of State Governments:

30. In the case of Central government, the existing e-PAO (Central Excise) and e-PAO (Service Tax) can work as e-PAO (IGST), e-PAO (CGST) in the GST regime. Another e-PAO (Additional Tax) can be operated till the time that the Additional Tax remains in force. All these e-PAOs can be located at Delhi 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 transactions of the previous day (date value T=0);

d) E-FPB of authorized banks would also send such scrolls on T+1 basis to central accounting authorities and to those e-Treasuries that may so desire;

e) They will also receive from GSTN, later in the day, results of reconciliation by GSTN with the bank’s and its own data;

f) The e-PAO and e-Treasuries of the States would reconcile the challan details [received in step b) above] with the e-Scroll information [received from RBI in step c) and from GSTN in step e) above], and do the detailed revenue accounting based on the information provided in the e-scroll provided by RBI to the accounting authorities;

g) They will receive TAXPAYER master from the respective Tax Authorities (backend module) and the same would be required to be kept updated on real time basis by the respective Tax Authorities. The said TAXPAYER master would be used by the Accounting Authorities for mapping the challan details with the Jurisdictional PAOs by having a suitable 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 Accountant General of the states:

Pr. CCA, CBEC (PRINCIPAL CHIEF CONTROLLER OF ACCOUNTS) AND ACCOUNTANT GENERAL OF THE STATES:

31. The following functions will be performed by them:

a) They will receive daily and monthly Put Through Statements from CAS, RBI;

b) They will also receive verified Datewise Monthly Statement (DMS) from e-PAOs and e-Treasuries of the States respectively;

c) The reconciliation of both the data will be carried out by them;

d) Office of Pr. CCA CBEC will also consolidate the total collection and forward the same to the Office of CGA for further consolidation.

II. OVER THE COUNTER PAYMENT THROUGH AUTHORIZED BANKS:

32. Another mode of payment that will be employed in the proposed GST regime will be Over the Counter (OTC) payments which will enable the taxpayers to make payment of the taxes at the Authorized Bank’s counter. This will be beneficial for smaller taxpayers that do not have access to internet banking facilities. CCA raised an issue that the authorized 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 ₹ 10,000/- per challan), will access GSTN for generation of a challan through which payment is to be made.

35. Upon creation of the draft challan, the taxpayer will fill in the details of the taxes that are to be paid. From the available payment options, the taxpayer would select option of cheque, DD or cash based payment. The name of the authorized bank and its location (city/town/village) where the instrument/cash is to be presented is required to be filled in necessarily. No outstation cheques are to be accepted except those which are payable at par at all branches of bank having presence at that location. In case cheque or DD is selected as the mode of payment, entry of Instrument details is recommended, but not mandatory, as the taxpayer may not have the instrument ready at the time of challan generation. The tax payers can partially fill in the challan form and temporarily “save” the challan for completion at a later stage. A saved challan can be “edited” before finalization. After the tax payer has finalized the challan, he will generate the challan, for use of payment 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 taxpayer will approach the branch of the authorized bank for payment of taxes along with the instrument or cash. Since the tax payer is required to pay four types of taxes and the amount is required to be credited in the accounts maintained by bank for each type of tax, one option for the tax payer is to submit four instruments for crediting to the respective accounts. Four instruments may not be required if pooled account for realization of instrument is maintained. The matter was discussed in detail and it was recommended, that in the interest of facilitating the payment, each e-FPB should maintain a GST pool account so that the tax payer can issue only one instrument which will be written in the name of the GST pool account of the concerned bank. The bank’s IT system upon realization of the instrument, will immediately first credit that amount to the GST pool account and then immediately transfer that amount to the respective tax accounts [CGST, IGST, Additional Tax or SGST(39 accounts) 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 the database of banks and also to facilitate the cashier / Teller to verify the details of the challan submitted by the remitter. This will eliminate the need for manual feeding of the challan details by the cashier / Teller in the banking system and thereby reduce the errors in data processing.

39. The taxpayer should preferably carry two copies of the challan, one for the bank’s record and another for himself to get acknowledgement. In the alternative, he can use a normal pay-in-slip and mention CPIN and challan amount in it. On approaching the bank, he should provide the challan itself or at least CPIN number on normal pay-in-slip to enable the cashier / teller to fetch the challan details in his system. There should be a customized IT application (software) in the bank’s system to accept GST receipts on OTC basis. While each branch can accept GST receipts, the credits should always be to the GST accounts maintained and operated by e-FPB . The banks not having such system should not 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 will be generated immediately at the authorized bank’s system which will be unique for each and every transaction. Such successful transactions shall be intimated to GSTN on real-time basis with details similar to those mentioned in para 21 above. This message will convey to the common portal that the payment has been successfully received at the bank’s counter.

42. After generation of BRN, the bank cashier may give a printed receipt from his system including the Bank’s transaction number (BTR/BRN) and CIN. However, if it not found feasible to print a separate receipt, the cashier should record the BRN and CIN generated from the system, on the tax payer’s copy of the challan or pay-in-slip as acknowledgment.

43. In case an instrument drawn on another bank in the same city is presented, the payment would not be realized immediately. In such case, CIN will not be generated immediately, and cashier should write only the system generated acknowledgment number on the challan / pay-in-slip 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 stage the Authorized bank will forward an electronic string to GSTN which will contain the following details:

a) CPIN;

b) GSTIN;

c) Challan Amount;

d) Bank’s acknowledgement number.

On receipt of the above first message, GSTN should send a SMS to the tax payer, in addition to showing the status of the payment on its portal as subject to realization.

47. The bank’s system would send a second message to GSTN once the cheque is realized, the total amount is credited first to GST pool account and thereafter the funds are credited to the respective tax accounts as per CPIN data (as stated in para 34 above, GST pool accounts are not required to be maintained by those banks who can credit the amount in the respective tax accounts ‘on the fly’). On the day of realization, it will become a successful transaction to be reported to RBI on T+1 (T = 0 being day of realization). After the successful completion of transaction, the second acknowledgement will have the same details as mentioned in 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 cheque is dishonoured, the presenting bank should inform GSTN about the fact of dishonour and same will be informed by GSTN to taxpayer and reflected on his dashboard.

Role to be played by each stakeholder:

50. The role played by each stakeholder in this mode of payment will be the same as mentioned in Mode I. There is an additional stakeholder in this mode, namely Branch of Authorized bank that receives the remittances and its role is discussed below.

Branch of Authorized bank:

51. Being the first point of contact for the remittance by the taxpayer, the branch of the Authorized bank receiving the payment will play a key role in the accounting and reconciliation of data with GSTN. It will perform the following functions:

a) Accept the payment only through the customized GST software/screen in its system.

b) Provide an acknowledgement to the tax payer;

c) Send the instrument (if pertaining to another bank) to the clearing house for realization and record the result in the IT system 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 will be maintained only by the e-FPB. Individual branches have not been authorized by RBI to operate Government account. It is also important to provide for a mechanism in GST Law to debar those tax payers whose cheques have once bounced from using this mode of payment. The most effective mechanism will be through GSTN which should debar such defaulters from using this mode.

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-

Show more