How is the EuroCloud Federation financed under CADA?

Summary The proposed Cloud and AI Development Act (CADA) establishes the EuroCloud Federation on a self-financing model. Rather than relying on permanent allocations from the general EU budget, the Commission recovers the costs of establishing and managing the Federation by levying fees on its members (Union entities and public-sector bodies). Under Article 36(3), these fee revenues are classified as internal assigned revenues, meaning they are legally ring-fenced to cover only the specific costs of the Federation's activities. Any surplus generated beyond these costs must be returned to the general budget of the Union. While Article 36(2) allows the general budget to cover initial setup costs, these must be reimbursed by members within three years, ensuring the long-term financial independence of the initiative.

Detail

The EuroCloud Federation, as proposed in Title IV, Chapter III of the Cloud and AI Development Act (CADA), is designed to facilitate the sharing of data centre services and cloud computing services among Union entities and public-sector bodies. A defining characteristic of this framework is its financial architecture, which prioritizes sustainability and cost recovery over permanent public subsidy. The proposal explicitly avoids creating a new, ongoing burden on the general EU budget for the Federation's daily operations.

The Self-Financing Mechanism under Article 36

The core financial principle of the EuroCloud Federation is established in Article 36(1), which states that "the costs arising from the activities carried out by the Commission pursuant to this Chapter shall be jointly financed by the members of the EuroCloud Federation through fees levied by the Commission."

This creates a direct "user-pays" relationship. The entities that benefit from the Federation's platform—by sharing idle capacity, accessing a catalogue of services, or utilizing the orchestration tools—contribute directly to the costs of maintaining that infrastructure. The scope of costs covered by these fees is comprehensive, encompassing:

The establishment and ongoing maintenance of the digital platform that facilitates the sharing of services.
The administrative assessment of membership applications from Union entities and public-sector bodies.
The operational management of the Federation, including the governance mechanisms required to ensure secure and compliant data sharing.

By mandating that members jointly finance these activities, the proposal ensures that the Federation scales with its usage. As more entities join and the platform's operational complexity grows, the fee base expands to cover the corresponding costs, preventing a scenario where the initiative becomes underfunded as it matures.

Internal Assigned Revenues: The Legal Status of Fees

A critical legal distinction in the CADA proposal is the classification of the revenue generated by these fees. Article 36(3) explicitly provides that "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" (the Financial Regulation).

In EU budgetary law, internal assigned revenues are a specific category of income. Unlike general revenue, which flows into the Union's general budget and is allocated through the annual budgetary procedure for any purpose, assigned revenues are "earmarked." This means the money collected from EuroCloud Federation members is legally bound to finance only the specific expenditures related to the Federation.

The implications of this classification are significant:

Ring-fencing: The funds cannot be diverted to other Commission priorities or general administrative costs. They must be used exclusively to cover the costs of the activities carried out by the Commission under the EuroCloud Federation chapter.
Budgetary Neutrality: The model aims for budgetary neutrality regarding the Federation's operations. The Commission does not seek to generate profit; the fees are calculated to match the costs incurred.
Surplus Handling: Article 36(3) further clarifies the treatment of any excess funds: "Any revenue remaining after covering those costs shall be entered into the general budget of the Union." This prevents the accumulation of a "slush fund" within the Federation's account and ensures that any over-collection is returned to the broader EU financial system, reinforcing the principle that the fees are strictly for cost recovery.

Initial Costs and the Three-Year Reimbursement Rule

Recognizing that a new initiative requires upfront investment before it can generate revenue, Article 36(2) provides a mechanism for initial funding. It states: "If the costs are initially borne by the general budget of the Union, they shall be reimbursed by the EuroCloud members over a period not exceeding three years from the date on which the costs were borne by the Union."

This clause serves as a bridge. It allows the Commission to use the general budget to launch the platform, assess applications, and set up the governance structures without waiting for the first fee payments. However, this is not a permanent subsidy. The obligation to reimburse is mandatory and time-bound. The three-year cap ensures that the transition to the self-financing model is swift, preventing the general budget from carrying the weight of the Federation's operations indefinitely.

