1 / 4

e-invoice API

The 39th GST Council Meeting deferred the roll-out date for e-invoicing gst to 1st Oct 2020. This gives businesses to get prepared and for the Govt systems to stabilise and integrate. New E-invoicing API specifications have been released on 14-May-2020 on the sandbox aka the test system of Govt.

ishagst19
Download Presentation

e-invoice API

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. E-invoice API Released Updated on 5th Aug 2020: Version 1.03 of E-Invoice API specification is published for testing on 05th Aug 2020 in sandbox. The modifications are in accord with the revised version of e-invoice schema- Version 1.1, published through GST Notification 60/2020 of Central Tax dated 30 July 2020. For details on varies according to new schema, it is possible to check on our website E-Invoice LIVE Date: 1st October 2020 -- Version 1.1 E-Invoice Schema Published . Updated on 23 July 2020: Taxpayers with turnover of Rs. 500 cr & over from the FY 2019-20 are mandated to Create e-invoice from October 2020 Released on 14th May 2020: Version 1.02 of all E-Invoicing API specification were published on 14th May 2020 on sandbox. The specification largely has changes associated with validation and brand new API for Generate EWB from IRN. Read below for details. The 39th GST Council Meeting deferred the roll date for e-invoicing into 1st October 2020. This provides companies to acquire also for and ready the Govt methods to stabilise and integrate. New APIs for e-invoicing are published Govt's evaluation procedure. Together with the APIs, eWay Bill and e-invoicing generation stream was enabled. Hence while sending invoice details for IRN generation, in case transport details are contained, eWay Bill Number (EWB) will have created. The APIs accessible for invoice are 1.Generate IRN -- Wherein transport details could be supplied alongside invoice details. According to transport details are supplied e-way bill amount gets created 2.Generate E-way Bill by utilizing IRN -- By the IRP portal , a E-way Bill could be made by supplying the IRN The next table summarises the functioning of this Bill generation flow Data you send API to be used Response from IRP Points to note · Invoice details Generate IRN · IRN · Generate EWB by IRN (API) not required · EWB with validity · All transport details

  2. · Invoice details Generate IRN · IRN · Generate EWB by IRN (API) cannot be used as EWB number is generated for the invoice · EWB (but not active – only Part A is created) · Minimum transport details (Transporter ID, Mode of transport, Distance) · Update PART B of NIC eWay Bill system to be used for updating vehicle details · Invoice details Generate IRN · IRN · Generate EWB by IRN can be used as · No transport details · No EWB against the invoice is generated · IRN Generate EWB by IRN · EWB with validity · Subsequent actions for EWB · All transport details · Invoice details · Generate EWB by IRN · EWB (but not active – only Part A is created) · Update PART B of NIC eWay Bill system to be used for updating vehicle details · Minimum transport details There aren't any data field associated changes in brand new APIs, however the validation rules are included. We're testing these validation rules and discussing our observations. The IRIS input format stay same and we're considering to incorporate a fresh input format where you can supply IRN and transport details to create the EWB number. The new specifications are available in https://einv-apisandbox.nic.in/index.html Released on: 6th March 2020

  3. E-invoice API Specification were published on 6th in accordance with the upgraded e-Invoice standard fields. In a move Government is mandating e-invoice in India from October 2020 that was scheduled to be mandated from April 2020. Under this typical businesses with turnover of over a hundred CR are expected to enroll each of their invoices together with the government portal site and create Invoice Reference Number (IRN). The GSTN systems are set up and testing APIs were made readily available for GSPs and taxpayers . Given it had been a testing phase, changes in e-invoice API specification were expected. GSTN published updated e-invoice normal fields. E-invoice API Specifications in accord with GSTN published subjects are published. Crucial modifications in New E-Invoice API Specification and its effect When compared with the earlier API version, the newest version has significant changes concerning data fields and its own technical specification. All of the changes in API result in proximity of this e- invoice regular released by GSTN, which could get educated. The newest specifications supply E-way Bill generation which will allow auto-generation of E-way Bill, subject to supplying the applicable data. On powerful E-way bill generation, the details will be returned together with IRN and QR code Added API for creating EWB utilizing IRN continues to be supplied. In case E-way bill details Aren't supplied during creating IRN, then that brand new API may be utilized There are some validation rules worth noting Validation Rule Impact The Document Date can be yesterday or today’s date. The maximum time gap between invoice generation and getting IRN can be at most 1 day. Back-dated or IRN for earlier dated invoices will not be allowed Document number should not be starting with 0, / and -. Also, alphabets in document number should not have alphabets in lower cases. If so, then request is rejected. Revisit the invoice numbering sequence. GST Invoicing rules however do not have any such conditions.

  4. Responsibility of Invoice and IRN generation in case of reverse charge transactions for B2B, is with the supplier of such goods and services. ‘Reverse Charges’ can be set as ‘Y’ in case of B2B invoices only and tax is being paid in reverse manner as per rule. Even in the case of Reverse Charged invoices, the seller has to generate the IRN. In case the supplier is SEZ unit, then he cannot generate e-Invoice. Only suppliers can initiate IRN generation. Hence if SEZ cannot generate e-invoice, then from purchase side invoices received from SEZ will not have any IRN e-invoice(IRN) cannot be re-generated for the cancelled e-invoice(IRN) also Revisions to invoice need to managed through Debit or Credit Note. Cancellation of IRN is equivalent to cancellation of invoice, which makes the invoice void for any further actions IRN cannot be cancelled, if the Valid/Active E-way Bill exists for the same. IRN and E-way Bill are tightly integrated and taxpayers need to accordingly align their systems. IRN should not be passed as part of the request; it is generated by the e-Invoice system and sent as response. IRN will be generated by IRP only. Taxpayers systems, if are generating IRN, should not be sent to IRP Separate validation rules for bill generation are supplied. We will keep you posted on our observations and are doing impact analysis of these changes. The specifications are available in E-invoice API Sandbox You can read more about e-invoicing here: e-Invoicing under GST becomes compulsory from 1st October 2020 IRIS Onyx is an automatic, integrated and easy e-invoicing solution! It's a solution that could integrate with your charging methods smoothly and create IRN without any disruption.

More Related