NetSuite India GST Setup: E-Invoicing, TDS, and Compliance

GST e-invoicing in Zoho Books compliance in NetSuite requires the India Localisation SuiteApp. This module adds GSTIN management, HSN/SAC codes, GST tax calculations, E-Invoicing, E-Way Bill generation, and return data export to NetSuite’s core financial module. Here is how to set it up.

Installing the India Localisation SuiteApp

Go to Customization > SuiteBundler > Search & Install Bundles and search for “India Localisation” or the bundle ID provided by Oracle. Install the bundle, which adds India-specific fields, tax codes, and transaction forms to your NetSuite instance.

GSTIN and Tax Registration Setup

After installation, configure your company’s GSTIN for each state where you are registered. Go to Setup > Company > Subsidiaries (or Locations for single-entity) and add the GSTIN. For companies registered in multiple states, each location or subsidiary has its own GSTIN.

The SuiteApp automatically determines whether a transaction is inter-state (IGST) or intra-state (CGST + SGST) based on the seller and buyer GSTINs.

HSN and SAC Code Configuration

Assign HSN codes (for goods) or SAC codes (for services) to each item in your item catalogue. The India Localisation adds an HSN/SAC field to the item record. These codes appear on invoices and are required for GST return filing and E-Invoicing.

E-Invoicing Integration

The SuiteApp connects to the IRP (Invoice Registration Portal) for automatic E-Invoice generation. When a B2B invoice is approved, NetSuite sends the invoice data to the IRP and receives the IRN and QR code. These are stored on the transaction record and included on the printed invoice.

E-Way Bill Generation

For shipments above Rs. 50,000, generate E-Way Bills directly from NetSuite. The SuiteApp adds transport fields (vehicle number, transporter ID, distance) to the sales order or invoice form. Submit to the E-Way Bill portal and the bill number is linked to the transaction.

TDS in NetSuite

Configure TDS sections and rates in the India Localisation settings. When recording vendor bills, select the applicable TDS section. NetSuite calculates the deduction, tracks the liability, and generates data for quarterly TDS returns (Form 26Q).

GST Return Data Export

The SuiteApp generates data files for GSTR-1, GSTR-3B, and GSTR-2A reconciliation. Export these and upload to the GST portal or use a GST return filing tool. NetSuite does not file returns directly, but the data export matches the government’s required format.

Common Pitfalls During GST Setup

Most GST problems in NetSuite trace back to how locations, items, and GSTINs were set up during the initial rollout, not to the SuiteApp itself. A few mistakes show up repeatedly in India Localisation implementations.

• GSTIN not tied to the correct location or subsidiary. Because the India Localisation determines IGST versus CGST+SGST from the GSTIN on the transacting location, a location created without its GSTIN attached before transactions start flowing through it forces a retroactive fix across every invoice already raised from that location.
• HSN and SAC codes copied from a spreadsheet without validation. The Invoice Registration Portal checks HSN and SAC codes against its own master list at the time of E-Invoice submission. An item imported in bulk with a code that does not exist in that master, or a services item tagged with a goods HSN code, generates an E-Invoice rejection that has to be traced back to the item record and corrected before resubmission.
• Goods and services mixed on one item type. An item record configured as a generic non-inventory type without the correct goods or service classification can pick up the wrong tax treatment by default, particularly on composite invoices that include both a product and an installation or service charge.
• Inter-company transactions set up after go-live rather than before. Stock transfers between subsidiaries in different states need inter-company GST invoices from day one. Retrofitting this after several months of transactions means reconciling GST returns for periods where the inter-company tax entries were missing or incomplete.
• Skipping IRP sandbox testing before go-live. The Invoice Registration Portal provides a test environment separate from production. Businesses that configure E-Invoicing directly in their live NetSuite account without first validating a batch of sample invoices in the sandbox tend to discover formatting or master-data issues only when a real customer invoice gets rejected.

The 24-Hour E-Invoice Cancellation Window

Once NetSuite sends an approved invoice to the IRP and receives back an IRN and QR code, that E-Invoice can only be cancelled within 24 hours of generation. This is a rule at the portal level, not a NetSuite limitation. After the window closes, the only way to correct a billing error is a credit note or debit note against the original invoice, not a cancellation.

This has a practical effect on how invoice approval should be configured. If NetSuite’s approval workflow lets an invoice trigger E-Invoice generation immediately on approval, any error caught after 24 hours, a wrong quantity, an incorrect customer GSTIN, a rate mistake, becomes an accounting correction rather than a simple void. Many finance teams add a manager review step before final approval specifically to catch these errors while the invoice can still be cancelled cleanly, rather than after the E-Invoice has already been reported to the government.

Because most of the setup effort goes into validating HSN and SAC codes against the government master and testing E-Invoice submissions in the sandbox, the smoothest go-lives are the ones that budget real time for this validation step rather than treating the SuiteApp installation itself as the hard part. Installing the bundle takes an afternoon. Getting every item, location, and GSTIN correct before the first invoice goes out is the part that actually takes the effort.