/
Challenges for E-invoice

Challenges for E-invoice

1.E-invoicing will apply only to B2B invoices, though the maximum amount of fraud and tax evasion takes place through B2C sales, as no ITC is involved - An essential goal for such a system must also be to plug this loophole and lay down a mechanism so that customers are able to report non-compliant invoicing which can then help curb tax evasion at its source

2.The network must come with minimal glitches, as downtime and failure impact compliance negatively - The capacity for the upload of e-invoices is based on the GSTR-1 data submitted over the last two years, as per the release. Hence, if the GSTN is prepared with the numbers, it should also be prepared with up-to-date robust technological systems, with the necessary back-end infrastructure and customer support in place

Things to be taken care of by the registered user

1. IRN is a unique combination of GSTIN No. , Document No. & Financial Year, hence it will be mandatory for all users to maintain an Invoice series with a suffix as financial year. If the Invoice No. is not unique every financial year , the IRP system will not generate IRN against that repetitive Invoice No.

  1. Company Logo cannot be printed in the Document. Logo of the ERP provided by the software company can only be printed on the document. Also the same would not be a part of JSON sent to IRP.

  2. Digital Signature by the IRP will be proof of valid Invoice. Signature by the Company is not mandatory hence the same will be not be considered as a proof of valid Invoice.