Summary Under the proposed Cloud and AI Development Act (CADA), the costs for the Commission's central procurement activities are jointly financed by participating entities through fees levied by the Commission, as mandated by Article 40(1). These fees are designed to cover all direct and indirect costs of the procurement activities and ancillary services, ensuring the framework is self-sustaining. Crucially, while initial establishment costs for the common procurement platform may be pre-financed by the Union's general budget, Article 40(2) requires these costs to be reimbursed by participating entities within a period not exceeding three years. These fees are legally and financially distinct from the administration fees applicable to the EuroCloud Federation under Article 36.

Detail

The proposed Cloud and AI Development Act (CADA) introduces a novel financial mechanism to support the European Commission's role as a central purchasing body for cloud computing services, AI systems, and software. To ensure this mechanism is financially sustainable and does not create a permanent burden on the EU budget, CADA establishes a specific fee structure governed primarily by Article 40 of the proposal. This section details how costs are allocated, calculated, and reimbursed for the common procurement framework.

Joint Financing Through Fees

The foundational principle of the financial model is explicitly set out in Article 40(1), which states that the costs arising from the procurement activities carried out pursuant to Chapter IV of Title IV shall be "jointly financed by the participating entities through fees levied by the Commission."

This provision establishes a "user-pays" model. The European Commission does not absorb the operational costs of these centralized procurement exercises from the general budget on a permanent basis. Instead, the entities that benefit from the Commission's central purchasing powerβ€”specifically contracting authorities of Member States, Union entities, and partner organisations selected by the Commissionβ€”contribute to the cost base. The fees are intended to create a closed financial loop where the users of the service fund its administration and execution, aligning with the principle of cost recovery for specific administrative services.

Scope of Costs Covered

The fees levied under Article 40 are comprehensive and extend beyond simple transaction fees. According to the text of the proposal, the fees must be sufficient to cover:

  • All direct costs incurred by the Commission in connection with the procurement activities.
  • All indirect costs associated with these activities.
  • Any ancillary services provided, such as technical infrastructure support, advice on preparing procurement procedures, or invoicing services (as referenced in Article 37(4)).

The fees are to be set in advance and must be proportionate to the estimated costs of the activities for which fees are chargeable. Article 40(4) mandates that these fees reflect practices of comparable procurement frameworks and are determined in a cost-effective manner. This ensures that the fees are not punitive but rather a fair reflection of the administrative effort required to manage the central procurement framework.

Pre-financing and Reimbursement of Set-Up Costs

Recognizing that launching a new common procurement platform requires significant upfront investment that cannot be immediately recovered, CADA provides a specific mechanism for initial funding. Article 40(2) specifies that the costs incurred in establishing the common procurement activities, including the development of the common procurement platform, "may be initially borne by the general budget of the Union."

However, this is a temporary measure, not a permanent subsidy. The same paragraph explicitly requires that these initial 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 provision ensures that while the Union can facilitate the rapid start-up of the framework to meet strategic needs, the long-term financial responsibility remains with the participating entities. The Commission is empowered to adopt implementing acts to lay down the practical and operational arrangements for this reimbursement process, ensuring transparency in how the recoupment is calculated and collected.

Revenue Allocation and Ring-fencing

The financial architecture of CADA ensures that fee revenue is strictly ring-fenced for its intended purpose. Article 40(3) states that revenues generated by the fees shall constitute "internal assigned revenues" within the meaning of Article 21(3)(a) of Regulation (EU, Euratom) 2024/2509 (the Financial Regulation).

These revenues are assigned specifically to cover the costs of the procurement activities carried out pursuant to Article 37. Any revenue remaining after covering these costs shall be entered into the general budget of the Union. This structure prevents the accumulation of surplus funds within the Commission for unrelated purposes and ensures transparency in how procurement-related funds are managed. It guarantees that the fees collected are directly linked to the services provided.

Implementation and Detailed Rules

