Recurring revenue billed through your real invoice spine
Plans, price books and coupons; a lifecycle with proration on every move; recurring invoicing and dunning that issue real sales invoices; metered usage rated against tier ladders; and deferred-to-recognised revenue. Enabled as a cloud marketplace pack.
A catalogue, not a price field
A plan carries its billing model — flat, tiered, volume, seat, usage, freemium or hybrid — plus a default cycle, trial days, setup fee, security deposit and GST rate. Each plan gets an effective-dated price book and a usage or seat tier ladder, alongside add-ons and coupons (percent, amount, free period or trial extension). Subscribing a customer resolves the price book, add-ons and coupon into a pricing snapshot held on the subscription itself.
Lifecycle with proration you can check first
Trial → active → change plan, pause, cancel (immediately or at period end) or renew, and paused or suspended → resume, with a live proration preview before you commit the change and an event timeline per subscription. The billing engine is pure: no clock, every date passed in, integer paise, largest-remainder splits so the parts sum exactly to the total, and exclusive period ends so no day is billed twice.
Bills as real invoices, dunning as a ladder
The recurring sweep issues each bill as an actual sales invoice through the standard spine — so GST, numbering, the PDF and the ledger behave exactly as they do for any other invoice — and receipts collect through the normal receipts spine. The dunning tick then works the ladder at day 0, 3, 7 and 14 past the due date; an exhausted ladder suspends the subscription, and a late fee is assessed separately once the plan’s grace period has passed.
Meter the usage, recognise the revenue
Define meters (what is measured, in what unit, aggregated how), post usage events that deduplicate on an idempotency key, then rate the period against the plan’s tier ladder — the per-tier breakdown is kept as a snapshot, so a rated summary can be explained line by line. Revenue recognition builds straight-line deferral schedules from billed subscription invoices and recognises due periods with an idempotent Dr Deferred / Cr Subscription Revenue entry.
MRR you can explain
MRR and ARR with per-status counts, an MRR movement bridge across new, expansion, contraction, churn and reactivation over a window, a churn-risk ranking with the drivers behind it, usage-near-cap upgrade candidates and the deferred-versus-recognised balance. Every figure is computed offline and works with AI switched off; an optional narration writes the same snapshot up in words. The pack also publishes an MRR dataset into the semantic model, so recurring revenue pivots in Analytics Studio.
What’s included
- Plans across flat, tiered, volume, seat, usage, freemium & hybrid models
- Effective-dated price books, tier ladders, add-ons & coupons
- Lifecycle: trial, activate, change plan, pause, resume, cancel, renew
- Deterministic proration with a preview before the change is applied
- Recurring sweep issues real GST sales invoices through the standard spine
- Dunning ladder at day 0/3/7/14, late fee after grace, suspend on exhaustion
- Usage meters with idempotency-key dedupe and tier-rated summaries
- Straight-line revenue recognition — idempotent Dr Deferred / Cr Revenue
- MRR/ARR, movement bridge, churn risk & expansion candidates
- Contributes an MRR dataset to the BI semantic model
Frequently asked
Do subscription bills sit in a separate ledger?
No. Every recurring bill is issued as a real sales invoice through the standard spine, so GST, numbering, the PDF and the General Ledger behave exactly as they do for any other invoice — and collections run through the normal receipts spine.
Can I trust the proration figures?
The billing engine is pure and deterministic — no clock, integer paise, largest-remainder splits that sum exactly to the total and exclusive period ends — so the same inputs always produce the same schedule. You also see the proration preview before the change is committed.
Is this only for SaaS?
No — it is horizontal. Any recurring-revenue model bills through the same plans and cycles: AMC contracts, memberships, rentals, licensing or retained services.
Is subscription billing in the offline desktop app?
No — it is a cloud marketplace pack. Enable it and a Subscriptions section appears with plans and catalog, subscriptions, recurring billing, usage metering, revenue recognition and revenue insights; it does not run in, or sync to, the offline desktop edition.
What exactly is included in Subscription Billing · Cloud pack?
plans across flat, tiered, volume, seat, usage, freemium & hybrid models, effective-dated price books, tier ladders, add-ons & coupons, lifecycle: trial, activate, change plan, pause, resume, cancel, renew, deterministic proration with a preview before the change is applied, recurring sweep issues real GST sales invoices through the standard spine and dunning ladder at day 0/3/7/14, late fee after grace, suspend on exhaustion, and 4 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is subscription billing · cloud pack handled differently here?
It rests on a catalogue, not a price field, lifecycle with proration you can check first, bills as real invoices, dunning as a ladder, meter the usage, recognise the revenue and MRR you can explain. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
How does Subscription Billing · Cloud pack affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever subscription billing · cloud pack produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.
Does Subscription Billing · Cloud pack cost extra?
No. Subscription Billing · Cloud pack is part of the accounting core rather than a paid add-on, so lifecycle with proration you can check first is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try Subscription Billing · Cloud pack before committing?
Yes — 14 days, no card. Test subscription billing · cloud pack against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.
Is anything in Subscription Billing · Cloud pack generated by AI?
None of the figures. Everything a catalogue, not a price field produces is computed by tested engines and would be identical with the model switched off — what AI contributes is the sentence around a number and the routing that brings the right one to your attention. Nothing it writes posts to your books without your approval.