Skip to Content
Technical Articles

GST India : E-Invoicing Solution

The GST Council of India has approved the introduction of ‘E-invoicing’ or ‘electronic invoicing’ in a phased manner for reporting of business to business (B2B) invoices to Invoice Registration Portal (IRP) System. E-Invoice is mandatory from 1-Oct-2020 for GST India taxpayers having turnover more than 500 crores in the financial year 2019-2020.

Table of contents:

  1. Overview
  2. Solution approach (Notes)
  3. Prerequisites
  4. Common issues/queries
  5. Important topics to consider while implementing Automated e-Invoicing solution
  6. Conclusion

Overview:

SAP proposes to introduce an e-Invoice solution to enable customers to comply with the new e-Invoice mandate.

Process%20of%20generation%20of%20eInvoice

Process of a generation of eInvoice

 

There are two sets of solutions released from SAP for eInvoicing:

  • Automated Solution:

Direct integration to eInvoicing (IRN) system via GSP. This is a licensed solution developed by SAP which will provide direct integration between the SAP ECC or SAP S/4HANA On-Prem systems or S/4HANA Cloud and the eInvoicing (IRN) via certified GSPs using the SAP Cloud Integration Platform. This will enable taxpayers to upload the payload from the backend SAP system to the eInvoicing (IRN) portal, generate the Invoice Reference Number and link the Invoice Reference Number (IRN) with the billing document in the backend system.Integration%20of%20SAP%20e-Invoice%20and%20e-Way%20Bill%20solution

Integration of SAP e-Invoice and e-Way Bill solution

In the automated process, the preparation of standardized format is done by SAP. Refer to the attached document in KBA 2894627 for more details on the business process, licensing, mandatory parameters, etc.

  • Manual Solution:

SAP manual process will read the response file and store the information of IRN, QR code & digital signature in the standard table and it will link the original invoice with IRN along with the current status in the table. The preparation of a standardized format (JSON request file) needs to be generated offline by the customer.

Solution approach:

  • Automated Solution:

SAP delivered notes can be referred to, in the implementation guide (SAP_Document_Compliance_e-Invoicing_for_India_Implementation_Guide.pdf) attached to the eInvoice master note 2884058 for the automated process.

Implement all the latest notes as mentioned in the guide as this will keep the system consistent and avoid errors.

  • Manual Solution :

Refer to the eInvoice master note 2872365 – GST IN: How to configure eInvoice (Invoice Reference Number (IRN)) for the manual process.

Prerequisites:

There are no pre-requisites required if GST solution pre-requisites are met (like minimum support package, refer the note 1175384 for the same).

Common Issues/Queries:

Refer KBA 2894627 – GST IN: E-invoice Frequently Asked Questions (FAQ’s)

Refer KBA 2872365 – GST IN: How to configure eInvoice (Invoice Reference Number (IRN))

Some of the frequently encountered issues with the automated e-Invoice solution are mentioned in section 7 in the implementation guide(SAP_Document_Compliance_e-Invoicing_for_India_Implementation_Guide.pdf) attached to the eInvoice master note 2884058.

Refer KBA 2973923 – GST IN : eInvoice : QR Code FAQs

Important topics to consider while implementing Automated e-Invoicing:

ECC/S4 configuration:

Automatic e-Document creation in EDOC_COCKPIT:

To create e-Documents for certain billing/document type, refer 2908488 – GST IN: DCS/eInvoice: Unable to create eDocument

To configure automatic e-Document creation for direct FI invoices, refer 2908256 – GST IN: DCS/eInvoice: How to configure automatic e-Document creation for direct FI invoices. In direct FI postings, the plant will not be available always as it is not needed and the ORG Unit will not be filled. The BAdI BADI_EDOCUMENT_IN_EINV, method FILL_ADDINFO_DETAILS can be used to fill the field ORG_UNIT1.

To restrict eDocument creation for a complete document type, remove the document type entry from the view EDOINEINVT003V. Alternatively, BAdI EDOC_ADAPTOR can be used to define customer-specific rules for the e-Document generation.

The solution provides sample code for method IS_RELEVANT and it can be accessed through the BAdI_SAMPLE CODE.txt attached to SAP Note 2631687.

Auto submission of e-Invoices to IRN portal:

In case the e-Document is generated but the e-Invoice is not auto submitted, refer the section “Steps to Create Inbound Destination for auto-submission of eInvoice” provided in the attachment ‘2958861-Manual_Post-Implementation_Steps .pdf’ of SAP Note 2958861.

Ensure that the “Supervisor Destination” is maintained in the transaction SBGRFCCONF. For more details regarding Supervisor Destination, refer to the link.

Ensure that the customizing view EDOINEINVINVCFGV is configured accordingly. Refer the section 6.3.2.13 View EDOINEINVINVCFGV in the document in SAP_Document_Compliance_e-Invoicing_for_India_Implementation_Guide.pdf attached in the latest version of SAP master note 2884058.

E-WayBill generation along with IRN:

