ERPNext GST 2026 Readiness Checklist for Indian SMEs

Indian GST changed more between 2025 and 2026 than in the previous five years, and every change lands on the invoice your ERP produces. For an ERPNext user, "2026 readiness" is not a vague aspiration — it is a concrete checklist. You need the GST 2.0 slabs (0%, 5%, 18% and a new 40% rate, live since 22 September 2025) reflected in your Item Tax Templates, e-invoicing switched on if your turnover has ever crossed ₹5 crore, the 30-day IRN deadline respected if you are a ₹10 crore-plus business, MFA activated for everyone who touches the government portals, and the 1 August 2026 Ship-To GSTIN change accounted for in your e-way bills.

If your ERPNext runs the current India Compliance app and your tax templates already use the new slabs, you are most of the way there — the gap most teams miss is the August 2026 e-way bill change and basic GSTIN data hygiene. I am Manoj, an ERPNext and Frappe implementation consultant at MithTech in Bengaluru, and I have taken Indian SMEs through each of these transitions on ERPNext. This is the exact checklist I work through with a client.

What does GST 2026 readiness mean for an ERPNext user?

GST 2026 readiness for an ERPNext user is the state where every current Indian GST rule is correctly reflected in the system's configuration and daily workflow. Readiness covers five moving parts: the GST 2.0 rate slabs on your items, e-invoicing enablement at the ₹5 crore threshold, the 30-day IRN reporting deadline, multi-factor authentication on government portals, and the incoming 1 August 2026 Ship-To GSTIN mandate. Miss any one and invoices get rejected.

None of these are ERPNext bugs to fix — they are government rule changes that your ERPNext setup has to keep pace with. The good news for anyone weighing open-source against a proprietary suite: because ERPNext ships GST compliance through the free, first-party India Compliance app from Resilient Tech, you get these updates at zero licence cost. There is no "compliance module" to buy and no per-invoice fee. What you do need is a disciplined update and data-hygiene routine, which is what the rest of this guide gives you.

Skimmable summary: ERPNext GST 2026 readiness = GST 2.0 slabs, ₹5 crore e-invoicing, the 30-day IRN rule, mandatory MFA, and the 1 August 2026 Ship-To GSTIN change, all reflected in your India Compliance configuration at zero licence cost.

Which GST rule changes actually affect ERPNext in 2026?

Five rule changes affect ERPNext users in 2026, each with a different effective date and a different action inside the system. Two are rate and threshold matters (GST 2.0 slabs and the ₹5 crore e-invoicing limit), two are process controls that started on 1 April 2025 (the 30-day IRN deadline and mandatory MFA), and one is brand new for 1 August 2026 (the Ship-To GSTIN mandate). The table below maps each change to what you actually do in ERPNext.

I keep this table pinned in every GST project because it separates "one-time config" (slabs, e-invoicing enablement) from "ongoing discipline" (30-day rule, MFA) from "coming up, act now" (August 2026). Sources for each date are the official GST e-invoice portal and the GSTN advisories linked through this post — always confirm your own turnover category with your CA.

Skimmable summary: Five 2026 GST changes touch ERPNext — GST 2.0 slabs (22 Sep 2025), ₹5 cr e-invoicing (since Aug 2023), the 30-day IRN rule and MFA (both 1 Apr 2025), and the Ship-To GSTIN mandate (1 Aug 2026) — each mapped to a specific ERPNext action.

How do I update GST rates in ERPNext for the GST 2.0 slab changes?

Updating ERPNext for GST 2.0 means moving items off the retired 12% and 28% slabs onto the new 5%, 18% or 40% rates using Item Tax Templates with a valid-from date, so historic invoices keep their old rate and new invoices pick up the correct one. Editing a live tax template in place is the classic mistake — always create dated, versioned templates. The India Compliance app ships default GST templates, but item-level rate reassignment is your responsibility.

Here is the sequence I follow on a client instance:

1. List every affected item. Filter your Item master by the tax templates or HSN codes that were on 12% or 28%. Most GST 2.0 movements pushed 12% items to either 5% or 18%, and many 28% items down to 18% — but a handful of luxury and sin goods went up to 40%. Do not assume; check each HSN against the current rate.
2. Create new Item Tax Templates for the new slabs (for example, "GST 18% — w.e.f. 22 Sep 2025") rather than editing existing ones.
3. Set the valid-from date on the tax rate so invoices dated on or after 22 September 2025 use the new rate and earlier invoices are untouched. This preserves an accurate audit trail.
4. Reassign items to the correct new template, in bulk via Data Import where the volume is large.
5. Test on a staging site first. Raise a sample Sales Invoice for a 5%, an 18% and a 40% item, confirm CGST/SGST/IGST calculate correctly, and confirm the IRN payload carries the right rate before you touch production.

