Subscriptions Anything that repeats, and the recurring revenue figure that comes out of it.

Subscriptions cover anything billed on a repeating basis, in both directions: what customers pay you regularly, and what you pay regularly.

What it holds

Each subscription carries what it is, what it costs, how often it is billed, and which category it belongs to.

Billing cycles are monthly, quarterly or annual.

Categories cover the usual shape of recurring cost: software, infrastructure, marketing, tools, security, and a catch-all.

Why the cost side matters

Most organisations know what they charge on subscription and have a much vaguer idea what they spend.

Recurring cost is the expense that grows without anybody deciding to grow it. A tool added for one project, a seat count that went up during a hiring push, an annual renewal nobody re-evaluated. None of those are decisions, and all of them are permanent until somebody looks.

Having them in one list with a total is most of the value. The rest is looking at it once a quarter.

Owning the list

Recurring cost is nobody's job by default, which is exactly why it grows.

The arrangement that works is one named owner for the whole list rather than per-category owners. Distributed ownership means each individual subscription looks reasonable to whoever owns it, and nobody ever sees the total.

Fifteen minutes a quarter, one person, one list.

Normalising the cycle

An annual subscription and a monthly one are not comparable until they are put on the same basis.

The surface handles that, so a mixed list of monthly, quarterly and annual commitments produces a monthly figure you can reason about. Comparing an annual invoice against a monthly one directly is the most common arithmetic error in this area.

Categories

Six, and they cover the shape of recurring cost in most organisations: software, infrastructure, marketing, tools, security, and a catch-all.

Use the catch-all sparingly. A list where a third of the spend sits in "other" cannot answer the question anybody actually asks, which is where the recurring money goes.

Recurring revenue

On the income side, subscriptions roll into a recurring revenue figure.

Two cautions worth carrying.

It is a snapshot, not a period total. Recurring revenue is what is currently contracted per period. Adding January's to February's is meaningless, and the distinction is the same flow-versus-snapshot one that runs through Analytics.

It is a commitment, not cash. A subscription that is contracted and unpaid still counts toward the figure and does not count toward your bank balance. Receivables is where the difference shows up.

What belongs here and what does not

Here: anything with a recurring commitment, whether or not it is invoiced automatically. Software, hosting, retainers, memberships, insurance.

Not here: one-off purchases, however large. A single annual payment for something you may not renew is an expense with a date, not a subscription.

The test is whether it continues unless somebody stops it. That property is what makes recurring cost dangerous and what this surface exists to make visible.

Seats

The most common way a software subscription grows is seat count, and it grows in one direction.

Seats are added during a hiring push and almost never removed when somebody leaves, because removing them is nobody's task and the invoice looks normal. Over two years that is a meaningful and entirely invisible cost.

Worth one check a year against actual headcount, per tool. It is the single highest-return item in this whole review.

Renewals

The value of tracking these is mostly in seeing what is coming.

An annual renewal noticed a month out is a negotiation. The same renewal noticed after it charges is an invoice. That difference is the whole argument for maintaining the list.

For anything material, put the renewal date somewhere it will interrupt you rather than somewhere you would have to go and look.

Reading the total honestly

The total is a per-period figure, and mixed cycles have to be normalised before it means anything.

Two mistakes worth avoiding. Do not compare an annual commitment against a monthly one without putting them on the same basis. And do not treat the monthly figure as cash out this month, since annual subscriptions charge once and sit at zero for eleven months.

The figure is a run rate. Cash timing is a different question and belongs in the cash view.

Currency

A subscription is held in the currency it is billed in, with the base-currency equivalent alongside.

That matters for recurring cost in particular, since most software is billed in dollars regardless of where the business operates. A rate movement changes what your recurring commitment actually costs you, and only the base figure shows it.

Keeping it accurate

Add it when you sign it, not at the quarterly review. A list assembled retrospectively is always missing the ones somebody forgot.

Record cancellations promptly. A cancelled subscription still on the list overstates your recurring cost, which sounds harmless and quietly distorts every decision built on the number.

Review quarterly. Fifteen minutes, and the question is not "do we use this" but "would we buy it again today". Those get very different answers.

Both directions in one place

Subscriptions cover what you receive and what you pay, and keeping them together is deliberate.

The two questions are the same question: what is contracted to repeat. Splitting them into a revenue list and a cost list means two habits, and the cost one is always the one that lapses.

Reading them together also gives you the number that actually matters for a subscription business, which is what recurs in against what recurs out.

What it does not do

It does not raise the invoices from this screen. A customer subscription here is a record of the arrangement, and invoicing is a separate step.

Recurring invoice templates do exist in the platform as a capability, but there is no screen for them yet, so in practice a monthly retainer means raising a monthly invoice today.

It does not cancel anything. Recording a cancellation here does not tell the supplier, which is worth stating because the list can otherwise give a false sense that something has been dealt with.

It does not detect what you are paying for. Anything not entered is invisible, and the subscriptions organisations most want to find are exactly the ones nobody wrote down.