Customs Clearance & Clearing-Forwarding for ERPNext

ECOSIRE builds a proper Frappe application — a versioned app installed on your own bench, not a pile of customisations bolted onto stock DocTypes. At its core are dedicated DocTypes: Customs Declaration and Bill of Entry (with child tables for line items, each carrying an HS code, assessable value, duty rate, and computed duty/tax), an HS Code tariff master, and a Clearing Job that ties a consignment to its declarations, disbursements, and the importer being billed. Duty and tax computation runs in server scripts wired through hooks.py doc events (validate, on_submit) so every line recalculates deterministically on the server — never trusting client-side math — and posts recoverable costs and agency fees into ERPNext's accounting via Journal Entries and Sales Invoices so cost recovery lands on the customer ledger automatically.

The app is engineered the way a Frappe app should be. Client scripts drive the data-entry UX — auto-fetching duty rates when an HS code is picked, flagging incomplete declarations before submit. Whitelisted methods expose the calculation and job-status logic to the Frappe REST API so your port agents, a broker portal, or an external declaration system can integrate over HTTP with token auth. Role profiles and permission rules (Clearing Agent, Customs Officer, Accounts) scope who can submit a declaration versus who can post a disbursement. Scheduler events run the demurrage/detention accrual nightly — incrementing day counts, applying free-time rules per shipping line, and raising alerts as a container approaches its free-time expiry — so charges are captured the day they arise instead of being discovered on an invoice weeks later. It is built and tested against Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing ships as an anonymous download. We start with a scoping call to map your declaration workflow, tariff sources, ports, and the charges you recover from importers, then confirm a fixed scope. Typical delivery is 2–4 weeks from confirmed scope. You get the installable app source for your ERPNext version, installation and configuration on your bench, UAT on a staging site with a rollback plan, technical documentation, a user guide with a live training session, a git repository handover, and a post-go-live support window.