Most MSPs can tell you their average margin. Very few can tell you what their vendors are actually charging them at the line-item level, whether those charges match the agreements they negotiated, and how much the total has drifted since the last time anyone looked carefully.
This is not a small gap. Vendor billing is the cost side of MSP margin, and cost-side drift is one of the most consistent and least visible sources of margin compression available. It happens gradually, across multiple vendors, in invoice line items that are approved on autopilot because they arrive regularly and look familiar.
The MSPs who audit their vendor billing quarterly consistently find something. Not always dramatic. But always consistent. And consistency is how a small vendor billing gap becomes a significant annual margin problem.
The first form is pricing tier creep. A vendor pricing tier was selected based on a volume commitment. The volume never fully materialized, or it contracted after the initial commitment. The MSP continues to pay for the tier that reflected the original expectation rather than the current reality. The gap between what they are paying and what the current volume would cost at a lower tier is a monthly cost with no corresponding value.
The second form is expired promotional pricing. Introductory rates, promotional discounts, and negotiated pricing agreements have expiration dates. When those dates pass without renegotiation, pricing reverts to standard rates. Most MSPs do not track these expiration dates systematically. The change appears on the invoice as a slightly larger number that gets approved because it is close enough to what was expected.
The third form is zombie line items. Services, add-ons, and licenses that were enabled for a specific purpose that no longer exists. The original purpose has been completed or abandoned. The line item continues to appear on the invoice and continues to be paid because nobody has explicitly cancelled it and nobody is reviewing invoices at the line-item level.
The fourth form is quantity drift. Vendor invoices that bill per seat or per device against quantities that no longer reflect actual deployment. The agreement was set at a quantity based on the client environment at the time of the original commitment. The environment has changed. The quantity on the invoice has not.
Start with a complete list of every active vendor relationship and the most recent invoice from each. For each vendor, answer four questions: Is the pricing tier still the right one for current volume? Are there any promotional rates or negotiated discounts that have expired or are approaching expiration? Are there any line items for services or add-ons that are no longer actively used? Do the billed quantities match actual current deployment?
The answers to these four questions surface the specific vendor billing gaps that are suppressing margin. They also create the inputs for renegotiation conversations with vendors whose pricing has drifted from the value being delivered.
For MSPs managing Microsoft licensing specifically, this audit is particularly valuable given the frequency of Microsoft pricing changes in recent years. The Microsoft Add-on for Reconcile supports this by continuously comparing Microsoft invoice data against billing agreements and surfacing discrepancies as they occur rather than requiring a periodic manual audit. The quarterly exercise becomes a byproduct of a correctly running reconciliation process rather than a separate initiative.
Why do most MSPs not know what their vendors are actually charging them at the line-item level?
Because vendor invoices arrive regularly, look familiar, and get approved on autopilot. Without a systematic process for reviewing vendor invoices at the line-item level against current agreements and current usage, billing drift accumulates invisibly across multiple vendors over time.
What are the most common forms of vendor billing drift?
Pricing tier creep where the tier no longer reflects actual volume, expired promotional pricing that has reverted to standard rates without renegotiation, zombie line items for services that are no longer actively used, and quantity drift where billed quantities no longer reflect actual current deployment.
How often should MSPs run a vendor billing audit and what does it involve?
Quarterly is the right cadence for most MSPs. The audit involves reviewing every active vendor relationship against four questions: Is the pricing tier still appropriate? Have any promotional rates expired? Are there zombie line items? Do quantities match actual deployment? For Microsoft licensing specifically, Reconcile's Microsoft Add-on makes this continuous rather than periodic.