For the full mechanics of tax templates, HSN codes and IRP setup, my companion GST e-invoicing in ERPNext setup guide walks through the configuration screen by screen.

Skimmable summary: To update ERPNext for GST 2.0, create new dated Item Tax Templates for the 5%, 18% and 40% slabs, set a valid-from date of 22 September 2025, reassign items by HSN, and test on staging before production.

Does the 30-day e-invoice reporting rule change how I use ERPNext?

The 30-day e-invoice reporting rule requires businesses with aggregate annual turnover of ₹10 crore or more to report every invoice, credit note and debit note to the Invoice Registration Portal within 30 days of the document date — in force since 1 April 2025. After 30 days the IRP rejects the document and no IRN is generated, which blocks your buyer's input tax credit. For ERPNext, the practical effect is that unsubmitted or back-dated invoices sitting in draft are now a live compliance risk.

If your turnover is at or above ₹10 crore, three habits keep you safe:

• Generate the IRN at submission, not later. India Compliance can push the payload to the IRP automatically when you submit an eligible Sales Invoice, so the IRN is fetched on the same day. Do not leave invoices in draft.
• Watch for stale drafts. A saved-but-unsubmitted invoice dated three weeks ago is a trap. A simple list-view filter or a scheduled reminder on draft invoices older than a few days closes the gap.
• Handle back-dated entries deliberately. If accounts post an invoice with an old document date, the IRP may already have rejected the window. Post to the current date or issue the correct document type instead.

Below ₹10 crore the 30-day rule does not yet apply, but the direction of travel is clear — thresholds only ever come down. Building the "IRN on submit" habit now means you are ready when it reaches you.

Skimmable summary: The 30-day IRN rule (₹10 crore+ turnover, since 1 April 2025) makes stale draft invoices a compliance risk in ERPNext; generate the IRN on submission, monitor old drafts, and avoid back-dated entries beyond the window.

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

Multi-factor authentication is mandatory for all taxpayers logging into the e-invoice and e-way bill portals, phased in through early 2025 and universal since 1 April 2025. MFA adds a one-time password — via SMS, the Sandes app, or NIC-GST Shield — on top of the username and password. This is a portal-login control that affects the people managing your GST credentials, not a change to the automated ERPNext-to-IRP data flow itself.

The distinction matters for planning. When ERPNext generates an IRN, it authenticates to the IRP using API credentials (a Client ID and Client Secret, directly from NIC or through a GSP) — so day-to-day, automatic IRN generation from ERPNext is not interrupted by MFA. Where MFA bites is human access: the staff member who logs into the e-invoice portal to create or rotate those API credentials, download reports, or manage e-way bills manually now needs a registered mobile and an active MFA method. The automated ERPNext-to-IRP path authenticates with the API credentials rather than an interactive OTP, so scheduled and on-submit IRN generation keeps running while the portal login is what MFA protects.

The readiness action is simple and often forgotten: before go-live or before a credential rotation, confirm the registered mobile number on your GSTIN is current and that at least two people can complete the MFA step. I have seen a month-end filing stall because the only person who could receive the OTP was on leave.

Skimmable summary: MFA is mandatory for all taxpayers on the e-invoice and e-way bill portals since 1 April 2025, but it governs human portal login — automated IRN generation from ERPNext uses API credentials and keeps working, provided the staff managing those credentials have MFA set up.

What is the August 2026 Ship-To GSTIN change and is ERPNext ready?

The 1 August 2026 change makes the Ship-To GSTIN a mandatory field in the e-invoice (IRN) and e-way bill APIs whenever ship-to details are present, and introduces a voluntary e-way bill closure facility for declaring that a delivery is complete. Confirmed by GSTN advisories, the deadline moved from 15 June 2026 to 1 August 2026, giving businesses extra time. For ERPNext, readiness means two things: your shipping addresses must carry a valid GSTIN, and your India Compliance app must be on a version that sends the new payload field.

Practically, when goods ship to a party different from the billing party, the IRN and e-way bill payload must now include the recipient's GSTIN (or "URP" for an unregistered consignee). In ERPNext terms:

