The EU AI Act's high-risk deadline moved to 2 December 2027: what it changes for a credit fund.
Important takeaways.
- Regulation (EU) 2026/1744, the digital omnibus on AI, was published on 24 July 2026 and entered into force on 27 July 2026. It moved the AI Act's Chapter III obligations for standalone Annex III high-risk systems from 2 August 2026 to 2 December 2027, and for high-risk systems embedded in Annex I products to 2 August 2028. The dates are fixed rather than conditional on standards being ready.
- Nothing else moved. The Article 5 prohibitions and the Article 4 AI literacy duty have applied since 2 February 2025, general purpose AI model obligations since 2 August 2025, and the Article 50 transparency rules from 2 August 2026, with a four month transition to 2 December 2026 for machine readable marking under Article 50(2).
- Scope turns on the phrase 'natural persons'. Annex III point 5(b) covers systems evaluating the creditworthiness of natural persons or establishing their credit score, with fraud detection carved out. Wholesale lending to corporates is largely outside it; consumer, sole trader and small business lending is inside it, and scoring an individual guarantor brings a corporate lender back in.
- The Act reaches funds with no EU presence. Article 2(1)(c) applies it to providers and deployers located in a third country where the output produced by the AI system is used in the Union.
- A fund is normally a deployer, not a provider, and Article 26 sets a short list: competent human oversight with real authority, relevant input data where the deployer controls it, incident reporting, logs kept for at least six months, and telling the natural person they are subject to the system.
- Article 25(1) turns a deployer into a provider where it puts its own name on a high-risk system, substantially modifies one, or repurposes a system that was not high-risk into a high-risk use. Pointing a general purpose assistant at consumer loan applications is that third route.
The date most compliance calendars carried was 2 August 2026. It moved. Regulation (EU) 2026/1744, the digital omnibus on AI, was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. It pushes the AI Act's obligations for the Annex III high-risk use cases out to 2 December 2027.
This guide answers for the European Union. One of those Annex III use cases is the assessment of creditworthiness, so for a fund lending to natural persons in the EU this is now the operative deadline. For everyone else the more useful question is whether the Act reaches them at all, and the answer is less obvious than the geography suggests.
What moved, and what did not.
The omnibus amends Article 113 of the AI Act. Standalone high-risk systems listed in Annex III come under Chapter III on 2 December 2027 instead of 2 August 2026. High-risk systems embedded in products regulated under Annex I move to 2 August 2028. The dates are fixed rather than conditional on standards being ready, which was the earlier proposal.
Nothing else moved with them, which is where the headline is most often misread.
- The prohibited practices in Article 5 have applied since 2 February 2025. The omnibus added two further prohibitions rather than deferring any.
- The AI literacy duty in Article 4 has applied since the same date. The omnibus softened it, from ensuring a sufficient level of AI literacy among staff to taking measures to support its development. It did not remove it.
- Obligations for general purpose AI models have applied since 2 August 2025. They bind the model provider, not the fund.
- The Article 50 transparency rules applied from 2 August 2026 as planned, with a four month transition to 2 December 2026 for machine readable marking of synthetic content under Article 50(2) where the system was already on the market.
Article 50 is the live obligation most likely to touch a fund today, and most of it binds providers. The deployer duties in paragraphs 3 and 4 cover emotion recognition, biometric categorisation, deep fakes, and AI generated text published to inform the public on a matter of public interest. A borrower facing chatbot and a public marketing surface are the realistic exposures. An internal credit assistant is not.
Whether a credit fund is in scope turns on two words.
Annex III, point 5(b) covers "AI systems intended to be used to evaluate the creditworthiness of natural persons or establish their credit score, with the exception of AI systems used for the purpose of detecting financial fraud".
Natural persons. Not borrowers, not counterparties, not obligors. That phrase splits the sector cleanly.
- A wholesale fund lending to corporates is largely outside point 5(b). Scoring a corporate borrower is not evaluating the creditworthiness of a natural person.
- A non-bank lender assessing consumers, sole traders or small business applicants is inside it, and should plan on that basis rather than wait for the point to be argued.
- Guarantors pull a corporate lender back in. Where the assessment scores an individual guarantor or a personal covenant, an individual is the subject of the assessment.
- Fraud detection is carved out, even where it reads the same data as the credit decision.
That is the same fault line as the Australian transparency obligation commencing on 10 December 2026, which also attaches to decisions about individuals rather than to lending as such. A fund exposed to both markets should do the scoping once and use it twice.
The Act reaches funds with no EU presence.
Article 2(1)(c) applies the Act to providers and deployers established or located in a third country "where the output produced by the AI system is used in the Union". An Australian or Singaporean manager with a European lending sleeve, or with EU borrowers inside a global fund, can be within the perimeter without anyone on the ground in Europe.
The usual position for a fund is deployer rather than provider, and that is a materially lighter set of obligations. Article 25(1) sets out how a deployer becomes a provider: putting its own name or trademark on a high-risk system, substantially modifying one, or modifying the intended purpose of a system that was not high-risk so that it becomes high-risk. The third route is the live one. A general purpose assistant pointed at consumer loan applications is a repurposing, and the fund that pointed it there wears the provider obligations for the result. That is a concrete consequence of the build, buy or embed decision rather than an abstract one.
What the deployer obligations actually ask for.
Article 26 is short and unglamorous. Assign human oversight to people with the competence, training, authority and support to exercise it. Ensure input data is relevant and sufficiently representative, where the deployer controls it. Monitor operation and report serious incidents. Keep the automatically generated logs for a period appropriate to the intended purpose and "of at least six months". And under paragraph 11, inform natural persons that they are subject to the system where it makes or assists decisions about them.
Article 86 sits behind that. A person subject to a decision taken on the basis of an Annex III system, other than the critical infrastructure entry, has a right to clear and meaningful explanations of the role the system played and the main elements of the decision. That duty is owed by the deployer, and no vendor can discharge it on the fund's behalf.
There is one real concession for the sector, in Article 17(4): a provider that is a financial institution already subject to internal governance requirements under Union financial services law is deemed to satisfy the quality management system obligation by complying with those rules, with risk management, post-market monitoring and incident reporting carved out. It only helps a fund that has become a provider.
Sixteen months is a build window, not a reprieve.
Our position is that the delay changes the deadline and nothing about the preparation. Every deployer obligation above is a record: who oversaw the system, what data went in, what the logs say, who was told. None can be produced retrospectively, so a fund that starts in late 2027 will be reconstructing 2027 from memory.
The list to work through now is short. Which decisions touch a natural person. Which systems feed them, and whether the fund is deployer or provider for each. Who is the named overseer, with authority to overrule. Where the logs live and for how long. What the applicant is told. It is close enough to what an APRA regulated investor already asks under CPS 230 that most of it is one exercise rather than three.
The obstacle is rarely the policy. Where AI arrived workflow by workflow, the fund cannot say which system informed a given credit decision, so the log and explanation duties have nothing to draw on. Where AI runs through a single layer that records the system, the model and the material behind each output, the same questions are answered by reading the fund's own records. The Act does not require any particular architecture. It does require an answer.
Primary sources: Regulation (EU) 2026/1744, the AI Act itself, and the article texts linked above. This guide is general information, not legal advice. Whether a particular fund, system or decision is caught depends on the facts and on how the amended Act is applied in each member state.
Questions this guide answers.
Did the EU AI Act high-risk deadline get delayed?
Yes. Regulation (EU) 2026/1744, the digital omnibus on AI, was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. It amends Article 113 of the AI Act so that Chapter III obligations for standalone high-risk systems listed in Annex III apply from 2 December 2027 rather than 2 August 2026, and high-risk systems embedded in Annex I regulated products apply from 2 August 2028. The dates are fixed, replacing the conditional trigger tied to the availability of harmonised standards that was originally proposed. The deferral is limited to those obligations: prohibitions, AI literacy, general purpose AI model rules and Article 50 transparency were not moved.
Does the EU AI Act apply to a private credit fund?
It depends on whether the fund's AI evaluates natural persons. Annex III point 5(b) makes systems used to evaluate the creditworthiness of natural persons or establish their credit score high-risk, excluding systems used to detect financial fraud. A wholesale fund lending to corporate borrowers is largely outside that entry, while a non-bank lender assessing consumers, sole traders or small business applicants should assume it is inside. Assessing an individual guarantor or a personal covenant counts as assessing a natural person. Obligations that do not depend on high-risk classification, such as the Article 5 prohibitions and the Article 4 AI literacy duty, apply to any deployer in scope of the Act.
Does the EU AI Act apply to a fund based outside the EU?
It can. Article 2(1)(c) applies the Act to providers and deployers that have their place of establishment or are located in a third country where the output produced by the AI system is used in the Union. An Australian or Singaporean manager running a European lending sleeve, or holding EU borrowers inside a global fund, can be within the perimeter with no staff or entity in Europe. The classification analysis is then the same one an EU manager runs.
What do we have to do before 2 December 2027?
If a system is in scope, Article 26 requires the deployer to assign human oversight to people with the competence, training, authority and support to exercise it, to ensure input data is relevant and sufficiently representative where the deployer controls it, to monitor operation and report serious incidents, to keep automatically generated logs for a period appropriate to the intended purpose and at least six months, and to inform natural persons that they are subject to the system. Article 86 gives an affected person a right to clear and meaningful explanations of the role the system played in a decision, owed by the deployer rather than the vendor. Each of those is a record that cannot be produced retrospectively, so the mapping work belongs in front of the date rather than behind it.
Working with Levercon.
Levercon helps private credit funds and non-bank lenders accelerate AI adoption to unlock their full potential. It does that through one of three routes: Levercon Agents, Levercon Systems or Levercon Strategy.
Talk to us: you can get in touch here.
This guide is general information, not advice. Factual claims that rely on public sources link to those sources in the text. Practical guidance also draws on patterns Levercon observes across Australian credit funds. No client is named and no figure is attributed to one. Written by Levercon, reviewed before publication and revised in place as the facts change.