MSP MRR Reporting: What Counts, What Doesn't, and How It Ties to Your P&L

Key Takeaways

• MRR is a management metric, not a GAAP accounting line — it measures predictable recurring contract value, not cash collected or revenue recognized in a given month.
• Setup fees, hardware sales, and one-time project charges should be excluded from MRR; including them overstates the stability of your revenue base.
• Recurring managed-services contracts typically carry gross margins of 70–90%, while project work runs 40–60% — a difference that disappears if you don't separate the two.
• MRR movement should be reported monthly as a waterfall: new, expansion, contraction, and churn — then reconciled to the GAAP revenue line on your P&L.
• Consistent classification policy is the foundation; without it, MRR becomes noise rather than a decision-ready signal.

MRR (monthly recurring revenue) for an MSP is the total contracted value of recurring managed services, support agreements, and subscription fees that clients pay on a predictable monthly schedule — excluding one-time charges, hardware, and project work. It is a management metric, not a GAAP accounting line. Your P&L recognizes revenue under ASC 606 as services are delivered; MRR measures the contracted run-rate that drives that recognition. The two figures should reconcile, but they are not the same number.

Understanding where they differ — and why — is the foundation of decision-ready financial reporting for any MSP.

What Counts Toward MRR for an MSP?

MRR includes revenue sources that are predictable, contractual, and recurring. As Zomentum describes it, monthly recurring revenue is the total amount clients pay regularly under a managed services agreement — including all subscription fees and service invoices generated from those agreements.

In practice, the following typically qualify:

• Fixed monthly managed-services fees — the core per-seat or per-device contract fee
• Support agreements and helpdesk retainers — ongoing, contracted support at a fixed monthly rate
• Subscription-based offerings — Microsoft 365 licensing passed through at a contracted margin, hosted VoIP, cloud backup subscriptions
• Cybersecurity monitoring — recurring security-as-a-service contracts billed monthly
• Disaster recovery (DR) planning and testing — when billed as an ongoing managed service
• Hardware as a Service (HaaS) — when structured as a recurring monthly fee rather than a one-time sale

Zomentum notes that managed services agreements are usually long-term, include an element of support, and often cover cloud suites like Microsoft 365 — and that MRR can apply to a wide range of ongoing support options MSPs deliver.

The common thread: the client has committed to a recurring payment on a defined schedule, and you have committed to delivering a defined service. That contractual predictability is what makes revenue "recurring" for MRR purposes.

A Hypothetical Illustration

Consider a hypothetical MSP with 50 clients each paying a flat $2,000/month for a managed-services package. That produces MRR of $100,000 — a figure cited as an illustrative example by Next Level Now. Every dollar in that figure is contractual, predictable, and recurring. Nothing else belongs in the MRR calculation.

What Should Be Excluded from MRR?

Excluding non-recurring revenue from MRR is just as important as including the right items. FinancialContent's coverage of MSP accounting is direct: setup fees, hardware sales, consulting projects, and other one-time charges should normally be excluded from MRR and ARR calculations.

Items to keep out of MRR:

The risk of including these is straightforward: one-time income inflates the apparent stability of your revenue base. A month with a large hardware sale or a one-time migration project can make MRR look like it grew when the underlying contracted run-rate was flat or declining. That misleads every downstream decision — hiring, spending, and growth planning — that depends on MRR as a signal.

FinancialContent puts it plainly: clear classification prevents one-time income from inflating recurring revenue and gives you more dependable numbers for evaluating performance.

How Does MRR Reconcile to GAAP Revenue on the P&L?

This is where most MSP financial reporting breaks down. MRR is a forward-looking, contract-based metric. GAAP revenue — what appears on your P&L — is recognized under ASC 606 as performance obligations are satisfied, regardless of when cash is collected.

Hasenbank Accounting Services explains that the essence of revenue recognition lies in recognizing revenue when it is earned and realizable, irrespective of when cash is received. ASC 606 requires that revenue reflect the consideration the company expects to receive in exchange for transferring promised services to customers.

For a standard monthly managed-services contract, MRR and GAAP revenue will often be equal in a given month — the service is delivered over the month, and the full monthly fee is earned. But several situations create a gap:

The reconciliation from MRR to GAAP revenue is not a single adjustment — it is a structured comparison that accounts for timing differences, partial periods, and revenue types that belong on the P&L but not in MRR (and vice versa).

For a deeper look at how prepaid and multi-month contracts create deferred revenue entries, see MSP Deferred Revenue: How to Record and Release Prepaid Contracts.

How Should MRR Movement Be Reported Monthly?

A static MRR number tells you where you are. A monthly MRR waterfall tells you how you got there — and that is the version that drives decisions.

The standard MRR movement report breaks the change from one month to the next into four components:

1. New MRR — recurring revenue from clients that did not exist in the prior month
2. Expansion MRR — additional recurring revenue from existing clients (upgrades, add-on services)
3. Contraction MRR — reduction in recurring revenue from existing clients (downgrades, scope reductions)
4. Churned MRR — recurring revenue lost from clients who cancelled entirely

