Import/export finance leads carry real currency risk: a purchase order priced in USD or EUR today settles weeks later at a rate nobody can predict, and the gap quietly eats the margin the sales team fought for. Treasury books forward contracts with the bank to lock those rates, but ERPNext core has nowhere to record them. There is no Forward Contract DocType, no link from a locked rate to the underlying invoice or PO, and no hedge accounting. Finance ends up tracking six-figure hedges in spreadsheets that never reconcile with the General Ledger, and the auditor's first question — "show me your hedge effectiveness testing" — has no answer inside the ERP.

ECOSIRE builds a proper Frappe app (its own module, installed on your bench with bench get-app and bench install-app) that puts the full hedging lifecycle inside ERPNext. The core is a Forward Contract DocType — deal date, value date/maturity, buy and sell currencies, notional amount, locked forward rate, counterparty bank, and a child table of hedged items. A Link field and dynamic-link child table tie each contract to the specific Sales Invoice, Purchase Order, or Payment Entry it hedges, so the exposure and its cover live on one screen. A companion Hedge Relationship DocType captures the designation (cash-flow or fair-value hedge), the hedged risk, and the effectiveness method your accounting policy uses.

Technically, the app runs on server-side logic rather than manual data entry. A scheduler event (registered in hooks.py under scheduler_events) pulls the day's spot and forward rates and writes a mark-to-market valuation row per open contract, so unrealised gain/loss is always current. hooks.py doc_events hook the on_submit of Sales Invoice/Purchase Order to flag exposures that lack cover, and hook the Forward Contract's own submit and settlement transitions to post the correct GL entries via ERPNext's Journal Entry API — moving mark-to-market through OCI or P&L depending on the hedge designation. Whitelisted methods (@frappe.whitelist()) expose effectiveness ratios and open-exposure summaries to the Frappe REST API for treasury dashboards, and client scripts add live rate-difference and settlement-amount calculations on the contract form. A dedicated role profile (Treasury / FX Manager) with permission rules keeps rate-locking and settlement authority separate from AP/AR clerks.

Because this is build-to-order, we start from your actual hedging policy, chart of accounts, and bank confirmations rather than a generic template. After a short scoping call we confirm the DocTypes, effectiveness method, and GL posting rules in writing, build the app against Frappe/ERPNext v15 or v16, and validate it on a staging copy of your data with your own contracts before anything touches production. Typical delivery is one working week from confirmed scope. You receive the complete source in a Git repository you own, so nothing about the app is locked to us.