ERP Compliance Guide · 2026 Edition
Compliance by Design: What Indian Regulations Now Require From Your ERP (2026 Edition)
This guide brings together the regulations that now shape what an ERP must do for an Indian manufacturer or trader, from GST and corporate law to the Income-tax Act, 2025, the labour codes and data protection. For each one, it explains who it applies to, what changed, and what your system must do. A compliance matrix and an interactive readiness checker help you see where you stand.
Book a compliance gap call →The short answer
Indian compliance has moved from the filing desk into the transaction itself. GST portals now block late e-invoices, old e-way bills and edits to locked return values, companies must keep an audit trail that cannot be switched off, and tax, labour and data laws changed in 2025–26. A compliance-ready ERP validates each transaction as it happens, not at month-end.
In August 2025, finance teams across India opened their GSTR-3B for the July period and found that the liability figures could no longer be edited. For years, the return had been the place where mistakes were quietly corrected. Now the portal took its numbers directly from the sales invoices already reported, and the only way to fix an error was to go back to the source. The lesson was simple: compliance is no longer something you do at the end of the month. It is something your system either gets right at the moment of each transaction, or gets wrong.
Why 2026 is different: from filing compliance to system-validated compliance
Until recently, most compliance errors could be corrected later: an invoice reported late, a return figure adjusted, a ledger entry quietly edited. That window is closing. The portals and laws introduced in 2025 and 2026 share one design principle: the data must be right when it is created, because it can no longer be fixed afterwards.
| What the system now blocks or locks | From | Practical effect |
|---|---|---|
| E-invoices, credit notes and debit notes reported to the IRP more than 30 days after the document date (AATO ₹10 crore and above) | 1 Apr 2025 | Late documents are rejected; the invoice must be re-raised and the buyer’s credit is delayed |
| E-way bills on base documents dated more than 180 days earlier; extensions beyond 360 days | 1 Jan 2025 | Old challans and invoices cannot move goods |
| Manual edits to auto-populated outward liability in GSTR-3B | July 2025 tax period | Errors must be corrected at source through GSTR-1A before filing |
| Filing of GST returns more than three years after the due date | July 2025 tax period | Missed returns become permanently time-barred |
| Disabling or tampering with the accounting audit trail (edit log) | 1 Apr 2023 | Auditor must report on whether the trail operated all year |
The 2026 ERP compliance matrix
Use this matrix as a checklist for your current system or for any ERP you are evaluating. The detail behind each row follows below.
| Requirement | Applies to | In force | What your ERP must do |
|---|---|---|---|
| GST e-invoicing (IRN + QR) | Aggregate turnover above ₹5 crore in any year since 2017-18 (B2B, exports) | Phased since 2020 | Generate IRN through API when the invoice is saved; print QR; handle cancellations within portal rules |
| 30-day IRP reporting window | AATO ₹10 crore and above | 1 Apr 2025 | Flag and escalate unreported invoices and credit notes well before day 30 |
| E-way bill limits | Movement of goods above ₹50,000 | 1 Jan 2025 | Raise e-way bills from the dispatch; validate document age; track extensions |
| GSTR-3B hard-lock and GSTR-1A | All regular GST taxpayers | July 2025 period | Produce accurate GSTR-1 data from source; maker-checker before upload; manage GSTR-1A corrections |
| Invoice Management System (IMS) and ITC | All buyers claiming ITC | Oct 2024; Table 4 auto-filled since Oct 2025 period | Reconcile purchases with GSTR-2B continuously; record accept/reject/pending decisions; chase vendors |
| Three-year return time bar | All GST taxpayers | July 2025 period | Show pending returns and periods at risk |
| GST 2.0 rate structure | All GST taxpayers | 22 Sep 2025 | Effective-dated rate and HSN masters; correct rate on transactions spanning a rate change |
| Post-supply discounts, credit notes, refunds | Suppliers giving discounts; refund claimants | 1 Nov 2026 | Link each discount to its credit note and the buyer’s ITC reversal; tag pre/post 1 Nov supplies |
| MCA audit trail (edit log) | Every company under the Companies Act, 2013 | 1 Apr 2023 | Log every create, edit and delete with user and timestamp; cannot be disabled; retained with the books |
| MSME payments (Section 43B(h) and MSMED Act) | Buyers from Udyam-registered micro and small suppliers | FY 2023-24 onwards | Tag MSE vendors; run 15/45-day payment clocks; ageing by bucket; MSME-1 data |
| Income-tax Act, 2025 | All taxpayers | 1 Apr 2026 | Single Tax Year; remapped TDS/TCS sections; new return forms; split logic for pre-April 2026 items |
| Four labour codes | All employers | 21 Nov 2025 | 50% wage definition in payroll; recalculated PF, gratuity, overtime; state rule variations |
| DPDP Act and Rules | Anyone processing digital personal data | Rules 13 Nov 2025; core duties 13 May 2027 | Role-based access, purpose-bound data, retention and erasure, breach logs for reporting |
GST: the system now checks your data, not just your returns
E-invoicing and the 30-day IRP window
E-invoicing is mandatory for B2B supplies and exports once aggregate turnover has exceeded ₹5 crore in any financial year since 2017-18. Since 1 April 2025, businesses with an annual aggregate turnover of ₹10 crore or more cannot report an invoice, credit note or debit note to the Invoice Registration Portal more than 30 days after its date; the portal simply rejects it. Two-factor authentication is also mandatory.
What your ERP must do: generate the IRN and QR code automatically through an API when the invoice is posted, not through a separate upload. It should show a daily list of documents awaiting IRN and alert well before day 30. Leading practice is an internal rule to report within 5 to 7 days. Credit and debit notes need the same treatment, because they fall under the same window.
E-way bills: 180-day documents and 360-day extensions
From 1 January 2025, an e-way bill can be generated only against a base document dated within the previous 180 days, and an e-way bill cannot be extended beyond 360 days from its original generation. These limits matter most for job work, branch transfers and goods returned after a long gap.
What your ERP must do: create the e-way bill from the dispatch or delivery challan itself, with the same data as the e-invoice, and warn when a document is approaching the 180-day limit.
GSTR-3B hard-lock, GSTR-1A and the three-year time bar
From the July 2025 tax period, the outward liability that GSTR-3B auto-populates from GSTR-1, GSTR-1A or the Invoice Furnishing Facility can no longer be edited at filing. Errors must be corrected through GSTR-1A before GSTR-3B is filed. From the same period, the portal blocks filing of GSTR-1, GSTR-3B, GSTR-9 and other returns once three years have passed from their due date.
What your ERP must do: treat sales data as the return. That means GST-correct invoices at creation, a maker-checker review before GSTR-1 upload, a clear view of amendments that need GSTR-1A, and a dashboard of any unfiled periods.
The Invoice Management System and input tax credit
Through the Invoice Management System (IMS), buyers accept, reject or keep pending each invoice their suppliers upload, and those decisions drive GSTR-2B and the credit in GSTR-3B. Since the October 2025 tax period, the ITC table in GSTR-3B has been auto-populated from GSTR-2B. A further step, locking that ITC figure as well, has been reported as targeted but should be checked on the GST portal before you rely on it. Invoices not actioned in IMS are treated as accepted by default.
What your ERP must do: reconcile the purchase register with GSTR-2B continuously, not just before filing; record the IMS decision against each purchase bill; and produce a vendor-wise list of missing or mismatched invoices to chase.
GST 2.0 and the November 2026 changes
GST 2.0 replaced the four main slabs with two, 5% and 18%, plus a 40% rate for specified goods, from 22 September 2025. From 1 November 2026, amended Sections 15, 34 and 54 of the CGST Act allow post-supply discounts to reduce taxable value through a GST credit note, with the recipient reversing the matching ITC, and allow up to 90% of eligible refunds to be sanctioned provisionally through system risk checks. Inverted-duty refunds now also include ITC on input services availed from that date.
What your ERP must do: keep tax rates and HSN codes as effective-dated masters, so the correct rate applies to each transaction date; link every discount to its credit note and the buyer’s ITC reversal; and tag transactions as before or after 1 November 2026.
Corporate law and income tax
MCA audit trail (edit log)
Since 1 April 2023, every company that keeps its books in accounting software must use software that records an audit trail of each transaction, creating an edit log of every change with the date, and the trail cannot be disabled. The statutory auditor reports under Rule 11(g) whether the feature operated throughout the year and was not tampered with. The requirement applies whether the software is on premise, in the cloud or delivered as SaaS.
What your ERP must do: log every create, edit and delete on books-related records with user, date and before/after values; make the log impossible to switch off; retain it for the statutory period; and give your auditor a usable report, not a raw database dump.
MSME payments: Section 43B(h) and the MSMED Act
Buyers must pay Udyam-registered micro and small suppliers within 15 days of accepting goods or services, or within the agreed period up to a maximum of 45 days. Under Section 43B(h), introduced by the Finance Act, 2023, an expense owed to such a supplier beyond that limit is deductible only in the year it is actually paid. Companies also file Form MSME-1 half-yearly, disclosing dues outstanding beyond 45 days. With the move to the Income-tax Act, 2025, confirm the corresponding provision and references with your CA.
What your ERP must do: tag MSE vendors from their Udyam registration; start a payment clock from the acceptance date; show payables in 0–15, 15–45 and 45+ day buckets; prioritise at-risk bills in payment runs; and produce the data for MSME-1 and the tax audit.
Income-tax Act, 2025
The Income-tax Act, 2025 replaced the 1961 Act on 1 April 2026, together with the Income-tax Rules, 2026. It replaces the “previous year” and “assessment year” with a single Tax Year, renumbers TDS and TCS provisions, and introduces new TDS and TCS return forms. Transactions before 1 April 2026 remain under the old Act, so systems must handle both for a period.
What your ERP must do: map every vendor and TDS/TCS type to the new section codes, update challan and return formats, report by Tax Year, and keep the old mapping for transactions and proceedings that still fall under the 1961 Act.
People and data: labour codes and DPDP
The four labour codes
The Code on Wages, the Industrial Relations Code, the Code on Social Security and the Occupational Safety, Health and Working Conditions Code came into force on 21 November 2025, replacing 29 central labour laws. The most immediate payroll change is the uniform definition of wages: basic pay, dearness allowance and retaining allowance must make up at least 50% of total remuneration, which raises the base for provident fund and gratuity. Central rules followed in 2026, while many state rules are still being notified.
What your ERP must do: recalculate wages, PF, gratuity and overtime under the new definition; support fixed-term employment; and handle state-specific variations as each state notifies its rules. For manufacturers, contractor and contract-labour records also need review.
Digital Personal Data Protection Act and Rules
The DPDP Rules were notified on 13 November 2025 with a phased timeline; the main obligations for businesses, including notice, consent, security safeguards, retention and breach reporting, apply from 13 May 2027. An ERP holds a great deal of personal data: employee records and payroll, customer contacts, dealer and vendor details.
What your ERP must do: restrict access by role, record why personal data is held, support retention and erasure rules, log access and changes, and help you assemble a breach report quickly.
What “compliance by design” means in an ERP
A system is compliant by design when the right outcome is the default, not the result of a person remembering a rule. Look for these eight characteristics:
- Effective-dated masters. Tax rates, HSN codes, TDS sections and wage rules change on specific dates. The system should apply the rule valid on the transaction date, not the one valid today.
- Validation at the point of entry. GSTIN, HSN, place of supply, document dates and vendor MSME status are checked when the transaction is created, so errors do not reach the return.
- Native portal integration. E-invoices, e-way bills and GST data move through direct APIs from the transaction, without re-keying or file uploads.
- An immutable audit trail. Every change is logged with user, time and before/after values, cannot be disabled, and is easy for auditors to review.
- Continuous reconciliation. Purchase registers are matched with GSTR-2B and IMS decisions throughout the month, not in a last-minute scramble.
- Deadline-aware workflows. 30-day IRP, 180-day e-way bill, 45-day MSME and return due dates appear as alerts and dashboards, not calendar reminders.
- Role-based access and data controls. People see only what their role needs, which supports both internal control and DPDP obligations.
- A vendor committed to regulatory updates. Ask how quickly past changes, such as GST 2.0, the IRP 30-day rule and the Income-tax Act, 2025, were delivered, and get the update commitment in your contract.
Compliance Readiness Checker
Answer five questions about your business. The checker lists the requirements that apply to you and what to verify in your ERP.
Want a second opinion on your gaps?
Book a 30-minute compliance gap call with a Pothera specialist. Bring your checker results and we will map each gap to a practical fix.
Book a compliance gap call →10 compliance questions to ask any ERP vendor
- Is e-invoice and e-way bill generation native and API-based, or through a third-party file upload?
- How does the system alert us before the 30-day IRP and 180-day e-way bill limits are breached?
- Can we see GSTR-1 data, GSTR-1A amendments and GSTR-2B reconciliation inside the ERP?
- How are IMS accept, reject and pending decisions recorded against purchase bills?
- Show us the audit trail: can any user, including an administrator, disable it? How long is it retained?
- How are MSME vendors identified, and how does the payment-ageing report work?
- How long did it take you to deliver GST 2.0 rate changes and Income-tax Act, 2025 section mapping to customers?
- How does payroll handle the 50% wage definition and state-specific labour rules?
- What role-based access, data retention and access-logging controls support DPDP?
- Is the regulatory update commitment written into the contract and support SLA?
Operating beyond India?
Many Indian manufacturers and traders now have entities or customers in the Gulf and Africa, where e-invoicing is moving just as fast. UAE e-invoicing becomes mandatory from January 2027 for businesses with revenue of AED 50 million or more and from July 2027 for the rest; Saudi Arabia’s ZATCA Phase 2 requires real-time integration with the Fatoora platform; and Kenya now validates income and expenses in tax returns against eTIMS invoice data. One ERP that handles all of these saves maintaining a separate compliance stack for each country.
Frequently asked questions
Is e-invoicing mandatory for my business?
E-invoicing is mandatory for B2B supplies and exports if your aggregate turnover exceeded ₹5 crore in any financial year from 2017-18 onwards. If your annual aggregate turnover is ₹10 crore or more, invoices and credit or debit notes must also be reported to the IRP within 30 days of their date.
What is the GSTR-3B hard-lock?
From the July 2025 tax period, the outward tax liability auto-populated in GSTR-3B from GSTR-1, GSTR-1A or IFF cannot be edited at filing. Any correction must be made through GSTR-1A before GSTR-3B is filed, so accurate sales data at source is essential.
Does the MCA audit trail rule apply to private limited companies?
Yes. Since 1 April 2023, every company under the Companies Act, 2013 that uses accounting software must use software with an audit trail (edit log) that records each change with the date and cannot be disabled. The statutory auditor reports on its operation.
How does an ERP help with the MSME 45-day payment rule?
An ERP tags Udyam-registered micro and small suppliers, starts a payment clock from the acceptance date, shows dues by age bucket, prioritises at-risk bills in payment runs, and produces the data needed for Form MSME-1 and the tax audit.
What changed in ERP systems with the Income-tax Act, 2025?
From 1 April 2026, systems must report by a single Tax Year, map TDS and TCS to the renumbered sections, and use the new return forms, while still handling transactions that fall under the 1961 Act.
Do the new labour codes affect our ERP payroll?
Yes. Since 21 November 2025, basic pay, dearness allowance and retaining allowance must form at least 50% of total remuneration, which changes the base for PF, gratuity and other benefits. Payroll must also follow state rules as they are notified.
When do DPDP obligations apply to our business data?
The DPDP Rules were notified on 13 November 2025, and the main obligations for businesses apply from 13 May 2027. ERPs hold employee, customer and vendor personal data, so access controls, retention and breach logging should be prepared now.
How often should an ERP be updated for compliance changes?
As often as the law changes. In 2025 and 2026 alone, GST portals, return rules, rates, income-tax sections, labour wages and data protection all changed. Ask vendors for their track record on past changes and a contractual update commitment.
About Pothera ERP
Pothera ERP by Bsquare Solutions (Noida, India) builds compliance into everyday transactions for manufacturing and trading businesses: GST e-invoicing and e-way bills, return reconciliation, audit trail, MSME payment tracking, TDS and payroll. With 25 years in business and 1,000+ enterprise clients across India, the Middle East and Africa, Pothera helps companies stay compliant across every country they operate in.
Talk to an ERP specialist →