How are EuroCloud Federation fees calculated and paid under CADA?

Summary Under the proposed Cloud and AI Development Act (CADA), the EuroCloud Federation operates on a strict cost-recovery model. Article 36 mandates that all costs arising from the Commission's administration of the Federation are "jointly financed by the members of the EuroCloud Federation through fees levied by the Commission." These fees are not a profit mechanism but are designed to cover the specific expenses of assessing membership, establishing the sharing platform, and ongoing administration. Crucially, if the Union budget initially covers the upfront establishment costs, members are legally required to reimburse the Commission over a period "not exceeding three years" from the date those costs were incurred.

Detail

The EuroCloud Federation represents a significant shift in how the EU public sector manages cloud capacity, moving from isolated national silos to a federated, shared infrastructure. To ensure this initiative is financially sustainable without placing an undue burden on the general EU budget, the proposal establishes a precise funding framework. This framework is entirely grounded in the principle that the beneficiaries of the Federation—the Union entities and public sector bodies that join—must bear the costs of its operation.

The Legal Basis: Article 36 and Joint Financing

The financial architecture of the Federation is defined in Article 36 of the CADA proposal. The regulation explicitly 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 provision establishes two critical legal realities:

Joint Liability: The financial responsibility is shared among all members. No single entity bears the full cost of the platform's existence; rather, the collective membership funds the administration.
Commission as Levy Authority: The European Commission is the designated entity to calculate, set, and collect these fees. This centralizes the financial management, ensuring consistency across all participating Member States and Union entities.

The scope of costs covered by these fees is specific. They are limited to the activities required to make the Federation functional. As detailed in the proposal, these include the administrative burden of assessing requests to join the Federation, the technical and operational costs of establishing the platform described in Article 34(3), and the ongoing management of the sharing mechanism. The platform itself is designed to provide a catalogue of available services and a service platform for the exchange of computing resources, and the fees ensure this infrastructure remains operational.

Cost Recovery and the Nature of Assigned Revenues

A defining feature of the CADA proposal is that the EuroCloud Federation is not intended to be a revenue-generating enterprise for the EU. The fees are strictly for cost recovery. The proposal clarifies 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."

In EU budgetary terms, "internal assigned revenues" are funds that are directly linked to specific expenditure. This means the money collected from members cannot be diverted to other EU priorities; it must be ring-fenced to cover the costs of the Federation's administration. The regulation further stipulates that "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 in a given year, the surplus is returned to the general budget, preventing the accumulation of unallocated funds within the Federation's specific account.

This mechanism guarantees budgetary neutrality for the Commission's operations regarding the Federation. The system is designed so that the Commission recovers exactly what it spends, neither profiting nor losing money on the administration of the shared cloud infrastructure.

The Three-Year Reimbursement Rule

One of the most critical operational details for potential members concerns the timing of payments, particularly regarding the initial setup of the Federation. Establishing a new EU-wide digital platform requires significant upfront investment in technology, legal frameworks, and administrative setup before the first member joins or the first service is shared.

To facilitate a smooth launch, the proposal allows the Commission to initially bear these establishment costs using the general budget of the Union. However, this is a temporary advance, not a permanent grant. Article 36(2) contains a mandatory reimbursement clause: "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 three-year window is a hard legal limit. It ensures that the initial public investment is returned to the general budget within a predictable timeframe. For public sector bodies, this means that joining the Federation early in its lifecycle may involve a retroactive or phased payment obligation to cover the setup costs incurred by the Commission prior to their entry. This rule prevents the general EU budget from subsidizing the Federation indefinitely and ensures that the long-term financial burden rests squarely on the members who benefit from the shared capacity.

How Fees Are Calculated and Paid

The CADA proposal does not set a fixed euro amount or a specific percentage for the fees in the primary text. Instead, it delegates the technical details to the Commission through secondary legislation. 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 will be adopted following the examination procedure referred to in Article 46(2), which involves a committee of Member State representatives. This ensures that the final fee methodology is transparent, proportionate, and agreed upon by the stakeholders.

