Every GST-registered business in India loses Input Tax Credit the same way: a supplier files late or wrong, an invoice that sits in your purchase register never shows up in GSTR-2B, or a GSTIN/invoice-number typo means the two records never match — and the ITC quietly slips through the cracks at return-filing time. Stock ERPNext gives you the GST accounting backbone (Purchase Invoice, GSTIN fields, tax templates, the GSTR-3B/GSTR-1 reports), but it has no native workspace to pull the government's GSTR-2B JSON back in and reconcile it against what you actually booked. Accounting teams end up exporting to spreadsheets, doing VLOOKUPs by hand every month, and hoping they caught everything before the ITC claim window closes — which is exactly where audit exposure and lost credit come from.

ECOSIRE builds a dedicated reconciliation app as a proper Frappe application (bench get-app installable), namespaced with its own module so it upgrades cleanly and never patches ERPNext core. At its heart is a GSTR-2B Import DocType that ingests the raw JSON downloaded from the GST portal (B2B, CDNR, amendments, and ISD sections), parsing it into child-table rows, plus a Purchase Reconciliation document that pairs each portal invoice against the matching Purchase Invoice in your books. The matching engine — implemented as whitelisted server-side methods (@frappe.whitelist()) rather than fragile client logic — keys on GSTIN, document number, document date, and taxable/tax values with configurable tolerance bands, then classifies every row as Exact Match, Probable Match (fuzzy on invoice number or ±rupee/±date tolerance), Mismatch, Only-in-2B, or Only-in-Books. ITC eligibility is flagged per line using the section, reverse-charge, and place-of-supply data so ineligible or blocked credit is separated out before you file.

Around that engine we build the workflow your team actually needs: a vendor-wise reconciliation summary (grouped Query Report with drill-down to the offending invoices), bulk accept/reject actions that write an audit trail back onto the linked Purchase Invoice, and a follow-up mechanism that can raise a ToDo or draft a supplier email for every Only-in-2B or mismatched line so your GSTIN owner has a concrete list to chase. hooks.py doc events keep the reconciliation status in sync when a Purchase Invoice is amended or cancelled, a scheduler event can auto-flag periods that still have unreconciled ITC as the filing date approaches, and Client Scripts add the one-click "Import 2B" and "Run Match" buttons where accountants expect them. Role profiles and permission rules scope who can import portal data versus who can approve/reject credit, and everything is exposed through the Frappe REST API if you want to trigger reconciliation from an external tax tool.

Because this is build-to-order, nothing ships until we understand your exact GST footprint. We start with a scoping call to confirm your ERPNext version (v15 or v16), number of GSTINs, invoice volume, tolerance rules, and how strict your ITC policy is, then build against a written scope. Typical delivery is one working week from confirmed scope. You get installable source, a git repository handover, UAT on a staging site with a rollback plan, user training, and a post-go-live support window — so the reconciliation runs on your own bench, on your own data, with no dependency on a third-party SaaS holding your purchase records.