Net MRR Change = New MRR + Expansion MRR − Contraction MRR − Churned MRR

This waterfall should be produced every month alongside the P&L close. It answers the question your P&L cannot: why did revenue move, and which client behaviors drove it?

Hypothetical MRR Waterfall Example

The following is a hypothetical illustration of how this report might look for a mid-size MSP. All figures are invented for illustrative purposes only and do not represent observed benchmarks.

In this hypothetical, the MSP grew net MRR by $4,000 — but churn and contraction together offset $7,000 of new and expansion gains. That context is invisible on a P&L that simply shows total revenue up month-over-month.

LogMeIn's MRR guidance for MSPs recommends digging into each client's profitability to understand whether any contracts are dragging margins down — a judgment that requires exactly this kind of movement visibility.

Why Separating MRR from Project Revenue Matters for Gross Margin

MRR and project revenue do not just differ in predictability — they differ substantially in profitability. Profitwise Accounting's 2026 analysis quantifies the gap:

• Recurring managed-services contracts typically yield gross margins of 70–90% once processes are efficient.
• Project revenue typically yields gross margins of 40–60%, depending on service complexity and overhead allocation.

Their worked examples illustrate the difference:

• A hypothetical project with $10,000 in revenue and $6,000 in COGS (labor, tools, vendor costs) produces a 40% gross margin.
• A hypothetical MRR contract with $15,000 in monthly recurring revenue and $4,500 in recurring COGS (support labor, monitoring tools, vendor costs) produces a 70% gross margin.

(Both figures above are from Profitwise Accounting's illustrative examples, not measured benchmarks.)

If project revenue and MRR are blended on a single revenue line without separation, the blended gross margin obscures both. A month with heavy project work will make recurring margins look worse than they are. A month with strong MRR growth will mask a deteriorating project business. Neither picture is accurate.

For a detailed breakdown of how to track gross margin by revenue line, see MSP Gross Margin by Revenue Line: Managed Services vs. Resale.

Building a Consistent MRR Classification Policy

The mechanics of MRR reporting are straightforward. The hard part is consistency — applying the same rules to every contract, every month, without exception.

FinancialContent recommends reviewing contracts, billing terms, and service agreements to confirm how each payment should be treated. That review should happen at contract inception, not retroactively at month-end.

A practical classification policy covers:

• Contract review at onboarding — classify each revenue component (recurring vs. one-time) before the first invoice
• Billing system alignment — tag recurring and non-recurring line items separately in your PSA or billing tool
• Monthly reconciliation — compare billed recurring revenue to the MRR schedule; investigate any variance
• Change-event triggers — any contract amendment, upgrade, downgrade, or cancellation should immediately update the MRR schedule
• Consistent treatment of edge cases — document how you handle partial months, bundled hardware, and variable-consumption add-ons

Hasenbank Accounting Services notes that clear, detailed policies aligned with ASC 606 should outline how the organization recognizes revenue across different types of contracts and services — and that these policies help ensure consistency and compliance across all financial transactions.

Without a written policy, classification decisions get made differently by different people in different months. The result is MRR data that cannot be trusted — and cannot be reconciled to the P&L.

For a broader look at how MSP financial reporting fits into a monthly close process, see What Is Included in a Monthly Close Package? and MSP Client Profitability: Formula, Allocation & Identifying Unprofitable Clients.

Frequently Asked Questions

What is MRR for an MSP?

MRR (monthly recurring revenue) is the total contracted value of recurring managed services, support agreements, and subscription fees that clients pay on a predictable monthly schedule. It excludes one-time charges, hardware sales, and project work. It is a management metric, not a GAAP accounting line.

Does MRR equal revenue on the P&L?

Not always. For standard monthly contracts, MRR and recognized GAAP revenue are often equal. But timing differences — such as mid-month starts, cancellations, or prepaid quarterly contracts — create gaps. Prepaid amounts sit in deferred revenue until the service is delivered, while MRR reflects the full monthly run-rate regardless of payment timing.

Should setup fees be included in MRR?

No. Setup fees are one-time charges and should be excluded from MRR. Including them overstates the predictability of your revenue base and makes month-to-month MRR comparisons unreliable. Under ASC 606, setup fees are recognized separately based on when the associated performance obligation is satisfied.

What is an MRR waterfall report?

An MRR waterfall breaks the month-over-month change in MRR into four components: new MRR (from new clients), expansion MRR (from existing client upgrades), contraction MRR (from downgrades), and churned MRR (from cancellations). Net MRR change equals new plus expansion minus contraction minus churn.

Laya provides this content for informational purposes only. This material does not constitute tax, legal, or accounting advice. Please consult your own tax, legal, and accounting advisors before engaging in any transaction.

If your MRR schedule and P&L are telling different stories each month, that's a reconciliation problem worth solving. Book an intro with Laya to see how we structure monthly close and reporting for MSPs.