1. Populate the GSTIN on every Shipping Address, not just the billing address — this is the field the new ShipDtls.Gstin / e-way bill node reads.
2. Audit your Address and Customer masters for missing or malformed GSTINs before August, because a blank ship-to GSTIN will start failing validation.
3. Update the India Compliance app to the current stable release ahead of 1 August 2026, and confirm its release notes cover the updated e-invoice and e-way bill API schema (the mandatory Ship-To GSTIN field and the voluntary closure facility).
4. Note the closure facility — the voluntary e-way bill closure lets a supplier, recipient or transporter mark delivery complete on the day of delivery or the next day. Decide whether your process will use it.

This is the change most teams have not clocked yet, and it is exactly where ERPNext's open-source model helps — the fix arrives as a free app update, not a paid patch. If you run distribution with a warehouse-per-distributor structure, the ship-to logic overlaps with the setup in my distributor secondary-sales tracking guide.

Skimmable summary: From 1 August 2026, Ship-To GSTIN becomes mandatory in the e-invoice and e-way bill APIs plus a voluntary e-way bill closure facility arrives; ERPNext readiness means populating shipping-address GSTINs and updating the India Compliance app to the compliant version.

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

Upgrading to ERPNext v16 is not strictly required for GST compliance, because GST features are delivered by the India Compliance app rather than the ERPNext core — but running a current ERPNext version and a current India Compliance branch together is the lowest-risk way to stay compliant. ERPNext v16 was released on 12 January 2026 as the current stable major version, with patch releases continuing through 2026. Older ERPNext versions still receive compliance updates only while their India Compliance branch is maintained.

The compliance question is really an app-support question. India Compliance ships branches aligned to ERPNext versions, and each GST schema change (new slabs, the August 2026 Ship-To GSTIN field) reaches you through an app update on a supported branch. If your ERPNext version is old enough that its matching India Compliance branch is no longer updated, you are exposed — that is the real trigger to upgrade.

My honest take: do not upgrade to v16 purely for GST — upgrade for the platform improvements, and treat GST-branch support as the deadline that decides your timing. For a version-by-version cost view, see my ERPNext implementation cost guide.

Skimmable summary: ERPNext v16 (released 12 January 2026) is not mandatory for GST compliance because GST lives in the India Compliance app, but staying on a version whose India Compliance branch is still maintained is essential — an unsupported branch is the real reason to upgrade.

Your ERPNext GST 2026 readiness checklist

The ERPNext GST 2026 readiness checklist — the GST compliance checklist an Indian SME actually runs — is a single pass through configuration, data and process that confirms every current rule is handled. Run it on a staging copy first, fix what fails, then repeat on production. Nine checks cover the full 2026 picture, from the GST 2.0 slabs through to the August 2026 Ship-To GSTIN mandate.

1. Confirm your turnover category with your CA — it decides which rules (₹5 cr e-invoicing, ₹10 cr 30-day rule) apply to you.
2. Update Item Tax Templates to the GST 2.0 slabs (5/18/40%) with a valid-from date of 22 September 2025.
3. Verify e-invoicing is enabled in India Compliance Settings if you have ever crossed ₹5 crore turnover.
4. Test IRN generation on submit for 5%, 18% and 40% items on a staging site.
5. Set the "IRN on submit" habit and monitor draft invoices older than a few days (critical at ₹10 crore+).
6. Activate MFA on the e-invoice and e-way bill portals; confirm the GSTIN-registered mobile is current and two people can pass it.
7. Audit Address and Customer masters for missing or malformed GSTINs — billing and shipping.
8. Populate Ship-To GSTIN on shipping addresses ahead of 1 August 2026.
9. Update the India Compliance app to the current stable branch matching your ERPNext version, and confirm it implements the August 2026 schema.

In my projects, a focused readiness pass like this is quick to run on a staging copy before it touches production. The pattern is always the same: the configuration changes are fast, and data hygiene — chasing missing GSTINs and stale drafts — is where the real work hides.

Frequently asked questions

Is ERPNext ready for the GST 2.0 new slab rates?

Yes — ERPNext handles the GST 2.0 slabs (0%, 5%, 18% and 40%) through the India Compliance app, but you must reassign your items to the new rates. The software supports any tax structure; what changed on 22 September 2025 is which rate each item carries. In my projects the ERPNext side is straightforward: I create dated Item Tax Templates for the new slabs and move items across by HSN code, testing on staging first. A tobacco or aerated-drinks seller, for instance, has to move specific lines up to 40%, while most 12% goods drop to 5% or 18%.

How do I update GST rates in ERPNext after the GST 2.0 changes?

Create new Item Tax Templates for the 5%, 18% and 40% slabs with a valid-from date of 22 September 2025, then reassign each item to the correct template rather than editing live templates. Setting a valid-from date keeps historic invoices on their old rate and applies the new rate only from the effective date, which protects your audit trail. When I do this for a client with a large catalogue, I filter items by their old 12%/28% HSN codes, prepare a Data Import sheet with the new template mapping, and validate a sample invoice for each slab before going near production.

