Choose WHMCS when its hosting and registrar ecosystem matches the services you sell. Evaluate BILLmanager when your purchase includes hosting or infrastructure sales and service delivery. Before comparing headline prices, model what each licence measures: customer count and turnover can produce very different costs for the same business.
This guide is for small hosts and agencies deciding which system should bill their next customer. If you need only invoices and recurring collection, identify that narrower requirement before buying another infrastructure platform.
Start with the service that must follow payment
WHMCS combines recurring billing, payment collection and reminders with hosting-oriented integrations. Its current pricing page distinguishes self-hosted and managed offerings. Compare the actual plan you intend to buy; managing your own server is not the only WHMCS route.
ISPsystem describes BILLmanager as a platform for automating hosting sales, service delivery and private or public clouds. That is a larger responsibility than issuing an invoice. Ask both vendors to demonstrate your actual service types, control panels and registrar routes rather than treating a generic integration count as proof.
| Your buying requirement | What to establish before choosing |
|---|---|
| Fixed monthly service | Invoice timing, payment method and overdue treatment |
| Resource-dependent charge | Where usage comes from, who validates it and how it reaches the bill |
| Hosting activation or suspension | Supported module, service state and owner of failed actions |
| Domain renewal | Registrar compatibility, renewal deadline and who funds the renewal |
| Hosted invoicing only | Whether a smaller collection platform can meet the requirement |
A system can generate a correct invoice while the service action fails. Conversely, a running server is not evidence that the customer's renewal was collected. Buy the billing and delivery responsibilities together only when that integration is useful to your business.
A 60-client worksheet: count and turnover are different
The following is an original hypothetical planning model, not a vendor quote or a measured customer result. Assume sixty active customers, each with one recurring service, billed in euros. Exclude tax and provider fees to keep the licensing question visible.
| Scenario | Active clients | Average monthly bill | Modelled monthly sales |
|---|---|---|---|
| Lower-value service mix | 60 | €50 | €3,000 |
| Higher-value service mix | 60 | €150 | €9,000 |
The client count is unchanged. The sales value triples. Under a client-count licence, both scenarios may remain in the same tier, subject to the vendor's definition of an active client and other plan conditions. Under turnover-based pricing, the licence cost may change even without another customer.
ISPsystem's Hosting&Cloud tariff FAQ describes a €50 minimum monthly licence and an additional extension when period turnover exceeds €5,000. Confirm the applicable current edition and quote. In this worksheet, €3,000 is below that documented threshold; €9,000 is above it. The minimum alone is therefore insufficient to price the second scenario. No extension amount is assumed here.
For each vendor quote, record licence + required modules + hosting/operation + support + payment processing. Add one-off migration work separately. Do not compare a dollar licence and a euro licence without recording exchange rate and tax treatment, or assume that a lower licence price means a lower total operating cost.
Add a tariff test before accepting the quote
For the sixty-client model, suppose forty-five services have a fixed price and fifteen need a resource-dependent charge. These counts are assumptions, not vendor capabilities. Supply one sample bill for each tariff type and ask the candidate vendor to show the source of every billable input.
For example, an assumed base service of €50 plus ten extra units at €2 produces €70 before tax. The arithmetic is easy; the purchasing question is whether the selected system receives those ten units reliably, corrects mistakes and prevents duplicate billing. PayRequest is not presented here as a replacement for an infrastructure metering engine.
If you cannot demonstrate the required tariff and service action, keep that system out of the production handover regardless of its price. This acceptance exercise is more useful than awarding a platform an unexplained score.
Separate migration scope from product fit
A new billing platform does not automatically inherit gateway permissions, stored payment authorizations or domain-renewal responsibility. Ask for a supported migration scope, an archive strategy for old invoices and an agreed date for the next billable event. Imported payment history is not permission to collect the next payment.
Use the WHMCS migration checklist for the wider handover. The existing WHMCS alternatives shortlist remains the starting point if you have not narrowed the purchase to these two platforms.
When PayRequest is a suitable smaller purchase
PayRequest's WHMCS alternative fits a business seeking hosted customer billing, invoices, a portal and supported recurring collection. It is proprietary hosted software. It does not replace an entire hosting-provisioning, infrastructure-metering or domain-registration suite.
Choose it only when those remaining responsibilities have a verified owner. Start with a fixed-price service cohort whose collection method is supported, and confirm the supported transfer scope before moving existing customers.
Business is €20/month, with 0% standard platform payment fees while active. Provider fees and commission-payment exceptions remain separate. New accounts complete setup and the paid product checkout before Business activates; selecting Business alone does not grant access.
If hosted billing is the work you want to buy, create a Business account and prepare that first fixed-price cohort. If integrated infrastructure automation is essential, choose the platform that can demonstrate it for your services.
*Method: primary sources checked 1 November 2026. Original hypothetical licence and tariff worksheets; no installed-platform comparison or migration test claimed. AI assisted the text and illustration, followed by editorial review.*
