ERPNext GST 2026 Readiness Checklist for Indian SMEs

Every GST change lands on the invoice your ERP produces, and 2025–26 brought several. For an ERPNext user, readiness is a concrete checklist. Item tax templates must reflect the GST 2.0 structure: 5%, 18% and a 40% rate, from 22 September 2025, with tobacco and pan masala moving to 40% (biri 18%) when their compensation cess ended on 1 February 2026. E-invoicing must be on if your turnover ever exceeded ₹5 crore. The 30-day IRN limit applies at ₹10 crore and above. MFA must be set up for everyone who uses the government portals. And the Ship-To GSTIN change for e-invoices and e-way bills, announced for 1 August 2026, is on hold, so it needs watching rather than a deadline.

If your ERPNext runs a current India Compliance release and your tax templates already use the new rates, most of the work is done; what teams usually miss is GSTIN data on addresses and invoices left in draft. I am Manoj, and I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru. This is the checklist I work through with a client.

What does GST 2026 readiness mean for an ERPNext user?

It means each current GST rule is reflected in the system's configuration and daily routine. Five parts move: the rates on your items, e-invoicing at the ₹5 crore line, the 30-day IRN limit, MFA on the government portals, and the address data the Ship-To GSTIN change will depend on if it returns. Miss one and invoices get rejected or go out wrong.

None of these are ERPNext bugs; they are rule changes your setup has to keep up with. ERPNext gets GST features through the open-source India Compliance app from Resilient Tech, with no licence fee; its API features use an India Compliance account with API credits. What you need is an update and data-hygiene routine, which the rest of this guide gives you.

Skimmable summary: 2026 readiness = GST 2.0 rates, ₹5 crore e-invoicing, the 30-day IRN limit at ₹10 crore, portal MFA and clean address GSTINs, all set in India Compliance.

Which GST rule changes affect ERPNext in 2026?

Five changes, each with its own date and action in the system:

I keep this table on GST projects because it separates one-time setup (rates, e-invoicing) from ongoing habits (30-day limit, MFA) from changes to watch (Ship-To GSTIN). The dates come from CBIC notifications and GSTN advisories listed in the sources; confirm your own turnover category with your CA.

Skimmable summary: GST 2.0 (22 Sep 2025), ₹5 crore e-invoicing (Aug 2023), the 30-day IRN limit and MFA (1 Apr 2025), and the Ship-To GSTIN change (on hold). Each maps to an ERPNext action.

How do I update GST rates in ERPNext for GST 2.0?

Move items off the retired 12% and 28% rates onto 5%, 18% or 40%, using Item Tax Templates with a valid-from date. Old invoices keep their old rate and new ones pick up the new rate. Don't edit a live tax template in place; create dated templates. India Compliance ships default GST templates, but assigning each item its rate is your job.

The sequence I follow:

1. List the affected items. Filter your Item master by the templates or HSN codes that were at 12% or 28%. Many 12% items went to 5% or 18%, many 28% items to 18%, and a few luxury and "sin" goods to 40%. Check each HSN against the notified rate; don't assume.
2. Create new Item Tax Templates for the new rates (for example, "GST 18%, from 22 Sep 2025") rather than editing the old ones.
3. Set the valid-from date so invoices dated from 22 September 2025 use the new rate and earlier ones are untouched. For tobacco and pan masala, the change date is 1 February 2026.
4. Reassign items to the new templates, with Data Import for large catalogues.
5. Test on a staging site. Raise a sample invoice for a 5%, an 18% and a 40% item, check CGST/SGST/IGST, and check the e-invoice payload carries the right rate.

My GST e-invoicing in ERPNext setup guide covers tax templates, HSN codes and IRP setup screen by screen.

Skimmable summary: create dated Item Tax Templates for 5%, 18% and 40%, valid from 22 September 2025 (1 February 2026 for tobacco and pan masala), reassign items by HSN, and test on staging.

Does the 30-day IRN limit change how I use ERPNext?

If your AATO is ₹10 crore or more, yes. From 1 April 2025 the IRP won't accept an invoice, credit note or debit note more than 30 days after its date (GSTN's example: a document dated 1 April can't be reported after 30 April). Without an IRN the document isn't a valid invoice, which puts your buyer's input tax credit at risk. In ERPNext, invoices left in draft or posted with old dates become a compliance risk.

At ₹10 crore and above, three habits keep you safe:

• Generate the IRN at submission. India Compliance can send the invoice to the IRP when you submit it, so the IRN comes back the same day. Don't leave invoices in draft.
• Watch stale drafts. A draft invoice dated three weeks ago is a trap. A list filter or a scheduled reminder on drafts older than a few days closes the gap.
• Handle back-dated entries deliberately. An invoice posted with an old date may already be outside the window. Ask your CA how to treat it rather than forcing it through.

