A country-specific hotfix to support Electronic invoice under GST for India in Microsoft Dynamics AX 2012 R3

Summary

An electronic invoice is a legally accepted digital tax receipt document that your organization registers at Invoice Registration Portal (IRP). By using Microsoft Dynamics AX to generate electronic invoices, you help make sure that the electronic invoices that your organization generates are secure, confidential, authentic, and legally acceptable. You can also make sure that required standards are applied to your electronic invoices.

You can generate an electronic invoice for the following documents:

• Customer invoice

• Free text invoice

• Project invoice

• and their Credit notes

More information

Prerequisites for using electronic invoices

To use electronic invoices in your organization, you must complete the following tasks as prerequisite:

• Obtain credentials for accessing sandbox and/or production e-Invoice System environment according to instruction at e-Invoice System Portal - https://einv-apisandbox.nic.in/apicredentials.html.

Note: You will need your GSTIN, Username, Password, Client ID and the Client secret.

• Download archive with public certificate from https://einv-apisandbox.nic.in/einvapiclient/EncDesc/GetPublicKey.aspx, using above mentioned credentials for logging in.

• Install the certificate on the local computer.

Configure a digital certificate for communication with IRP

Complete the below steps to extract certificate and import it for the local computer:

 1. Double-click the downloaded certificate file having '.cer' extension.

2. In the opened window click "Install Certificate…":

3. In the next window select "Local Machine" and click Next:

4. In the next window select the option "Place all certificates in the following store" and click Browse:

   Select "Personal" folder and click OK:


   Then click Next.
5. In the next window click Finish:

6. Installation is complete:

 

Information that is included in electronic invoices

An electronic invoice includes the following details:

• The name, address, contact information and GSTIN numbers of the organization (seller) and a customer (buyer)

• The invoice number, the date, and the document type

• Details of goods and services for each item sold:

• • Serial number of the item

  • Indication whether it is a service supply

  • SAC \ HSN code

  • Quantity, unit of measure and unit price

  • GST rate

  • Applied charges or discounts

  • Totals for invoice line

• The document total details containing itemization of invoice totals

Configuring system to use electronic invoicing

Please complete the below procedures to set up the system to use electronic invoicing for India.

Working with electronic invoices

When you post an invoice for e-invoice enabled customer from a sales order, Free text invoice or Project invoice proposal, the electronic invoice will be created. You get information in notification center that Electronic invoice [……..] has been created.

The central place to work all electronic invoices is Accounts receivable > Periodic > eInvoices > Electronic invoices (India). Review Details tab to see all the information which will be populated at different stages of electronic invoice processing.

Source invoice opens an invoice journal for the invoice used as base for electronic invoice. Upon electronic invoice registration, among other information you get the IRN and QR code that can be printed in Tax invoice and Debit\Credit reports available in the Sales or Project invoice journals:

Adding a field to JSON electronic invoice

This topic is addressed to users customizing the JSON electronic invoice to include additional information, in necessary. It is provided only as guidance and illustration for a person possessing required skills to customize the product using X++.

1. Identify the contract which corresponds to the JSON part you are going to modify. Einvoice contract classes have the following name pattern Einvoice*Contract_IN. For example:

2. • EInvoiceSupplierInformationContract_IN (with 2 descendants for customer and project invoices: EInvoiceSupplierInfoCustInvContract_IN and EInvoiceSupplierInfoProjInvContract_IN)

   • EInvoiceBuyerInformationContract_IN with 2 descendants for customer and project invoices: EInvoiceBuyerInfoCustInvoiceContract_IN and EInvoiceBuyerInfoProjInvoiceContract_IN)

3. Add a method to the parent abstract class which will return the needed data. In case data is extracted differently for customer and project invoices, override this method in each descendant and provide the necessary implementation. Otherwise, method can be added to the abstract parent class only.

4. Identify the class responsible for JSON generation. Such classes have the following name pattern "Einvoice*Details_IN" and implement ITaxEngineJsonSerializable interface. For example:

5. • EInvoiceSellerDetails_IN

   • EInvoiceBuyerDetails_IN

6. Add a variable to the class declaration corresponding to the parameter you are going to add to the JSON file.

7. Add a parm- method for this variable.
   

8. Modify getJsonAttributes method correspondingly by adding the newly created parm- method to the end of the list returned by the getJsonAttributes  method. Also, in the getJsonAttributes you will have to add the attribute name - just the same as should be written in JSON file.
   

9. In the EInvoiceCreateOutputFile_IN class locate the method responsible for creating a JSON part which you are changing. For example:

10. • insertSeller

    • insertBuyer

11. Add a line to this method in order to add new data to the JSON. For example

_sellerDetails.parmGSTIN(supplierInformationContract.getGSTIN());

This line will get the GSTIN number from the contract and will pass it to the "Details" class.

If your parameter cannot be empty, use the following pattern for additional validation:

    if (!_sellerDetails.parmGSTIN(supplierInformationContract.getGSTIN()))

    {

        ret = checkFailed(strFmt("@SYS136411", "@SYP4887805"));

    }

Note: Compile the project with your changes and restart all the AOSes before testing these changes.

Frequently asked questions

Q: Can I specify additional criteria to be considered when selecting invoices for electronic processing, either to register or cancel invoice?

You can review and modify queries used for invoice after using Send or Cancel function in Accounts receivable > Periodic > eInvoices > Electronic invoices (India). Button Select opens system query form to setup additional or modify existing query criteria.

Q: Where can I find detailed information what went wrong for an invoice which was not successfully registered?

You can review received error code end message in Accounts receivable > Periodic > eInvoices > Electronic invoices (India).

Q: What is not is cope of electronic invoice solution for India?

• Digital signature by seller

• Generation of IRN

• ISD Invoice

• AP e-Invoice import

Q: What are the supported formats of electronic invoice for India?

The export of electronic invoice can be done in JSON format that containing all required fields defined in technical specification. If there is another format or you need to add extra information to the electronic invoice message, it is to be done as customization. Please refer to Adding a field to JSON electronic invoice section of this article, for more details how to extend the supported JSON format.

Q: What are the supported integrations for Indian electronic invoice registration?

The supported out of the box integration is to IRP directly. Any other integration, for example with any GSP of your choice, is to be custom built by your ISV or implementation partner.

Note: Integration through GSP is not supported by Microsoft natively.