back to blog

The MSP Revenue You Never Invoice and the Credits You Never Claim

Read Time 5 mins | Written by: Gradient MSP

MSP financial leakage runs both ways: revenue you never invoice and vendor credits you never claim. See where it hides and how to close both gaps.

When MSPs hear "financial leakage," they usually think of underbilling: a user added and never invoiced, a license that slipped through. That is real, but it is only half the picture. The other half is money your vendors owe you, in credits, rebates, and incentives, that never gets claimed because nobody is watching for it. Both leaks are quiet, both are small month to month, and together they take a real bite out of what you keep from work you already do.

 

What Is Financial Leakage in an MSP?

Financial leakage is any money an MSP has earned or is owed but does not collect. It shows up on two sides:

  • The revenue side: services you deliver but never invoice, or invoice at the wrong price or quantity.
  • The vendor side: credits, refunds, rebates, and incentives that a vendor owes you under its program terms or after a billing error, but that you never request.

 

Neither side triggers an alarm. Nothing breaks, no client complains, and no vendor volunteers a credit. The money simply never arrives.

 

Where Does Unbilled Revenue Come From?

Most unbilled revenue comes from the gap between what the agreement says and what you actually deliver. The usual sources are:

 

  • Quantity drift: users, devices, or licenses added during the term and never added to the invoice.
  • Services added informally: a new tool or protection layer deployed for a client without a matching line in the agreement.
  • Vendor increases not passed through: the cost went up and the client price did not.
  • Expired discounts: a promotional or first-year price that kept applying after it should have ended.
  • Out-of-scope work: projects and extra hours absorbed instead of billed.

 

What Vendor Credits and Compensation Do MSPs Leave Unclaimed?

Vendor compensation is money a vendor owes an MSP under program terms or to correct a billing mistake. What is available depends on each vendor's program, so check the terms for every vendor you buy from. Common examples include:

  • Billing error credits: duplicate charges, wrong quantities, or wrong rates on a vendor invoice.
  • Charges after cancellation: seats or licenses still billed after you reduced or canceled them.
  • Service level credits: credits owed when a vendor misses its own uptime or response commitments.
  • Partner rebates and tier incentives: payments tied to reaching a purchase or growth threshold.
  • Proration refunds: money owed after a mid-term downgrade or cancellation.
  • Promotional or trial credits: offers that should have applied but never showed up on an invoice.

 

Many of these have claim windows. If the window closes before anyone notices, the money is usually gone.

 

Why Do These Leaks Go Unnoticed?

Because the evidence lives in different places. The vendor invoice is in one portal, the agreement is in your PSA, and what you actually invoiced is somewhere else. Finding a gap means lining all three up, line by line, every month. When that comparison is slow or only happens when someone has time, small gaps repeat for months before anyone sees them.

 

What Does It Add Up To?

 

Illustrative example, not a benchmark: a mid-sized MSP with a few dozen clients finds four small leaks. None looks serious alone.

 

Leak How it happens Illustrative annual value
Unbilled licenses 25 licenses at $15 a month, never added to invoices $4,500
Missed pass-through Vendor increases on three products never reached clients, $420 a month $5,040
Expired discounts Two clients still on a first-year price, $300 a month $3,600
Unclaimed vendor credits Two billing corrections and one rebate never requested $2,400
Total   $15,540

 

Almost all of that is margin, because the cost to deliver was already paid.

 

How Can You Close Both Gaps?

 

  1. Compare three things every month: the vendor invoice, the agreement, and what you billed.
  2. Keep a vendor credit calendar: list each vendor's claim windows, rebate thresholds, and service level terms, and review it monthly.
  3. Log every discrepancy: record the vendor, amount, date found, and claim status, so nothing sits in someone's inbox.
  4. Assign one owner: a gap with no owner is a gap that repeats.
  5. Set a pass-through rule: decide in advance how vendor increases reach client agreements, and when.
  6. Review at renewal: fix quantities, prices, and discounts while the client is already expecting a conversation.

 

Gradient Reconcile compares your vendor invoices against your agreements, so quantity and price gaps are found while they are still small, and you have the line-level detail you need when a vendor correction is due. If you would like a quick read on your own gaps, Gradient's Free Billing Audit shows your over-under on two vendors at no cost: https://www.meetgradient.com/free-billing-audit

 

FAQ

 

What is unbilled revenue for an MSP?

Revenue from services you delivered but did not invoice, or invoiced at the wrong quantity or price.

 

What vendor credits can MSPs claim?

It depends on the vendor's program. Common ones include billing error credits, refunds after cancellations, service level credits, and partner rebates. Read each vendor's terms.

 

How often should an MSP check vendor invoices for errors?

Monthly, because many credits and corrections have claim windows.

 

Why do MSPs miss vendor credits?

Credits are rarely announced. They only surface when someone compares the invoice against the agreement and program terms.

 

How do I find out how much I am leaking?

Compare one month of vendor invoices against your agreements and your client invoices. Start with your largest vendors.