How ERPNext with India Compliance supports GST obligations
If you are a finance or tax lead running ERPNext for an Indian entity, you still have to produce GSTR-1, file GSTR-3B, reconcile purchases against GSTR-2B and issue e-invoices and e-waybills. India Compliance is the layer that supports those jobs inside ERPNext. Its documentation covers e-waybill and e-invoice setup and generation, GSTR-1 and GSTR-3B preparation, the Invoice Management System, purchase reconciliation, GSTIN verification and an audit trail. Those are the obligations the app helps you carry out. It does not decide them for you.
Several responsibilities stay with the company and its tax advisor. Filing decisions, including what goes into each return and when it is submitted, belong to you. So do rate determination and tax treatment of each item and customer, because the app applies the rates and categories you configure, not the rates the law requires for your product. The accuracy of master data is also yours: GSTINs on customers and suppliers, HSN or SAC codes on items, place of supply, and the company's registration details. A clean configuration cannot correct a wrong GSTIN or an item code that does not describe the goods. Confirm each of these with your tax advisor before go-live.
DeployOpen's role is to prepare the system, the controls and the evidence that go with them. That covers installing and configuring India Compliance on your ERPNext version, setting up GST settings and accounts, testing e-invoice and e-waybill flows against the portals you use, and documenting how each return is produced and reviewed. DeployOpen does not file returns, generate e-invoice IRNs on the company's behalf, or certify compliance. Independent auditors and the tax authority make those determinations. Ask any implementation partner to state this split in writing in the scope.
Mapping GST requirements to ERPNext and India Compliance settings
This table maps each GST obligation to what India Compliance provides on ERPNext and the settings you must complete before it works. Read each row as a checklist: the capability tells you what the app can do, and the configuration column tells you what your team must set up. Confirm current filing rules, e-invoice thresholds and reporting formats with your tax advisor before relying on any setting.
| Requirement | Platform capability | Configuration needed |
|---|---|---|
| GSTR-1 outward supply return | Prepares GSTR-1 data from sales invoices and credit or debit notes | GST settings, company GSTIN, party GSTINs, HSN codes on items, tax templates |
| GSTR-3B summary return | Prepares GSTR-3B summary figures from ledger and tax data | GST accounts mapped to input and output tax heads, reverse charge flags where applicable |
| Purchase reconciliation with GSTR-2B | Matches purchase invoices against supplier-filed GSTR-2B data | Supplier GSTINs validated, purchase invoice tax accounts set, reconciliation run each period |
| E-invoicing through the NIC portal | Generates and records e-invoice data for eligible invoices | NIC portal credentials or GST API access, e-invoice enablement on the company, applicability checked with your advisor |
| E-waybill generation | Generates e-waybill data for goods movement from linked documents | Transporter and vehicle details captured, e-waybill settings on the company, applicability confirmed |
| GSTIN verification | Looks up and validates GSTINs for customers and suppliers | GST API access if required, validation enabled on party masters |
| Audit trail | Keeps records of GST-related changes and submissions | Access roles limited, change control on customizations, retention confirmed with your auditor |
How India Compliance fits into ERPNext's accounting and stock flow
India Compliance is an app layered on ERPNext, not a separate ledger, so every GST figure it produces is derived from documents that ERPNext already holds. It can be installed on Frappe version 14 or above, whether on Frappe Cloud, in a custom Docker image built with frappe_docker, or manually with bench get-app and install-app. The install route decides who patches and rebuilds the image when the app updates, so confirm that ownership before you choose. The version you run is also constrained by ERPNext's own lifecycle. According to Frappe's supported versions page, version 14 reached end of life on January 31, 2026, version 15 is planned to be supported until the end of 2027, and version 16 until the end of 2029. Check the current page before you commit, since a GST rollout that lands on an unsupported core will need its own upgrade project.
GST returns are only as accurate as the masters behind them. The company's GSTIN and registered state, the address on each customer and supplier, the item tax template on each item, and the tax accounts in the chart of accounts all feed the sales invoices, purchase invoices and stock movements that GSTR-1 and GSTR-3B are built from. A wrong place of supply on a customer address, or an item missing its GST rate, does not show up as an error in ERPNext. It shows up later as a mismatch in the return or in a reconciliation against GSTR-2B. Stock entries and delivery notes matter as well, because the goods movements that generate e-waybills depend on the same item and address data.
Before go-live, have the finance lead and an ERPNext administrator review a sample of masters per company, and reconcile one month of test invoices to the tax ledger by hand. Ask whoever sets up the environment to document which masters are locked after first use and who may change them, since changing a GST rate or address after invoices exist can alter historical reporting. Confirm the current India Compliance requirements for your ERPNext version against the India Compliance installation guide before you fix the master data design.
What audit evidence ERPNext produces for GST and how to keep it
GST evidence in ERPNext sits in several places: the India Compliance records, the ERPNext document history, the e-invoice and e-waybill logs, and the backups and app versions behind them. Each one answers a different question an auditor may ask, so collect them on a schedule rather than when a review starts. Auditors decide whether the evidence is sufficient for their purpose.
India Compliance audit trail
The India Compliance app records the GST-related actions it performs, which gives you a record of who triggered what in the GST workflow. Confirm in your installed version which events are logged, where the log is viewed, and whether it can be exported in a form your auditors accept. Export it at each filing period and store the file with the return it supports, because the log is only useful if it still exists when someone asks for it.
Generated return and e-invoice records
Keep the GSTR-1 and GSTR-3B preparation outputs, the invoice data sent for e-invoicing and the IRN responses returned for each invoice. These show what was reported and when, and they let you trace a return figure back to source invoices. Save the generated files with the filing reference, and confirm that cancelled or amended invoices keep their original record instead of being overwritten.
E-waybill records
E-waybill generation, update and cancellation each leave a record that should match the goods movement in stock and sales. Export the e-waybill list for each period and reconcile it against delivery notes and transporter details. Check that cancelled e-waybills still show their history, because an auditor will look for gaps between dispatched goods and the waybills that covered them.
Purchase reconciliation against GSTR-2B
The purchase reconciliation output compares supplier invoices recorded in ERPNext with the GSTR-2B data made available for your GSTIN. Save the reconciliation report for each period, along with the GSTR-2B file it was run against and the actions taken on mismatches, such as supplier follow-up or corrected entries. An unexplained difference is the item auditors ask about most, so record the reason for each one.
ERPNext version history on documents
ERPNext can track changes to documents, and amended documents keep their earlier versions. These histories show how a tax invoice or payment changed after it was first saved, which matters when a return figure depends on a later correction. Confirm which doctypes have version tracking enabled in your site, and export the history for any document in scope before a review, since the record is only as complete as the settings that created it.
Backups and app version records
Backups and the exact India Compliance and ERPNext versions in use explain why a return looked the way it did at a given date. Keep a dated backup schedule, test restores, and record the app versions alongside each release in your change log. Route any change to GST settings, tax accounts or custom scripts through change control, so you can show what was in force on each filing date.
Sequence for configuring GST in ERPNext
This sequence takes a company from a confirmed ERPNext and Frappe version to a production GST setup, with each stage checked on a test site before live invoices and filings depend on it. It keeps the accounting, tax and integration decisions in a order that makes later reconciliation and audit questions easier to answer.
Confirm Frappe and ERPNext versions
Before any install, check the Frappe and ERPNext versions you run against Frappe's supported versions page and confirm that India Compliance supports your Frappe major version (version 14 or above). Decide whether you will run on Frappe Cloud, a custom Docker image built with frappe_docker, or a manual bench install, since this choice sets who applies patches and who owns the upgrade path. The step is done when the version pair, hosting model and support position are written into the project record and approved by finance and IT.
Install India Compliance on a test site
Create a separate test site and install the India Compliance app using the method chosen in the previous step, either through Frappe Cloud, a custom Docker image or bench get-app and install-app. Keep production data out of this site and load only the sample company, masters and transactions you need for testing. The step is done when the app installs cleanly, appears in the installed apps list and the site runs its background jobs without errors in the logs.
Configure company GST settings and accounts
On the test site, set the company GSTIN, registered address, GST registration type and the GST-related accounts that the tax templates will post to, such as output and input tax ledgers. Confirm with your tax adviser how each ledger maps to your chart of accounts and which cost centers and tax treatments apply to your sales and purchases. The step is done when a sample sales and purchase invoice post to the expected GST accounts and the trial balance matches your manual calculation for the same documents.
Build tax templates and validate master data
Create sales and purchase tax templates for each GST rate your items use, then assign HSN or SAC codes and tax templates to items, and set customer and supplier GSTINs. Use the GSTIN verification feature in India Compliance to check counterparties, and fix any records with missing place of supply, state or tax category before they reach invoices. The step is done when a sample of items, customers and suppliers passes validation and the exception list for missing or invalid master data is empty or explained.
Run GSTR-1 and GSTR-3B on a test period
Post a full test month of sales, purchases, credit notes and debit notes on the test site, then generate the GSTR-1 and GSTR-3B preparation reports. Compare the totals by tax rate and document type against an independent extract from the books, and record each difference with its cause. Your filing team or tax adviser signs off the outputs before they are treated as a valid model for live filing. The step is done when two consecutive test periods reconcile with no unexplained variance.
Reconcile purchases with GSTR-2B
Import or load a GSTR-2B data set for the test period into the purchase reconciliation tool, then match it against the purchase invoices in ERPNext. Review unmatched supplier invoices, timing differences and supplier filing gaps, and agree with the purchasing and tax teams how each category is handled before the next period. The step is done when the reconciliation summary explains every unmatched item and the agreed process for supplier follow up is documented.
Configure e-invoice and e-waybill access
Register the company for e-invoice and e-waybill access through the NIC portal, then enter the API credentials in the India Compliance settings on the test site. Limit who can generate, cancel or view these documents using ERPNext roles, and confirm the Invoice Management System workflow your team will use for invoices that need follow-up. The step is done when test invoices generate their e-invoice and e-waybill references, cancellations work as your process requires and the access list has been reviewed by the people responsible for compliance.
Cut over to production with a documented plan
Write a cutover plan that lists the production installation or upgrade date, the freeze on master data changes, the first live invoice run and the fallback procedure if a critical issue appears. Confirm which settings, templates and accounts move from the test site to production, and keep the test evidence, sign-offs and configuration exports together in the change record. The step is done when the plan is approved, the first live period has been reconciled to the same standard as the test period and the team knows who owns ongoing GST configuration.
What ERPNext and India Compliance do not cover
India Compliance automates much of the GST workflow, but it does not take over filing, tax judgment or sign-off. The cards below mark the decisions and controls that stay with your finance, tax and IT owners, and the points where a quote or a separate workstream is needed.
Return filing and legal sign-off
Preparing GSTR-1 and GSTR-3B in ERPNext produces drafts for review. The company's authorized person files the returns on the GST portal and accepts legal responsibility for what is declared. Confirm who reviews each period, who holds filing rights, and how reconciling differences are documented before filing deadlines arrive.
Tax rate and classification decisions
HSN codes, GST rates, reverse charge treatment and zero-rated or exempt supplies are set by your tax team against the applicable rules and your products. ERPNext applies the tax templates and item settings you maintain, so a wrong master record produces wrong invoices at scale. Ask who approves changes to item tax data and how those changes are logged.
GSTIN and portal credentials
Each GSTIN, its portal login and any e-invoice or e-waybill credentials are sensitive and tied to a legal entity. Limit which ERPNext roles can view or edit company tax identifiers and stored credentials, and rotate access when staff change. Confirm where secrets are stored in your deployment and who can read them through the database or admin tools.
Paid GST API access costs
Some e-invoice, e-waybill and GSTIN verification features depend on a paid GST API service that is separate from the open-source app. Ask the provider for the fee model, what counts toward usage, whether the fee recurs, the contract term, data handling terms and what happens if the service changes. Budget for it as an ongoing cost, not a one-time setup item.
TDS configuration as a separate topic
Tax deducted at source is part of Indian tax compliance but follows its own rules, categories, thresholds and certificates. It is configured separately from GST settings and needs its own review of accounts, vendors and deduction logic. Plan it as a distinct workstream so GST go-live is not delayed by TDS questions, and confirm which TDS setup your India Compliance version includes.
Auditor attestation
DeployOpen prepares configuration, controls and evidence, but it does not issue audit reports, attestations or certifications. Independent auditors decide whether your GST controls are adequate for your assessment. Ask your auditor early which records, change logs and reconciliation evidence they expect to see, and agree the evidence list before the review period begins.
Questions buyers ask before hiring GST implementation help
What drives the cost of an India GST implementation on ERPNext?
The cost follows the size and shape of the work written into the scope: how many legal entities and GSTINs need configuration, how many invoices, purchase bills and e-waybills the business issues each month, whether the e-invoice and e-waybill connections go through the NIC portal or a paid GST API, how much historical invoice data must be migrated, and whether custom print formats are needed for tax invoices. Each of these adds configuration, testing and review time. Ask the implementation partner to price each item separately so you can see which parts you can drop or handle in house.
How long does a GST setup on ERPNext take?
Duration depends on the number of entities, the volume of historical data, how many portal integrations are in scope, and how quickly your finance and tax team can confirm tax masters, accounts and test cases. Parallel work on the chart of accounts and India Compliance settings shortens the calendar, while late changes to tax treatment lengthen it. Ask for a timeline tied to written milestones in the fixed-scope proposal, with named dependencies on your side, rather than a generic estimate.
What does the finance and tax team need to provide during the project?
Your finance and tax team needs to own the decisions that the software cannot make for you. That includes the GSTIN for each registration, the tax rates and HSN or SAC codes used on items, the treatment of exempt, nil-rated and zero-rated supplies, the place of supply rules for your transactions, and the reconciliation process with GSTR-2B. They also need to approve test invoices, review GSTR-1 and GSTR-3B outputs against your filed returns, and sign off on the e-invoice and e-waybill flow before go-live. Agree the named reviewers and their available time at the start.
Can our in-house team set up India Compliance without outside help?
Yes, if you have engineers who can run Frappe benches or build a custom image with frappe_docker, and a finance lead who understands GST returns in detail. India Compliance installs on Frappe version 14 or above, and the documentation covers settings, e-invoices, e-waybills, GSTR-1, GSTR-3B and purchase reconciliation. The risk is less in the installation than in the tax logic and in the controls around it. Outside help is most useful for the configuration review, the test plan and the first filing cycles.
What recurring costs should we plan for after go-live?
Plan for four recurring items. Hosting is the first: ERPNext itself is free to self-host, while Frappe Cloud pricing starts at a published monthly rate for shared site hosting and higher for servers, according to the ERPNext pricing page, so confirm which option applies to your environment. Paid GST API access, where you use a provider rather than direct portal connections, is billed separately by its provider. Third-party app upkeep, upgrades and testing come next, and support retainers from DeployOpen or another partner are optional. Ask the partner to list each recurring item with its owner and billing cycle.
What should we ask for in a fixed-scope quote for GST work?
Ask for a written scope that names each entity and GSTIN in scope, the modules and India Compliance features included, the portal connections and whether they use NIC directly or a paid API, the migration boundary for historical invoices, and the custom print formats or reports. Require acceptance criteria for each deliverable, such as a reconciled test filing for GSTR-1 and GSTR-3B, the list of test invoices and the sign-off owner. Also ask what is excluded, which assumptions the price depends on, how change requests are priced, and what support follows go-live.
What are the common causes of GST errors after go-live?
Most post-go-live errors come from master data rather than from the software logic. Common causes include wrong HSN or SAC codes on items, tax templates not mapped to the correct accounts, customers or suppliers with missing or invalid GSTINs, and place of supply set incorrectly for interstate or export transactions. Engineers should check that GSTIN verification and the audit trail are working, and tax reviewers should compare the first returns to the source documents. Build a test checklist before go-live so these checks run each filing period.
What changes for your finance and tax team after go-live
Go-live does not end the GST work. Each month, the finance team runs the same cycle: confirm that sales and purchase invoices have been submitted, reconcile purchases against GSTR-2B, prepare GSTR-1 and GSTR-3B, and file them on the government portal. Assign a named owner to each step and a backup, and set a fixed internal close date ahead of the statutory deadlines. Ask your implementation partner to document the exact sequence in your environment, including which India Compliance reports are used at each step and where the reconciled file is stored as evidence.
Rejected e-invoices and e-waybills will happen. Build a triage routine: the error is recorded on the document, the cause is classified as master data (GSTIN, HSN code, address, tax template), configuration, or a portal-side issue, and the fix is made on the source record before resubmitting. Track rejections in a shared log so repeated causes surface as a configuration problem rather than a series of one-off fixes.
Keep the platform current. Plan a recurring review of ERPNext and India Compliance minor releases, test each one on a staging copy of your site, and confirm that the India Compliance version you run matches your Frappe version, using the India Compliance installation guide as the reference. Restrict who may change GST settings, tax templates, accounts and HSN master data, require a second approver for those changes, and keep the approval record with the release notes. Confirm with your partner whether the post-go-live support is a fixed-scope engagement or a retainer before the first filing cycle.
How DeployOpen works on this
DeployOpen plans, implements, customizes, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For ERPNext and Indian GST compliance, we scope the India Compliance setup, build it in your environment, and hand over the settings, runbooks and evidence your team needs to file returns and answer questions with confidence.
How we scope
- Written scope lists the GST settings, accounts, return workflows and e-invoice or e-waybill features covered.
- We confirm your Frappe and ERPNext version, hosting model and whether the GST API is paid or handled elsewhere.
- Scope records which GSTINs, branches and return periods are in and which integrations are out.
How we build
- We install India Compliance on your ERPNext site and configure GST settings, tax accounts and item tax templates.
- We test GSTR-1 and GSTR-3B preparation against sample invoices, returns and credit notes from your books.
- We run purchase reconciliation with GSTR-2B exports and document how mismatches are reviewed and resolved.
How we hand over
- You receive a configuration record, the test cases used, and step-by-step runbooks for monthly filing.
- We document e-invoice and e-waybill credentials handling, access roles and who approves each filing step.
- Handover includes a walkthrough with your finance and tax staff so they can run the process without us.
How we support
- Fixed-scope delivery ends with handover, and any later changes are priced from a new written scope.
- Ongoing support, upgrades and testing for India Compliance releases are available as a retainer.
- Before each Frappe or ERPNext upgrade, we retest GST workflows so filings keep working after the change.
