Q: Purpose of the API
Ans: To get invoices uploaded in IRP and their status of auto population in GSTTR1. Even if you change any value in GSTR1 for auto populated invoice, this API will always return data uploaded in IRP.
Q: If GET E Invoice API is used to pull the data from e Invoice (IRP portal) whether it will auto populated into GSTR 1 or ASP should get the data into system and do another action with Save GSTR 1
Ans: GST System is fetching this data and also auto populating it in GSTR1. This API is returning data fetched by GST System from IRP. So all auto populated invoices will be also available in getB2B/getCDN… APIs of GSTR1.
Q: If the data is auto populated from IRP via push then we don’t see any data auto populated in GSTR 1 till now?
Ans: It has not yet gone to production yet.
Q: If the data is auto populated from IRP did user required to push again the same data via save GSTR 1?
Ans: Not required.
Q: Please confirm that IRN generated date will be the KEY for Return period determination.
Ans: No return period will be determined from invoice date as per current design.
Q: What is the purpose of those new field Auto Draft status, Auto Drafted Date, Error Code and Error Message in get Einvoice API. Can you throw some light on what these fields are?
Ans: It is for, whether Invoice got auto drafted in GSTR1 or not, date of auto drafting, if there is any error in auto drafting then error code and message.
Q: What will be the filing flow of GSTR-1 after implementation of this new API?
Ans: GSTR-1 flow is to be same as present.
Q: Is it always necessary to fetch E-invoice data before filing or can we upload imported data?
Ans: No it is not necessary but it is a good practice to do reconciliation, so that over writing of auto populated data can be avoided. Also successfully auto populated data will be available through getB2B/getCDN ….APIs of GSTR1 also.
Q: What will be the change in SAVE API? IS there any increase in save Parameters like- IRN no. and/or IRN date etc?
Ans: There will be no new addition.
Q: It is mentioned in Excel attribute that ctin wise data can also be fetched however the same parameter is not available in request URL
Ans: for getEinvoice api it is not available for attribute sheet or url
Q: In b2b section, Invoice type-CWB (Custom Bonded Warehouse) is also available, how we are deriving this parameter because no such information is going in IRN generation?
Ans: It will not come from IRP. As save and get APIs are for GSTR1 and in GSTR1 this field exist, so it will remain in APIs but will not be available in data auto populated through IRP data.
Q: In request payload for get Einvoice API, there is afrom_date field, which date will be considered for this from_time. E.g. an invoice for which IRN is generated has following dates Document date is 10/10/2020, IRN generation date is 12/10/2020 and Auto Populate date is 13/10/2020. What from_time we need to send in request payload in order to get this invoice?
Ans: It can be used to get data after a particular date-time. It will be based on auto population date (GST System receipt date)
Eg: consider that Document date is 15-10-2020 and it is added into GST system on 19-10-2020. If from_time is specified as 16-10-2020, as it was inserted on 19-10-2020 that document will be part of response.
Q: The field Ack no., Ack. date, signed QR are not added in any of the APIs. (Even not in GET Einvoices API) Will these be included at a later stage?
Ans: There is no plan to include it. IRN will be the key for all auto populated data.
Q: If IRN auto populated data is edited then will that flag also be available in Get B2B/CDN/EXP/CDNUR?
Ans: Source, IRN no and date will be removed once auto populated data will be edited through GSTR1 Online/Offline/API save.
Q: If we send any delete request from API for an invoice which is already auto populated in these sections, then will it be deleted from this section or retained with a flag marked as Deleted?
Ans: Record will be deleted from only GSTR1. It will be available in get einvoice API.
Q: If someone deletes the full auto populated data from these sections and then save all invoices again (all data may be same or edited in some invoices and not edited in some) through API or added from UI or offline tool, then will it be compared with the “Get Einvoice” data and will the IRN nos and date be brought back to this collection for respective invoices?
Ans: Data coming from E-invoice (IRP) will be kept separate and it will not change. User can edit anything in GSTR1 and GSTR1 will reflect changed data. This change will be tracked for analysis purpose.
Q: If there are some invoices in “Get Einvoice (New API)” and the status of IRN is Cancelled then these will not be auto populated in “Get B2B/EXP/CDNUR/CDNURA” collections. Let us know if our understanding is correct.
Ans: There are many scenarios around it:
- If cancelation happen on the same day. Data will be available in getEinvoice API but not be auto populated in GSTR1.
- If cancelation happens next day than it will be first auto populated in GSTR1 and on cancelation it will be deleted from GSTR1 if user has not edited that invoice,
- If user has edited GSTR1 data then nothing will change in GSTR1.
Q: Earlier we had asked this question but at that time it was still under discussion, is it now decided? Which date will be considered for auto population: Document Date or IRN generation date? Let us know if our understanding below is correct in the example:
If Document date is 28.10.2020 but IRN is generated on 05.12.2020
(a) if Oct 2020 return is not yet filed, then this document will be populated in Oct 2020 month
(b) If Oct 2020 return is already filed then this document will be populated in Nov 2020 month
(c) If Nov 2020 return is also already filed then this document will be populated in Dec 2020 month (i.e. open month)
Ans: As per current implementation if return is filed than records coming for that period in future will only available in getEinvoice API of October month only. It will not be auto populated in any other period.
Q: While saving invoice data through APIs, if we are sending all invoices that are already auto populated by GSTN, again for save, without changing any data, then will it also be flagged that it is edited? Additionally, in such cases or any cases where any edit is done through API, the fields like IRN, source type and IRN generation date will still be retained or removed?
Ans: Please refer ansers above
Q: When are the APIs expected to be released to us on sandbox for testing?
Ans: It will be by mid of next week. Provide time. I think we are only releasing getEinvoice API. Not autopopualtion to GSPs.
Q: Currently there are no common GSTINs on sandbox for einvocing and GSTN. So how will we do the testing for the same? Will we be allowed to add GSTN sandbox GSTINs on einvocing portal? or will the einvocing/NIC test GSTINs will be automatically added in GSTN portal?
Ans: We will provide you some GSTIN for testing.