Below ₹10 crore, GSTN says there is no such restriction "as of now". Generating the IRN at submit is still the safe habit.

Skimmable summary: at ₹10 crore AATO and above (from 1 April 2025), the IRP refuses documents older than 30 days; generate IRNs at submit and watch old drafts.

Is MFA required to run GST e-invoicing from ERPNext?

MFA is mandatory for logging in to the e-invoice and e-way bill portals: above ₹20 crore AATO from 1 January 2025, above ₹5 crore from 1 February 2025, and for all other taxpayers and users from 1 April 2025 (GSTN advisory, 17 December 2024). It adds an OTP (on the registered mobile, the Sandes app or similar) to the username and password. It is a control on people logging in, not a change to how ERPNext talks to the IRP.

When ERPNext generates an IRN, it uses the API user saved in GST Settings and India Compliance's API service, not an interactive login, so automatic IRN generation isn't interrupted by MFA. Where MFA bites is human access: whoever logs in to the portal to create or reset the API user, download reports or handle e-way bills by hand needs the registered mobile and an active MFA method.

The readiness step is simple and often missed: before go-live or a credential change, confirm the registered mobile on your GSTIN is current and that more than one person can complete the MFA step. I have seen a month-end stall because the only person who could receive the OTP was on leave.

Skimmable summary: MFA has been mandatory on the e-invoice and e-way bill portals for all taxpayers and users since 1 April 2025. It governs human logins; automatic IRN generation keeps working.

What happened to the Ship-To GSTIN change?

GSTN announced that, for bill-to/ship-to transactions needing an e-way bill, the ship-to party's GSTIN (or "URP" for an unregistered consignee) would become mandatory in the e-invoice and e-way bill APIs, with a voluntary e-way bill closure facility for confirming delivery. The date moved from 15 June 2026 to 1 August 2026. On 29 July 2026 GSTN put both changes on hold "until further notice", said no production changes were needed, and withdrew the related advisories. No new date had been announced by 12 October 2026.

What to do meanwhile:

1. Keep GSTINs on shipping addresses, not just billing addresses. They help today (correct e-way bills, place of supply) and the change will need them if it returns.
2. Audit your Address and Customer masters for missing or malformed GSTINs.
3. Keep India Compliance current, so a revived schema change arrives through a normal update.
4. Watch GSTN's news page for a new date, and plan on the advisory's notice period.

If you run distribution with a warehouse-per-distributor structure, the ship-to logic overlaps with my distributor secondary-sales tracking guide.

Skimmable summary: the Ship-To GSTIN and e-way bill closure changes, announced for 1 August 2026, have been on hold since 29 July 2026; keep shipping-address GSTINs clean and watch for a new date.

Do I need ERPNext v16 to stay GST-compliant in 2026?

No. GST features come from the India Compliance app, not ERPNext core. What matters is running an ERPNext version whose India Compliance branch is still maintained. ERPNext v16 was released on 12 January 2026; India Compliance releases for both the version-15 and version-16 branches in October 2026.

Each GST schema change reaches you through an app update on a maintained branch. If your ERPNext version is old enough that its India Compliance branch no longer gets updates, you are exposed, and that is the real trigger to upgrade.

My view: don't upgrade to v16 just for GST. Upgrade for the platform, and let India Compliance branch support set the timing. For what moves the cost, see estimate your price.

Skimmable summary: v16 isn't required for GST; a maintained India Compliance branch is. An unsupported branch is the real reason to upgrade.

Your ERPNext GST 2026 readiness checklist

One pass through configuration, data and process. Run it on a staging copy first, fix what fails, then repeat on production.

1. Confirm your turnover category with your CA: it decides which rules (₹5 crore e-invoicing, ₹10 crore 30-day limit) apply.
2. Update Item Tax Templates to the GST 2.0 rates with the right valid-from dates.
3. Check e-invoicing is enabled in GST Settings if your turnover ever exceeded ₹5 crore.
4. Test IRN generation on submit for 5%, 18% and 40% items on staging.
5. Make "IRN at submit" the habit and watch drafts older than a few days (essential at ₹10 crore and above).
6. Activate MFA for every portal user; confirm the registered mobile and that more than one person can pass it.
7. Audit Address and Customer masters for missing or malformed GSTINs, billing and shipping.
8. Watch the Ship-To GSTIN change on GSTN's news page (on hold since 29 July 2026).
9. Update India Compliance to the current release of your version's branch.

The configuration changes are quick. Data hygiene (missing GSTINs, stale drafts) is where the work is.

Frequently asked questions