Summary Under the proposed Cloud and AI Development Act (CADA), the European Commission would act as a central purchasing body for public entities, with costs recovered through a strict fee mechanism defined in Article 40. These fees are not arbitrary; they must be set in advance, determined in a cost-effective way, and be proportionate to the estimated direct and indirect costs incurred by the Commission. Crucially, the proposal allows initial costs for establishing the common procurement platform to be borne by the general EU budget, with participating entities required to reimburse these costs over a period not exceeding three years. This ensures budget neutrality while enabling the framework to launch without immediate capital barriers for public buyers.
Detail
The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a novel mechanism to leverage the collective purchasing power of the EU public sector. By allowing the Commission to act as a central purchasing body for cloud computing services, data centre services, software, and AI systems, the Act aims to secure better terms, reduce administrative burdens, and foster a resilient European digital ecosystem. However, the financial sustainability of this mechanism is a cornerstone of the proposal, governed explicitly by Article 40 of the draft regulation.
The Cost-Recovery Principle: No Profit, Only Coverage
The fundamental financial philosophy underpinning the Commission's procurement activities in CADA is cost recovery. Article 40(1) establishes that the costs arising from these procurement activities shall be jointly financed by the participating entities through fees levied by the Commission.
This provision ensures that the operational costs of the central purchasing framework do not drain the general EU budget indefinitely. Instead, the entities that benefit from the serviceβMember States' contracting authorities, Union entities, and selected partner organisationsβcontribute to its upkeep. The regulation is explicit that the Commission is not a commercial entity in this context; it does not seek to generate profit. The fees are strictly designed to cover the expenses incurred in executing the procurement activities.
How Fees Are Determined: The Four Criteria
Article 40(4) provides a rigorous framework for calculating these fees, preventing arbitrary pricing and ensuring fairness for public buyers. The fees must satisfy four cumulative conditions:
- Set in Advance: Fees cannot be retroactive or surprise charges. They must be established before the procurement activities commence, allowing public buyers to plan their budgets accurately.
- Proportionate: The fee amount must be directly proportional to the estimated costs of the specific activities for which the fee is chargeable. A larger procurement volume or more complex procedure would logically incur higher fees, but the ratio must remain fair.
- Cost-Effective: The determination of fees must reflect a cost-effective approach, ensuring that the administrative overhead of collecting the fee does not exceed the value it covers.
- Reflective of Comparable Frameworks: The methodology must align with practices found in other comparable procurement frameworks, ensuring consistency with international and EU standards for central purchasing bodies.
- Sufficient to Cover Costs: Finally, the fees must be sufficient to cover the total costs incurred. This ensures the financial viability of the platform without requiring external subsidies for ongoing operations.
The Role of Implementing Acts
The specific numerical values or detailed formulas for these fees are not hardcoded in the regulation itself. Instead, Article 40(5) empowers the Commission to adopt implementing acts to lay down the detailed rules. These acts will specify:
- The estimated costs attributable to the procurement activities.
- The individual amounts of the chargeable fees.
- The manner and conditions under which the fees are to be paid.
These implementing acts are subject to the examination procedure referred to in Article 46(2), ensuring that the European Parliament and the Council have oversight over the fee-setting methodology. This democratic scrutiny is vital for maintaining trust in the financial arrangements of the proposed Act.
Reimbursement of Initial Setup Costs: The Three-Year Rule
A critical feature of the proposal is its handling of the "chicken-and-egg" problem of launching a new digital platform: who pays for the initial development? Article 40(2) addresses this by allowing the costs incurred in establishing the common procurement activitiesβincluding the development of the common procurement platformβto be initially borne by the general budget of the Union.
However, this is a temporary bridge, not a permanent grant. The regulation mandates that these initial establishment costs shall be reimbursed by the participating entities over a period not exceeding three years from the date on which they were borne by the Union.
This mechanism serves two purposes:
- Lowering Entry Barriers: It allows the framework to launch without requiring participating public bodies to front large capital sums for platform development, which could deter early adoption.
- Ensuring Long-Term Sustainability: By spreading the reimbursement over three years, the financial impact is smoothed out, allowing the fee structure to mature as the platform becomes operational and generates regular revenue.
Financial Flow: Internal Assigned Revenues
The financial architecture of CADA procurement is designed to be transparent and ring-fenced. Article 40(3) states that revenues generated by these fees shall constitute internal assigned revenues within the meaning of Article 21(3), point (a), of Regulation (EU, Euratom) 2024/2509 (the Financial Regulation).
This classification means that the money collected from participating entities is legally earmarked specifically to cover the costs of the procurement activities carried out pursuant to Article 37. It cannot be diverted to other Commission priorities. Furthermore, the regulation includes a "clawback" mechanism: any revenue remaining after covering those costs shall be entered into the general budget of the Union. This ensures that if the fees collected exceed the actual costs incurred, the surplus returns to the EU's general coffers rather than being retained by the Commission. This strict adherence to budget neutrality reinforces the non-profit nature of the initiative.
Scope of Covered Costs
It is important to distinguish what these fees cover. Under Article 37, the Commission's role includes providing ancillary support such as:
- Technical infrastructure enabling entities to use awarded contracts.
- Advice and support on preparing and implementing procurement procedures.
- Preparation and conduct of procurement procedures on behalf of entities.
- Invoicing and administrative services.
The fees levied under Article 40 cover the operational and administrative costs of providing these services. They do not cover the price of the cloud computing services, software, or AI systems themselves. Those costs are part of the contract with the vendor and are paid separately by the participating entity. The Article 40 fee is essentially the "service charge" for the Commission's role as the central buyer and platform manager.
What this means for you
For public-sector procurement officers, legal counsel, and financial managers in Member States and Union entities, the fee structure under the proposed CADA has several practical implications:
- Predictable Budgeting: Because fees must be set in advance and defined in implementing acts, you will not face unexpected cost spikes. You can factor the fee into your total cost of ownership (TCO) calculations for cloud and AI projects with greater confidence.
- Cost-Effectiveness vs. Independence: While there is a fee, the proposal argues that the economies of scale achieved through joint procurement will result in better vendor pricing and terms than individual national procurements. The fee is an investment in accessing these superior market conditions.
- Transparency of Methodology: The requirement for the Commission to adopt implementing acts means the fee calculation methodology will be public. You will be able to scrutinize how the "proportionate" and "cost-effective" criteria are applied.
- Transition Planning: If your entity joins the framework early, be aware of the three-year reimbursement period for initial platform costs. This might influence the fee structure during the first few years of operation as the system recovers its setup investment.
- No Hidden Profits: You can be assured that the Commission is not acting as a commercial reseller. The internal assigned revenue mechanism and the requirement to return surplus to the general budget guarantee that your fees are strictly for cost recovery.
Common misconceptions
Misconception 1: The Commission will charge a profit margin on these procurement services. Reality: Article 40(4) explicitly requires fees to be "sufficient to cover those costs" and "proportionate." Article 40(3) mandates that any surplus revenue be entered into the general budget. There is no legal basis for the Commission to retain a profit from these activities.
Misconception 2: Fees are arbitrary and can be changed at the Commission's discretion. Reality: Fees are not discretionary. They must be set in advance via implementing acts adopted under the examination procedure (Article 46(2)). This process involves scrutiny by Member State representatives and ensures the methodology is transparent, cost-effective, and aligned with comparable frameworks.
Misconception 3: Public buyers must pay the full cost of the platform development upfront. Reality: Article 40(2) allows the general EU budget to cover initial establishment costs. Participating entities only reimburse these costs over a period not exceeding three years, smoothing the financial impact and avoiding a large upfront capital burden.
Misconception 4: The fee covers the cost of the cloud services being purchased. Reality: The fee under Article 40 covers the administrative and operational costs of the procurement process (e.g., platform maintenance, legal support, tender management). The actual cost of the cloud services, software, or AI systems is paid separately to the vendor as part of the contract.
Related
- When can a public buyer use a derogation from CADA's assurance-level procurement rules?
- CADA Public Procurement Checklist: Risk Assessments, Assurance Levels & Added Value
- How does a startup get its cloud service in front of CADA public buyers?
- How do public buyers find recognised cloud services on the CADA central repository?
- Who pays for the independent audit under CADA? Costs for Levels 1β4
This is general information about a draft EU regulation, not legal advice.