Perfect paperwork, no licenses
A Czech hospital bought 90 Office licenses with flawless documentation. Verification directly with the companies in the license chain showed the transactions never took place. How to verify the origin of secondary software and what to put in the contract.
Ninety Office licenses, impeccable documentation, a working activation key and electronic signatures in all the right places. A Czech public hospital did everything a careful buyer could be expected to do when checking the delivery. Yet when we verified the license chain directly with the companies named in it, both confirmed in writing that the transactions described had never taken place.
Secondary software is legal in the European Union and, for many organizations, an economically sensible choice. Since the Court of Justice of the EU ruled in UsedSoft v Oracle (C-128/11), the rightholder's distribution right in a copy of a program has been exhausted by its first sale in the EU, and the license can be lawfully resold. The secondary market therefore rests on solid legal ground. What the specific license you are buying rests on, however, is a question that paperwork alone cannot answer.
A tender that looked exemplary
In summer 2026, a Czech public hospital launched a small-scale public contract for office software licenses. The winning bidder offered secondary software, that is, previously used perpetual licenses: 90 licenses of Microsoft Office LTSC Standard 2024 for CZK 450,000 excluding VAT.
The hospital received an electronic certificate with a single MAK (Multiple Activation Key) for 90 activations, a link to download the installation files, and documentation tracing the licenses step by step: European CSP distributor → first acquirer → supplier → hospital.
The check was thorough. The chain was consistent, the electronic signatures on the declarations were valid and the key activated successfully. By common standards, there was nothing to object to.
A warning sign
The supplier's name was familiar to us. In 2023, another contracting authority excluded it from a similar tender for Office licenses because, according to a publicly available decision, the information in its bid did not correspond to reality.
One detail was decisive. The license documentation described a purchase of licenses from a company that did not yet exist on the date of the stated transaction. The invoice was dated two weeks before the company was incorporated, and the documentation was electronically signed by the supplier's own managing director.
When the same supplier appeared in another tender, we decided to look into the delivery.
How we verified it
The verification took 48 hours. It required no special tools, just patience and ordinary contact with each link in the chain.
Freedom of information request. Under Act No. 106/1999 Coll., on Free Access to Information, we obtained a description of the delivery from the hospital: product, quantity, licensing program and the declared chain, including the license agreement number.
Query to the distributor. We asked the support team of the distributor at the start of the chain to check the order and provided the first acquirer's identification details.
Query to the first acquirer. We asked the company named as the first acquirer to confirm the sale to the supplier. It searched its records by the supplier's name, company ID, VAT number and address.
Comparison with the documentation. We set both answers against the documents the hospital had received from the supplier.
Two answers, one conclusion
Both the distributor and the first acquirer confirmed in writing that the transactions described in the documentation never took place.
Distributor: no order for 90 licenses exists in its system or in Microsoft's records. The license agreement number given in the documentation is not in its database.
First acquirer: the supplier never bought these licenses from it and purchased only two licenses of a different product. The first acquirer issued no declaration and is taking legal action against the unauthorized use of its name.
Yet the very same documentation passed the hospital's formal review without a single objection. That is the heart of the story.
Why a formal review is not enough
With secondary software, the end user's right to use the program derives from the law, not from a contract with the manufacturer. The Czech Copyright Act (Section 14(2)) and the case law of the CJEU, however, set one condition: it must be a copy that the rightholder actually placed on the market in the EU. None of the usual formal checks verifies that condition:
A consistent chain of documents proves that the documents refer to one another. It does not prove that the transactions took place.
A valid electronic signature proves who signed the document. It does not prove that its content is true.
A working MAK key proves that the key currently activates. It does not prove that the license was lawfully acquired.
A signed declaration proves that someone declared something. It does not prove that the declaration came from the party it claims to come from.
There is only one way to verify a license's origin: by asking each link in the chain directly. Today, anyone can produce a neat, electronically signed document, as Igor Weinlich points out in the interview An activation key is not a license [link]. The appearance of a document says nothing about whether its content is true.
What the buyer risks
Anyone using licenses without proper provenance is using software without authorization, even if they bought it in good faith. Liability lies with the user, not the seller.
Vendor audit: without documented provenance, the licenses must be repurchased, usually at full price.
Key blocking: the vendor can block the MAK key. Office will then fail to activate, with knock-on effects on any systems that depend on it.
Rightholder claims: in the event of unauthorized use, the rightholder may claim the surrender of unjust enrichment, which under the Czech Copyright Act amounts to at least twice the usual license fee.
Security: with installation files of unclear origin, tampering cannot be ruled out. In an environment that handles sensitive data, such as a hospital, that alone is a serious risk.
Value for money: the delivery paid for may not be worth what was paid. For public contracting authorities, this may also attract the attention of oversight bodies.
Software acquired this way cannot be legalized after the fact.
Checklist: how to verify secondary software
Full chain. Request documentation all the way back to the official distributor, not just the last invoice.
Verification at source. Contact each link in the chain directly, not through the supplier. Verify that the licenses exist, not just on paper. A perfect “original” and an electronic signature are not proof.
Dates. Company incorporation dates, invoice dates and transfer dates must be consistent. Check them in the Commercial Register.
Payments. Ask for proof of payment between each link in the chain.
Installation. Download installation files only from official Microsoft sources.
Supplier history. Check the supplier's previous contracts, including any exclusions.
A key is not proof. Successful activation says nothing about a license's origin.
Independent audit. Licenses whose origin has already been verified by an independent auditor are also a reliable option. The auditor's report confirms that the licenses were lawfully acquired and transferred, so you do not have to verify the chain yourself.
License provenance should not be a secret
The most effective safeguard can be built into the contract itself. Information proving the origin of licenses cannot be a trade secret. Whoever genuinely holds the licenses has no reason to hide their origin, and every subsequent acquirer, auditor and oversight body must be able to verify it.
Whether you buy through a public tender or a regular corporate purchase, we recommend including the following clause in the contract:
Information and documents proving the origin and transfer of the licenses (the “License Provenance Documentation”) do not constitute a trade secret or confidential information of either contracting party. This applies notwithstanding any other provisions of this contract or any other confidentiality agreement between the parties. License Provenance Documentation includes, in particular:
identification of the first and all subsequent acquirers,
license agreement numbers (e.g. Enterprise Agreement, Open License, MPSA, CSP, OEM) and authorization numbers,
type, edition, version and number of licenses and date of acquisition,
proof of acquisition,
uninstallation declarations,
details of the independent auditor (company name, company ID, registered office) and its audit report or certificate for the specific license.
The Seller agrees that the Buyer may disclose the License Provenance Documentation to subsequent acquirers, to the licensor and auditors appointed by it, and to distributors, courts and public authorities. The Buyer may do so for the purpose of demonstrating the exhaustion of the distribution right that occurred upon the first sale of the licenses within the EU/EEA pursuant to Section 14(2) of the Czech Copyright Act.
Such a clause places no burden on suppliers with lawfully acquired licenses. It does, however, take away the option of hiding behind confidentiality from anyone who does not actually hold the licenses. If the original owner does not want to reveal its contracts and prices to every subsequent buyer, there is an elegant solution: an independent auditor's report. We explain what such a report actually proves in How to verify the origin of secondary software and what an independent auditor's report proves [link].
Does this concern you?
If you have bought Microsoft licenses in recent years, it is worth verifying their origin. The approach depends on the type of license:
Secondary software: verify the entire license chain directly with the companies named, not just on the basis of documents from the supplier (see the checklist above).
New licenses (Volume Licensing, CSP): check through which channel they were delivered. Properly purchased licenses are visible in your organization's own Microsoft account, for example in the Microsoft 365 admin center or the Volume Licensing portal. If you only have a key and an invoice but cannot see the licenses in your account, be cautious.
OEM licenses: an OEM license is tied to a specific device and is supplied with it. Make sure the Certificate of Authenticity (COA) labels were not acquired separately, for example from online auctions. A label on its own is not a license.
How Forscope can help
We verify license provenance physically, with each link in the chain, and give you the results in writing. That way you have certainty before an audit arrives. We supply secondary software with a documented history or verified by an independent auditor, and we help set up contract terms so that a formal review is not your only safeguard.
We will verify your licenses
Want to be sure your licenses will stand up to an audit? We'll verify them. Contact us.
Related articles
An activation key is not a license. How can you verify the origin of secondary software?
How to verify the origin of secondary software and what an independent auditor's report proves