Did the EU Just Erase Your RPO? Not So Fast.

For the full discussion of this topic, tune into the latest episode of the Gaapsavvy Podcast here or subscribe to the Gaapsavvy substack here.

The Panic: “Did We Just Lose Our EU Backlog?”

When the EU Data Act officially went live on September 12, 2025, my phone lit up like it was earnings season. CAOs, CFOs, and Deals Desk leads all asked versions of the same question:

“Devon, are we about to lose our entire EU backlog? Do we need to rip up every single contract we’ve signed?”

I get it. A sweeping new law about data portability sounds like the kind of thing that makes auditors sharpen their pencils and executives break out in a cold sweat. Add in a bit of LinkedIn fearmongering, and suddenly every three-year contract looks like it might collapse into a two-month deal.

Here’s the truth: take a breath. The EU didn’t just erase your RPO. Let's find out why.

TL;DR: Most SaaS companies can likely treat EU Data Act switching provisions as a legal risk (ASC 450) to monitor, not a rev rec reset (ASC 606) today. Actions: Get legal review, size EU RPO by penalty bucket, document your stance, align with auditors, continuously monitor, and update contract templates ahead of Jan 2027 fee prohibitions.

Why the Panic Spread So Quickly

The EU Data Act is designed to give customers more control over their data. Chapter VI, the section that triggered all the late-night phone calls, focuses specifically on switching data-processing service providers. It potentially applies to cloud contracts (IaaS, PaaS, SaaS, although this is still up for legal interpretation) and has extraterritorial reach, which means non-EU providers serving EU customers are in scope.

Scope check: Chapter VI targets data-processing services delivered as cloud (IaaS, PaaS, SaaS). Purely on-prem or perpetual licenses without hosting are generally outside the switching provisions.

The scary part for accountants? Under ASC 606, if customers can walk away with little penalty, your multi-year contract might suddenly look like a short-term deal. Contracts must enable switching on a maximum of two months’ notice, and once the switching process is completed, the contract is deemed terminated. On paper, that could slash RPO, impact rev rec, and give your EU customers some negotiation power.

For readers under IFRS 15, the conclusions are directionally similar to ASC 606: enforceable contract terms and substantive penalties remain the anchor for multi-year recognition. In practice, IFRS 15 and ASC 606 outcomes converge here because the analysis turns on enforceable terms and substantive penalties, not on generalized switching rhetoric.

No wonder everyone freaked out. Think of it as Brussels telling cloud providers they can’t build toll booths at the exit ramp: customers should be able to take their data and go without paying a ransom.

💡 We unpacked this exact “why everyone panicked” scenario in detail on the Gaapsavvy Podcast. If you want the deep legal and accounting nuance, it’s worth a listen.

Why the Reality Is More Measured

Here’s where cooler heads prevail.

First, this is best framed as a legal risk under ASC 450, not an accounting problem under ASC 606, at least for now. No lawsuits have been filed, no regulator has forced a restatement, and without precedent, there’s nothing “probable and estimable” to accrue. Translation: disclose it, monitor it, and move on.

Many obligations relate to enabling switching during a defined transition period. That legal facilitation does not automatically convert multi-year contracts into cancellable month-to-month arrangements for accounting.

Second, substantive termination penalties still matter. The Act targets punitive exit fees, but it does not eliminate reasonable compensation for committed services already delivered or contractually available. If your contracts require customers to pay the balance of the committed value to exit, that remains a substantive defense. Your multi-year accounting conclusion doesn’t suddenly vanish. The only catch: make sure those penalties are written as compensation for services, not disguised switching charges.

If in doubt, bring in counsel, and maybe bring them coffee, because they’ll be knee-deep in fine print.

Note: The Act allows proportionate early-termination penalties for fixed-term contracts. This is distinct from switching charges, which are being phased out and then banned from 12 January 2027.

What You Should Actually Do

None of this means you can sit back and ignore it. Prudence requires a plan. Here’s what that looks like in practice:

1. Get legal involved. This is a legal interpretation first, accounting conclusion second. Internal and external counsel should review your contract language.

2. Size your exposure. How much EU RPO is on your books? Break it into three buckets: no penalty, nominal penalty, and substantive penalty. Focus review on the first two.

3. Document your stance. Draft a memo, align with auditors, and lock in your position. Example: “This is a contingent liability under ASC 450, not probable or estimable, based on legal advice.” Back it up with a legal rep letter.

4. Watch the early movers. September-quarter 10-Qs filed after September 12, 2025 are a useful litmus test. If major cloud providers start adding Data Act risk factors, expect auditors to follow suit.

5. Monitor quarterly. Keep revisiting this as EU FAQs, enforcement, and market practice evolve, especially as January 2027 approaches, when switching fees become fully prohibited.

6. Controls: Add a quarterly EU-exposed-RPO review control (legal + rev rec + deal desk) to reassess risk factors, disclosures, and contract language.

7. Sample 10-Q/10-K risk factor sentence: “Certain EU regulations on cloud switching and data portability could increase customer flexibility to migrate services and limit our ability to charge switching-related fees. While we do not currently expect a material impact on our revenue recognition or RPO disclosures, we are monitoring ongoing regulatory developments and market practice.”

Expect your auditors to press on this in year-end reviews. Big Four firms are already flagging EU Data Act risk factors in their client conversations, so come prepared with memos, legal letters, and clear exposure sizing.

Bottom Line

• The immediate RPO risk is minimal for most SaaS providers. This is a legal disclosure item, not an accounting adjustment yet.

• Your task is to monitor, not panic. Stay aligned with counsel and auditors, document your position, and keep perspective.

• Look ahead. Switching fees are restricted now and prohibited in 2027, so update contract templates before this sneaks up on you.

So no, the EU didn’t just blow up your RPO. The sky isn’t falling. And if you’re still losing sleep, it’s probably less about the Data Act and more about that double espresso you downed at 3 p.m.

👉 Want the deep dive with all the nuance (and a few laughs)? Check out the Gaapsavvy Podcast episode here where Angela and I unpack this from every angle.

Disclaimer

The information provided in this podcast and transcript is for educational and informational purposes only and does not constitute legal, financial, or accounting advice. The views expressed are those of the hosts and do not necessarily reflect the views of their employers or clients. You should consult with your own professional advisors before making any decisions based on this information. The hosts and producers of Gaapsavvy Podcast assume no liability for any actions taken in reliance on the information contained herein.