If your turnover is above the India GST e-invoicing threshold, every B2B, export, and credit/debit-note document has to carry a valid IRN and a government-signed QR code before it is legally issued — and stock movements above the value limit need an e-way bill with an active Part-A and Part-B. ERPNext core gives you clean Sales Invoices, GST tax templates, and HSN codes, but it does not talk to the Invoice Registration Portal (IRP) or a GSP. Teams end up re-keying every invoice into the government portal or a third-party tool, reconciling IRN and e-way bill numbers by hand, and discovering rejections (wrong HSN, missing PIN code, place-of-supply mismatch) only after the customer is waiting at the gate. That manual bridge is where errors, penalties, and month-end GSTR-1 pain come from.

This is a build-to-order connector: ECOSIRE builds you a proper Frappe app (its own module, hooks.py, DocTypes, and fixtures) that turns your ERPNext into the single system of record for GST compliance. On Sales Invoice submit, a doc_events hook validates the document against IRP schema rules, builds the JSON payload, and calls your chosen IRP/GSP endpoint through a queued background job. The returned IRN, acknowledgement number, acknowledgement date, and the government signed QR are written back to custom fields and rendered on your print format so the PDF is ready to send. E-way bill generation — including transporter ID, vehicle number, and Part-B updates — runs from the same Sales Invoice (or Delivery Note), with a whitelisted method exposed via the Frappe REST API so warehouse or dispatch staff can update the vehicle at the gate. A dedicated E-Invoice Log DocType stores every request/response for audit, and cancellation is handled inside the 24-hour IRP window with the correct reason codes.

Technically it is built to Frappe conventions so your team can own it. GSP credentials and endpoint config live in a single Settings DocType (not hard-coded); token refresh and any retry of failed submissions run on scheduler_events so a transient GSP outage self-heals instead of blocking invoicing. Role profiles and permissions gate who can generate, cancel, or override — accounts users generate, only a GST manager can cancel. A GSTR-1 reconciliation export (Query Report / whitelisted method) reconciles your ERPNext invoices against generated IRNs so nothing slips before you file. Client scripts add the action buttons and status indicators on the form; server scripts and validations keep bad payloads from ever reaching the IRP. It targets Frappe/ERPNext v15 and v16 and respects your existing GST tax templates rather than replacing them.

Because it is built to order, we start from your actual setup — your GSTINs, tax templates, invoice series, GSP contract, and whether you need e-way bill, e-invoice, or both. After a short scoping call we confirm the exact schema fields, edge cases (SEZ, exports with/without payment, RCM, multi-branch), and acceptance criteria, then build and test on a staging bench against the GST sandbox. Typical delivery is one working week from confirmed scope. You receive the installable app source, a git repository, install and configuration docs, a training session, and a post-go-live support window — ECOSIRE installs it, migrates it live against the production IRP, and stands by through your first filing cycle.