VLSC reports for true-up preparation are the contractually authoritative source for entitlement counts and Software Assurance coverage; the buyer-side discipline is to pull eight specific reports at T-150 and reconcile them against three independent buyer-side deployment sources. The eight reports are licence entitlement summary, licence reservation summary, SA coverage detail, true-up history, key history, online services subscription detail, MPSA enrolment detail, and the consolidated licence statement. The reconciliation discipline is what makes the pre-modelled true-up position defensible against Microsoft's opening reconciliation number. The companion VLSC complete guide covers the broader workspace; the companion true-up calculator framework consumes the report outputs.
The starting fact about VLSC reports for true-up preparation: the Volume Licensing Service Center is the authoritative entitlement-of-record system for Microsoft Enterprise Agreements. Every reconciliation conversation between the buyer-side licence-management team and the Microsoft seller-side runs against the VLSC entitlement record. The buyer-side discipline is to pull the right reports at the right time, reconcile them against the buyer's own deployment evidence, and walk into the anniversary conversation with the pre-modelled position grounded in VLSC data. The teams that skip this discipline accept the seller-side anchor by default; the teams that run the discipline land 30 to 55 percent reductions on the opening number.
The eight VLSC reports for true-up preparation
Each report has a single purpose and a single output that feeds the pre-modelled position. The order below reflects the buyer-side workflow: entitlement first, then SA coverage, then transaction history, then consolidation.
The per-SKU entitlement count at the latest reconciliation date
The foundational report. The per-SKU entitlement count VLSC currently shows for the enrolment, including base EA quantities plus all prior true-up amendments. This count is the contractual entitlement; if a deployment count exceeds this number, there is true-up exposure on that SKU. Pull this report at T-150 and again at T-60 to compare the seller-side opening anchor against the latest VLSC state.
VLSC → Downloads and Keys → Licence Summary → Export to CSVPending true-up additions and amendments not yet reflected in entitlement
Distinct from the entitlement summary. The reservation summary shows the true-up additions, amendments, and SCU allocations that have been submitted but not yet reflected in the entitlement count. The gap between reservation and entitlement is the in-flight transaction risk; reservations that are stuck or rejected materially shift the true-up position.
VLSC → Licences → Reservations → Filter by EnrolmentSoftware Assurance coverage status per SKU and per agreement line
The per-SKU SA-coverage status determines whether SA offsets apply against apparent deployment gaps. The report shows SA-covered vs SA-uncovered split, SA expiration date per SKU line, and any SA renewal or step-up activity. The 2026 amplifier is the SA step-up pattern for E3-to-E5 and E5-to-E7 (Frontier Suite); the SA coverage detail report is the contractually authoritative source for which SKUs carry which step-up rights.
VLSC → Downloads and Keys → SA Coverage Report → ExportPrior anniversary true-up transactions across the EA term
The transaction trail of prior true-ups across the current EA term. The history shows which SKUs were added in which anniversary year, the price per SKU at the time of addition, and the prorating treatment applied. This report is the basis for arguing pricing-schedule continuity for the current anniversary; if a SKU was added at a negotiated tier two anniversaries ago, the current anniversary should anchor to the same tier, not retail.
VLSC → Licences → True-Up History → Filter by EnrolmentProduct activation key issuance history per SKU and per agreement
The product activation key issuance history is the indirect deployment-count evidence VLSC carries. For on-premises SKUs (Windows Server, SQL Server, the Office desktop family), the key issuance history correlates with the actual deployment count and serves as a reconciliation cross-check against the buyer's MECM or hypervisor inventory. Gaps between key issuance and actual deployment usually indicate misallocated keys that should be carved out of the true-up math.
VLSC → Downloads and Keys → Product Keys → Export HistoryPer-subscription detail for M365, Azure, Dynamics, and Power Platform
For cloud SKUs the entitlement summary is augmented by the online services subscription detail, which shows per-subscription quantity, term, and renewal anchor. The report is the basis for arguing prorating against partial-year subscriptions and for identifying which subscriptions are mid-cycle versus aligned to the EA anniversary.
VLSC → Subscriptions → Online Services → ExportMPSA-enrolment SKU and price detail for buyers with an MPSA in addition to the EA
For organisations that maintain an MPSA alongside the EA (a common pattern for transactional purchases outside the EA scope), the MPSA enrolment detail is critical for separating which SKUs sit in the EA true-up envelope versus the MPSA order trail. The most common mis-categorisation is MPSA-purchased SKUs appearing in the EA true-up number; the MPSA enrolment detail is the contractually authoritative basis for the carve-out.
VLSC → Enrolments → MPSA Detail → Filter by ResellerThe unified entitlement-plus-coverage statement Microsoft publishes annually
The annual consolidated licence statement is the unified document VLSC publishes that combines entitlement, SA coverage, and true-up history into a single per-agreement view. This is the document Microsoft's seller-side will reference in the anniversary conversation; the buyer-side discipline is to pull this report at T-90, compare it against the seven detail reports above, and document any discrepancies in the methodology note.
VLSC → Reports → Consolidated Licence Statement → Annual ExportVLSC reports reconciliation discipline
Pulling the reports is half the work; reconciling them against the buyer's own deployment evidence is the other half. Three independent buyer-side sources reconcile against the VLSC entitlement record.
| VLSC source | Buyer-side reconciliation source | What the gap means |
|---|---|---|
| Report 1 entitlement count for M365 E3/E5 | M365 admin centre licence-assignment export | Provisioned-but-unused split — argue active-use rebuttal (Move 5 of the reduction playbook) |
| Report 1 entitlement count for Azure consumption SKUs | Azure billing export + MACC consumption detail | Mis-categorisation risk — consumption belongs in MACC, not true-up (Move 6) |
| Report 1 entitlement count for Windows Server cores | Hypervisor inventory + MECM core count | Core-count reconciliation — argue licensable cores, not provisioned cores (Move 4) |
| Report 3 SA coverage for E3-to-E5 step-up | Internal SA tracking + step-up amendment trail | SA offset application — apply E3-to-E5 step-up credit (Move 3) |
| Report 4 true-up history per-SKU pricing | EA pricing schedule + prior amendments | Pricing-schedule continuity — anchor to prior negotiated tier (Move 1) |
| Report 5 product key issuance history | MECM deployment log + hypervisor activation log | Misallocated key carve-out — remove inactive keys from the true-up math (Move 4) |
| Report 6 online services subscription detail | Per-subscription term and activation log | Prorating against partial-year subscriptions (Move 2) |
| Report 8 consolidated statement | Seller-side opening reconciliation number | The pre-modelled position vs the seller anchor — the negotiation room |
Anniversary in the next 150 days? The VLSC pull at T-150 is the foundation of every pre-modelled position.
30-minute scoping call with a senior partner. VLSC reconciliation is standard advisory work.
When to pull each VLSC report
The pull schedule is sequenced to feed the broader true-up timing discipline.
- T-150 · Pull Reports 1, 2, 3, and 6. These are the foundational entitlement and coverage exports. Reconcile against deployment sources. Identify the SKUs tracking above entitlement and feed them into the Window-1 pre-anniversary scoping (see the true-up timing strategy article).
- T-120 · Pull Report 4 (true-up history) and Report 5 (key history). These exports anchor the pricing-schedule continuity argument and the misallocated-key carve-out. Both feed the pre-modelled position in the six-input calculator framework.
- T-90 · Pull Report 8 (consolidated licence statement). Compare against the seven detail reports. Document any discrepancies in the methodology note. The consolidated statement is the document Microsoft's seller-side will reference.
- T-60 · Pull Reports 1 and 8 again. Compare against the T-150 and T-90 pulls. The deltas are the in-flight transactions; the seller-side opening anchor should match the T-60 state, not the T-150 state.
- T-30 · Pull Report 2 (reservations). Confirm no stuck reservations are blocking the settlement. Stuck reservations are a common reason settlements drag past anniversary; clear them before the settlement signature.
- Post-anniversary · Pull Report 4 and Report 8. Confirm the settlement is reflected in the VLSC record. The post-anniversary pull is the audit trail for the next cycle's true-up history report.
2026 amplifiers that change the VLSC report mix
Four 2026 inflection points shift which reports carry the most weight in the reconciliation discipline.
- Agent 365 tier mix. Agent 365 Standard / Pro / Enterprise appears in Report 1 (entitlement) and Report 6 (online services subscription detail). The tier-mix drift across the year is the most common 2026 true-up overshoot; the buyer-side discipline is to reconcile Report 1 against the Agent 365 activation log per tier. See the Agent 365 article.
- Copilot Studio CCCU / ACU. Copilot Studio consumption appears in Report 6 (subscription detail) and in the Azure billing meter. The mis-categorisation pattern is Copilot Studio consumption appearing in the EA true-up envelope when it belongs in the consumption meter; Report 6 plus the Azure billing detail is the contractually authoritative basis for the carve-out. See the Copilot Studio 2026 article.
- E7 Frontier Suite step-up. E5-to-E7 step-up appears in Report 3 (SA coverage detail) as a new step-up family. The buyer-side discipline is to pull Report 3 specifically to confirm the E7 step-up eligibility before applying the SA-offset move. See the E7 article.
- EA tier collapse. The collapse of the A/B/C/D banding shifts the structure of Report 1 entitlement counts at the upper bands. Reconciliation against the pre-collapse pricing schedule needs an additional cross-check against the post-collapse tier framework. See the EA tier collapse pillar.
VLSC access permissions are the single most overlooked operational dependency in the report-pull discipline. Many buyers discover at T-150 that the licence-management lead does not have the VLSC role permissions needed to export Reports 1, 3, and 8 at the enrolment-level detail. The access-permission request takes two to three weeks through Microsoft support; the recovery path is to begin the permission request at T-180 alongside the T-150 report-pull plan. The cleanest discipline is to maintain export-level VLSC permissions year-round so the T-150 pull is friction-free. The cost of maintaining permissions is zero; the cost of discovering missing permissions at T-150 is the entire T-150 to T-120 reconciliation window.
The Microsoft Negotiations briefing
Monthly. VLSC discipline, true-up tactics, audit defence, 2026 inflection-point intelligence. One-click unsubscribe.
Independent since 2016. Not affiliated with Microsoft Corporation.
Where to take the VLSC reconciliation discipline next
The VLSC discipline pairs with the broader true-up framework. The VLSC complete guide covers the broader VLSC workspace beyond the true-up reports; the true-up calculator framework consumes the report outputs; the true-up reduction playbook walks the nine moves that build on VLSC evidence; the true-up timing article covers the four windows; the true-up risk assessment tool is the 10-question scorecard; the true-up defence service is the productised engagement. For organisations approaching anniversary, the scoping call is the direct engagement channel; for organisations in active EA renewal cycles, the free EA assessment is the broader scoping channel.