Indian exporters leak real money in the gap between what they are entitled to and what they actually claim. RODTEP and duty drawback rates change by HS code and notification, Advance Authorisation licences carry export obligation and validity clocks that must be closed before the DGFT deadline, and the numbers that prove a claim — FOB value, shipping bill number, port code, scheme rate — live in spreadsheets that no one reconciles against the ledger. ERPNext gives you Sales Invoices, Delivery Notes and a general ledger, but it has no concept of an Advance Authorisation licence, no RODTEP or drawback claim register, and no export-obligation monitor. The EXIM team ends up tracking incentives outside the system entirely, and shortfalls surface only when a licence lapses or an audit asks for the paper trail.

ECOSIRE builds a proper Frappe app — its own module, installed into your ERPNext v15 or v16 bench — that models the schemes as first-class DocTypes rather than notes bolted onto invoices. Advance Authorisation Licence holds the licence number, CIF import entitlement, corresponding export obligation (value and quantity), issue and expiry dates, and a child table of permitted inputs; Export Incentive Claim captures each RODTEP or duty drawback claim with its scheme, rate, computed benefit, scrip number and status. Both link directly to the originating Sales Invoice and shipping bill, so every rupee of claimed benefit traces back to a real export document. A Shipping Bill DocType (or fields on the Sales Invoice via a fixture) records port code, LEO date, FOB currency and value so claims compute against the correct realised value.

The automation lives where Frappe expects it. hooks.py doc events fire on Sales Invoice submit to draft the corresponding incentive claim and decrement the relevant Advance Authorisation obligation; server scripts compute RODTEP and drawback benefit from a maintainable Scheme Rate table keyed on HS code and effective date, so a rate-notification change is a data edit, not a code change. Scheduler events run a daily job that flags licences approaching their export-obligation deadline or expiry and raises ToDos or email alerts to the EXIM owner. Client scripts add "Create Claim" and "Reconcile Obligation" actions on the relevant forms, whitelisted methods expose claim status and utilisation over the Frappe REST API for your CHA or dashboard, and role profiles (EXIM Officer, Finance Manager, Auditor read-only) plus DocType permissions keep the workflow scoped to the right hands.

Because this is build-to-order, nothing ships until we agree exactly what you need. We start with a scoping call to confirm which schemes you claim, your HS-code and rate sourcing, how shipping bills reach you, and your v15/v16 and hosting setup. We then build against that scope, prove it on a staging bench with your own sample shipping bills during UAT, and install into production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source as an installable Frappe app in a git repository you own, along with documentation, a training session for the EXIM and finance team, and a post-go-live support window.