Determining the Fee Structure

The primary legislation (the Regulation itself) does not fix the exact amount of the fees. Instead, it establishes the framework for their calculation and collection. Article 36(4) empowers the Commission to "adopt implementing acts laying down detailed rules for determining the estimated costs, the individual amount of the fees, and 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) of CADA. This means that a committee of Member State representatives will scrutinize and vote on the proposed fee rules before they can enter into force. This comitology process ensures that the fee structure is transparent, proportionate, and subject to democratic oversight by the Member States. The implementing acts will specify:

How the estimated costs are calculated (e.g., based on platform development, staff time, hosting costs).
The methodology for determining individual fee amounts (e.g., flat fee per member, or proportional to usage).
The payment schedule and conditions.

This flexibility allows the Commission to adjust the fee structure as the Federation evolves, ensuring that the costs remain aligned with the actual operational needs of the platform.

What this means for you

For public-sector bodies, Union entities, and IT procurement officers, the financing model of the EuroCloud Federation has distinct practical implications for budgeting and strategic planning.

1. Budgetary Planning and Forecasting

You must anticipate that participation in the EuroCloud Federation will incur a direct, recurring cost. Unlike some EU initiatives that are fully grant-funded, the Federation operates on a cost-recovery basis. When preparing your annual IT or procurement budgets, you should include a specific line item for "EuroCloud Federation fees." These fees are not optional for members; they are the mechanism by which the platform is sustained.

2. Cost Recovery vs. Profit

It is important to understand that the fees are not a revenue-generating tool for the EU. The legal framework mandates that fees be set at a level "sufficient to cover those costs" but not to generate a surplus for the Commission. This suggests that the Federation could be a cost-effective alternative to individual procurement, as the fees reflect only the administrative overhead of the shared platform, not a profit margin. For smaller public authorities, this shared cost model may offer significant economies of scale compared to building or procuring sovereign cloud capabilities in isolation.

3. Transparency and Predictability

The fee structure will not be arbitrary. Because the Commission must adopt implementing acts to define the fees, and these acts are subject to the examination procedure, the methodology will be transparent. You will have access to the detailed rules explaining how your specific fee amount is derived, allowing for accurate long-term financial planning.

4. Transition Period Management

If your entity joins the Federation during its initial phase, be aware that the general budget may cover the setup costs initially. However, under Article 36(2), you will be required to reimburse these costs within a maximum of three years. This means that even if the initial launch appears "free," your budget must account for the reimbursement obligation in the medium term.

Common misconceptions

Misconception 1: The EuroCloud Federation is a free service funded entirely by the EU budget. While the initial setup costs may be temporarily covered by the general budget, the Federation is explicitly designed to be self-financing. Article 36(1) mandates that members jointly finance the costs through fees. The general budget is not a permanent funding source for the Federation's operations.

Misconception 2: The fees collected will be used to fund other EU digital projects. This is incorrect. Article 36(3) classifies the fee revenues as "internal assigned revenues." This legal status means the money is ring-fenced. It can only be used to cover the costs of the EuroCloud Federation activities. Any surplus must be returned to the general budget; it cannot be diverted to other Commission initiatives.

Misconception 3: The fee amount is fixed in the CADA proposal. The Regulation does not set a specific euro amount. Instead, Article 36(4) delegates the power to the Commission to adopt implementing acts that determine the exact fees. This allows the fee structure to be adapted to the actual costs of the platform and the number of members, subject to Member State approval via the examination procedure.

Misconception 4: The Federation is a tax on public-sector cloud usage. The fees are not a general tax. They are a specific charge for the administrative and platform services provided by the Commission. They are directly linked to the costs of maintaining the EuroCloud platform and assessing membership, ensuring a direct link between the service provided and the cost incurred.

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