Subscription (Subscription Model)
A subscription (subscription model) is a business model in which customers pay recurringly for a product or service – usually monthly or annually – and receive ongoing access or delivery in return, instead of buying once.
A subscription (subscription model) is a business model in which a customer does not buy once but pays at recurring intervals – typically monthly or annually – and in return receives continuous access to a product, a piece of software, or a regular delivery. Instead of acquiring ownership of a product, the customer pays for ongoing use or supply. Well-known examples range from streaming services and software-as-a-service to maintenance contracts and physical subscription boxes in e-commerce.
At the core of the model are predictable, recurring revenues instead of one-off transactions. For the provider, the focus shifts from the individual sale to long-term customer retention, because revenue is generated over the entire contract term. Metrics such as MRR (Monthly Recurring Revenue), ARR (Annual Recurring Revenue), churn rate, and customer lifetime value replace the classic view of turnover. This places particular demands on billing, revenue recognition, and the ERP system.
At a glance
- Recurring payment for ongoing access instead of a one-off purchase
- Predictable, recurring revenue (MRR/ARR) instead of a single transaction
- Key metrics: churn rate, customer lifetime value, renewal rate
- Automated recurring billing and period-accurate revenue recognition required
- Common in SaaS, streaming, maintenance, and e-commerce subscription boxes
What characterises a subscription (subscription model)?
The defining feature of a subscription is the recurring payment over time in exchange for an ongoing service. The customer enters into a continuing obligation that automatically renews in fixed cycles until one party cancels. This makes the subscription fundamentally different from a one-off purchase: it is not the closing of the sale but the continuous delivery of value and renewal that determines economic success.
Typical components are a billing cycle (monthly, quarterly, annually), a rate or plan with a defined scope of service, a minimum term or renewal logic, and a stored payment method for automatic collection. Many providers tier their offerings into several rate levels and add usage-based components. A subscription does not end through fulfilment but continues as long as the customer stays – cancellation and renewal are therefore central processes.
Variants: flat rate, tiered, and usage-based
Subscription models differ in their pricing logic. With a flat rate, the customer pays a fixed amount for unlimited or lump-sum usage. Tiered pricing models offer several packages with increasing functionality. With usage-based (or pay-per-use) billing, the amount depends on actual consumption, such as API calls made, active users, or shipments sent. In practice, many providers combine a base fee with variable components (hybrid pricing).
How does billing work in the subscription model?
Unlike a one-off sale, invoicing in a subscription must run automatically and recurringly. A recurring billing process automatically generates the invoice on the respective cycle date, triggers payment collection via the stored payment method, and posts the incoming payment. Failed payments – for example due to expired cards – are followed up through a retry and dunning process. Contract changes such as upgrades, downgrades, or mid-term cancellations require proportional billing (proration).
From an accounting perspective, period-accurate revenue recognition is decisive. If a customer pays an annual subscription in advance, the revenue must not be booked in full immediately but has to be spread across the twelve months of service delivery. The portion not yet earned is reported as deferred income (a prepaid revenue accrual). This deferral is required under the German Commercial Code (HGB) and IFRS 15 and, without system-supported automation, is hard to handle error-free across many contracts.
Why the subscription (subscription model) matters
The central advantage lies in predictability. Recurring revenues make turnover and cash flow foreseeable, which makes forecasting, investment decisions, and company valuation easier. Existing customers generate ongoing revenue without every cycle having to be sold anew – this lowers relative sales costs and increases customer lifetime value. For the customer, the barrier to entry falls because high one-off investments are avoided and the service scales to demand.
These benefits come with challenges. The churn rate largely determines success: even a few percent of monthly cancellations noticeably erode recurring revenue. The model therefore demands lasting value delivery, active customer management, and a clear understanding of metrics such as MRR, ARR, churn, and contribution margin per customer. As the contract base grows, the complexity of billing and accounting also increases sharply.
The subscription (subscription model) in the ERP system
An ERP system ideally maps the subscription lifecycle end to end – from signing the contract through recurring billing to financial accounting. The contract, rate, term, billing cycle, and payment method are stored in the customer master data. A contract or subscription module automatically generates the periodic invoices from this, manages renewals, cancellations, and proportional calculations, and hands the documents over to accounts receivable and dunning.
Particularly important is automatic revenue recognition: the system spreads amounts invoiced in advance period-accurately over the term and reports open items correctly. For DACH companies, audit-proof, GoBD-compliant posting and the handover to the tax advisor via DATEV or BMD are added. Not every ERP handles true subscription management out of the box; sometimes specialised billing systems are connected via interfaces.
Subscription features in the standard of many ERP systems
Cloud ERP systems such as weclapp, xentral, or Oracle NetSuite offer functions for recurring invoices, contract management, and in some cases revenue recognition as standard. SAP S/4HANA Cloud and Microsoft Dynamics 365 Business Central cover subscription-based billing via their own modules or add-ons. Whether the ERP is sufficient or a specialised billing tool is needed depends on volume, pricing logic (such as usage-based), and international reach.
Distinction: subscription vs. purchase, licence, and SaaS
A subscription differs from a classic purchase through the recurring payment and the absence of ownership: the customer acquires use, not possession. Compared with leasing, which also targets use, a subscription is usually more flexibly cancellable and more oriented toward software or services than toward individual assets.
Subscription, licensing model, and SaaS are frequently confused. A subscription is initially only the payment and provisioning form. A licensing model governs the usage rights to software and can be designed as a perpetual licence or as a subscription. SaaS (software-as-a-service) is a cloud-based provisioning type that is almost always billed as a subscription – but not every subscription is SaaS, since physical products, media, or maintenance contracts are also sold on subscription. Subscription therefore describes the revenue and contract principle, while SaaS and the licensing model describe provisioning and usage rights.
Example
Example: e-commerce retailer with a coffee subscription
An online retailer of speciality coffee offers a subscription alongside classic one-off sales: customers receive a freshly roasted pack of their choice every four weeks, collected by SEPA direct debit. In the ERP system, the rate, delivery interval, and payment method are stored for each subscriber. On the due date, the system automatically generates the invoice and delivery order, collects the amount, and triggers picking and shipping.
If a customer changes the quantity or pauses for two cycles, the system adjusts the next invoice proportionally. If someone pays an annual subscription in advance, accounting spreads the revenue period-accurately over twelve months instead of recognising it immediately. Through a dashboard, the retailer tracks MRR and churn rate and thus spots early whether cancellations are rising and countermeasures are needed.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Subscription (Subscription Model) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.