e-invoicing Structure
The government has recently released a blueprint for implementing the E-invoicing system all over India, which proposes a working model as well as a standard format for the generation of E-invoices.
We shall look into the fundamentals of E-invoicing, to understand its mechanics in a better way.
The Two Important Components of the E-invoicing Model
The E-invoicing working pattern has been agreed upon globally with some minor variations in the mode of implementation. In India, it comprises of two essential components as given below:
- Invoice Registration Portal (IRP) – The invoices, credit notes, and debit notes which are generated by the taxpayers, should be registered on the IRP, which subsequently generates a unique reference number known as the Invoice Reference Number (IRN), a QR code, and a digital signature for these items. In fact, an invoice will be valid for the purpose of Input Tax Credit, refund, etc., only if it is registered on the IRP
- A standard format for the E-invoice – This standard pattern comprises of data fields and the necessary specifications. It is highly recommended for the businesses/taxpayers to upgrade their systems so as to follow this E-invoice format which enables seamless interoperability as well as data exchange all through the system.
The E-invoice Standard
The standardized E-invoice format recommended for India has been formulated in accordance with the global practices and the industry requirements for businesses in India. Further, this format has been confirmed after consulting with the respective trade authorities, the Institute of Chartered Accountants of India (ICAI), and also as per the opinions from the public.
There are around 120 fields, out of which about 50 are to be uploaded mandatorily on the Invoice Registration Portal for attaining the reference number as well as the digital signature.
Section
|
Compulsory |
Non-compulsory |
Total |
Scope |
Details of Invoice |
11
|
7 |
18
|
Recognizing the distinctiveness and nature of invoices like the invoice number, type, date, etc., and also the IRP-generated details like the IRN |
Details of Items |
9
|
24 |
33
|
Details of line items like quantity, HSN, tax rate, etc. |
Invoice Reference Details
|
2 |
8 |
10
|
Provides reference for previously generated or supplementary documents for the invoice |
Additional Details of Items |
1
|
8 |
9
|
Extra details which are related to line items like batch, barcode, serial numbers, etc. |
Details of the Suppliers
|
5 |
5 |
10
|
GSTIN and address of the suppliers |
Details of the Buyers |
6
|
3 |
9
|
GSTIN and address of the buyers |
‘Ship To’ Details |
7
|
2
|
9
|
Address and other information like mode of supply, type of transaction, etc. |
‘Dispatch From’ Details
|
4 |
4 |
8
|
Address and other information like E-commerce operator through which it was dispatched, state, etc. |
*Details of Supporting Documents |
0
|
2 |
2
|
The URLs which support the documentation, if any |
*Payment Details |
4
|
5 |
9
|
Payment terms, account information, etc. |
Total |
49 |
68 |
117 |
|
These sections are non-compulsory. If used, the mandatory fields are highly recommended. For other sections, ‘compulsory’ indicates that it is essential for registering on the IRP. In the case of line item, the data would repeat for each of these.
The E-invoicing Workflow
After the taxpayers generate the invoice using their respective accounting/ERP systems, the procedure of getting it registered with the government on the IRP, should be carried out.
There exists two components for the E-invoicing workflow namely,
- The communication between the government and the taxpayers
- The communication between GST, E-way bill system, and the IRP
Now let us look into the details of these two E-invoicing components.
The communication between the government and the taxpayers
The taxpayers are required to upload the compulsory fields from the invoices to the IRP in the JSON format. Further, there is provision to upload it through different methods like offline tools, GSPs (GST Suvidha Providers), web portal, mobile app, SMS, and via direct API.
Apart from providing a standard format for E-invoice, the government has also offered a model in which a unique IRN would be generated, which is technically referred to as ‘hash’, using SHA-256. Although the taxpayers could generate the IRN using their respective systems, the invoice would be valid only if it is registered with the IRP. The IRN thus generated along with the digital signature and QR code, would be reverted to the taxpayers through the same channel.
The communication between GST, E-way bill system, and the IRP
Considering the high volume of transactions on the IRP system while getting the invoice registered, the IRP comes with multiple nodes known as ‘Registrars’. The taxpayers have the option to register their invoices via any of these Registrars, and further, the latter preserves the data for the past 24 hours.
The IRP system is connected to the GST system, which acts as the repository of all IRNs, so as to ensure that there is no duplication of records. This arrangement also enables the populating of GST ANX-1 for the suppliers. Further, the E-invoice data is made available in the E-way bill system, and the transporters/taxpayers would just have to update the information on Part B in order to obtain a valid E-way Bill Number.
In fact, the taxpayers would have to upload the invoice data only once to the IRP system, wherein, the GST and E-way bill requirements would be dealt with.
To conclude, the basics of the E-invoice standard has been dealt with in detail here, which helps you to understand the entire process in a better manner.