Microsoft 365 license reconciliation that matches billing to reality
Seats get added for starters and not removed for leavers, distributor subscriptions drift from PSA agreement quantities, and the gap shows up as lost margin or an awkward client conversation. We build a monthly workflow that pulls license assignments from each Microsoft 365 tenant and subscriptions from your distributor, compares them with active users and agreement quantities in the PSA, and lists every mismatch with a suggested fix for approval. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why Microsoft 365 licenses drift from MSP billing
An MSP resells and manages licenses across dozens of tenants. Each month the numbers in the Microsoft admin center, the distributor portal and the PSA agreement should match. With more than a handful of clients, reconciling them in spreadsheets becomes a quarterly job or one that happens only after a complaint.
The common gaps are predictable: disabled users still holding a paid license, seats bought but never assigned, agreement quantities that were never updated after a true-up, and add-ons nobody remembers buying. Each is small; together they decide whether managed services make money.
What we build
What our license reconciliation workflow includes
Tenant license pull
Assigned and available licenses per SKU from each client tenant through Microsoft Graph.
Distributor subscriptions
Subscription quantities from Pax8 or your distributor through its partner API or a scheduled export.
Agreement comparison
PSA agreement additions and quantities compared with what the tenant and distributor show.
Exception list
Disabled users with licenses, unassigned seats, quantity mismatches and unknown SKUs per client.
Prepared adjustments
Suggested billing changes and license removals laid out for the account manager to approve.
Audit record
Each month's reconciliation stored per client, so true-ups and disputes have evidence.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Monthly run
Before invoicing, the workflow pulls tenant licenses, distributor subscriptions and PSA agreements.
-
02
Automated
Compared
Quantities are matched per client and SKU, and users are checked against sign-in status.
-
03
Automated
Exceptions listed
Mismatches and suggested fixes are written to a review sheet per client.
-
04
Technician review
Account manager reviews
The account manager approves billing adjustments and license removals.
-
05
Engineer or vCIO decides
Client conversation
Changes to the client's agreement or spend are agreed with the client by the vCIO or owner.
How it behaves
How monthly license reconciliation behaves
What the client sees
- Invoices that match the users they actually have
- A clear note when unused seats are found
- Questions about spend answered with evidence
What the account manager sees
- One exception list per client before invoicing
- Suggested fixes to approve or reject
- A stored record of each month's reconciliation
What the automation does
- Pulls tenant, distributor and PSA quantities on schedule
- Matches clients and SKUs and checks user status
- Applies only approved changes and logs them
Edge cases and fallbacks
- SKU name differs between systems
- Matched through a mapping table; unknown SKUs are flagged.
- Tenant access expired
- That client is marked not reconciled and the account manager is told.
- Shared mailbox holding a license
- Listed separately for a technician to check before any change.
- Distributor API unavailable
- The run waits and retries; billing is never prepared from partial data.
Architecture
Monthly license reconciliation at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 Before invoicing, n8n pulls license assignments from each tenant, distributor subscriptions and PSA agreement quantities.
- 2 Matching rules line up clients and SKUs and check which licensed users are disabled or inactive.
- 3 Every mismatch is written to an exception list with a suggested fix.
- 4 The account manager approves billing adjustments and license changes; client-facing changes are agreed with the client.
Project planner
How the project runs, phase by phase.
Microsoft 365 license reconciliation & billing checks project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Tenants, distributor, agreement structure, SKU naming and the current billing run.
-
02
Design
2 to 3 days
SKU mapping, matching rules, exception categories and review format.
-
03
Build
1 to 2 weeks
Graph and distributor pulls, PSA agreement reads, matching and exception list.
-
04
Shadow run
About 1 week
One billing cycle run in parallel with your manual reconciliation.
-
05
Launch
1 to 2 days
Schedule set before invoicing and the team walked through the review.
-
06
Support
Ongoing
New SKUs, new clients and changes to agreement structure.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
SKU mapping, matching rules and review format.
$200 – $400
-
Build
Data pulls, matching, exception list and approvals.
$500 – $1,300
-
Integrations
Microsoft Graph, distributor and PSA agreements.
$150 – $400
-
Testing and shadow run
One billing cycle run in parallel.
$100 – $250
-
Launch and training
Schedule and account manager walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Covers Microsoft 365 plus one distributor; other vendor portals can be added in a second workflow.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Spreadsheet: Google Workspace or Microsoft 365, which you already have.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
Read-only where possible
The reconciliation run only reads; license removals use the least-privileged LicenseAssignment.ReadWrite.All permission and only after approval.
Source: learn.microsoft.comAudit unused accounts
CISA and partner agencies recommend periodically auditing accounts and disabling unused ones; the exception list doubles as that audit.
Source: www.cisa.govEU and UK: client user data
User names and sign-in status are personal data processed for the client, covered by your GDPR Article 28 processor terms.
Source: gdpr-info.euFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Microsoft 365 license reconciliation & billing checks questions, answered.
Comparing what each client is licensed for in their tenant, what you buy from the distributor and what you bill in the PSA, then fixing the differences. Software license reconciliation done monthly keeps margin and client trust intact.
No. It lists disabled users with licenses and unassigned seats and suggests removals; the account manager approves each change, and changes that affect what the client pays are agreed with them.
Yes. Pax8 has a partner API with subscription endpoints using OAuth client credentials. For other distributors we use their API or a scheduled export, confirmed per project.
It can prepare the new quantity and, after approval, write it through the PSA API. Many MSPs prefer to approve in the review sheet first and let the workflow update the PSA once approved.
The data pull and matching run unattended. The review usually takes minutes per client, because only exceptions are listed.
Exceptions found per month, seats removed or billed after review, clients reconciled before invoicing and disputes raised about license billing.
Free 20-minute call
Want this for your it support & msp?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for it support & msps
All servicesMSP CRM & managed-services sales pipeline
Capture every prospect from web forms, referrals, assessments and calls into one MSP CRM pipeline, with follow-ups, proposal reminders and a clean hand-off into the PSA once the agreement is signed.
From $1,000 · About 4 weeks Details
PSA ticket triage & enrichment
Classify every new ticket by type, client, contract and priority, attach device and user context from the RMM and documentation, ask the user for missing details and route it to the right board.
From $1,000 · About 4 weeks Details
RMM alert grouping & safe first response
Group duplicate RMM alerts into one ticket, close self-cleared conditions with a log, run only pre-approved remediation scripts and escalate high-risk patterns straight to the on-call engineer.
From $1,000 · About 4 weeks Details