A build-to-order ERPNext app that tracks Advance Authorisation licences, RODTEP scrips and duty drawback claims, monitors export obligation fulfilment, and links every claim to its shipping bill. ECOSIRE scopes, builds, installs and supports it for your EXIM team. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $399.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that tracks Advance Authorisation licences, RODTEP scrips and duty drawback claims, monitors export obligation fulfilment, and links every claim to its shipping bill. ECOSIRE scopes, builds, installs and supports it for your EXIM team.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
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.
`Advance Authorisation Licence` DocType tracking licence number, CIF entitlement, export-obligation value/quantity, validity dates and permitted-input child table
`Export Incentive Claim` DocType covering RODTEP, duty drawback and other DGFT schemes with scheme, rate, computed benefit, scrip number and lifecycle status
Maintainable `Scheme Rate` table keyed on HS code and effective date so rate-notification changes are data edits, not code deployments
`hooks.py` doc events on Sales Invoice submit that draft the matching incentive claim and decrement the linked Advance Authorisation obligation
Export-obligation monitor: daily scheduler event flags licences nearing obligation shortfall or expiry and raises ToDos / email alerts to the EXIM owner
Server-script benefit computation for RODTEP and duty drawback against realised FOB value and HS-code rate, with rounding and cap rules
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 2 to 4 weeks 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.
Owns Advance Authorisation licences and their export obligations. Needs a single register that shows entitlement, consumption and deadline risk before a licence lapses, instead of chasing figures across shipping bills and spreadsheets.
Responsible for booking RODTEP and drawback benefit and reconciling scrips against the ledger. Needs claims computed on realised FOB value, traceable to shipping bills and Sales Invoices, so nothing is under-claimed or double-counted at audit.
Wants working-capital certainty from incentive recovery and a defensible audit trail inside ERPNext, without funding a full custom ERP build or trusting an unmaintained marketplace plugin.
Maintains the bench and integrations. Needs a clean Frappe app with proper hooks, whitelisted methods and fixtures — not core patches — so v15/v16 upgrades and CHA/portal integrations stay manageable.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Advance Authorisation & RODTEP Export Incentives アプリの ZIP をダウンロードします。
ZIP をベンチのアプリ フォルダーに抽出するか、抽出されたアプリへのパスを指定して「bench get-app」を実行します。
`bench --site SITE_NAME install-app APP_NAME` を実行し、続いて `bench maigrate` を実行して、Advance Authorisation & RODTEP Export Incentives をインストールし、そのスキーマを適用します。
サイトの ECOSIRE ライセンス設定を開き、ライセンス キーをアクティブ化します。無料の ecosire_connect アプリと ecosire_license_client アプリが必要です。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Fit to Indian export schemes | Advance Authorisation, RODTEP and drawback modelled as first-class DocTypes for your process | Whatever you specify, if the developer knows DGFT rules | Generic incentive tracking, rarely India-scheme aware | |
| Export obligation monitoring | Daily scheduler job flags obligation shortfall and expiry risk with alerts | Possible but must be built and tested from scratch | Usually absent or manual | |
| Rate maintenance | Editable `Scheme Rate` table by HS code and effective date — no redeploy | Depends on how it was built; often hardcoded | Often fixed logic requiring vendor updates | |
| Shipping-bill linkage | Every claim ties to shipping bill and Sales Invoice for audit trail | Achievable with effort | Partial or spreadsheet-based | |
| v15/v16 upgrade safety | Clean Frappe app, no core patches, supported hooks and methods | Varies with developer discipline | Unknown; may lag on new versions | |
| Ownership and lock-in | Full source in a git repo you own, no lock-in | You own it, at full custom build cost | Licensed; source often closed | |
| Delivery time | 2-4 weeks from confirmed scope, UAT and rollback included | Months, plus discovery and hiring risk | Instant install but rework to fit | |
| Support after go-live | Defined support window plus training and docs | Only if separately retained | Vendor tier, variable quality |
This is build-to-order, not an instant download. After a scoping call to confirm schemes, rate sourcing and your v15/v16 setup, typical delivery is 2 to 4 weeks from confirmed scope. That includes the build, UAT on a staging bench with your sample shipping bills, and production install with a rollback plan.
Yes. Every build includes a post-go-live support window for defect fixes and configuration help. Because scheme rates and DGFT notifications change, rates live in a maintainable `Scheme Rate` table you edit yourself — no code change needed. Longer-term maintenance or v15-to-v16 upgrade support can be arranged as a separate engagement, and you own the git repo either way.
Yes. We build it as a standard Frappe app tested against your target version — v15 or v16 — using supported patterns (DocTypes, hooks.py doc events, server and client scripts, scheduler events, whitelisted REST methods). We do not patch ERPNext core, so your upgrades stay clean.
Rates are stored in a `Scheme Rate` DocType keyed on HS code and effective date. When a rate notification changes, your team updates the table and new claims compute against the correct rate from the effective date. We seed the initial rates during build; ongoing rate upkeep is a data task, not a redeployment.
Yes. Each `Export Incentive Claim` links to its shipping bill (number, port code, LEO date, FOB value) and to the originating Sales Invoice, so benefit computes on realised export value and every claim carries a full audit trail. Sales Invoice submit can auto-draft the matching claim via a doc event.
Yes. We expose whitelisted methods over the Frappe REST API for claim status and licence utilisation, scoped by permission. That lets a CHA portal, BI dashboard or internal tool pull data without direct database access.
You get the complete source as an installable Frappe app in a git repository you own, plus technical docs and a training session. There is no lock-in — your ERPNext administrator or another partner can maintain and extend it independently.
A build-to-order ERPNext app that tracks Advance Authorisation licences, RODTEP scrips and duty drawback claims, monitors export obligation fulfilment, and links every claim to its shipping bill. ECOSIRE scopes, builds, installs and supports it for your EXIM team.