The story that travelled this summer was that the EU AI Act had been softened and pushed back. The parts that arrived on schedule are precisely the two that touch anyone running or buying AI for professional work, and they applied from 2 August 2026.

Under Article 113, that date is the Regulation's general application date. Two consequences follow from it. Chapter IV, containing the Article 50 transparency obligations, now applies. And the Commission's power to fine providers of general-purpose AI models under Article 101 is live, at up to 3% of worldwide annual turnover or €15m, whichever is higher.

For a UK accountancy or tax practice, the second of those is the more interesting, because it introduces a risk that sits above the contract you have with your software vendor.

Article 50 sits inside Chapter IV and covers transparency for providers and deployers of certain AI systems. In ordinary language, it requires that people are told when they are dealing with a machine rather than a person, and that certain machine-generated content is identifiable as such.

For a practice, the question this raises is narrow. If you deploy anything that talks directly to clients, that duty is live rather than pending. A back-office research tool used by staff raises the question in a different and generally lighter form.

Article 101 governs fines on providers of general-purpose AI models. The Commission may impose fines not exceeding 3% of annual total worldwide turnover in the preceding financial year, or €15m, whichever is higher, where a provider intentionally or negligently infringes the relevant provisions, refuses to supply documents or information, supplies false information, fails to comply with a Commission-ordered measure, or denies access to a model for evaluation.

Before imposing a fine the Commission must communicate preliminary findings and give the provider an opportunity to respond, and the Court of Justice can review, cancel, reduce or increase the amount.

Reading the timeline in reverse is as useful as reading it forwards, because it explains where the "delayed" headlines came from.

Article 6(1), which contains the classification rules for certain high-risk AI systems, and the obligations that follow from it, apply from 2 August 2027 rather than 2026. High-risk classification is the heaviest part of the Regulation for anyone building or deploying systems in sensitive domains, and it is the part with a further year to run.

So the accurate summary of this summer is narrow: the transparency duties and the enforcement machinery arrived on time, and the high-risk classification regime did not, because it was never due. A firm that read "delayed" and filed the whole subject away has the two halves the wrong way round.

📌 Key date: 2 August 2026. Not a proposal, not a consultation. Chapter IV and the Article 101 enforcement powers apply from that date under Article 113. The high-risk classification rules in Article 6(1) follow on 2 August 2027.

Most software risk is contractual. If a vendor fails you, the remedy lives in the agreement you signed.

Enforcement against a model provider works differently. The AI Office can require technical documentation, evaluate a model, and order corrective measures. A model can be required to change, or restricted in the European market, by a regulator acting on the provider rather than on you or your vendor.

No clause in a reseller agreement reaches that. It is a supply-chain risk with a regulator inside it.

"A continuity risk that sits one floor above your vendor's service level agreement."

It shifts one question from theoretical to sensible: what does your firm do if the model underneath a tool you rely on becomes unavailable, or materially changes, at short notice?

For a practice using a single tool for a single workflow, the answer may be "we go back to doing it the old way for a fortnight", which is a perfectly reasonable answer as long as it has been thought about once.

A tool whose value comes from a specific model generation is exposed to that model's availability. A tool whose value comes from sourcing, retrieval, citation and a verification workflow is considerably less so, because the layer that does the work sits above whichever model is current.

✅ In practice: This is the argument for buying on architecture rather than on model branding. GAIN Tax grounds each answer in UK legislation, HMRC guidance and case law and shows the source against the point, and our published benchmark records how that performs: 93.2% correct across 250 questions in 21 UK tax domains, 4.8% partially correct and 2.0% incorrect. We publish what the tool will not do and how client data is handled. You can create an account and judge it against your own questions.

Narrower than the headlines suggest, and dependent on facts about your practice rather than on a general rule. The Regulation reaches a British firm through where its clients sit and where its outputs land, so the answer turns on your client list rather than on your office address.

Both possible mistakes are expensive in different ways. Assuming you are out of scope when EU clients are being served by a client-facing AI tool leaves an obligation unmet. Assuming you are in scope when you are not produces a compliance project nobody needed.

⚠️ Watch: This article summarises what applied on 2 August 2026 and why it matters commercially. It is not legal advice on the Regulation's territorial scope. Where EU clients are material to your practice, get the scope question answered properly.

1. List the AI tools in use across the practice, including the ones nobody formally approved.
2. Note the underlying models each tool runs on, and whether the vendor will tell you.
3. Ask each vendor what happens to your service if a model is restricted or withdrawn in the EU, and record the answer.
4. Check anything client-facing already makes clear that a person is dealing with a machine.
5. Establish your actual scope, based on where your clients and your outputs sit.

An hour with that list this month is worth considerably more than another quarter of watching for the word "delayed" in AI Act coverage.

Two parts of the EU AI Act arrived on 2 August 2026 without fanfare, and both matter to professional firms. Article 50 transparency now applies under Chapter IV. And the Commission can fine a general-purpose model provider up to 3% of worldwide turnover or €15m, whichever is higher, as well as require documentation, evaluate a model and order corrective measures.

For most UK practices the direct compliance burden is small and the indirect lesson is larger. Model availability has become a regulatory variable, not merely a commercial one, and tools built on a verification layer rather than on a particular model generation carry that risk better.

The checklist above takes an hour. For the wider framework on assessing tools, see our guide to choosing AI tax research software in the UK, or browse the blog.

Not in the parts that matter most to professional-services users. Under Article 113, 2 August 2026 is the Regulation's general application date, and Chapter IV, containing the Article 50 transparency obligations, applied from then, alongside the Commission's enforcement powers over general-purpose AI model providers.

Article 50 sets transparency obligations for providers and deployers of certain AI systems. In plain terms, people must be able to tell when they are interacting with a machine rather than a person, and certain machine-generated content must be identifiable as machine generated. It applies from 2 August 2026 as part of Chapter IV.

Under Article 101, the Commission may impose fines not exceeding 3% of a provider's annual total worldwide turnover in the preceding financial year, or €15m, whichever is higher. Grounds include infringing the relevant provisions, refusing information requests, supplying false information, failing to comply with an ordered measure, or denying access for model evaluation.

It can, but it depends on the facts. The Regulation reaches a UK practice through where its clients sit and where its outputs land, rather than through the location of its office. Where EU clients are material to the practice, the scope question is worth answering properly rather than assuming either way.

Because it introduces a continuity risk that no vendor contract covers. The AI Office can require a model's provider to make corrective changes, and a model can be restricted in the EU market. If your software depends on a specific model, its availability is now partly a regulatory question rather than purely a commercial one.

List the AI tools in use, identify the underlying models, ask each vendor what happens if a model is restricted or withdrawn in the EU, confirm anything client-facing discloses that it is a machine, and establish your actual scope based on your client base. That is an hour of work for most practices.