License Passthrough

Pax8, Sherweb, or direct — reconcile and bill any way you choose

Custom Bundles

Consolidate multiple services into a single per-user line

Weighted Users

Full users vs frontline workers — different cost, different weight

Dept & Location Splits

Invoice per location, department, or cost center

Shared Tenants

One M365 tenant, two entities — split billing handled correctly

Agency Billing

True per-user cost across all managed tenants for agencies

💱 Passthrough + Markup

Bill the customer exactly what you paid, plus a defined markup percentage. Simple, transparent, and easy to explain. Set a minimum markup floor so no license ever goes out at cost.

🏷️ MSRP Pricing

Bill at Microsoft’s published retail price regardless of what you paid. Your margin is the difference between what you charge and your provider cost — which varies as you negotiate better rates over time.

🔧 Management Fee

Pass the license through at cost and charge a separate management fee on top — per seat, per service, or flat. The customer sees what the license actually costs and what you charge to manage it.

🧩 Bundled Per-User

Consolidate M365, MDR, email security, SaaS backup, and your management fee into a single per-user price. The customer gets one clean line. You see exactly what it costs and what you make.

⚖️ Weighted User Billing

Not all users cost the same. Your billing shouldn’t pretend they do.

A company with 40 office workers and 30 warehouse staff isn’t a 70-user account — not really. The office workers need M365 Business Premium, full endpoint protection, email security, and backup. The warehouse staff clock in on shared kiosks and need basic F-series licenses and nothing else.

Charging both at the same per-user rate either overcharges the frontline workers or undercharges the full users. MSP Mesh Map lets you assign weights to user types so your cloud management fees and bundle pricing reflect what each group actually costs — and what they actually use.

• Define user tiers — Full User, Frontline Worker, Shared Kiosk, External, or any custom type you need
• Assign cost weights — a Full User might carry 1.0x weight, a Frontline Worker 0.4x, a Kiosk user 0.2x
• Fair fee allocation — cloud management fees and flat charges split proportionally by weighted headcount, not raw headcount
• Per-user bundle pricing — different bundles for different user types, billed at the right rate for each
• License alignment — the system checks that user types match the licenses assigned — no F-series license on a Full User account

🔗 Shared Tenant Billing

One tenant. Two entities. Two separate invoices — done right.

It’s more common than you’d think — a parent company and subsidiary sharing a single Microsoft 365 tenant, or two related businesses that merged their IT but kept separate billing. Every platform treats this as one account. Your invoices shouldn’t.

MSP Mesh Map lets you split a shared tenant across multiple billing entities — allocating licenses, shared resources like guest accounts, and management fees to each party based on rules you define. Both get their own invoice. You see the whole picture.

• Tag users by entity — assign each licensed user to the correct billing account within the shared tenant
• Allocate shared resources — guest accounts, shared mailboxes, and resources split by rule or by percentage
• Independent invoices — each entity gets its own invoice with its own line items and totals
• Management fee proration — flat tenant management fees split proportionally by user count, license cost, or custom allocation

🏢 Department & Location Billing

Your customer’s finance team wants to charge IT costs back to each department. Now you can.

Larger customers — and plenty of mid-size ones — run internal chargebacks. They want to see what IT is costing each department or location so those groups can be held accountable. That means your invoice needs to break down by org structure, not just show a single total.

MSP Mesh Map maps each user and device to a department or location, then produces invoice sections — or entirely separate invoices — for each one. You build the agreement once. The splits happen automatically at billing time.

• Location-level billing — HQ, branch offices, remote sites each get their own section or separate invoice
• Department chargebacks — IT, Finance, Operations, Sales — each sees only what they’re responsible for
• Shared service allocation — infrastructure and management costs split across departments by user count, device count, or custom weight
• One agreement, any output format — combined invoice with sections, fully split invoices, or a summary with department totals

New Hires Never Added to Billing

HR onboards a new employee, IT provisions their M365 account — but nobody updates the agreement. That user is managed for weeks or months before anyone notices the count is off. MSP Mesh Map flags user count changes in M365 against your active agreement quantities automatically.

Contractors Billed at the Wrong Rate

Contractors often get the same license type as full employees but should be billed under a different tier — or not billed at all if the customer is managing them directly. User tagging lets you define how each account type is handled at billing time.

License Count Drift Between Systems

Your RMM says 47 managed devices. Microsoft says 52 licensed users. Pax8 billed you for 49 M365 seats. Which number is right? MSP Mesh Map cross-references counts across every connected system and surfaces the discrepancies so you can resolve them before they affect your invoice.

Departed Employees Still on Agreements

Offboarding is handled in HR and IT, but the billing agreement isn’t always updated. You’re managing and billing for a user that left three months ago. Account status changes in M365 trigger a billing review prompt so departures don’t silently inflate your customer’s invoice.

🏛️ Agency & Multi-Client Billing

True per-user cost across every client — not an estimate, not a blended average.

Agencies and multi-client MSPs need a real picture of what they’re spending and making per user, per client — not a spreadsheet they update manually each month. When one client’s margin drops to 9% and you don’t know until you reconcile the quarter, that’s a problem.

MSP Mesh Map aggregates vendor costs across all managed tenants, maps them to each client, and calculates true per-user cost and margin in real time — across every licensing tier, every vendor, and every agreement structure.

• Per-client per-user cost — true cost from all vendors, divided by the actual billable user count
• Margin alerts — flag any client where margin drops below your defined threshold before the invoice goes out
• Cross-client reporting — see all clients ranked by per-user margin, revenue, or headcount
• Renewal intelligence — know which clients are underpriced before their agreement comes up, not after