Finance teams running ERPNext get a solid general ledger, Bank Account and Bank Transaction DocTypes, and the Cash Flow statement report — but treasury is a different discipline. A treasurer who needs to answer "how much cash do we truly have across all banks right now, and what does the next 13 weeks look like?" ends up exporting balances into spreadsheets, hand-keying expected receipts and payments, and reconciling forecasts that go stale the moment a Payment Entry posts. ERPNext core has no dedicated treasury workspace, no approval workflow for treasury movements, no consolidated multi-account position, and no rolling forecast that reads directly from open Sales and Purchase Invoices. That gap is where liquidity risk hides.

ECOSIRE builds a proper Frappe application — not a pile of loose customizations — installed into your bench as its own app with a Treasury module. We add DocTypes such as Treasury Entry (recording deposits, withdrawals, inter-account transfers, FX conversions and short-term placements against your existing Bank Account records), Cash Position Snapshot, and a Cash Flow Forecast document with child rows for projected inflows and outflows. A configurable Workflow governs the approval lifecycle (Draft → Pending Approval → Approved → Posted) with role-based transitions, so no treasury movement is confirmed without the right sign-off. hooks.py doc events (on_submit, on_cancel, validate) keep positions consistent and, where you want it, write the corresponding Journal Entry or Payment Entry so the GL never drifts from treasury.

Forecasting is computed server-side. Scheduled jobs registered under scheduler_events refresh cash position snapshots and rebuild the forecast on a cadence you choose (nightly, hourly), pulling expected receipts from open Sales Invoices and Payment Schedule due dates, and expected payments from open Purchase Invoices, so the projection reflects live ERPNext data rather than a stale export. A whitelisted method (@frappe.whitelist()) exposes the consolidated multi-account position and the forecast series to a Number Card / dashboard chart and to the Frappe REST API, so your treasurer sees today's position and a rolling forward view in one place. Client Scripts drive in-form behavior — currency-aware balance validation, quick inter-account transfer actions — and Role Profiles plus permission rules ensure only Treasury and Finance roles can record, approve, or view sensitive positions.

Because this is build-to-order, we start from your actual chart of accounts, bank structure, currencies and approval hierarchy — nothing is assumed. After a short scoping call we confirm the exact DocTypes, workflow states, and forecast logic in writing, build against a staging bench, and run UAT with your finance team before go-live. Typical delivery is one working week from confirmed scope, targeting Frappe/ERPNext v15 and v16. You receive the installable app source and a git repository so the solution is fully yours to run, audit, and extend.