Hours bank with live state.
Every MSP engagement has a live bank balance computed from committed hours, rollover, time entries, and overage. The state is current, not month-end.
Hours-bank retainers that hold their shape.
Managed services are not the same as project work. The unit is the hour bank, not the milestone. The question is utilization against commitment, not percent complete. The math is rollover and overage, not fixed-fee or T&M. Generic PSAs flatten all of this into a single recurring-revenue line. PartnerView holds managed services as its own engagement type with hours-bank semantics, per-period state, three rollover rules, three overage behaviors, and a portfolio surface tuned for the question MSP operators actually ask: which clients are at risk of overage and which are at risk of underuse.
The contract said hours can carry. Three months in, nobody knows how many hours are actually in the bank. The client asks. Someone opens a spreadsheet. Negotiations happen on guesswork.
The team worked twelve extra hours in week three. By the time finance notices in the close cycle, the work has been delivered, the client did not approve overage, and now the invoice is a negotiation.
Recurring revenue is the most important number on a managed services book. It lives in invoices, in retainer-period rows, and in a finance person's head. The dashboard cannot tell you what your MRR is by practice without an afternoon of work.
Evaluate this against your current MSP tooling. Comparison below.
| Project-based PSA | PartnerView | |
|---|---|---|
| Engagement type | Retainers as a flat monthly line. No bank model. | Managed Services as a fifth engagement type with hours-bank semantics. |
| Rollover | Flat or not modeled. | Three rules: use-it-or-lose-it, full rollover, capped rollover. |
| Overage | Discovered at close. | Three behaviors: auto-invoice, require approval with notification, warn only. |
| Period close | Manual reconciliation. | Automatic close applies rollover rule, writes revenue recognition, generates overage invoice if configured. |
| MRR reporting | Bring your own BI. | Built-in: bank balance summary, at-risk projection, MRR pivoted by practice. |
Every MSP engagement has a live bank balance computed from committed hours, rollover, time entries, and overage. The state is current, not month-end.
Use-it-or-lose-it for clients who want a clean reset. Full rollover for clients with banked credit. Capped rollover for the cases in between. Set per engagement, applied automatically at period close.
Auto-invoice when overage hits a threshold, require approval and notify the engagement owner, or warn only. The choice is yours, the discipline is the system's.
The bank balance summary report shows per-engagement state. The at-risk report projects which clients are heading for overage or under-utilization. The MRR report pivots by practice. No BI tool required.
Every MSP engagement is configured once and runs on rails after.
The work of running a managed services book, encoded.
The view that lets you run the book, not just one engagement.
When you subcontract in or out, the engagement is its own record with hours, rate, and a capacity calculation sales can query.
Bring your last MSP period close. We will show you how PartnerView would have run it. Healthy, at risk, or overage, on one screen.
Get a demo→