What is the 30-day e-invoice reporting rule in ERPNext?

The 30-day rule requires businesses with ₹10 crore or more aggregate annual turnover to report each invoice to the IRP within 30 days of its date, in force since 1 April 2025 — after which the portal refuses to generate an IRN. In ERPNext this means you cannot let invoices sit in draft or post them with old back-dates. I configure India Compliance to fetch the IRN automatically on submission and set up a list filter so the accounts team spots any draft invoice older than a few days before it becomes uninvoiceable.

Is MFA required for ERPNext GST e-invoicing?

MFA is mandatory for logging into the e-invoice and e-way bill portals for all taxpayers since 1 April 2025, but it applies to human portal login, not to ERPNext's automated IRN generation. ERPNext authenticates to the IRP with API credentials, so scheduled and on-submit IRN generation keeps running. The readiness step is human: I make sure the GSTIN-registered mobile number is current and that at least two staff can complete the OTP, because I have watched a filing stall when the one person who could receive the code was unavailable.

Does ERPNext support the August 2026 Ship-To GSTIN e-way bill change?

Support comes through an India Compliance app update, and your readiness work is populating the Ship-To GSTIN on shipping addresses before 1 August 2026. From that date the e-invoice and e-way bill APIs require the recipient's GSTIN (or "URP" if unregistered) whenever ship-to details are present, plus there is a new voluntary e-way bill closure facility. I audit a client's Address and Customer masters for missing GSTINs well ahead of the deadline and update the India Compliance app to the release that carries the new payload field, then test a bill-to/ship-to invoice end to end.

Do I have to upgrade to ERPNext v16 for GST 2026 compliance?

No — GST compliance is delivered by the India Compliance app, not the ERPNext core, so you do not need v16 specifically. What you do need is an ERPNext version whose matching India Compliance branch is still maintained, because each GST schema change reaches you through that app branch. ERPNext v16 (released 12 January 2026) gives the longest support runway and the best performance, so I recommend upgrading for the platform benefits and letting India Compliance branch support decide the timing, not the GST rules alone.

Is the India Compliance app free, and does it cover all these 2026 changes?

The India Compliance app is open source and free to use, with no per-user or per-invoice fee from Frappe, and it is the single app that delivers GST 2.0 rates, e-invoicing, e-way bills and the upcoming schema changes into ERPNext. Your only costs are hosting and implementation. This is the core open-source advantage I point clients to: when a rule like the August 2026 Ship-To GSTIN mandate lands, the fix arrives as a free app update on a supported branch — not as a paid compliance patch you have to license, the way many proprietary ERPs handle it.

How do I enable GST and e-invoicing in ERPNext?

You enable GST in ERPNext by installing the India Compliance app and entering your GSTIN and state in GST Settings; e-invoicing is switched on separately in India Compliance Settings by toggling Enable E-Invoicing and adding your IRP credentials. Vanilla ERPNext has no "activate GST" button — the India Compliance app supplies the entire GST layer. On a new client instance I install the app, set the company GSTIN, load the default tax templates, then enable e-invoicing only once the ₹5 crore threshold applies. My GST e-invoicing setup guide walks through every screen.

What is the GST compliance checklist for an ERPNext business in 2026?

The GST compliance checklist for an ERPNext business in 2026 is the nine-point readiness pass in this article: confirm your turnover category, update Item Tax Templates to the GST 2.0 slabs, enable and test e-invoicing, adopt the IRN-on-submit habit for the 30-day rule, activate MFA, clean GSTIN master data, populate Ship-To GSTIN before 1 August 2026, and keep the India Compliance app on a supported branch. I run exactly this list on a staging copy before a client's month-end so nothing surfaces later as a rejected invoice.

Is the SAC code 4 digits or 6 digits in ERPNext?

For businesses above the ₹5 crore e-invoicing threshold, current GST rules require a 6-digit HSN code for goods and a 6-digit SAC code for services on B2B invoices, while smaller businesses may report 4 digits. ERPNext stores the HSN/SAC code on each Item master, and the India Compliance app ships with all 12,000+ HSN codes preloaded so you select the right one instead of typing it. The 6-digit requirement for ₹5 crore-plus turnover has applied to e-invoices since 15 December 2023. I always confirm every item carries a valid 6-digit code before enabling e-invoicing, because a missing or short HSN/SAC code is one of the most common IRN rejection errors.