December, the last weeks before fiscal year close. Email from the Microsoft account manager: “Reminder about the upcoming true-up. Please send current usage data by January 15.” The IT manager opens the Excel with licenses - last updated 8 months ago. They try to count: how many Office 365 users do we have? How many Windows servers? How many SQL Server cores? Panic rises. Deadline in 3 weeks.
This story repeats in thousands of companies every year. True-up - the annual reconciliation of license usage under Enterprise Agreement (Microsoft) or Unlimited License Agreement (Oracle) contracts - is the moment of truth. And for many companies, it’s a moment of expensive truth. Flexera research shows that the average enterprise overpays on true-up by an average of 340,000 PLN annually due to poor preparation, overcounting, and lack of optimization.
What is true-up and why do companies regularly lose on it?
“For every $1 invested in IT asset management, organizations typically see a return of $5 to $25 in savings and risk reduction.”
— IAITAM, The Value of IT Asset Management | Source
True-up is a mechanism in Enterprise agreements that allows a company to start using additional licenses during the year, paying for them only at the annual reconciliation. In theory - business flexibility. In practice - a trap for the unprepared.
Microsoft Enterprise Agreement with true-up works like this: at the beginning of the agreement, you declare a baseline number of users/devices/cores. During the year, you can add more. At year end (anniversary date), you report actual usage - and pay for the increase. Problems start when you don’t know how much you’re actually using.
Oracle Unlimited License Agreement (ULA) is a different beast. During the agreement period (typically 3-5 years), you can deploy unlimited quantities of specified products. At ULA end, you “certify” how much you deployed - and that number becomes your perpetual entitlement. Undercounting = you lose licenses you paid for. Overcounting = you pay support from an inflated base.
Why do companies lose? First: lack of visibility. They don’t know how many users, installations, cores they really have. Shadow IT, unmanaged deployments, legacy systems - all escapes tracking. Second: bad timing. Optimization a week before deadline is too late - decisions to shut down systems require time.
Third: information asymmetry. The vendor knows more about their products and licensing rules than you do. The account manager is motivated to maximize sales. Without SAM expertise, you negotiate blindfolded. Fourth: fear of undercounting. Better to overpay than risk an audit - thinks the IT manager. And pays for licenses they don’t need.
What does the true-up preparation cycle look like and when to start?
True-up preparation doesn’t start in December - it starts in January. Or, realistically, should be a continuous practice throughout the year. But if you haven’t done it before, minimum 3 months before the anniversary date is the absolute minimum.
Month -6 to -3: Discovery and baseline. Inventory all assets - servers, devices, users, applications. Compare with owned entitlements. Identify gaps and overcounts. This requires tools (SCCM, ServiceNow, Flexera) and time for configuration and data collection.
Month -3 to -2: Analysis and optimization. Analyze discovery results. Which licenses are unused? Which deployments can be consolidated? Which users have too high a license tier? Develop an optimization plan and execution timeline.
Month -2 to -1: Optimization execution. Shut down unused servers, decommission legacy, move users to lower tiers where justified, virtualize where cost-effective. Changes must be made BEFORE the true-up date to be counted.
Month -1 to 0: Finalization and report. Final count, report preparation for vendor, review with lawyer/SAM expert, preparation for negotiations. Buffer for unexpected issues.
Post true-up: Negotiations and future planning. True-up is also a time to renegotiate terms, add products, change agreement structure. Use the data collected in the process.
How to conduct effective Microsoft license discovery before true-up?
Microsoft licensing is notoriously complex - different products, different metrics (per user, per device, per core), different editions (Standard, Enterprise, Premium). Discovery must account for all these dimensions.
Active Directory as the source of truth for users - but only partial. AD shows all users, but you don’t need to license all AD users. Service accounts, inactive users, terminated employees, external guests - all require classification.
Azure AD and Microsoft 365 Admin Center for cloud subscriptions. How many Office 365 E3, E5, F3 licenses do you have? How many are assigned vs. available? How many users are “active” (logged in within the last 30 days)? Inactive licenses are an opportunity to downgrade or remove.
System Center Configuration Manager (SCCM) or Intune for endpoint discovery. How many devices have Windows Enterprise installed (and how many would Pro suffice)? How many have Office locally (maybe they can move to web-only)? How many have applications requiring CAL?
SQL Server discovery is a separate challenge. How many instances? How many cores on each? Edition (Standard, Enterprise)? Features used? SQL licensing is notoriously expensive - the difference between proper and improper sizing is hundreds of thousands of zlotys. SQL Assessment Tools from Microsoft help.
Virtualization host licensing for Windows Server and SQL requires understanding the rules. Windows Server 2022 in Datacenter edition licenses all VMs on the host. Standard - only 2 VMs per 2-socket host. SQL in virtual requires counting physical host cores, not VM. Errors here are costly.
How to conduct effective Oracle license discovery before ULA true-up?
Oracle licensing is even more complicated than Microsoft - and Oracle is much more aggressive in audits. ULA certification is a moment when precision is critical - overcounting means higher support forever, undercounting means compliance risk.
Oracle LMS (License Management Services) scripts are the standard for Oracle database inventory. Run them on all servers - physical and virtual. Output shows: editions, features used, processor type and count. But caution: scripts sometimes overcount.
Named User Plus (NUP) vs. Processor licensing - you must know which model you have in ULA and how to count. NUP requires counting users with access (direct and indirect). Processor requires counting physical cores (with processor multiplier factor dependent on CPU type).
Enterprise features activation check. Oracle Database Enterprise Edition has many optional features (Partitioning, RAC, Advanced Compression) - each separately licensed. Even if a feature is enabled but unused - Oracle claims you need a license. Check DBA_FEATURE_USAGE_STATISTICS and disable what’s unnecessary BEFORE certification.
Virtualization complexity - Oracle doesn’t recognize soft partitioning (VMware, Hyper-V). If Oracle DB runs on a VM, you must license all physical cores in the cluster the VM can migrate to. Exception: hard partitioning (Oracle VM, Solaris Zones, IBM LPAR with DLPAR disabled). This often shocks companies at certification.
Cloud and outsourcing - do you have Oracle in AWS, Azure, GCP? Does an outsourcer use Oracle on your behalf? ULA may not cover these scenarios - check agreement terms. Oracle Authorized Cloud Environments have special rules.
What optimizations can be done before true-up to reduce costs?
User cleanup - removing inactive users. An employee left 6 months ago but still has an Office 365 license? Remove. A service account has a full E5 license when it only needs Exchange? Downgrade. An external guest has a license when free tier would suffice? Change.
Tier optimization - matching licenses to needs. Does every user really need E5 (the most expensive) or would E3 or E1 suffice? Does every SQL server need Enterprise or would Standard suffice? Feature usage analysis reveals overtiering, which is often significant.
Server consolidation and decommission. An old server that “still works” but no one knows why - shut down before true-up. A VM that was “temporary” 2 years ago - is it still needed? A test environment running 24/7 instead of on-demand - change the model.
Edition downgrade where possible. Windows Server Datacenter on a host with 3 VMs? Standard (with 2 licenses) would be cheaper. SQL Enterprise used only for basic operations? Standard may suffice (with RAM and core limitations, but OK for many workloads).
True virtualization optimization. Regrouping VMs onto fewer physical hosts can reduce licensing footprint. But requires coordination with operations - don’t do this at deadline.
Hybrid benefit and license mobility. If you have on-premise licenses with Software Assurance, you can use them in Azure instead of paying for included licenses. Make sure you’re using these options before true-up cloud subscriptions.
How to negotiate with the vendor at true-up?
Data preparation is a negotiating weapon. If you know exactly how much you have and need - you negotiate from a position of strength. If you don’t know - you accept what the vendor says. The vendor usually knows more about your environment than you (through telemetry) - equalize this asymmetry.
Timing leverage. True-up isn’t just a payment moment - it’s a renegotiation moment. The EA agreement can be extended, changed, expanded. The vendor wants your business for the next 3 years. Use this: “we’re considering alternatives” (even if you’re not seriously considering) gives leverage.
Bundle negotiation. Instead of paying for individual products, maybe a bundle is more advantageous (Microsoft 365 instead of separate Office + EMS + Windows)? Maybe additional products in the package at marginal cost? Vendor prefers to sell a bundle than lose everything.
Multi-year commitment for better pricing. If you’re certain you’ll stay with the vendor - a longer agreement may have better terms. But caution: 5-year lock-in is also a risk (if technology changes).
Real alternatives strengthen position. Migration to Google Workspace, Linux, open source - is that a real option? If so, mentioning it changes the conversation dynamics. “We’re analyzing TCO of alternatives” signals you’re not a captive customer.
Avoid paying for shelfware. If products in the EA aren’t used - don’t renew them. “But we have a package deal” - maybe, but maybe the package can be renegotiated without unused components. The account manager has flexibility they won’t show without asking.
What are the most common mistakes at true-up and how to avoid them?
Last-minute panic counting. A week before deadline, trying to count everything - inaccurately, rushed, with errors. Under stress, you overcount (because better to overpay than risk). Solution: start early, continuous tracking.
Counting virtual cores instead of physical. Microsoft and Oracle in most cases count physical host cores, not virtual. One VM with 4 vCPU on a 24-core server requires licensing for 24 cores (with some exceptions). This error costs a fortune.
Ignoring SAM tools output. You have ServiceNow or Flexera, but reports are old, incomplete, unused. A tool is only as good as the data in it - requires maintenance and trust in output.
Not understanding licensing rules. “I thought that’s how it works” - famous last words. Microsoft and Oracle licensing rules fill volumes and change yearly. Without a SAM expert, you’re probably misinterpreting.
Forgetting about edge cases. Disaster recovery site - requires licenses (with exceptions). Dev/test environments - require licenses (but may have special programs). External users accessing internal systems - may require External Connector or per-user licensing. Edge cases are expensive.
Not negotiating at all. Accepting the first number from the vendor without discussion. The account manager gave an estimate - you don’t have to accept it without verification. True-up is a negotiation, not an invoice to pay.
What does the Oracle ULA certification process look like and what are the pitfalls?
ULA certification is the formal process at the end of the Unlimited License Agreement where you declare how much you deployed of the products. This declaration becomes your perpetual entitlement - an error is hard to correct later.
Certification timeline: typically 30-45 days before ULA end, you must submit a certification notice. Then 30 days to collect data and prepare the report. Oracle has the right to verification (quasi-audit). After acceptance - perpetual licenses are issued.
Undercounting risk - if you declare less than you actually have deployed, after ULA you have a compliance gap. Oracle can audit after ULA ends and demand purchase of missing licenses at list price. Defense is difficult.
Overcounting risk - if you declare more than you actually need, you pay support from a higher base. Support is ~22% annually of license value - overcounting by 20% is 4.4% extra cost annually, forever.
Virtual deployment causes the most problems. If Oracle DB runs on VMware, you must count all physical cores in the entire cluster (not just VM cores). Companies are often shocked when they discover this. Solutions: hard partitioning, dedicated hosts, or accepting a higher count.
Feature usage audit. Oracle can challenge your count if scripts show feature usage you’re not certifying. Disable unused features BEFORE certification, document that they were disabled.
Consider ULA renewal vs. certification. Sometimes it’s better to extend ULA for another 3-5 years instead of certifying - if you plan further growth, if the certification count is very high, if new ULA terms are favorable. This is a strategic decision.
What role does professional SAM play in the true-up process?
Inventory and discovery expertise. SAM specialists know how to configure and interpret discovery tools. They know what reports to generate, what data is needed, how to classify edge cases. Without this expertise, DIY discovery is prone to errors.
Licensing rules expertise. Microsoft licensing: PUR (Product Use Rights), SPUR (Services PUR), Product Terms - hundreds of pages, changing. Oracle licensing: its own rules, processor factors, named user minimums. A SAM consultant knows these rules and their interpretation.
Optimization identification. An experienced SAM sees opportunities IT overlooks. “Here you can move the workload and save 50%,” “This deployment doesn’t require Enterprise,” “This configuration is licensed suboptimally.” Fresh eyes + expertise = found savings.
Negotiation support. SAM can participate in negotiations with the vendor as your advisor. Knows market rates, knows typical concessions, knows what arguments work. Levels the playing field with an account manager who has years of selling experience.
Audit defense preparation. True-up data may later be used in an audit. SAM ensures documentation is complete, defensible, following best practices. If an audit comes - you’re prepared.
Long-term SAM practice establishment. True-up isn’t a one-time event - it should be part of continuous SAM practice. SAM will help establish processes, tools, governance for the whole year, not just before deadline.
Table: True-up preparation checklist
| Area | Action | Timeline | Owner | Status |
|---|---|---|---|---|
| Discovery | Run inventory tools | M-6 | IT Ops | ⬜ |
| AD user extraction and classification | M-5 | Identity team | ⬜ | |
| Server inventory (physical + virtual) | M-5 | IT Ops | ⬜ | |
| Cloud subscription audit | M-5 | Cloud team | ⬜ | |
| Database discovery (SQL/Oracle) | M-4 | DBA | ⬜ | |
| Analysis | Entitlement vs. deployment comparison | M-3 | SAM | ⬜ |
| Optimization opportunities identified | M-3 | SAM | ⬜ | |
| Cost impact analysis | M-3 | Finance + SAM | ⬜ | |
| Optimization | Inactive user removal | M-2 | IT Ops + HR | ⬜ |
| License tier optimization | M-2 | IT Ops | ⬜ | |
| Server decommission/consolidation | M-2 | IT Ops | ⬜ | |
| Feature/edition downgrade | M-2 | DBA + IT Ops | ⬜ | |
| Preparation | Final count validation | M-1 | SAM | ⬜ |
| Report preparation | M-1 | SAM | ⬜ | |
| Legal review (if needed) | M-1 | Legal | ⬜ | |
| Negotiation strategy | M-1 | IT + Procurement | ⬜ | |
| Execution | Report submission | M-0 | SAM | ⬜ |
| Negotiation meetings | M-0 | IT + Procurement | ⬜ | |
| Sign-off and payment | M-0 | Finance | ⬜ | |
| Post | Documentation and archiving | M+1 | SAM | ⬜ |
| Lessons learned | M+1 | All | ⬜ | |
| Next year planning | M+1 | SAM | ⬜ |
True-up is the moment when years of (or lack of) SAM practice show in hard numbers on the invoice. Prepared companies pay for what they need. Unprepared companies pay for chaos, errors, and lack of optimization - often hundreds of thousands of zlotys more than they must.
Key takeaways:
- True-up preparation is a year-round process, not a last-minute sprint
- Discovery requires tools, time, and expertise - don’t guess, measure
- Optimization before deadline requires execution time - start minimum 3 months before
- Negotiations are possible - don’t accept the first number from the vendor
- Oracle ULA certification is a moment that defines costs for years
- Professional SAM pays for itself many times over in found savings
True-up doesn’t have to be stressful. With proper preparation, it becomes a routine operation that confirms you have control over your licenses - not the other way around.
ARDURA Consulting specializes in Software Asset Management and supporting clients through Microsoft, Oracle, and other vendor true-up processes. Our pre-true-up audits regularly identify savings in the hundreds of thousands of zlotys. Contact us minimum 3 months before your anniversary date.