Subscriptions and Usage Billing

CRM → Subscriptions bills customers on a repeating cycle without anyone raising invoices by hand. Invoicing needs the Accounting module.

Setting one up

Choose the customer, a start date and a billing cycle: monthly, quarterly or yearly. The billing day stays the same each cycle; when a month is shorter (for example 31 January to February) the last day of the month is used and the next bill goes back to the usual day.

Kinds of line

• Flat fee — the same amount every cycle.
• Per unit — a price times a quantity, for example £12 per user.
• Usage — billed for what was used in the period, with optional tiers. For example: the first 1,000 messages at £0, the next 9,000 at 2p, everything above at 1p.

Changing a subscription mid-cycle

When you change a quantity or price part-way through a period, Plenix works out the difference for the days left and adds it to (or credits it on) the next invoice.

Pausing, resuming and cancelling

Pause a subscription to stop billing, and resume it later. Cancel at the end of the current term (the customer keeps the service until then) or now. Preview next invoice shows exactly what will be billed before it goes out, and the history lists every billing run and change.

Sending in usage

Enter usage by hand on the subscription, or send it from your own systems through the Plenix API with a key that has the usage:write permission. Each usage record takes an idempotency key: sending the same key twice records it once, so retries never bill a customer twice.

Where the revenue shows

Subscription revenue counts towards the MRR dashboard alongside services, and towards each customer's figures on their Customer 360 tab.