If you run a subscription or usage-based business on ERPNext, you have probably hit the ceiling of the native Subscription DocType. Core ERPNext can generate a recurring Sales Invoice on a fixed plan cycle, but it cannot meter consumption, prorate a mid-cycle plan change, chase failed payments on a schedule, or recognize revenue over the service period. Finance teams end up exporting to spreadsheets, hand-adjusting deferred revenue via manual Journal Entry, and manually emailing customers whose cards declined — exactly the error-prone, un-auditable work an ERP is supposed to eliminate. ERPNext Subscription & Recurring Billing Pro closes that gap as a proper Frappe app installed on your own bench.

We build a dedicated Frappe app (its own module, DocTypes, and hooks.py) rather than bolting scripts onto core. Typical DocTypes include Billing Plan (with tiered and volume price rules), Usage Record (metered events posted via a whitelisted REST endpoint), Dunning Policy, and Revenue Schedule. A nightly scheduler_events job aggregates Usage Record rows per subscription, applies your rating rules, and drafts or submits the period Sales Invoice. Proration and plan upgrades are handled with server-side logic on document events (on_submit, on_update) so a mid-cycle switch generates the correct credit and charge lines automatically, with full ledger backing rather than a manual adjustment.

Dunning runs as a scheduled job that walks overdue invoices, follows your configured retry cadence (for example day 1 / 3 / 7 / 14), fires templated email or SMS reminders through Frappe's Notification and Email Queue, and escalates to suspend/cancel actions when the policy exhausts. Deferred revenue is posted through ERPNext's native deferred-accounting fields plus a Revenue Schedule DocType, so month-by-month recognition ties back to your Chart of Accounts and reconciles against invoiced amounts — auditors see a clean trail, not a black box. Where you need a payment gateway (Stripe, Razorpay, a local processor), we wire the webhook to a whitelisted method that updates payment status and short-circuits dunning on success.

Everything respects Frappe's permission model: role profiles, permission levels, and user-permission scoping so a billing clerk, an AR manager, and an auditor each see only what they should. Client scripts add the in-form UX (live proration preview, one-click "run dunning now"), and every automated behavior is covered by hooks.py doc events and scheduler entries so it survives upgrades. The app targets Frappe/ERPNext v15 and v16, and we pin to your exact bench version at scoping time.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, produce a written specification and fixed quotation, then build against your real plans, tax rules, and gateway. Typical delivery is one working week from confirmed scope. You get UAT on a staging site, a rollback plan, the full git repository, and a post-go-live support window — not a mystery zip from a marketplace.