WHMCS Reports Are Too Basic. Here Is What You Actually Need
WHMCS built-in reports show revenue and invoices but miss MRR, churn, profit margins, and client profitability. Here is what you need to track instead.
MX Modules Team
(Updated )

Go to WHMCS > Reports. You will find about a dozen built-in reports: Income by Date, Invoices by Status, Orders by Product, Income Forecast, Tickets Overview, and a few more.
Now try to answer these questions:
- What is your MRR right now?
- Which clients are losing you money?
- What is your churn rate this month compared to last?
- Which product has the best profit margin?
- How much can you afford to spend acquiring a new client?
You can't. Not from WHMCS reports. Not without exporting data to spreadsheets and spending hours on manual calculations.
This is not a bug. WHMCS reports were designed for bookkeeping, not business intelligence. The gap between what WHMCS shows you and what you need to run your business is where most hosting providers lose money.
What WHMCS Reports Actually Show
Here is the complete list of built-in WHMCS reports and what each one tells you:
| Report | What It Shows | What It Misses |
|---|---|---|
| Income by Date | Total revenue in a date range | Profit, costs, margins |
| Income Forecast | Projected revenue from upcoming invoices | Whether that revenue is profitable |
| Orders by Product | How many orders per product | Revenue or margin per product |
| Invoices by Status | Paid, unpaid, overdue counts | Impact on cash flow or MRR |
| Tickets Overview | Ticket count and response times | Cost of support per client |
| Client Overview | Active client count | Client value or profitability |
| Credit Balance | Total client credits | How credits affect cash flow |
Every one of these reports answers "what happened" but not "what should I do about it." They are accounting reports, not management reports.
The Five Reports WHMCS Should Have
1. Monthly Recurring Revenue (MRR) Report
What it is: The total predictable monthly revenue from all active subscriptions, normalized to monthly values.
Why WHMCS can't show it: WHMCS tracks invoices, not subscriptions. A $240/year client shows as a $240 payment in one month and $0 for the next eleven. MRR would normalize that to $20 every month.
Why it matters: MRR is how serious operators measure hosting businesses. It smooths billing cycle noise and shows the real trend. Without it, a month with several annual renewals looks like a growth spike. A month without them looks like a decline. Neither is true.
We covered MRR calculation in detail: How to Track MRR in WHMCS (Step by Step).
2. Client Profitability Report
What it is: Revenue minus costs for each individual client. Includes server costs, license costs, payment processing fees, and support time.
Why WHMCS can't show it: WHMCS has a "Product Cost" field, but it only captures direct product cost. It ignores payment processing fees (2.9% + $0.30 per transaction), support labor, allocated infrastructure overhead, and per-service resource usage.
Why it matters: Not all clients are equal. Client A pays $200/month and never opens a ticket. Client B pays $50/month and opens four tickets a week. One is your best client. The other is your worst. WHMCS treats them the same.
Without per-client profitability data, you can't identify which clients deserve premium attention and which are silently draining your margins. The 80/20 rule applies: about 20% of your clients generate 80% of your profit. You need to know which 20%.
See the full calculation method: Calculate Per-Client Profit in WHMCS.
3. Churn Rate Report
What it is: The percentage of clients or MRR lost to cancellations in a given period.
Why WHMCS can't show it: WHMCS marks cancelled services as "Terminated" and moves on. It doesn't aggregate cancellations into a rate, track the trend over time, or calculate MRR impact.
Why it matters: A 5% monthly churn rate means you lose half your clients every year. Even if total revenue looks stable, you might be running on a treadmill, spending heavily on acquisition just to replace the clients you lose.
Reducing churn by 1% often has more business impact than acquiring ten new clients. But you can't reduce what you can't measure.
More on churn: How to Reduce Churn with Data Analytics.
4. Product Margin Report
What it is: Revenue per product line minus the cost of delivering that product. Shows which products are profitable and which are subsidized by other products.
Why WHMCS can't show it: WHMCS reports revenue by product but not cost by product. You can see that "Business Hosting" generated $5,000 last month, but not whether it cost $2,000 or $4,500 to deliver.
Why it matters: If your cheapest plan has a 5% margin after support costs and your premium plan has a 55% margin, where should you focus your marketing? Without margin data, you might be promoting your least profitable products.
5. Customer Lifetime Value (LTV) Report
What it is: The total revenue a client generates over their entire relationship with your business. Calculated as average revenue per client divided by churn rate.
Why WHMCS can't show it: LTV depends on churn rate. Since WHMCS doesn't track churn, it can't calculate LTV.
Why it matters: LTV determines how much you can afford to spend acquiring a new client. If your average LTV is $1,200, spending $100 on marketing per acquisition is a great deal. If your LTV is $150, that same $100 is a disaster.
Full LTV calculation: Calculate Customer LTV in WHMCS.
Why Manual Reporting Fails
The common workaround is exporting WHMCS data to Excel or Google Sheets. It works. Once. Maybe twice.
Here is what manual reporting actually looks like:
- Export invoices from WHMCS (15 minutes)
- Export client list with services (10 minutes)
- Enter your cost data manually (20 minutes)
- Build formulas for MRR normalization (45 minutes the first time)
- Calculate per-client profitability (30 minutes)
- Cross-reference cancellations for churn (20 minutes)
- Format and review (20 minutes)
Total: 2-3 hours for one monthly report. And the result is already outdated by the time you finish.
Most providers do this once, maybe twice, then stop. The effort is not sustainable for ongoing tracking.
We covered this in depth: Why Spreadsheets Fail for WHMCS Cost Tracking.
What Good Reporting Looks Like
Good hosting business reporting answers questions in seconds, not hours:
- "How is the business doing?" MRR trend, net growth, churn rate. At a glance.
- "Which clients need attention?" Sorted by profitability. High-revenue but high-cost clients flagged.
- "Where should I invest?" Product margins show which products to promote. LTV shows how much to spend on acquisition.
- "Is growth real?" MRR growth minus churn shows net expansion. Revenue growth without this context is misleading.
This is the difference between bookkeeping reports (what WHMCS provides) and business intelligence (what you need to make decisions).
Getting These Reports in WHMCS
You have three options:
Option 1: Build Custom Reports
Use WHMCS hooks, the API, or direct database queries to build custom reports. This gives you exactly what you want.
The catch: You need a developer. Custom reports need maintenance. WHMCS updates can break your queries. Most providers underestimate the ongoing cost.
Option 2: External BI Tools
Export WHMCS data to tools like Metabase, Grafana, or Google Data Studio. Connect your database and build dashboards.
The catch: Complex setup. Requires database access configuration, SQL knowledge, and ongoing data pipeline maintenance. Overkill for most hosting businesses.
Option 3: MX Metrics
MX Metrics adds the missing reports directly inside WHMCS. Install the module, enter your cost data, and the dashboard populates immediately:
| Report | What MX Metrics Shows |
|---|---|
| MRR Dashboard | Current MRR, trend, growth rate |
| Client Profitability | Revenue vs costs per client, margin ranking |
| Cost Tracking | Server costs, licenses, overhead per service |
| Product Margins | Revenue and margin per product line |
No spreadsheets. No SQL. No external tools. Data updates in real-time as WHMCS processes invoices, activations, and cancellations.
Setup takes about five minutes. The reports are available immediately.
Frequently Asked Questions
Can WHMCS custom reports do everything I need?
WHMCS allows developers to create custom report modules. However, custom reports are limited to what WHMCS stores natively. Since WHMCS doesn't track costs, support time, or normalized MRR, custom reports alone cannot calculate profitability or churn. You need additional data sources.
Why doesn't WHMCS add these reports natively?
WHMCS is primarily a billing and automation platform. Business intelligence is a different product category. Adding full analytics would require WHMCS to track cost data, support labor, and client lifecycle events that are currently outside its scope. It is more likely that WHMCS will continue to focus on billing and leave analytics to third-party modules.
How much time does manual reporting actually take?
Based on hosting provider feedback, the first monthly report takes 4-8 hours to build (creating the spreadsheet, setting up formulas, entering cost data). Subsequent months take 2-3 hours each (updating data, adjusting formulas). The effort compounds if you want weekly reports or real-time dashboards.
What is the minimum data I need to start tracking these metrics?
At minimum, you need your product costs (what each hosting plan costs you to deliver) and your monthly fixed expenses (servers, licenses, tools). With just these two inputs, you can calculate basic profit margins. Over time, add support cost tracking and per-client cost overrides for more accurate numbers.
Do other billing platforms have better reporting?
Blesta and HostBill include more reporting options than WHMCS but still lack full business intelligence features like MRR normalization, churn tracking, and per-client profitability. The gap exists across the industry, not just in WHMCS.
Related
- WHMCS Revenue Analytics: The Complete Guide - Comprehensive analytics framework for hosting providers
- Best WHMCS Analytics Modules in 2026 - Compare tools that fill the reporting gap
- How to Set Up Revenue Dashboards in WHMCS - Build the dashboards WHMCS should have
- Why WHMCS Does Not Show Your Real Profit - The fundamental problem with WHMCS reporting
- MX Metrics vs MetricsCube: WHMCS Analytics Compared - Side-by-side comparison of WHMCS analytics options
- How to Track MRR in WHMCS (Step by Step) - MRR calculation guide
- Calculate Per-Client Profit in WHMCS - Per-client profitability analysis
- 7 KPIs for Hosting Providers (With Formulas) - Complete metrics framework
- Why Spreadsheets Fail for WHMCS Cost Tracking - Why manual reporting doesn't scale
- How to Track Server Costs per Client in WHMCS - Cost allocation methods
MX Metrics
Revenue Analytics for WHMCS
Track MRR, ARR, and real profit per client directly in your WHMCS dashboard. Starts with a 15-day free trial.
Documentation
Did you find this helpful?
Join other WHMCS professionals and get our latest guides and AI tips directly in your inbox.
MX Modules Team
We run a hosting business on WHMCS. These modules are the tools we built to solve our own problems, and now we share them with other providers.


