Real estate firms and landlords running on ERPNext quickly hit a wall: ERPNext ships strong accounting, buying, and selling, but it has no native concept of a property, a rentable unit, a floor/block hierarchy, or a lease that generates recurring rent on its own schedule. Teams end up modeling buildings as warehouses, tenancies as loose subscriptions, and rent runs as manually keyed sales invoices — which breaks the moment you need escalation clauses, deposit accounting, meter-based utility recovery, or a portal where a tenant can raise a complaint. The Subscription DocType covers simple recurring billing but knows nothing about occupancy, vacancy, notice periods, or renewals.

ECOSIRE builds a proper Frappe application (its own installable app with a dedicated module) that adds first-class DocTypes for Property, Property Unit (with parent floor/block links), Lease Contract, Tenant, Landlord, Broker, Maintenance Request, and Utility Reading. Lease contracts drive automated rent invoicing through Frappe scheduler events (scheduler_events in hooks.py) that generate ERPNext Sales Invoices against the correct customer, cost center, and income account on each billing cycle, and apply escalation rules on the contract anniversary. Document lifecycle logic — proration on move-in, deposit hold and refund postings, status transitions from Draft to Active to Terminated — is enforced through on_submit, validate, and on_cancel server-side controller methods and doc_events hooks, never left to manual discipline. Client scripts add unit-availability checks and dynamic filters in the desk UI.

The three portals (tenant, landlord, broker) are built on Frappe's web/portal layer with role-scoped visibility. A tenant signs in to see their active lease, invoice and payment history, deposit balance, and can submit a Maintenance Request that routes into an assignment and SLA-tracked workflow; a landlord sees occupancy, rent roll, and net income across their portfolio; a broker sees their listings and commission ledger. Access is governed by ERPNext role profiles, permission rules, and User Permissions so a tenant can never read another tenant's records. Where you need to push data to a mobile app, website, or external CRM, we expose whitelisted methods (@frappe.whitelist()) and use the standard Frappe REST API rather than direct database access.

Utility and meter billing is handled as its own flow: meter readings are captured per unit, consumption is computed against the previous reading, and a scheduled job raises the utility charge as an invoice line or a separate invoice per your accounting preference. Deposits are tracked as liabilities with clean refund and deduction postings, so your ledger stays audit-clean. Everything is built against ERPNext v15/v16 conventions so it upgrades cleanly and coexists with the accounting, CRM, and payments you already run.

Because this is build-to-order, nothing ships as an anonymous marketplace download. We start with a scoping call to confirm your unit hierarchy, lease and escalation rules, tax treatment, and portal requirements, then build to that spec. Typical delivery is one working week from confirmed scope. You get the installable app source for your version, a UAT pass on a staging bench with a documented rollback plan, install and configuration on your instance, technical and user documentation, a training session, and a post-go-live support window — plus the Git repository handed over so you own what you paid for.