If you run an MSP on InventoryOS, the portal now has three new capabilities that connect directly to how you structure, price, and bill your managed services: service plans, price policies, and billing reconciliation. They live in your MSP Portal page (or under MSP Team if you’re a hub account). Here’s a plain-English walkthrough of each one.
Service Plans: Define the Stack You Sell
A service plan is the bundle you sell, given a name. You pick the software it includes (EDR, RMM, DNS filter, remote access—whatever your stack is) and set the monthly price per device type: Primary devices, Secondary devices, and Mobile.
When you assign a plan to a client organization, two things happen. First, the per-device pricing for that org follows the plan. Second, the plan name shows up as a column on that org’s Agents and Users tables—so every device and every user is visibly tagged with its service tier.
What it looks like in the portal: Go to MSP Team (or MSP Portal from the left nav), then open the Service Plans tab. You’ll see a wizard that walks you through naming the plan, picking the software tools that are part of it, and setting prices for each device type. Plans you create are listed as cards; you can edit or delete them at any time.
How Managed Plan shows up for devices: Once you assign a plan to a client org, their Agents table gets a “Managed Plan” column with colored pills showing the tier assigned to each device. No manual tagging—every device in the org shows its service tier automatically.
MSP licensing alerts also use plan data: InventoryOS will flag you when a client’s device count doesn’t match what you agreed to in the plan, so you catch quantity drifts before they show up on an invoice.
Price Policies: One Price Doesn't Fit All
Once you have service plans, you’ll often find that the same plan needs slightly different pricing for different clients. A healthcare client needs a higher rate. An education account gets a discount. A legacy client is grandfathered at old prices. Price policies handle all of this without touching your main service plan.
A price policy is a named override of the default prices in a service plan. You create the policy (e.g., “Healthcare premium”), set the modified prices for whichever device types you want to change, and assign it to a plan or directly to an org.
The precedence order is: overall prices → price policy → per-client override. Each level overrides the one before it. A per-client override on an org’s Licenses page stays in effect regardless of what policy is assigned to the plan.
Example: Your Managed plan charges $100/mo for Primary devices. You have five healthcare clients who agreed to $120. Create a “Healthcare premium” policy with Primary = $120, assign it to the Managed plan, and apply it to those five clients. Your other Managed clients still get $100. No plan duplication needed.
Billing Reconciliation: Close the Loop With Your Books
This one solves a very specific but very common problem: your billing system (QuickBooks, whatever you use) doesn’t know about device count changes until someone manually updates it. By then it’s invoice day and things don’t match.
Billing reconciliation exports a period-by-period comparison between InventoryOS device counts and your billing line items. You match each InventoryOS organization to a customer name in your accounting software once, and then each period shows you the differences: which clients added devices, which removed them, and by how much.
Here’s what the reconciliation view looks like in practice:
How it works step by step:
- Open Billing Reconciliation from the MSP Portal.
- Match each InventoryOS organization to its name in your billing system. This is a one-time setup per client; matches are remembered.
- Each billing period, review the comparison. Each client shows its current device count, what changed since last period, and the calculated amount.
- Check off clients you’ve updated in your billing system. The “confirm” action marks the period as reconciled for that client.
- Export to CSV if you need to upload to QuickBooks or your PSA.
You can also turn on a reminder email that goes out before invoice day. Set how many days ahead it sends and who it goes to, so the right person gets a heads-up without you having to remember.
MSP Team: Cross-Org Staff Access
The MSP Team feature isn’t new, but it’s worth covering alongside the billing features because they work together. When you add a technician as MSP staff, they get Admin, Viewer, or a custom role across every client org under your hub—including orgs you create later.
The difference between an MSP staff invite and a regular org invite: regular invites are scoped to one org. MSP staff access follows your whole client portfolio. You manage it once, from the MSP Team tab, not separately in each client.
Custom roles you define in your hub are also copied to client orgs when staff sync. So if you’ve built a “Helpdesk” role that grants read-only on devices and write on tickets, that role propagates to every client automatically.
MSP Defaults: New Client Setup in Seconds
One more feature worth knowing: MSP Defaults (in the MSP Portal under the Defaults tab) lets you set software rules, custom Agents columns, and custom Users fields that apply to every new org you create. Save time on the repetitive parts of client onboarding, and ensure every new client starts with your standard baseline.
Where to Find Everything
All of this lives in the MSP Portal, which you reach from the left sidebar → Orgs → MSP Portal (if you’re a hub account). Or navigate directly to the MSP Team page. The main tabs are:
- Service plans — create and manage plan definitions
- Price policies — create overrides per plan or per client
- Billing reconciliation — period-by-period billing comparison
- MSP team — add and manage cross-org staff
- Defaults — set what new orgs inherit automatically
You can also set a per-client price override directly from a client org’s Licenses page—it’s a permanent exception for that one client regardless of plan or policy.
Getting Started
If you’re already managing multiple clients in InventoryOS, the quickest way to start is to set up one service plan that matches your most common stack, assign it to a few client orgs, and check that the Managed Plan column appears correctly in their Agents tables. Once that’s working, billing reconciliation is just one more tab away.
If you’re new to the MSP side of InventoryOS, start with the multi-org overview to understand how organizations work, then come back here for billing.
As always, the support team is happy to walk through any of these features live if you’d rather see them in your own account.