While Article 40 sets the high-level principles, the specific mechanics of fee calculation, payment schedules, and cost attribution are to be detailed in secondary legislation. Article 40(5) empowers the Commission to adopt implementing acts specifying:

  • The estimated costs attributable to the procurement activities for which fees are chargeable.
  • The individual amounts of the chargeable fees.
  • The manner and conditions under which the fees are to be paid.

These implementing acts will be adopted in accordance with the examination procedure referred to in Article 46(2), ensuring a level of scrutiny and coordination with Member States regarding the financial burden placed on them. This process allows for adjustments based on actual participation levels and cost realities.

Distinction from EuroCloud Federation Fees

It is critical for public sector officers and financial controllers to distinguish between the fees for central procurement activities (Article 40) and the fees for the EuroCloud Federation (Article 36). These are two separate mechanisms with different purposes, cost structures, and legal bases:

  • Central Procurement Fees (Article 40): Apply specifically to the Commission's role as a central purchasing body for cloud services, AI systems, and software. These fees cover the administrative and operational costs of running the procurement process itself (e.g., tendering, contract management, platform maintenance for procurement).
  • EuroCloud Federation Fees (Article 36): Apply to the administration of the European public sector cloud federation. These fees cover the costs of the Commission's activities in assessing membership applications, managing the platform for sharing idle capacity, and maintaining the federation's infrastructure.

While both are financed by fees levied on participants and constitute internal assigned revenues, they are calculated independently. A participating entity may be subject to both types of fees if it engages in both the common procurement framework and the EuroCloud Federation. Confusing the two could lead to budgeting errors or compliance issues.

What this means for you

For public-sector procurement officers and financial managers, the fee structure under Article 40 implies a significant shift towards a user-pays model for centralized EU procurement activities.

  1. Budget Planning: You must account for these fees in your annual or multi-annual budget planning. While the Commission's central purchasing power may lead to better pricing for cloud and AI services through economies of scale, the administrative fees for using the central framework are an additional cost that must be factored into the total cost of ownership.
  2. Cost Predictability: Since fees are set in advance and must be proportionate to estimated costs, you should expect a degree of predictability. However, as the Commission adopts implementing acts under Article 40(5), stay vigilant for updates on how these fees will be calculated (e.g., as a percentage of contract value, a flat fee per transaction, or a tiered structure based on entity size).
  3. Reimbursement Timeline: If your entity benefits from the initial setup of the common procurement platform, be aware that the Union budget's initial investment will be recouped from participants within three years. This creates a clear timeline for when the full fee burden will be realized, allowing for phased financial planning.
  4. Separate Accounting: Ensure your financial systems can distinguish between fees paid for procurement services (Article 40) and any fees associated with the EuroCloud Federation (Article 36). These will likely be invoiced separately, serve different compliance and reporting requirements, and relate to distinct activities (buying vs. sharing capacity).

Common misconceptions

Misconception 1: The EU budget fully funds the central procurement framework. Reality: While the Union budget may initially cover the set-up costs of the common procurement platform, Article 40(2) requires full reimbursement from participating entities within three years. Long-term operational costs are entirely funded by participant fees, not the general budget.

Misconception 2: These fees are a tax on cloud usage. Reality: The fees under Article 40 are specifically for the procurement activities and ancillary services provided by the Commission. They are not a general tax on the use of cloud or AI services, nor are they linked to the volume of data processed or compute power used. They are strictly administrative costs for the purchasing mechanism.

Misconception 3: EuroCloud Federation fees cover procurement costs. Reality: The fees for the EuroCloud Federation (Article 36) and central procurement (Article 40) are distinct. EuroCloud fees relate to the sharing of idle capacity and federation administration, while procurement fees relate to the Commission's role as a central purchasing body. Participating in one does not exempt an entity from fees in the other if they engage in both.

Related

This is general information about a draft EU regulation, not legal advice.