The ELP Evidence File That Holds Up

A reconciled Effective License Position is only as strong as the file behind it. When you tell an auditor that a workload is test, that an entitlement exists, or that an instance was double counted, the claim holds only if you can produce the record that proves it. Microsoft's count is built from its own methodology and its own telemetry, and a correction with no evidence behind it is just an assertion. This article sets out the evidence file that survives challenge: what it contains, how it is organized, and why assembling it before an audit, not during one, is what makes it work.

Why the file decides the argument

In a formal audit a third party accounting firm produces the ELP, and Microsoft's calculation governs unless you can show it is wrong. The operative word is show. Every favorable correction you want, more entitlement credited, less deployment counted, the 5 percent threshold not crossed, has to be backed by a document the auditor can verify. The buyers who reduce their exposure are not the ones with the best arguments. They are the ones with the best files. The file is the difference between a position the auditor accepts and one they set aside.

The entitlement side of the file

Entitlement is where buyers most often leave money on the table, because rights they genuinely hold were never credited. The file has to make those rights undeniable.

• Every active agreement, with the editions, quantities, and terms it grants
• Purchase records and license confirmations across the full history, including older agreements
• Rights and benefits that apply, with the conditions that make them valid documented
• Any reassignment or transfer of licenses, with the dates that govern them

The goal is that no license you are entitled to is invisible to the reconciliation. Anything the auditor cannot see, they will not credit.

The deployment side of the file

Deployment is where overcounting happens, and the file has to give context the raw telemetry lacks. For each material workload you want to characterize, keep the proof of what it actually is.

• Evidence that an environment is test, development, or non production rather than production use
• Records that identify when the same workload appears in two data sources, to defeat double counting
• Configuration evidence that passive or failover instances are genuinely passive
• Sign in and assignment records that show which users actually consumed a product

The reconciliation that ties it together

The two sides meet in a reconciliation that maps deployment to entitlement product by product, with each adjustment pointing to its supporting record. This is the spine of the file. A good reconciliation does not just state a net position. It shows the path from Microsoft's likely count to your defended count, line by line, so an auditor can follow and check each step. When the reconciliation is traceable, the conversation moves from whether your number is plausible to whether each specific document is valid, which is a far stronger place to stand.

What a holds up file looks like in practice

The summary below is indicative and shows the structure, not real quantities.

Indicative structure of a defensible evidence file, not real quantities.

Build it before you need it

The evidence file is far cheaper to build before an audit than under one. Assembled in advance, it becomes your own position, ready to meet the auditor's report rather than scrambling to answer it. Built under deadline, records are missing, classifications are guessed, and the auditor's count wins by default. The most defensible buyers treat the file as a standing asset, kept current, so that when an audit arrives the reconciliation is already done. For how to construct it from scratch, see documenting your reconciliation, and for the discipline of reconciling the two sides, read reconciling deployment to entitlement. Both sit under the pillar guide.

The next step

If you want a file that holds up against a third party auditor, the fastest route is to build it with people who know exactly what the auditor will test. We assemble defensible ELP evidence files and reconcile them against the way Microsoft will count, on a Fixed Fee from $18,000 or a Gainshare share of verified savings with zero retainer and no risk to you. Our guarantee is simple: we reduce your exposure or we reimburse our service fee. Read the full method in the Effective License Position Guide, then get a quote.

When the numbers start to look serious, our ELP exposure modeling service builds your own defensible position first.