Enable the view EDOINEINVINVCFGV to configure the e-Way Bill to be generated along with eInvoice. Refer section 6.3.2.13 View EDOINEINVINVCFGV of implementation guide attached to master note 2884058.

‘Submit More’ option in EDOC_COCKPIT is for creating an e-Way bill with IRN. Submit more option is allowed when the e-Document is in “eInvoice Generated” status.

At the submit option or auto-submit e-Way bill configuration is validated but at the time of Submit More EDOINEINVINVCFGV configuration is not checked.

Once IRN is generated successfully, use the ‘Edit’ button to update e-Way bill information and then click on submit more.

In the e-Invoice node, the response payload for eWay bill specific files will not be displayed. In case e-Invoice and e-Way bills are generated in a single submission, the same response will be available and can be seen via the ‘Display’ option. XML files (request/response) against any eWay bill generated via India eInvoice node will not appear under the ‘History’ / ‘Display’ option of India eWay bill node.

Download XML file according to the status of e-Document:

e-Document Created: Select the eDocument -> Click on ‘Display’ -> XML -> Download
e-Invoice Generated: Select the eDocument -> Click on ‘Export File’

IRN for Inward invoices:

The two notes mentioned below are released to capture IRN in the supplier invoice:

2958243 – GST India: IRN Development for MIRO/FB60/FB65
2948482 – GST India: DDIC Activities for IRN Capture in Supplier Invoices

As of now, the process will be a manual activity by the user to write the IRN number during each invoice posting through MIRO. IRN field is provided at the header level in MIRO.

Duplicate IRN:

IRN will not be generated for invoices with identical key parameters (Eg: Supplier GSTIN, Invoice Number/ODN, Document type, Financial Period, etc.). In case there are invoices generated with identical ODN, assign a separate number range in the view EDOINEWBCONFIGV.

More on this can be found inside the configuration document attached under eInvoice parent note 2884058.

Alternatively, BADI BADI_EDOCUMENT_IN_EINV, Method FILL_ADDINFO_DETAILS can be used to determine the Invoice Number as per the scenario.

Dispatch address details:

The dispatch details are taken from the plant because the ships are moving from the plant location.

To fill these details with the business place address, use the BADI BADI_EDOCUMENT_IN_EINV eDocument India eInvoice Enhancements.

TCS provision:

The changes to include the TCS amount as other charges as part of the standard are provided in below notes including some other bug fixes. There is no need for an enhancement to include the TCS amount as other charges after implementing the below notes.

2969855 – eDocument India Gen: Bug fixes for TCS and Tax base amount
2966226 – SAP Solution for e-Invoice/IRN India: Bug fixes for issues like original invoice number, export invoice, display action, cancel e-Invoice, and other issues

RCM cases:

IRN is only required for B2B RCM invoices from the supplier perspective and not from the buyer and receiver perspective as this is not a legal requirement and there is no API available for the same in Govt. portal.

For RCM invoices, the supplier is responsible for the creation of e-Invoice. Please refer to line#13 in NIC FAQ.

Finalize:

After finalizing, no action can be performed on the e-Document. The status color will be green once finalizing the e-Document is done.

Cancellation:

According to govt, IRN cancellation can only happen within 24 hours of its generation. Any cancellation after 24hrs could not be possible on IRN, however one can manually cancel the same on the GST portal before filing the returns.

If the source document needs to be canceled in SAP post 24 hours of IRN generation:

  1. Perform the ‘Cancel eDocument’ action under ‘More’ in EDOC_COCKPIT and it should fail with the error “Error Code 2270: The allowed cancellation time limit is crossed, you cannot cancel the IRN.”
  2. Use the ‘Allow Cancellation’ action under ‘More’ in EDOC_COCKPIT to enable the cancellation of the source document. The status will be changed to ‘ALLOW_CANCEL’ to allow source document cancellation.

Note: This does not have any impact on IRP portal data and only allows to cancel source document in the SAP system. After canceling the source document, ensure to cancel the outward liability while filing GSTR1 returns.

Contingency:

In case the automated solution is being used for an e-Invoice generation but the e-Invoice got generated offline, later eDocument status can be updated using contingency mode. The contingency report J1IGIRN can be used to upload the IRN response file back to EDOC_COCKPIT.

Download the respective response JSON file from the IRP portal and upload it in the J1IGIRN transaction. The e-Document status will get updated and associates the IRN details in e-Document tables.

The below notes can be implemented to enable J1IGIRN:

2966960 – SAP Solution for eInvoice/ IRN India – Issues with tax amount, cancel eDocument and buyer address
2971204 – SAP Solution for eInvoice/IRN India: Contingency Process Enablement

Cancellation within 24hours: The correct schema/ JSON download option from the IRP portal for cancel response has not been received yet.

Master data setup:

Update the J_1IEXCDEFN table with the condition types. Refer the below note and attachment within that note:

2434329 – GST INDIA S4HANA: Changes to tax procedure and pricing procedure->Tax Procedure Configuration.pdf

