Summary As proposed in the Cloud and AI Development Act (CADA), the European Commission may initially bear the start-up costs of the EuroCloud Federation from the Union's general budget. However, these costs are not a permanent grant; they must be reimbursed by the Federation's members. Under Article 36(2), this reimbursement must occur over a period not exceeding three years from the date the costs were incurred. The mechanism relies on Article 36(3), which designates the fees levied by the Commission as "internal assigned revenues" strictly ring-fenced to cover the Federation's operational and administrative costs, ensuring no surplus is generated for the general budget.

Detail

The EuroCloud Federation, established under Article 34 of the proposed CADA, aims to facilitate the sharing of public sector data centre and cloud computing services between Union entities and Member State public sector bodies. To ensure the Federation's financial sustainability and prevent long-term reliance on the general EU budget, Article 36 establishes a precise cost-recovery framework.

Initial Funding and the Three-Year Reimbursement Rule

The proposal acknowledges that establishing a new digital platform and governance structure requires significant upfront capital. Article 36(1) states that the costs arising from the Commission's activities related to the EuroCloud Federation shall be jointly financed by its members through fees levied by the Commission.

However, to facilitate the launch, Article 36(2) provides a specific derogation for initial establishment costs. It stipulates:

"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 provision ensures that while the Union budget can act as a bridge to launch the initiative, the financial burden is ultimately shifted to the participating public entities that benefit from the service. The three-year cap prevents indefinite reliance on taxpayer funds for foundational infrastructure.

The Assigned Revenue Mechanism

The financial architecture of the EuroCloud Federation relies on the concept of "internal assigned revenues." Article 36(3) explicitly classifies the revenues generated from the membership fees levied under Article 36(1) as internal assigned revenues within the meaning of Article 21(3)(a) of Regulation (EU, Euratom) 2024/2509 (the EU Financial Regulation).

This classification is critical for budgetary discipline and transparency. It means that:

  1. Ring-fencing: The fee income is strictly allocated to cover the costs of the activities carried out by the Commission pursuant to Chapter III of Title IV of CADA. These activities include assessing requests to join the Federation and establishing/maintaining the platform referred to in Article 34(3).
  2. No Surplus: Any revenue remaining after covering these specific costs "shall be entered into the general budget of the Union." This prevents the Commission from accumulating a profit or surplus from the Federation's operations.

Determining Fee Amounts and Payment Conditions

The primary legislation (the CADA proposal) does not fix specific fee amounts. Instead, Article 36(4) empowers the Commission to adopt implementing acts to lay down detailed rules for:

  • Determining the estimated costs attributable to the Federation's activities.
  • Calculating the individual amount of the fees.
  • Specifying the manner and conditions under which the fees are to be paid.

These implementing acts must be adopted in accordance with the examination procedure referred to in Article 46(2), ensuring Member State oversight during the rule-making process. This allows the fee structure to be adapted to the actual costs incurred and the number of participating members.

What this means for you

For public-sector procurement officers, IT managers, and financial controllers, this framework implies a clear, phased financial obligation for participating in the EuroCloud Federation.

  1. Anticipate Reimbursement Liabilities: If your entity joins the Federation during its initial phase, you must anticipate a potential liability to reimburse the Union's initial set-up costs. While the Commission may front these costs, your entity will be required to pay them back over a maximum three-year window. This should be factored into multi-year IT and administrative budgets.
  2. Monitor Implementing Acts: The exact fee you will pay is not yet defined in the proposal. It will be determined by future implementing acts. You should monitor the Commission's development of these acts to understand how fees are calculatedβ€”whether they are flat rates, proportional to capacity shared, or based on usage.
  3. Cost Recovery, Not Profit: The fee structure is designed as a strict cost-recovery mechanism. This suggests that fees should be proportional to the actual administrative and operational costs incurred by the Commission. This could make the EuroCloud Federation a cost-effective alternative to commercial cloud procurement, particularly when leveraging the ability to share idle capacity with other public bodies without additional commercial markups.
  4. Compliance with Payment Terms: As a member, you will need to comply with the payment conditions set out in the implementing acts. While Article 36 does not detail specific penalties for non-payment of fees, failure to pay could impact your standing in the Federation or your ability to access shared resources.

Common misconceptions

  • Misconception: The EuroCloud Federation is free to join.
    • Reality: While the sharing of services between members is free of charge (as per Article 35), participation in the Federation itself requires paying fees to the Commission. These fees cover the administrative costs of the Federation, including the platform maintenance and membership assessments.
  • Misconception: The EU budget permanently funds the EuroCloud Federation.
    • Reality: The Union budget may only front the initial set-up costs. Article 36(2) mandates that these costs be reimbursed by members within three years. Long-term operational costs are covered entirely by member fees.
  • Misconception: Fees can be used for other EU initiatives.
    • Reality: The fees are "internal assigned revenues." They must be used exclusively to cover the costs of the EuroCloud Federation activities. Any surplus goes back into the general Union budget, but the funds cannot be diverted to other unrelated Commission projects.

Related

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