Subscription businesses on ERPNext hit a wall fast. The stock Subscription and Subscription Plan DocTypes handle a flat monthly or annual invoice against a fixed price, but they were never designed for real recurring-revenue operations: mid-cycle plan changes with correct proration, metered usage rated at period close, tiered or volume pricing, grace periods, or a dunning sequence that retries a failed charge and escalates before it suspends the customer. Teams end up patching the gap with spreadsheets, manual credit notes, and a monthly scramble to reconcile who owes what — which quietly leaks revenue and burns finance hours every billing run.

ECOSIRE builds a proper Frappe app (its own module, installed on your bench alongside ERPNext) that closes that gap without forking core. We introduce dedicated DocTypes — Subscription Plan Tier, Usage Record, Billing Run, and Dunning Attempt — linked to native Customer, Sales Invoice, and Payment Entry so your ledger, GL, and reporting stay ERPNext-native. Recurring invoice generation and dunning retries run on scheduler_events (cron and daily hooks) so nothing depends on someone remembering to click a button. Proration on upgrades and downgrades is computed against the exact day count of the current billing period; usage-based and metered lines are aggregated from Usage Record rows (ingested via whitelisted REST endpoints or your product's telemetry) and rated at period close.

Technically, the app is wired the way a maintainable Frappe app should be. Business rules live in hooks.py doc events (validate, on_submit, on_cancel) and typed server-side controller methods rather than scattered client logic; whitelisted @frappe.whitelist() methods expose a clean surface for the Frappe REST API so your app, website, or payment webhook can push usage and trigger billing securely. Client Scripts drive the plan-change and quantity UX in the Desk, custom Role Profiles and permission rules keep billing operators out of the GL, and every automated action writes to a comment/timeline trail for audit. It targets Frappe/ERPNext v15 and is v16-ready, and we validate against your actual instance and payment gateway, not a generic demo.

Because this is build-to-order, nothing is a black-box download. We start with a scoping call to map your plans, proration policy, metering source, dunning cadence, and gateway. We build against your requirements, run UAT on a staging bench, and only then install on production with a rollback plan. Typical delivery is one working week from confirmed scope depending on complexity (metered billing and multi-gateway retries add time). You receive the full source in a git repository you own, so you are never locked to us.