eInvoicing
Proprietary format | Reference |
---|---|
Cygnet GSP e-Invoice | 1.1 - GSP e-Invoice schema 2.1 - Cygnet GSP - Enriched API Specification |
Cygnet GSP Enriched e-Invoice | 1.0 - Cygnet GSP Enriched e-Invoice Schema 2.1 - Cygnet GSP - Enriched API Specification |
GST-India Invoice Document | 1.01 - User manual - Bulk generation and cancellation tool 1.1 - e-Invoice schema |
Under the Goods and Services (GST) Law, businesses are required to report electronic invoices to the government for validation before they are delivered to the customer. These e-Invoices must be reported to the Invoice Registration Portal (IRP) managed by the GST Network (GSTN). The IRP electronically signs the invoice and applies a unique identification code called an Invoice Reference Number (IRN) and a unique QR code. Only invoices with an IRN are considered valid.
Also, an e-Way bill must be created by the Supplier or the Transporter and generate the e-Way bill number (EBN) before transporting goods across India. This e-Way bill is generated in ILSP together with the output file type GST-India Invoice Document. To generate an IRN or an IRN with EBN, taxpayer can integrate with GST Suvidha Provider (GSP) or manually upload invoices in the format of .json files to IRP. ILSP supports both solutions.
Select GST-India Invoice Document to generate .json files and manually upload to IRP. This option supports generation of multiple invoices in a single .json file.
Select Cygnet invoice to integrate with Cygnet's eInvoicing services. This solution uses LSP Webservices Gateway for connectivity. The enriched invoice uses Cygnet's own schema and allows the user to send more information, as well as giving them the ability to use CygNet Portal's features that the standard GST invoice cannot do.
- Customers must arrange their own account with GSP.
- The eWaybill is currently not supported by Cygnet.