LastPass MSP Billing
Overview
The LastPass billing report gives each managed company's daily
average license count over a billing cycle, its license type and its
add-ons (mfa, sso). That is the consumption figure MSP billing is
reconciled against. A company with status: active is billed for the
month; suspended is not. Reconciliation means checking that what LastPass will charge the
MSP matches what the MSP charges each client.
All three tools need an MSP key; a Business key gets 403. Every tool
here is tier read in Conduit; none is admin-gated.
Common Workflows
Month-end reconciliation
- Get the cycle dates.
lastpass_reports_billing_cycles_list with
number_of_cycles: 1 for the current cycle, or up to 12 for history.
Each cycle has startDate and endDate.
- Pull consumption.
lastpass_reports_billing_list with
start_date and end_date set to the cycle's dates (both required,
yyyy-MM-dd). Page with max_results: 50 and page_token. Each row
gives the company's dailyAverageLicenseCount, licenseType,
addons and parentId.
- Pull the companies.
lastpass_managed_companies_list with
max_results: 500 for name, licenseLimit, status, type and
addons, keyed by id.
- Join and flag (below). Join the billing rows to the companies on
the company ID.
- Compare with the PSA. If a PSA plugin is connected, compare each
client's billed LastPass quantity with the rounded-up
dailyAverageLicenseCount. Otherwise produce the table for a human
to compare.
Quick over-limit check
lastpass_managed_companies_list alone gives licenseLimit. Compare it
with the latest billing report count. A client running at or near its
limit is a renewal or upsell conversation.
What to Flag
| Finding |
Rule |
| Billed but not invoiced |
Company in the billing report with a count above 0 and no matching PSA line |
| Under-invoiced |
PSA quantity below the rounded-up daily average |
| Over limit |
Daily average at or above licenseLimit |
| Add-on drift |
addons includes mfa or sso but the client's agreement does not |
| Paying for a dead client |
status: active for a client the MSP has offboarded; suspend it in LastPass |
| Trial still running |
licenseType: msp-trial past the trial period |
Output
A table per cycle: company, type, status, license limit, daily average
count, add-ons, PSA quantity (if available), difference, and flag. Then
totals and a short list of actions (suspend, raise invoice, adjust
limit). Money figures come from the PSA or the MSP's price list; the
LastPass API returns counts, not prices.
Gotchas
- Daily average, not a headcount. A client that added ten users on
the last day of the cycle barely moves the average. Do not compare it
with a live users list.
- Grandchildren. Rows carry
parentId. A managed-msp company is a
sub-MSP with its own children; roll its children up under it if the
MSP bills the sub-MSP rather than its clients.
license_type filter values are msp, msp-trial,
msp-managed-company, msp-distributor and managed-msp. Leave it
unset for a full reconciliation.
- Dates are inclusive, and both
start_date and end_date are
required.
Related Skills
1---2name: lastpass-msp-billing3description: >4 Reconciling LastPass MSP license consumption: billing cycles, the5 per-company billing report (`dailyAverageLicenseCount`, `licenseType`,6 `addons`), managed-company license limits and active/suspended status,7 and matching all of it against what the MSP bills each client in the8 PSA. MSP keys only.9when_to_use: >-10 When checking what LastPass will bill the MSP this cycle, finding11 clients that are over their license limit or billed for add-ons they12 do not pay for, or preparing month-end reconciliation of LastPass13 seats against client invoices. Use when: lastpass billing, lastpass14 licenses, lastpass seat count, lastpass reconciliation, lastpass15 invoice, lastpass license limit, or lastpass msp billing.16metadata:17 source: https://skillmd.com/skills/wyre-ai/lastpass-msp-billing18---1920# LastPass MSP Billing2122## Overview2324The LastPass billing report gives each managed company's **daily25average** license count over a billing cycle, its license type and its26add-ons (`mfa`, `sso`). That is the consumption figure MSP billing is27reconciled against. A company with `status: active` is billed for the28month; `suspended` is not. Reconciliation means checking that what LastPass will charge the29MSP matches what the MSP charges each client.3031All three tools need an **MSP** key; a Business key gets 403. Every tool32here is tier **read** in Conduit; none is admin-gated.3334## Common Workflows3536### Month-end reconciliation37381. **Get the cycle dates.** `lastpass_reports_billing_cycles_list` with39 `number_of_cycles: 1` for the current cycle, or up to 12 for history.40 Each cycle has `startDate` and `endDate`.412. **Pull consumption.** `lastpass_reports_billing_list` with42 `start_date` and `end_date` set to the cycle's dates (both required,43 `yyyy-MM-dd`). Page with `max_results: 50` and `page_token`. Each row44 gives the company's `dailyAverageLicenseCount`, `licenseType`,45 `addons` and `parentId`.463. **Pull the companies.** `lastpass_managed_companies_list` with47 `max_results: 500` for `name`, `licenseLimit`, `status`, `type` and48 `addons`, keyed by `id`.494. **Join and flag** (below). Join the billing rows to the companies on50 the company ID.515. **Compare with the PSA.** If a PSA plugin is connected, compare each52 client's billed LastPass quantity with the rounded-up53 `dailyAverageLicenseCount`. Otherwise produce the table for a human54 to compare.5556### Quick over-limit check5758`lastpass_managed_companies_list` alone gives `licenseLimit`. Compare it59with the latest billing report count. A client running at or near its60limit is a renewal or upsell conversation.6162## What to Flag6364| Finding | Rule |65|---------|------|66| Billed but not invoiced | Company in the billing report with a count above 0 and no matching PSA line |67| Under-invoiced | PSA quantity below the rounded-up daily average |68| Over limit | Daily average at or above `licenseLimit` |69| Add-on drift | `addons` includes `mfa` or `sso` but the client's agreement does not |70| Paying for a dead client | `status: active` for a client the MSP has offboarded; suspend it in LastPass |71| Trial still running | `licenseType: msp-trial` past the trial period |7273## Output7475A table per cycle: company, type, status, license limit, daily average76count, add-ons, PSA quantity (if available), difference, and flag. Then77totals and a short list of actions (suspend, raise invoice, adjust78limit). Money figures come from the PSA or the MSP's price list; the79LastPass API returns counts, not prices.8081## Gotchas8283- **Daily average, not a headcount.** A client that added ten users on84 the last day of the cycle barely moves the average. Do not compare it85 with a live users list.86- **Grandchildren.** Rows carry `parentId`. A `managed-msp` company is a87 sub-MSP with its own children; roll its children up under it if the88 MSP bills the sub-MSP rather than its clients.89- **`license_type` filter** values are `msp`, `msp-trial`,90 `msp-managed-company`, `msp-distributor` and `managed-msp`. Leave it91 unset for a full reconciliation.92- **Dates are inclusive**, and both `start_date` and `end_date` are93 required.9495## Related Skills9697- [api-patterns](../api-patterns/SKILL.md) - pagination, filters, errors