The Cloud Exit Invoice Has an Egress Fee. Does the January 2027 Deadline Apply?
Classify each cloud-exit invoice line as a switching charge, standard service fee, early termination penalty, additional service or parallel-use egress before scoping a Data Act migration request.
Signals to watch
- A named data-processing service has an exit invoice tied to a dated provider-to-provider or provider-to-on-premises migration
- Egress, support, remaining-term and ordinary service lines have been grouped together although they may follow different Data Act definitions
- Procurement or FinOps must approve, dispute or budget the invoice before a migration or contract decision with a named owner
On 13 August 2026, a cloud provider may still impose a reduced switching charge, but it cannot exceed the provider’s costs directly linked to the switching process concerned. From 12 January 2027, Article 29 of the EU Data Act prohibits switching charges for that process. The deadline does not automatically erase ordinary service fees, every fixed-term early termination penalty or every egress line. Classify what the invoice pays for before calling it a prohibited charge.
This distinction matters to a cloud-migration services business-development lead monitoring authorised cloud operations, FinOps (cloud financial operations), procurement and legal Telegram groups. A useful commercial Signal is a named exit invoice attached to a provider-to-provider or provider-to-on-premises move, plus an approval, dispute or migration decision with a date. Seeing it a day late may mean missing the invoice-review meeting that assigns migration validation, cost reconstruction or provider negotiation to another firm.
Definition: a switching charge pays for the regulated switch
Article 2 of Regulation (EU) 2023/2854 defines switching as a process in which a customer changes from one data-processing service to another service of the same type or another service from a different provider, or to on-premises information and communications technology infrastructure. It can include extracting, transforming and uploading data.
A switching charge is a charge—other than a standard service fee or early termination penalty—imposed by the data-processing-service provider for actions the Regulation mandates for that switch. The definition includes data-egress charges: network transfer fees for extracting customer data from one provider’s infrastructure to another provider or on-premises infrastructure.
That boundary explains why the invoice description alone is weak evidence. Data transfer, support or remaining term says little about the work, purpose, dates and contract basis. The original contribution here is a dated fee-line record, not a new legal category: place each line beside its migration event, governing date and evidence owner.
Three neighbouring terms that must stay separate
Standard service fee
A standard service fee pays for provision of the data-processing service itself. Recital 89 says it is not a switching charge, is not subject to withdrawal and remains applicable until the relevant service contract ceases. A charge for ordinary storage or compute during the notice or transitional period may therefore require a service-period and contract check rather than immediate classification as switching cost.
Early termination penalty
An early termination penalty addresses ending a fixed-duration contract early. The Data Act’s switching-charge definition excludes it. Recital 89 says the Regulation does not prevent parties from agreeing to fixed-duration data-processing contracts, including proportionate early termination penalties, in accordance with Union or national law. That is not a conclusion that every remaining-term fee is valid: duration, formula, proportionality and applicable law remain fact-specific matters for authorised advisers.
Data egress
Egress can be a switching charge when it funds data transit required for the regulated move. Article 29’s staged reduction and prohibition then matter. But Article 34(2) separately permits egress charges for in-parallel use—ongoing use of services from multiple providers—only to pass on incurred egress costs and without exceeding those costs. Ask whether the transfer completes a switch or supports continuing multi-cloud use.
Additional migration help creates another boundary. Recital 89 allows a provider to charge for services requested by the customer that go beyond the provider’s Data Act switching obligations, when the customer agrees to the price in advance. Work description and approval evidence decide whether a support line belongs there; the label professional services does not decide it.
The date changes the permitted amount
The Commission says the Data Act entered into application on 12 September 2025. Its Data Act explained page describes removal of switching charges, including switching-related egress, from 12 January 2027, with a transitional cost-based period before that date.
Article 29 supplies the exact stages:
- From 11 January 2024 to 12 January 2027, a provider may impose reduced switching charges that do not exceed costs it incurred and that are directly linked to the switch concerned.
- From 12 January 2027, a provider must not impose switching charges for the switching process.
- Before contract signature, the provider must give clear information about possible standard service fees, early termination penalties and reduced switching charges during the transitional period.
The invoice date is not enough. Preserve the switch request, work dates, service period and contract term. A January invoice might describe December transfer work; a December estimate might fund January activity. The customer and its advisers must determine which facts and rules govern the actual line.
Example: one exit invoice, four unfinished classifications
Consider this illustrative composite Telegram exchange, not a customer record or legal conclusion:
“Exit invoice came in. There’s egress plus two months service.”
“They also added migration support and the rest of the term. Cutover is before renewal, I think.”
“FinOps needs an answer tomorrow. Destination is another provider.”
The message identifies a move and an urgent invoice review, but not the service, switch-request date, contract end, invoice period, data volume, rate, support statement of work, advance approval, direct-cost basis or whether the old service runs in parallel after cutover.
Do not total the invoice and apply one label. Create four rows:
| Invoice line | Initial question | Evidence owner |
|---|---|---|
| Egress | Was this transit necessary for the provider-to-provider switch, or continuing parallel use? What amount and period? | Cloud engineering and provider billing |
| Two months service | Does it pay for ordinary service during notice or transition, or a mandated switching action? | Contract owner and FinOps |
| Migration support | Was it required provider assistance, or customer-requested additional work agreed in advance? | Migration owner and statement-of-work approver |
| Remaining term | Is it an early termination penalty under a fixed-duration contract, and how was it calculated? | Procurement and authorised legal adviser |
The cloud-migration provider can offer technical validation of export work, transfer purpose, data volume and parallel-use setup. It should not promise that the classification is a legal conclusion, decide proportionality or invent the provider’s direct costs.
Why this becomes a migration-services request
The fee dispute becomes commercially reviewable when it reveals technical work with a deadline: a named source service, destination, switch request, transfer or cutover plan, invoice line and owner. If the only issue is contract interpretation, route it to qualified legal or procurement support. If the egress quantity cannot be reconciled to the export run, or the invoice bundles migration assistance with an untested cutover, a cloud-migration provider may have a bounded technical engagement.
The broader Data Act cloud-switching demand analysis distinguishes legal briefing, contract inventory, export test and executable migration. Cloud FinOps cost qualification helps separate a billing spike from a cost-governance project. Pricing describes access to authorised-group discovery.
TOP Prospect can filter, merge, deduplicate and rank relevant fragments from Telegram groups a user intentionally connects and is authorised to access, preserving original message, source, time, AI summary and ranking reasons for human review. It cannot read the contract or invoice, inspect either cloud, calculate the provider’s direct costs, certify Data Act compliance or contact the writer. The Telegram business Signal workflow explains that discovery boundary.
Key facts as of 13 August 2026
- The Data Act has applied since 12 September 2025 under Article 50.
- Article 29 still permits reduced, directly linked, cost-capped switching charges until 12 January 2027; the prohibition starts on that date.
- Standard service fees and early termination penalties are excluded from the definition of switching charges.
- Switching-related egress falls within switching charges; in-parallel-use egress follows the separate cost ceiling in Article 34(2).
- Articles 23–31 also contain contractual, information, cooperation and technical duties whose scope must be checked against the service and switching event.
FAQ
Are switching charges already prohibited on 13 August 2026?
No. Article 29 permits reduced switching charges until 12 January 2027, but they must not exceed costs incurred by the provider that are directly linked to the switching process concerned. From 12 January 2027, providers must not impose switching charges for the switching process.
Is every cloud data-egress fee a Data Act switching charge?
No. Data egress is included when charged for the regulated switching process, but ongoing egress for in-parallel use follows Article 34(2), and the invoice still needs to be tied to the actual transfer purpose and service.
Are standard service fees and early termination penalties switching charges?
The Regulation defines switching charges as excluding standard service fees and early termination penalties. Recital 89 says standard service fees remain applicable until the service contract ends and recognises proportionate early termination penalties for fixed-duration contracts in accordance with Union or national law.
What should a cloud-migration provider verify before quoting?
Verify the source service, destination or on-premises target, switch request and dates, contract term, each invoice line, work performed, direct-cost basis, whether support went beyond statutory switching duties, parallel use, export boundary, migration owner and the decision deadline.
For the composite invoice, tomorrow’s answer should be four line statuses with evidence requests—not one claim that the whole bill disappears in January 2027.
Frequently asked questions
Are switching charges already prohibited on 13 August 2026?
No. Article 29 permits reduced switching charges until 12 January 2027, but they must not exceed costs incurred by the provider that are directly linked to the switching process concerned. From 12 January 2027, providers must not impose switching charges for the switching process.
Is every cloud data-egress fee a Data Act switching charge?
No. Data egress is included when charged for the regulated switching process, but ongoing egress for in-parallel use follows Article 34(2), and the invoice still needs to be tied to the actual transfer purpose and service.
Are standard service fees and early termination penalties switching charges?
The Regulation defines switching charges as excluding standard service fees and early termination penalties. Recital 89 says standard service fees remain applicable until the service contract ends and recognises proportionate early termination penalties for fixed-duration contracts in accordance with Union or national law.
What should a cloud-migration provider verify before quoting?
Verify the source service, destination or on-premises target, switch request and dates, contract term, each invoice line, work performed, direct-cost basis, whether support went beyond statutory switching duties, parallel use, export boundary, migration owner and the decision deadline.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
