AI Act Due Diligence in M&A: What to Check Before You Buy a Company That Runs on AI
An acquisition does not pause the AI Act. This is the diligence programme for buying a company that runs on AI: extracting the inventory, auditing classification, testing Article 25 and Article 22 exposure, and planning remediation before completion and the first ninety days.
Deals do not wait for compliance calendars, and the AI Act does not wait for deals. Buy a company that runs on AI — a disputes-automation startup, or a manufacturer whose maintenance tool is now a product feature — and you inherit its classification reasoning, vendor chains and unresolved exposure on completion day.
That is why AI Act due diligence M&A is a workstream of its own: Article 99 penalties and Article 50 transparency applied from 2 August 2026, and Annex III duties arrive on 2 December 2027. What follows is a buying a company with AI systems checklist — extract the inventory, audit the classification, test the contracts, set the remediation clock. Everything else in AI compliance in company acquisition hangs off those four steps.
Extract the AI inventory before anything else
Where to look. Most targets have no register. Build one from the accounts-payable ledger for model and API invoices, the SSO app catalogue, repositories holding API keys, and an anonymous survey of departmental tools. Default-on AI features inside software you already pay for count.
What one row needs. Name, vendor, purpose, role (provider, deployer or importer), tier with reasoning, data categories, oversight owner, contract.
Why first. AI inventory during due diligence is the first row every questionnaire asks; without it there is no classification audit and no schedule to warrant. One payments buyer found 48 model-backed lines in a target’s ledger, 11 on no IT list — two screening tools.
Run the classification audit, system by system
Roles before tiers. Provider if the target put its name on the system or substantially modified one; deployer if it runs it under its own authority; importer if it brought a third-country system onto the Union market.
Then the tier. Test each row against Article 6 and Annex III, recording reasoning rather than labels, and screen against Article 5: emotion inference at work, social scoring and untargeted facial scraping have no compliance route, so the only honest finding is removal.
Against the calendar. Prohibitions, Article 4 literacy and Article 50 transparency are enforceable now; Annex III duties follow on 2 December 2027. Keep two columns — breaches today, systems to remediate by then. A CV-ranking tool is Annex III whether the target built it or bought it.
Article 25: when the acquisition makes you the provider
AI Act risk in mergers and acquisitions concentrates here: the transaction itself converts nobody. A share purchase leaves the target as it was; conversion happens through post-closing action.
The three triggers. Under Article 25(1), a distributor, importer, deployer or third party becomes a provider — taking the Article 16 set: Annex IV documentation, quality management, conformity assessment, registration and monitoring — if it puts its name or trademark on a high-risk system, substantially modifies one so it stays high risk, or changes a non-high-risk system’s intended purpose so it becomes high risk. Rebranding the target’s product, folding its model into your platform for a new purpose, or reselling a fine-tune as your own all count.
Two clauses to hunt for. Article 25(2) lets the initial provider step out but requires close cooperation and technical access, unless it barred its system from becoming high risk — which would block your documentation route. Article 25(4) requires written agreements on information and access with third parties supplying tools or components integrated into a high-risk system, short of free open-source components.
Article 22: authorised representatives and third-country vendors
Third-country providers must appoint an authorised representative in the Union, by written mandate, before making high-risk systems available. The representative verifies the conformity declaration and technical documentation, keeps them for ten years, supplies information and log access on request, and must terminate the mandate, informing the market surveillance authority, if the provider appears to be breaching its obligations.
Three checks. Does each third-country supplier hold a current mandate covering Article 22(3)? Does the target itself act as an authorised representative, and do those mandates survive a change of control? Will your group place systems on the Union market under your own name after completion?
Article 26 duties and the GDPR Article 28 chain
Most mid-market targets sit on the deployer side, and Article 26 audits row by row: use systems per instructions; assign trained oversight with authority; keep input data relevant where you control it; monitor, inform the provider, suspend and report serious incidents; keep logs at least six months; inform workers before workplace use; use the provider’s Article 13 information for the GDPR Article 35 assessment; inform people subject to decisions.
The chain runs alongside. Where the target processes personal data for customers, GDPR Article 28 applies: sufficient guarantees from processors, prior specific or general written authorisation for sub-processors with a controller right to object (28(2)), and flow-down by contract (28(4)). A group restructure can change that chain without changing a system, so the Article 30 record must be corrected on day one.
Timing. These duties bite on 2 December 2027; today’s live duties are literacy, transparency and prohibitions. Ask which systems will be Annex III by then, and how long the missing pieces take.
IP, open-source licences and pending regulatory exposure
Model licences. Weights or API access only? Commercial use and redistribution of fine-tunes permitted? Confirm that the copyright policy and training-data summary required of general-purpose AI providers transfer with the business.
Code and data. Run a dependency and licence scan before signing: copyleft in distributed code burdens the combined work after closing, and research-only datasets invalidate products built on them. Confirm that IP assignment covers what the business runs on.
Pending exposure. Collect open market-surveillance correspondence, data protection complaints, escalations and incident history. Penalties reach €35M or 7% of worldwide turnover for prohibited practices, €15M or 3% for most other breaches and €7.5M or 1% for misleading information to an authority; SMEs pay the lower of the fixed sum and the percentage (Article 99(6)), measured on worldwide turnover — so inherited exposure can be assessed against your larger post-closing group.
Contracts, change-of-control clauses, warranties and indemnities
Change of control and assignment. AI vendor contracts often carry termination on change of control, re-pricing or consent-to-assignment requirements, and data processing agreements add notice and objection rights. Map which contracts need consents, which auto-terminate, which re-price, then confirm in writing that documentation and support continue after completion.
Warranties. Draft them against the audit: inventory completeness covering embedded vendor AI; classification and role accuracy; no prohibited practices; Article 50 disclosures live; literacy records; no unreported incidents; valid licences; current sub-processor lists.
Indemnities. Penalties are assessed against the breaching entity, which after completion is yours, so indemnity is the only route back to the seller. Seek a specific indemnity for pre-completion findings, a super-cap or carve-out from the general cap, and survival past 2 December 2027, since inherited conduct only becomes actionable under the high-risk regime after that date. Where the inventory cannot be verified, escrow beats a warranty claim.
Pre-closing remediation and the first 90 days after completion
Before completion. Remove and evidence any Article 5 prohibited use; freeze new AI procurement behind one change-control gate; complete Annex III rows with written rationales; obtain missing vendor documentation and Article 22 mandates; secure consents; snapshot the register, incident log and processing agreements; name the day-one owner.
Days 1–30. Merge registers, confirm roles, correct the Article 30 record and sub-processor list, notify affected controllers, and build the incident process around Article 73: 15 days generally, 10 for serious disruption of critical infrastructure, 2 where there is death or serious harm.
Days 31–60. Re-run classification against a dated rule pack, assign and train named overseers, set log retention to the six-month floor in Article 26(6), and start works-council consultation, which runs two quarters.
Days 61–90. Close Annex III gaps against 2 December 2027, scope an Article 27 assessment where the trigger applies, issue re-procurement notices for tools that cannot be fixed, and run the first quarterly register review.
How to check your own position
Run this table against the target during confirmatory diligence, or against your own company if you expect to be the seller. Every answer should come from a document, not an interview.
| Diligence area | The question to ask | The red flag | Source of evidence |
|---|---|---|---|
| AI inventory | Every system listed with purpose and owner? | Model spend missing from IT lists | AP ledger, SSO catalogue |
| Classification | Tier recorded with reasoning? | Tier with no written rationale | Register export, rationale |
| Roles, Article 25 | Provider or deployer per system? | Third-party model branded as own | Role analysis, packaging |
| Prohibited uses, Article 5 | Banned practice running? | Scoring or emotion inference on staff | Tool config, HR policy |
| Representative, Article 22 | Mandate per third-country supplier? | Mandate ends on control change | Mandate letters, vendor pack |
| Deployers, Article 26 | Oversight, six-month logs, worker notice? | No overseers; logs rotated weekly | Oversight records, settings |
| GDPR chain, Article 28 | Controllers’ sub-processor approvals? | Sub-processor swapped without consent | DPAs, sub-processor register |
| IP and open source | Who owns the code, models and data? | Copyleft shipped; IP unassigned | Licence scan, contracts |
| Contracts and exposure | Change-of-control clause? Open enquiry? | Vendor may terminate; unreported incident | Contract register, log |
Answer every row from documents and diligence becomes a mapping exercise; cannot, and that gap is what gets priced — the same gap an authority would find.
Frequently asked questions
Do AI Act obligations transfer when we buy a company?
In a share purchase the target stays the same legal entity, so obligations, findings and liability travel with it. In an asset purchase nothing transfers automatically: you take obligations for systems you supply under your own name, while the seller keeps what it placed on the market. The transition of AI Act obligations on sale belongs in the agreement — that allocation decides AI Act liability after acquisition.
Does completing a share purchase make us a provider under Article 25?
No. Provider status follows from what you do with the systems — putting your name on a high-risk system, substantially modifying one, or changing a non-high-risk purpose so it becomes high risk — not from the transaction. The target stays provider of what it already supplies.
Which AI Act items should become warranties and indemnities?
Warranties should cover inventory completeness with a defined scope, classification accuracy, absence of prohibited practices, transparency disclosures, literacy records, no unreported incidents, licence validity and current sub-processor lists. Pair them with a specific indemnity for pre-completion findings and survival beyond 2 December 2027.
Can we close before remediation is finished?
Yes, if the residual items are mapped, owned and priced. What you cannot do is close with an incomplete inventory: without it you cannot prove classification, answer an authority or size the budget. Finish the inventory and classification rationale before signing, carry the rest on a 90-day plan, and let warranties and indemnity hold what remains open.
Put this guide to work on your own estate.
Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.
- Free forever plan
- No credit card
- EU-hosted · GDPR-native
Build a live AI register in minutes — upgrade only when you need the audit pack.