How MSPs Can Reconcile Client Software Licence Seats | 4KM Tech

Reconcile the actual subscription entitlement before changing seats

Start with the client's approved software tenant, product, subscription, assigned licence types, total purchased quantity and renewal point. Verify current facts in the vendor's authoritative administration and billing systems. A user may have several bundled service plans or add-ons, and an apparently unassigned seat in one console may remain subject to a commercial commitment. Keep an explicit distinction between technical assignment, contract quantity and actual charges.

Record the scope and date of the inventory snapshot. A comparison performed against a month-old assignment export can be misleading when starters, leavers and project teams have changed since it was taken.

Match assignments against recognised identities and roles

Review named users, service identities, shared functions and approved temporary accounts against client-authorised staffing and role information. An unfamiliar name is a question for the client owner, not evidence that access is unauthorised. Note whether each seat is confirmed necessary, potentially redundant or unresolved, with the source of that determination.

Do not infer that inactivity alone justifies removal. Some licences support periodic statutory reporting, specialist tasks or seasonal processes. Ask the relevant service or department owner to confirm business need before releasing an entitlement that could interrupt a legitimate user.

Separate assignment correction from account security

An account retaining a licence after a person's departure may also require offboarding review, but those are separate controls. Follow the client's authorised identity and access process for actual account disablement, session revocation or role changes. A licence being released does not prove a departed person has lost access to every service; equally, an account may properly remain for retained records while requiring no paid seat.

Where a proposed reassignment could affect data ownership, mailbox content or application capability, check the supported vendor procedure and relevant retention requirements. Do not remove or downgrade a plan merely to reduce a count before the business understands the effects.

Inspect bundles, dependencies and edge cases

Review add-ons, inherited licences, trial entitlements and products whose eligibility depends on another assigned plan. A simple one-person-one-seat spreadsheet can conceal dependencies that would leave a feature unavailable after reassignment. Confirm actual platform behaviour rather than relying on generic licensing assumptions.

For shared, device-based or concurrent models, use the provider's documented assignment rules. Preserve uncertainty where a product's contract permits a different counting basis and refer commercial interpretation to the authorised licence owner.

Prepare a client decision register before renewal

Present confirmed assignments, unallocated quantities, likely but unapproved reductions, planned starters and unresolved cases in a concise reconciliation sheet. Include the current subscription terms and supplier notice periods where verified. The client should see which actions are purely technical and which change a payable commitment. Do not present potential savings as guaranteed until commercial terms and timing have been checked.

Assign each proposed reduction, purchase or tier change to a person with appropriate client authority. If the decision depends on an external supplier, retain the provider case reference and next review point.

Apply approved changes with a traceable outcome

After approval, use supported administration tools to release, reassign or adjust entitlements. Record the affected identity, plan, approval, before-and-after state and actual completion time. Be aware that a licence assignment update may propagate separately from billing or subscription quantity changes. Confirm the relevant result in each authoritative system instead of assuming a successful interface click completes the commercial process.

When a change fails or cannot be verified, preserve the pending case and avoid repeating actions blindly. Keep affected users informed through the appropriate support route.

Verify business continuity and downstream totals

Check that users who still require the software retain the needed capability, and that removed or reassigned seats are reflected in the platform's actual count. Review billing or subscription reports after the appropriate processing point for approved commercial changes. A reduction in technical assignments need not immediately reduce invoices under the contract.

Retain a list of unresolved exceptions with owners rather than counting every seat as reconciled merely because the spreadsheet total matches the purchased quantity.

Make reviews part of normal MSP service maintenance

Use starter, leaver, role-change and renewal events to trigger proportionate licence checks. Review repeated mismatches for missing handoffs, unclear approval responsibilities and inconsistent product catalogues. Update those upstream processes rather than relying on large periodic clean-ups alone.

This extends ART1's core distinction: licence-seat reconciliation establishes which entitlements are assigned, which are justified and which commercial decisions the client has actually authorised, while identity security and supplier billing remain linked but separately controlled responsibilities.