A build-to-order ERPNext app that records foreign-exchange forward contracts, links them to your invoices and purchase orders, and tracks hedge effectiveness and mark-to-market valuation through to settlement. ECOSIRE scopes, builds, installs, and supports it — this is not an off-the-shelf download. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that records foreign-exchange forward contracts, links them to your invoices and purchase orders, and tracks hedge effectiveness and mark-to-market valuation through to settlement. ECOSIRE scopes, builds, installs, and supports it — this is not an off-the-shelf download.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
`Forward Contract` DocType capturing deal date, value/maturity date, buy and sell currency, notional, locked forward rate, and counterparty bank
Dynamic-link child table binding each contract to the specific `Sales Invoice`, `Purchase Order`, or `Payment Entry` it hedges
`Hedge Relationship` DocType recording hedge type (cash-flow vs fair-value), hedged risk, and the designated effectiveness method
Scheduler event in `hooks.py` that pulls daily spot/forward rates and writes a mark-to-market valuation row per open contract
Automated GL posting via ERPNext Journal Entry API, routing MTM through OCI or P&L per hedge designation
Hedge effectiveness tracking with dollar-offset / ratio testing and a pass/fail flag stored per relationship
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 2-4 weeks from confirmed scope. You receive the complete source in a Git repository you own, so nothing about the app is locked to us.
Owns currency risk on cross-border POs and invoices. Needs every forward contract recorded against its underlying exposure so booked margins survive settlement, and wants a single net-unhedged-exposure view instead of reconciling spreadsheets to the GL.
Books forwards with banks and manages the maturity ladder. Needs rate-lock and settlement authority separated by role, daily mark-to-market on open positions, and a maturity workflow that pushes settlement actions before value dates slip.
Responsible for hedge accounting compliance. Needs documented hedge designations, effectiveness testing with a pass/fail trail, and automated OCI/P&L postings so the audit question on hedge effectiveness is answered inside ERPNext.
Runs the ERPNext bench and vets any new app. Needs a clean Frappe module on v15/v16, source in a Git repo they own, migration-safe fixtures, and no lock-in to the vendor.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Forward Contracts & FX Hedging 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 Forward Contracts & FX Hedging 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Forward contract recording | Dedicated Forward Contract DocType with rate lock, maturity, and counterparty | Possible but you design the schema from scratch | Generic contract app not built for FX terms | |
| Link to invoices / POs | Dynamic-link child table ties each contract to its exposure | Must be coded and tested yourself | Rarely linked to source documents | |
| Hedge effectiveness testing | Built-in ratio/dollar-offset testing with pass-fail trail | Depends entirely on your developer's accounting knowledge | Usually absent | |
| Mark-to-market valuation | Scheduler-driven daily MTM row per open contract | You build the rate feed and revaluation job | Often manual or missing | |
| GL posting (OCI vs P&L) | Automated Journal Entries routed by hedge designation | Hand-coded posting logic | Typically no hedge-accounting postings | |
| Settlement workflow | State workflow with role-gated transitions and realised G/L | Build and maintain your own workflow | Limited or generic status field | |
| Ownership & fit | Purpose-built to your policy; full Git repo handover | You own it but carry all build risk | Vendor-locked, one-size-fits-all | |
| Support & upgrades | Post-go-live window plus optional v15/v16 upgrade retainer | Only your own team | Generic vendor support, no policy context |
This is a build-to-order app, not an instant download. After a scoping call we confirm the DocTypes, effectiveness method, and GL posting rules in writing, then typically deliver in 2-4 weeks from confirmed scope. Complex hedge-accounting policies or many exposure types may extend that, and we tell you before you commit.
No. ECOSIRE designs, builds, installs, and supports it specifically for your hedging policy and chart of accounts. You are not buying a pre-existing listing — you are commissioning a purpose-built Frappe app that you then own outright via the Git repository handover.
We build and test against Frappe/ERPNext v15 and v16. Tell us your exact version and hosting (Frappe Cloud, self-managed bench, or containerised) during scoping and we target it directly, including migration-safe fixtures for your setup.
Mark-to-market and settlement entries post automatically through ERPNext's Journal Entry API. Cash-flow hedge movements route through OCI and fair-value movements through P&L, based on each contract's hedge designation, using the accounts you map during configuration — nothing is posted with hardcoded accounts.
Every engagement includes a post-go-live support window covering defect fixes and questions. Because you receive the full source in your own Git repo, your team or ECOSIRE can extend it later. We also offer ongoing support and version-upgrade retainers if you want us to maintain it across future ERPNext releases.
Yes. A scheduler event registered in hooks.py fetches daily spot and forward rates and writes a mark-to-market row per open contract. We wire it to your preferred rate source — your bank feed, a market data provider, or ERPNext's existing exchange-rate mechanism — during the build.
Your written hedge accounting policy (or a description of how you hedge), the effectiveness testing method you use, your chart of accounts and the accounts to post to, sample bank forward confirmations, and your ERPNext version. We turn that into a confirmed scope before any code is written.
A build-to-order ERPNext app that records foreign-exchange forward contracts, links them to your invoices and purchase orders, and tracks hedge effectiveness and mark-to-market valuation through to settlement. ECOSIRE scopes, builds, installs, and supports it — this is not an off-the-shelf download.