Arlo
Technology · United States · Enterprise
Successful expansion into personal security segment with significantly reduced churn
- Churn Reduction To
- 2.6%
- Churn Reduction To
- Churn Reduction From
- Double digits
- Churn Reduction From
Updated July 2026 · By the ERP Research Editorial Team · Independent and vendor-neutral — no vendor pays for placement or ranking.
Subscription and billing platforms for SAP rate and invoice recurring, usage-based and hybrid pricing models, passing invoices and receivables into SAP. SAP offers BRIM (Billing and Revenue Innovation Management) as its native suite for high-volume consumption billing; independents compete on configuration speed and on fitting businesses that do not need BRIM's scale.
| Product | Best for | Pricing | Deployment |
|---|---|---|---|
| Enterprise / Mid-market | Custom quote | Cloud/Hybrid | |
| Mid-market / Enterprise | Quote-based / custom | Cloud | |
| Mid-market / Enterprise | Subscription / quote-based | Cloud | |
| Mid-market / Enterprise | Quote-based / custom | Cloud |
SAP BRIM is a powerful suite assembled from several components — subscription order management, convergent charging, convergent invoicing and contract accounting — designed for telecom-scale consumption billing. Where you genuinely need that scale, it is a strong and deeply integrated answer.
The mismatch to watch for is BRIM being proposed to businesses nowhere near that scale. A software company billing a few thousand subscriptions monthly does not need convergent charging, and implementing BRIM for it is a multi-year commitment to solve a problem an independent platform handles in months. The vendors below occupy exactly that middle ground.
SAP BRIM combines subscription order management, convergent charging for real-time rating of high-volume usage, convergent invoicing that consolidates charges from multiple sources, and contract accounts receivable and payable for very large customer bases — integrated with S/4HANA finance and SAP RAR for revenue recognition. It is engineered for telecoms, utilities and large-scale consumption businesses. For subscription models of ordinary complexity and volume, BRIM's capability is disproportionate to the requirement, and its implementation profile reflects the scale it was built for rather than the problem you have.
SAP
Oracle
NetSuiteSalesforce+1
SAP
Oracle
NetSuite
Workday+5
SAPSalesforce
NetSuite
SAP
WorkdaySalesforce+4Customer stories from the vendors compared above, summarised from their published case studies.
Technology · United States · Enterprise
Successful expansion into personal security segment with significantly reduced churn
Telecommunications · Singapore · Enterprise
Simplified operations, provided cloud-native infrastructure for digital transformation
Media & Entertainment · Denmark · Mid-Market
Successfully consolidated operations with API capabilities for partner integration
Technology · Canada · Enterprise
Long-term partnership providing consistent billing and business value
Telecommunications · Germany · Mid-Market
Successfully launched unified BSS in 90 days, improved agility and automation
Technology · United Kingdom · Enterprise
Unified billing across multiple acquisitions with consistent processes
Summarised from each vendor's published customer stories. Figures are the vendor's own claims, not independently verified by ERP Research. See all 11 Aria Systems case studies →
A vendor-neutral shortlisting guide to billing & subscriptions: how the 4 systems we track compare on capability, what to check before you sign, and the questions that separate a good fit from an expensive one.
Billing & Subscriptions Buyer's Guide
4 systems compared · 2026
ERP Research
Vendors in this category publish too little pricing detail for us to quote a range. These are the questions that decide what you end up paying.
4 of the 4 vendors we track in this category publish no list price at all.
List the specific billing & subscriptions outcomes you need — volumes, workflows, countries, systems in the loop — and rank them. Vendor demos are optimised to reframe your requirements around their strengths; a written list keeps the evaluation yours.
Every vendor here “integrates with SAP” — the differences are in depth. Ask each to demo the integration against a realistic SAP configuration: your entity structure, your fields, your transaction volumes, and what happens when a sync fails.
Look for SAP-certified integration (SAP Store listing) and a current listing on SAP Store (store.sap.com). Certification doesn't guarantee fit, but it confirms the vendor keeps pace with SAP releases — uncertified integrations are where upgrade breakage concentrates.
Ask for two reference customers on SAP at your size and in your industry, and ask them what broke in the first year. Implementation quality varies more than product quality in the billing & subscriptions category.
Compare subscription plus implementation plus internal effort — not headline price. SAP subscription billing software pricing models differ (per user, per volume, per entity), so normalise every quote to your actual usage before comparing.
When usage volumes genuinely require real-time convergent charging — telecoms, utilities, large-scale IoT or consumption platforms rating millions of events. In that world BRIM's architecture is the point and alternatives struggle. If you bill thousands rather than millions of transactions with recognisable subscription pricing, BRIM is oversized, and a proposal recommending it for that profile is worth a second opinion.
An independent billing platform feeding SAP receivables, in most cases. These deploy in months rather than years and let commercial teams change pricing without engineering involvement — which is usually the real requirement, since the cost of billing is mostly the cost of changing it. Straightforward recurring models with stable pricing can often stay in S/4HANA's own contract and billing functionality entirely.
Billing determines what the customer is invoiced and when; revenue recognition determines when revenue may be recorded, and IFRS 15 makes these diverge routinely. SAP RAR can consume billing data from BRIM or from a third-party platform. Design that handoff deliberately — passing only invoiced amounts loses the contract and performance-obligation context the standard requires, and reconstructing it later is expensive.
This comparison currently covers 4 options that work with SAP, including Aria Systems, BillingPlatform, SAP BRIM (Subscription Billing). Each links to a detailed profile with features, integrations, pricing and alternatives, and the directory is updated as the market changes.
Most vendors here quote rather than publish. Tell us your SAP version, seat count and must-haves and we'll come back with an independent view of what it should cost — and which options are worth quoting against each other.