Summary Under the proposed Cloud and AI Development Act (CADA), fees levied on members of the EuroCloud Federation are classified as internal assigned revenues. As proposed in Article 36(3), these funds are legally earmarked to cover the specific costs of the Commission's activities related to the Federation, such as assessing membership requests and maintaining the sharing platform. Any revenue remaining after these specific costs are covered is entered into the general budget of the Union, ensuring that the fee structure operates on a strict cost-recovery basis rather than generating profit for the EU budget.

Detail

The Cloud and AI Development Act (CADA) establishes the European public sector cloud federation, known as the "EuroCloud Federation," to facilitate the sharing of data centre and cloud computing services among Union entities and public sector bodies. A critical component of this framework is the financial mechanism that sustains the Federation's administration and platform operations without placing an undue burden on the general EU budget. This mechanism relies on the concept of internal assigned revenues.

The Legal Basis: Article 36

The financial rules governing the EuroCloud Federation are set out in Article 36 of the CADA proposal. This article establishes that the costs arising from the Commission's activities pursuant to the chapter on the EuroCloud Federation are jointly financed by the members through fees levied by the Commission.

Article 36(3) explicitly defines the nature of these fees within the EU's financial architecture:

"Revenues generated by the fees shall constitute internal assigned revenues within the meaning of Article 21(3), point (a), of Regulation (EU, Euratom) 2024/2509. Those revenues shall be assigned to cover the costs of the activities carried out by the Commission pursuant to this Chapter, including assessing request to join the EuroCloud Federation and the establishment of the platform referred to in Article 34(3). Any revenue remaining after covering those costs shall be entered into the general budget of the Union."

Understanding "Internal Assigned Revenues"

To understand the implications for compliance officers and in-house counsel, it is necessary to distinguish "internal assigned revenues" from general EU revenue. Under the Financial Regulation (Regulation (EU, Euratom) 2024/2509), Article 21(3)(a) defines internal assigned revenues as revenues that are:

  1. Derived from the European Union; and
  2. Assigned to cover specific expenditure items.

In the context of CADA, this means the fees paid by EuroCloud members are not general taxation or unallocated income. They are legally "ring-fenced" to fund the specific administrative and operational tasks the Commission performs to manage the Federation. These tasks include:

  • Assessing requests from public sector bodies to join the Federation.
  • Establishing and maintaining the technical platform for the exchange and orchestration of computing, storage, and network resources (as referenced in Article 34(3)).

Cost Recovery and Surplus Handling

The principle of internal assigned revenues ensures a direct link between the costs incurred by the Commission and the fees paid by the beneficiaries. This prevents cross-subsidization, where one part of the EU budget would otherwise have to fund the administrative overhead of the EuroCloud Federation.

However, the mechanism is not a perfect zero-sum game in practice. Article 36(3) acknowledges that the amount of fees collected may exceed the actual costs incurred in a given period. In such cases, the surplus is not retained by the Commission for discretionary use, nor is it returned directly to the members as a rebate. Instead, any remaining revenue is entered into the general budget of the Union. This aligns with the broader EU budgetary principles of unity and universality, where unspent assigned revenues revert to the general pot to fund other Union priorities.

Conversely, if the fees do not cover the costs, Article 36(2) provides a transitional safety net. If costs are initially borne by the general budget of the Union, they must be reimbursed by the EuroCloud members over a period not exceeding three years from the date the costs were incurred. This ensures that the long-term financial burden of the Federation remains with its users, as intended by the internal assigned revenue model.

Implementation and Calculation

The specific methodology for calculating these fees is not detailed in the primary text of CADA but is delegated to secondary legislation. Article 36(4) empowers the Commission to adopt implementing acts that lay down detailed rules for:

  • Determining the estimated costs.
  • Setting the individual amount of the fees.
  • Defining 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 that the fee structure is transparent, proportionate, and subject to scrutiny by the Member States and the European Parliament.

What this means for you

For in-house counsel and compliance officers in public sector bodies or entities preparing to join the EuroCloud Federation, the classification of fees as internal assigned revenues has several practical implications:

  1. Budgetary Predictability: You can expect fees to be calculated based on verifiable costs rather than arbitrary political decisions. The Commission is obligated to demonstrate the cost-effectiveness of its administration.
  2. Transparency Requirements: Because the fees fund specific activities (assessment and platform maintenance), you have a right to understand what those costs entail. The Commission will be required to report on the costs incurred and the total fees charged, ensuring accountability.
  3. No Profit Motive: The Commission is not seeking to profit from the EuroCloud Federation. Any surplus generated by your payments will return to the general EU budget, reinforcing that the fee is a cost-recovery mechanism, not a tax.
  4. Reimbursement Liability: If your entity joined the Federation during its initial setup phase when costs were borne by the general budget, be aware of the three-year reimbursement window outlined in Article 36(2). Your entity may be required to repay these initial setup costs as part of the fee structure.

Common misconceptions

  • "The fees are a tax on cloud usage." Incorrect. The fees are specifically for the administration of the Federation and the platform that facilitates sharing. They do not cover the actual cost of the cloud computing services themselves, which are governed by separate agreements between sharing and using entities under Article 35.
  • "Surplus fees are kept by the Commission." Incorrect. As per Article 36(3), any revenue remaining after covering the specific costs of the Federation's administration and platform must be entered into the general budget of the Union. The Commission cannot retain surplus funds for its own discretionary spending.
  • "Internal assigned revenues mean the money stays in a separate 'EuroCloud' bank account forever." Incorrect. While the revenue is "assigned" to cover specific costs, the legal mechanism ensures that once those costs are met, the remaining funds flow back into the general EU budget. It is a flow-through mechanism, not a permanent endowment.

Related

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