An ISP or telecom operator runs two businesses at once: a network that must be provisioned, monitored and repaired, and a subscription book that must be rated, invoiced and collected every month across thousands of accounts. ERPNext already does the second half well at the accounting layer — Customer, Sales Invoice, Payment Entry, the GL, and the built-in Subscription DocType handle recurring billing against a Subscription Plan. Where ERPNext runs out of road is everything specific to telecom: it has no concept of a service instance tied to a circuit ID, ONU serial or MSISDN; no usage rating engine that turns CDRs or RADIUS accounting records into billable quantities; no proration rules for mid-cycle upgrades, suspensions and reconnections; no provisioning state machine that separates "invoice raised" from "service actually live on the network"; and no dealer or franchise ledger for the collection channels most regional operators depend on. Operators usually bridge that gap with spreadsheets, a separate billing box that never reconciles to the GL, and a WhatsApp group standing in for trouble-ticket operations.

ECOSIRE builds this as a first-class Frappe application — its own app in apps/, with a telecom module, versioned fixtures and a clean hooks.py — never as a pile of Customize Form overrides that break on the next bench update. The core model introduces a Telecom Plan DocType (rental, included quota, tiered overage tariff bands, contract term, tax template) and a Service Subscription DocType linking Customer, plan, service address and the network identifiers your OSS actually uses. Rating runs off a Usage Record ledger fed either by scheduled import of CDR/RADIUS/NetFlow exports or by an authenticated push from your NMS into a @frappe.whitelist() endpoint. A nightly job registered in scheduler_events aggregates unrated usage, applies the plan's tariff bands in testable Python — not a Server Script buried in the database — and stamps rated quantities back onto the subscription. The billing run then generates ERPNext Sales Invoices through the framework API, so tax templates, cost centers, accounting dimensions and the GL behave exactly as your accountants expect; proration, outage credit notes and one-off installation charges all post as ordinary ERPNext documents you can audit.

Operations sit on the same spine. A Service Order DocType covers new connection, upgrade, relocation, suspension and disconnection, driven by a Frappe Workflow with role-gated transitions and on_submit / on_update_after_submit doc events in hooks.py that fire the real provisioning action — a webhook to your OLT or BNG controller, a RADIUS profile change, or a queued background job with retry and a written audit trail on the document timeline. Dunning becomes policy rather than memory: a scheduler job walks overdue subscriptions through grace, throttle, suspend and reconnect, so nobody is suspended by a manual mistake or left live after ninety unpaid days. Trouble tickets extend the ERPNext Issue DocType with fault category, affected service instance, outage window and SLA clocks, so a fault is linked to the subscription it interrupted and can justify a credit note automatically. Dealer and collection channels get Dealer and Collection Receipt DocTypes with commission rules, a running ledger, and a permission model — role profiles plus User Permissions and, where tenancy demands it, a permission_query_conditions hook — so a dealer sees only their own subscribers on the desk, the portal and the REST API alike. Client Scripts add the field conveniences: serial and barcode capture, one-click reconnect, live balance on the subscription form.

Every integration point is designed to be operated, not merely demonstrated. The Frappe REST API plus a small set of whitelisted methods gives your NMS, payment aggregator and mobile collection app a documented contract with API-key authentication, idempotent handling and rate limiting. Failed provisioning calls land in an error log with a retry action instead of vanishing. The rating engine ships with unit tests you can run under bench run-tests, so a tariff change is verified before it touches a live cycle. The app targets Frappe/ERPNext v15 and v16 and is built for the version you actually run, on your hosting — Frappe Cloud private bench, your own VPS, or the Docker stack.

This is a build-to-order engagement, not an instant download. It begins with a scoping call covering your plans, tariff bands, usage source format, provisioning targets and dealer structure. We return a written scope and a fixed quotation; once you confirm it, typical delivery is 2-4 weeks. We build against a staging copy of your site, run UAT with your billing and NOC teams over a real cycle, then install to production with a documented rollback. You receive the complete source in a Git repository you own, so nothing here is a black box.