The implementing acts will likely address several key variables:

Cost Estimation: How the total administrative and platform costs are calculated for a given period.
Individual Allocation: The formula for distributing these total costs among members. This could be based on the size of the organization, the volume of capacity shared, or a flat membership fee, though the proposal emphasizes proportionality.
Payment Conditions: The specific timelines, invoicing methods, and currency for payments.

Until these implementing acts are adopted, the exact calculation remains a matter for the Commission's future rule-making. However, the principle is clear: the fees will be calibrated to cover the verifiable costs of the Commission's activities under the Federation chapter.

What this means for you

For public sector procurement officers, IT directors, and financial managers in Union entities and Member States, the fee structure of the EuroCloud Federation introduces a new, predictable cost line item that must be integrated into long-term digital strategies.

Budgeting for Membership and Setup When planning to join the EuroCloud Federation, you must account for two distinct financial obligations. First, there are the ongoing administrative fees levied by the Commission to cover the platform's operation. Second, if you join during the initial phase, you may be liable for a share of the setup costs initially borne by the EU budget. Because Article 36(2) mandates reimbursement within three years, your finance department should prepare for potential phased payments that could span multiple fiscal years. It is advisable to review your multi-year budget forecasts to ensure these future liabilities are covered.

Understanding the Cost-Benefit Ratio While the fees represent a new cost, they should be evaluated against the strategic value of the Federation. The fees cover the administration of a shared, sovereign infrastructure that allows members to access idle capacity from other public bodies. This can significantly reduce the need for individual entities to procure redundant infrastructure or rely on expensive commercial hyperscalers. The fee is essentially an administrative charge for accessing a coordinated, secure, and sovereign alternative. The cost recovery model ensures that this alternative remains financially sustainable without draining the general EU budget.

Transparency and Participation As the Commission prepares the implementing acts under Article 36(4), stakeholders will have the opportunity to provide input through the examination procedure. Public sector bodies should monitor these developments closely to understand how the "individual amount of the fees" will be determined. If the calculation method is based on usage or capacity shared, organizations should track their potential contribution to the Federation to better forecast their specific fee liability.

Distinction from Service Fees It is vital to distinguish the Commission's administrative fees from the fees charged between members for actual service usage. Article 35 allows a "sharing entity" to charge a fee to a "using entity" for the actual sharing of data centre or cloud services. However, that fee is strictly limited to the "costs that the sharing entity incurs in relation to the sharing of the service" (e.g., isolating resources, managing access). The fees under Article 36 are separate; they are paid to the Commission for the existence and administration of the Federation itself, not for the specific gigabytes or compute hours consumed.

Common misconceptions

Misconception 1: The fees are a tax or a profit center for the EU. Some may assume the Commission is using the Federation to generate surplus revenue. This is incorrect. The proposal is explicit: fees are for "cost recovery." Any surplus generated after covering the Commission's administrative costs is returned to the general budget. The system is designed to be financially neutral for the Commission, not a revenue generator.

Misconception 2: The fee amount is fixed in the law. The primary regulation does not state "€X per year." Instead, it delegates the calculation to implementing acts. This means the fee structure is flexible and can be adjusted by the Commission (with Member State oversight) to reflect the actual costs of running the platform as it scales. Members should not expect a static fee but rather a dynamic one tied to operational reality.

Misconception 3: Members only pay for the services they use. While members pay for the actual cloud services they consume from other members (under Article 35), they also pay an administrative fee to the Commission (under Article 36) simply for being part of the Federation. This administrative fee covers the platform, the membership assessment, and the governance structure, regardless of how much capacity an individual member shares or consumes.

Misconception 4: The reimbursement of setup costs is optional. The three-year reimbursement rule in Article 36(2) is mandatory. If the Union budget fronts the initial costs, members must reimburse the Commission within three years. This is not a voluntary contribution but a legal obligation for all members who benefit from the Federation's establishment.

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