If your team bids on tenders, EMD and security deposits leak straight out of ERPNext's structured accounting. Out of the box, ERPNext has no concept of an earnest money deposit tied to a specific tender or contract, so people track them in spreadsheets or park them in a generic advance account. When a bid is lost and the deposit should be refunded, or a contractor defaults and it should be forfeited, someone has to remember, chase the bank, and hand-post a journal entry. Deposits sit against the wrong party, refunds slip, forfeitures are booked late, and month-end reconciliation of the EMD control account becomes guesswork. There is no aging, no outstanding report, and no link to the bank guarantee that often backs the deposit.

ECOSIRE builds a proper Frappe application — its own installable module with a dedicated Earnest Money Deposit DocType plus supporting DocTypes for refund, forfeiture and bank-guarantee linkage — that turns this into a controlled workflow inside ERPNext. Each EMD document captures the tender or contract reference, party, amount, mode (cash, DD, or bank guarantee), expected release date and the GL accounts to use. Server-side logic in hooks.py doc events (on_submit, on_cancel, and a validate hook for account and amount checks) posts the deposit Journal Entry automatically against a configurable EMD control account, and reverses or reclassifies it on refund or forfeiture. Refund posts back to the party or bank; forfeiture moves the balance to an income/other-income account you choose during scoping. Every posted entry is linked back to the source EMD document so the audit trail is complete.

Technically it is a clean Frappe/ERPNext v15/v16 app, not a pile of customizations. Automation runs through whitelisted server methods and doc-event handlers rather than manual journals; a scheduler event runs daily to flag deposits past their expected release date and drive the aging report. A client script on the EMD form guards the workflow (you cannot refund an already-forfeited deposit, cannot exceed the held amount) and surfaces the linked bank guarantee and its expiry. Everything respects ERPNext permissions — we ship a role profile so a project coordinator can raise and track deposits while only Accounts users can submit the journals. Reports (EMD Aging, Outstanding EMD by tender/party) are native query/script reports, and the whole thing is reachable over the Frappe REST API and whitelisted methods for any portal or integration you need.

Because this is build-to-order, nothing is a black box. We start with a short scoping call to confirm your account mapping, deposit modes, forfeiture treatment and approval roles, then build and configure the app against your chart of accounts. Typical delivery is one working week from confirmed scope, depending on how much of the bank-guarantee and reporting depth you need. You get the full source in a git repository, UAT on a staging bench before anything touches production, and a post-go-live support window. It runs on your own Frappe/ERPNext instance — self-hosted or Frappe Cloud — and stays yours.