ERP for subscription business — software for SaaS and recurring revenue
Subscription business has become the dominant revenue model for software, but it has also spread into media, mobility, B2B services and even consumer goods (rent-a-bike, razor refills, coffee capsules). Subscription business breaks the assumptions of a classical ERP in fundamental ways: revenue is no longer a transactional event, it is a continuous stream that has to be recognised over the service period; the customer relationship is no longer a sequence of unrelated orders, it is one long contract with upgrades, downgrades, pauses and cancellations; and the most important business metrics (MRR, ARR, net revenue retention, churn) do not exist as native fields in a transactional ERP. Subscription-business ERP closes the gap.
MRR, ARR and recurring-revenue metrics
Monthly Recurring Revenue (MRR) and Annual Recurring Revenue (ARR) are the central operating metrics of a subscription business. They have to be calculable any day of the month, broken down by new MRR, expansion MRR, contraction MRR and churned MRR. Net Revenue Retention (NRR) follows from those four components and is the single best leading indicator of long-term enterprise value. A subscription ERP must produce these natively, with drill-down to the underlying contracts and invoices, and with an audit-ready link to the general ledger. Plugging MRR together from invoices in Excel is the standard early-stage hack — and the standard reason that reported numbers diverge from audited numbers later on.
Deferred revenue and IFRS 15 / HGB
When a customer pays annually in advance for a monthly service, the cash arrives in month one but the revenue is earned over twelve months. Deferred revenue accounting under IFRS 15 (or HGB §252 for German GAAP filers) requires the ERP to recognise revenue rateably and keep the deferred-revenue balance on the balance sheet until earned. Contract modifications mid-term (upgrades, downgrades, plan changes) have to be re-allocated correctly. For DACH companies preparing for audit, automated, defensible deferred-revenue accounting is one of the strongest reasons to put a specialist subscription engine in front of a general-purpose ERP.
Lifecycle workflows: upgrade, downgrade, pause, churn
The subscription lifecycle is non-linear. A customer starts on the Pro plan, upgrades to Enterprise mid-quarter, adds three more seats, downgrades to Pro after the renewal, pauses for the summer holiday, and finally churns. The ERP / billing engine must price each of these events correctly — prorated, with credits, with carry-over — and present the customer with one clear invoice each month. Dunning workflows for failed credit-card payments need to be tuned for the subscription context: a hard cancellation after one failed charge wastes good customers; an indefinite grace period leaks revenue. Three retries over ten days, with an in-product notification, is a common DACH default.
Churn analytics and customer health
Churn is the dominant value lever in mature subscription businesses. Reducing churn by 1 percentage point typically beats raising new-business growth by 5 percentage points in long-term enterprise value. The ERP / customer-data layer must integrate product-usage data (logins, feature adoption, support tickets) with billing data to compute a customer-health score, flag at-risk accounts and trigger customer-success interventions. This is the area where pure-play subscription-billing tools (Chargebee, Recurly, Zuora, Stripe Billing) outperform general-purpose ERPs — and where the integration with the back-office ERP must be designed carefully.
Selection: ERP module or specialist tool?
- Subscription contract management with versioning
- MRR / ARR / NRR reporting with audit trail
- Deferred-revenue accounting under IFRS 15 / HGB
- Prorated upgrade / downgrade billing
- Tunable dunning workflow with payment retries
- Customer-health scoring with product-usage data
- Multi-currency and multi-entity for global expansion
- OSS / IOSS VAT handling for EU B2C SaaS
- Revenue cohort analysis and waterfall reporting
Specialist subscription engines in DACH-relevant use include Chargebee, Recurly, Zuora, Stripe Billing and SAP Subscription Billing — usually integrated with a primary ERP for general ledger and tax compliance. ERP-native subscription modules include NetSuite SuiteBilling, Microsoft Dynamics 365 BC with subscription add-ons (e.g. Subscription Management by Suite Engine) and weclapp for SMB SaaS. For software companies above ~5 MEUR ARR, a specialist-billing-engine plus general-ERP topology tends to scale better than a single-ERP solution.
Related Topics
Frequently Asked Questions
At what scale does a dedicated subscription engine pay back?
Below ~500 active subscriptions with simple plans, a competent ERP module (NetSuite SuiteBilling, Microsoft Dynamics 365 BC subscription add-on, weclapp) usually suffices. Above ~1.000 active subscriptions, with multiple plans and mid-term changes, the operational burden of running this inside a general-purpose ERP grows faster than the cost of a Chargebee / Recurly / Zuora licence.
How do EU OSS and IOSS affect a DACH SaaS subscription ERP?
For B2C SaaS sold cross-border in the EU, the One-Stop-Shop (OSS) VAT scheme applies: the seller charges VAT at the customer's country rate and reports through a single OSS return. Import One-Stop-Shop (IOSS) applies to low-value goods imports. A subscription ERP needs to determine VAT rate per customer country, store the customer's VAT-ID, validate B2B exemptions (reverse charge), and produce OSS-ready reports. Most specialist subscription engines and competent ERPs handle this; spreadsheet workarounds become unworkable above modest cross-border volumes.
Can a subscription ERP also support a hybrid one-off-plus-subscription model?
Yes — and this is increasingly the norm. Many DACH software vendors sell a one-off implementation fee plus a recurring subscription. The ERP must support mixed invoice lines (one-off product, recurring service) on the same customer order, with the correct revenue recognition treatment for each. This is straightforward in specialist engines and increasingly so in ERP-native subscription modules; older general-purpose ERPs without a subscription module force ugly workarounds.