Capture Legal Name of Customer:

Follow the steps mentioned in the note 2921570 – GST IN: How to capture legal name of Customer/Supplier/Business Place

To extend the standard fields, BADI BADI_EDOCUMENT_IN_EINV, method CHANGE_HEADER_DETAILS can be used to capture more information.

IRN for Export invoices:

For B2B invoices, if bill-to and ship-to partners are the same, Ship Dtls need not be provided.

To capture Export Port details, refer to 2921673 – GST IN: How to capture Export Port details for generating e-Invoice & e-Way bill-> Export_Port_Details_For_eInvoice_eWay_Bill.pdf.

If the bill-to-party is located outside India, it is considered as B2C supply. eInvoice is not required for B2C invoices.

In case, of export of goods ship to party should be maintained as a port address. To identify the port address below should be configured.

i. Create a new partner function, as mentioned in KBA 2921673.
ii. Create each port as a customer master.
iii. Maintain partner function which is defined in step 1 in view EDOINEWBCONFIGV. Refer to the implementation guide.(Note:2884058)
iv. Maintain partner function and respective port customer at the time of sales order/outbound delivery creation.

Implement the BADI ‘BADI_EDOCUMENT_IN_EINV’ and use the method ‘CHANGE_HEADER_DETAILS’ to fill the export details.

QR Code generation:

Print IRN and QR code:

It is confirmed from the IRP team that the QR code should be printed in an encoded format.
The tax officials will scan the QR code that is printed and will be verified with a signature which is part of the QR code and this will make the QR code authentic.
Hence QR code is printed as it is from the response.

Download the latest version of the below note and update the XML file logic in the print form with the attachment present in the note.
2482854 – GST: Invoice Form (ECC)

Consulting note:
2884502 – GST India S4HANA: Corrections to print IRN and QR Code in Invoice Form (S4HANA)

2900304 – GST India S4HANA – QR code is not getting printed in encoded form on Print form of outgoing invoices

For more information about the QR code refer to link.

Dynamic QR code for B2C cases:

Refer to the FAQ published by the government on the differences between the B2B eInvoice QR code, and B2C dynamic QR code (for POS payment purposes).

FAQ clearly mentions that “This requirement has no relevance or connection with e-invoicing mandated for B2B Supplies and Exports by a notified class of taxpayers. ”

Display complete QR code in table EDOINEINV :

As per govt. legal notification, QR code needs to be encrypted. As per SAP standard, the complete QR code cannot be viewed at the table level (in EDOINEINV).

Go to edoc_cockpit transaction, Select the e-Document and Click on Display which will display/preview the XML. The complete QR code can be seen under the tag <n0: SignedQRCode>.

Connecting ECC/S4 ->CPI -> GSP->NIC:

SOAManager:

For the SOAManager configuration, refer to section 6.2.2.1 of the implementation guide in the latest version of SAP master note 2884058. Refer 1361688 – Interop issue: SAP consumer calls 3rd party provider.

If certificate-based authentication is being used in SOAManager, to enable certificate-based authentication between the source system to SAP Cloud Platform Integration, the certificate presented by the source system should be signed by one of the Certification Authorities (CA) approved by the SAP load balancer component.

Refer to the SAP help document on the list of supported CAs.

Refer the link for creating the CSR and importing the certificate response.

Ensure that the same logical port name is maintained in SOAManager and in the view EDOSOASERV.

iFlow deployment: 

For the e-Invoicing solution, there is no Cloud Application available. The complete solution works from the SAP ECC/S4 system itself with the help of SAP Cloud Platform Integration. Related to CPI iFlow deployment, URLs, and user API credentials GSP will share the guide.

Before configuring the logical port in SOAManager, set up SCPI tenant with iFlows shared by GSP. Refer to the implementation setup guide provided by GSP for the same.

Once the SCPI setup done, configure the router URL obtained after deploying iFlows in SCPI in SOAManager.

The same iFlow cannot be deployed in a single-tenant with different names. For different systems sharing the same CPI tenant, the same router endpoint URL can be configured in the SOAManager of both the systems. Multiple iFlows are not needed to be deployed for different systems.

A summary of the configuration is available in the eInvoice implementation guide which is attached to master note 2884058.

Download e-Invoice payloads: 

Refer KBA 2966494 – GST IN: eInvoice: How to download eInvoice JSON request/response from SCPI

IRP Links:

e-Invoice Trial Website – Contains latest updates, FAQs, Bulk generation tool

Developer’s portal – Contains API overview, Sample JSON

IRN Validations version 1.03 – Contains payloads schema, validations

Conclusion:

The common and important configurations to consider while implementing e-Invoicing are addressed in this blog to connect SAP ECC/S4 ->CPI -> GSP->NIC seamlessly.

Further, raise an incident in the component CA-GTF-CSC-EDO-IN-IV, for queries related to the e-invoicing automated process and in the component XX-CSC-IN-SD, for queries related to the e-invoicing manual process.

12 Comments
You must be Logged on to comment or reply to a post.