Summary Under the proposed Cloud and AI Development Act (CADA), Article 36 and Article 40 establish two distinct fee mechanisms to fund different pillars of the EU's sovereign cloud strategy. Article 36 fees are levied on members of the EuroCloud Federation to cover the administrative costs of sharing idle public-sector data centre and cloud capacity. Article 40 fees are charged to participating entities to fund the Commission's activities as a central purchasing body for cloud, software, and AI services. Both operate on a strict cost-recovery basis, meaning the beneficiaries bear the costs. Crucially, if the Commission initially pre-finances setup costs from the general EU budget, both mechanisms require beneficiaries to reimburse these costs within a maximum period of three years.

Detail

The proposed CADA introduces a dual-track financial framework to ensure the long-term sustainability of its demand-side measures without placing a permanent burden on the EU budget. While both fee structures aim to enhance strategic autonomy and reduce third-country dependencies, they serve fundamentally different operational purposes, target different groups of payers, and are governed by separate legal provisions within the Regulation.

EuroCloud Federation Fees: Funding Capacity Sharing (Article 36)

Article 36 specifically addresses the financial governance of the EuroCloud Federation, established under Article 34. This federation is a voluntary network designed to facilitate the sharing of public-sector data centre services and cloud computing services between Union entities and public sector bodies.

  • Purpose of Fees: The fees levied under Article 36 are strictly intended to cover the costs arising from the Commission's activities in establishing and managing the federation. This includes the operational costs of the platform that enables the sharing of services, the assessment of membership applications, and the administrative oversight required to ensure compliance with the federation's conditions.
  • Who Pays: The financial burden falls on the members of the EuroCloud Federation. Participation is voluntary for Union entities and public sector bodies. Only those entities that choose to join the federation and share or access capacity are liable for these fees.
  • Cost Recovery and Pre-financing: The Regulation mandates that costs are jointly financed by the members. A critical provision in Article 36(2) addresses the initial setup phase: if the costs are initially borne by the general budget of the Union (e.g., for developing the initial platform), the EuroCloud members must reimburse these costs. This reimbursement must occur over a period not exceeding three years from the date the costs were incurred.
  • Revenue Treatment: Revenues generated from these fees constitute internal assigned revenues within the meaning of the Financial Regulation. They are assigned specifically to cover the costs of the federation's activities. Any surplus remaining after covering these costs is entered into the general budget of the Union.

Central Procurement Fees: Funding Aggregated Buying (Article 40)

Article 40 governs the financial arrangements for the Commission's central procurement activities outlined in Chapter IV. This mechanism empowers the Commission to act as a central purchasing body, aggregating demand from Member States, Union entities, and partner organisations to procure data centre services, cloud computing services, software, and AI systems.

  • Purpose of Fees: These fees are designed to cover the costs arising from the procurement activities themselves. This encompasses the development and maintenance of the common procurement platform, the execution of procurement procedures (including framework contracts and dynamic purchasing systems), and the provision of ancillary support services such as technical infrastructure, advice, and contract management.
  • Who Pays: The fees are levied on the participating entities. This group includes contracting authorities from Member States, Union entities, and partner organisations selected by the Commission. Unlike the EuroCloud Federation, which focuses on sharing existing capacity, this mechanism focuses on the active procurement of new services.
  • Cost Recovery and Pre-financing: Similar to the EuroCloud model, Article 40(2) stipulates that costs are jointly financed by the participating entities. If the Commission initially bears the establishment costs (such as platform development) from the general budget, the participating entities are required to reimburse these costs. The reimbursement period is capped at three years from the date the costs were borne by the Union.
  • Fee Calculation Principles: Article 40(4) establishes strict principles for fee setting. Fees must be set in advance, be proportionate to the estimated costs of the activities, and be determined in a cost-effective way reflecting practices of comparable procurement frameworks. Crucially, the fees must be sufficient to cover the direct and indirect costs incurred by the Commission.
  • Revenue Treatment: Like EuroCloud fees, revenues from procurement fees are internal assigned revenues. They are assigned to cover the costs of the procurement activities. Any remaining revenue is transferred to the general budget.

Comparative Summary

The table below highlights the structural differences between the two fee regimes as proposed in CADA:

Feature EuroCloud Federation Fees (Art. 36) Central Procurement Fees (Art. 40)
Primary Objective Administering the sharing of idle public-sector capacity. Funding the Commission's role as a central purchaser for new services.
Legal Basis Article 36 (Chapter III: EuroCloud Federation). Article 40 (Chapter IV: Commission Procurement).
Target Payers Members of the EuroCloud Federation (voluntary public sector bodies). Participating entities (Member States, Union entities, partners).
Cost Basis Costs of establishing/managing the federation platform and membership assessment. Costs of procurement procedures, platform development, and ancillary support.
Reimbursement Rule Up to 3 years for costs pre-financed by the EU budget. Up to 3 years for costs pre-financed by the EU budget.
Revenue Status Internal assigned revenues (surplus to general budget). Internal assigned revenues (surplus to general budget).

What this means for you

For public sector bodies, Union entities, and their financial officers, distinguishing between these two fee streams is essential for accurate budgeting and strategic planning under the proposed CADA framework.

  1. Distinct Budget Lines: Your organization must plan for two separate potential liabilities. If you join the EuroCloud Federation to optimize existing infrastructure, you will incur fees under Article 36. If you participate in a central procurement exercise to buy new cloud or AI services, you will incur fees under Article 40. These are not interchangeable; participation in one does not automatically trigger fees for the other.
  2. The Three-Year Reimbursement Window: Be prepared for potential retroactive financial obligations. If the Commission uses the general EU budget to fund the initial setup of either the federation platform or the procurement framework, your entity could be liable for reimbursement. Article 36(2) and Article 40(2) explicitly limit this reimbursement period to three years. Financial models should account for the possibility of these charges appearing in future budget cycles.
  3. Monitoring Implementing Acts: The proposal delegates the detailed calculation of fees to the Commission via implementing acts. Article 36(4) and Article 40(5) empower the Commission to specify the estimated costs, individual fee amounts, and payment conditions. You must monitor these secondary legislative acts closely, as the specific fee rates and payment schedules will be defined there, not in the primary Regulation text.
  4. Cost-Neutrality Principle: Understand that these are not profit-generating mechanisms for the Commission. The fees are strictly cost-recovery tools. The Commission is legally bound to set fees that are proportionate and sufficient only to cover the actual costs incurred. Any surplus generated must be returned to the general budget, ensuring that the EU budget remains neutral over the long term.

Common misconceptions

"These fees are taxes or penalties." Incorrect. Both fee structures are strictly cost-recovery mechanisms. They are not punitive fines, nor are they general taxes levied on the public sector. They are designed to ensure that the specific beneficiaries of the EuroCloud Federation or the central procurement service bear the direct and indirect costs of those specific services.

"One fee covers both services." Incorrect. Article 36 and Article 40 are legally and financially distinct. Participating in central procurement does not automatically make you a member of the EuroCloud Federation, and vice versa. You will be billed separately based on your specific participation in each mechanism.

"Fees are fixed and unchangeable." Incorrect. The fees are dynamic and subject to adjustment. Article 40(4) requires fees to be proportionate to estimated costs, and Article 36(4) allows the Commission to specify amounts via implementing acts. As the cost base evolves or participation levels change, the fee structure may be recalibrated to maintain strict cost recovery.

Related

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