EMIR Active Account Notification: The CSSF Form for Article 7a(1)

On 6 July 2026 the CSSF published a single spreadsheet on its website, the active account notification form under Article 7a(1) of EMIR. It carries more weight than its size suggests. This EMIR active account notification is the declaration a Luxembourg financial or non-financial counterparty makes to say whether it has been pulled inside the active account requirement that EMIR 3 built into the clearing rulebook, and it is the entry that puts a firm on the CSSF and ESMA radar for everything that follows.

The active account requirement became applicable on 25 June 2025. A counterparty that is subject to the clearing obligation and trades enough of the euro and Polish zloty interest rate derivatives that EMIR 3 singles out has to hold at least one active account at an EU authorised central counterparty, and it has to notify ESMA and its competent authority when it crosses that line. In Luxembourg that competent authority is the CSSF, and the form it posted on 6 July 2026 is the vehicle for the notification. Get the status call wrong, or file the wrong sheet, and the six-month clock to stand up a working clearing account starts from a date you did not intend.

This article walks through what the notification declares, which Luxembourg entities have to complete it, the three status questions at the heart of the form, and how it differs from the two other EMIR reporting streams it is constantly confused with.

Related reading: our guide to the EMIR 3 clearing obligation thresholds and the active account requirement.

The dates that frame the Article 7a(1) notification

The notification itself has no fixed calendar deadline. It is event driven: the obligation to notify arises when a counterparty becomes subject to the requirement to hold an active account, and the account has to exist within six months of that point. What follows is the framework timeline that gives those events their reference points.

• 27 November 2024: EMIR 3, Regulation (EU) 2024/2987, adopted by the Parliament and the Council.
• 4 December 2024: EMIR 3 published in the Official Journal (OJ L, 2024/2987).
• 24 December 2024: EMIR 3 entered into force. From that date, counterparties that become subject to the obligation to hold an active account under Article 7a(1) must notify ESMA and their competent authority.
• 18 December 2024: ESMA last updated the active account notification template that the CSSF now hosts.
• 25 June 2025: the active account requirement became applicable, per ESMA.
• 13 April 2026: ESMA published the separate reporting templates and instructions for the six-monthly monitoring of the requirement under Article 7b.
• 6 July 2026: the CSSF published the active account notification form (XLSX, around 180 KB) on its website.
• 31 July 2026: the first six-monthly monitoring submission under Article 7b is expected, covering the period from 25 June 2025 to 30 June 2026.

Two of those dates belong to a different filing. The 13 April 2026 templates and the 31 July 2026 submission are about the recurring monitoring report, not the one-off notification. Keeping the two apart is the first discipline this topic demands, and the section below returns to it.

What the active account notification actually declares

The notification is a status declaration. On one spreadsheet a counterparty tells ESMA and its competent authority who it is, whether it belongs to a group under consolidated Union supervision, and whether it meets the conditions that bring it inside the active account requirement. The legal hook sits in the first subparagraph of Article 7a(1): where a financial or non-financial counterparty becomes subject to the obligation to hold an active account, it must notify ESMA and its relevant competent authority and establish that account within six months of becoming subject.

Three EMIR filings share the word “report” in practitioners’ heads and pull apart cleanly once you look at what each one does. Trade reporting under Article 9 sends the details of every derivative contract to a trade repository, transaction by transaction, and it applies to almost everyone; you can see the shape of it in our EMIR trade reporting guide. The active account notification under Article 7a(1) is a one-time status message that says “this requirement now applies to me.” The monitoring report under Article 7b is the six-monthly demonstration that the active account is real and being used. The notification is the smallest of the three and the one that switches the other on.

The form carries an attestation. The person submitting confirms they are duly authorised to notify on the counterparty’s behalf and that the information is accurate and complete to the best of their knowledge. That single sentence is why the sign-off should sit with someone who can stand behind the clearing figures, not with whoever happens to own the mailbox.

Which Luxembourg counterparties have to file

Two conditions have to be true together. First, the counterparty is subject to the clearing obligation under Article 4a (financial counterparties) or Article 10 (non-financial counterparties) of EMIR. Second, it exceeds the clearing threshold in at least one of the categories of derivatives that Article 7a(6) names, measured either in an individual category or on aggregate across the categories. Meet both and the counterparty is inside the active account requirement and has to hold at least one active account at a CCP authorised under Article 14, meaning an EU CCP, where that CCP clears the derivatives concerned.

The CSSF page lists the Luxembourg entity types it is relevant for, and the spread is wide: credit institutions, investment firms, investment fund managers, pension funds, UCITS, specialised investment funds, Part II UCIs, specialised PFS and support PFS. A fund manager reading that list should not assume the requirement stops at the management company. For UCITS and AIFs, EMIR calculates clearing positions at the level of the fund, so the status question can land differently across a manager’s range.

Group structure changes the arithmetic. Under Article 7a(2), a counterparty that belongs to a group subject to consolidated supervision in the Union has to consider all the Article 7a(6) derivatives cleared by itself and by other entities in the group, with the exception of intragroup transactions, when it works out whether it is caught. A Luxembourg entity that looks small on its own books can be dragged over the line by activity elsewhere in the group. That is why the form asks for the group’s identity, not only the filer’s.

The two derivative categories that trigger the requirement

Article 7a(6) narrows the whole requirement to two families of contract, and both are interest rate products. The first is interest rate derivatives denominated in euro or Polish zloty. The second is short-term interest rate derivatives denominated in euro. These are the clearing services that the EU determined are of substantial systemic importance, the ones EMIR 3 is trying to draw back from the largest third-country CCPs and into the Union.

The practical consequence is a scoping trap in reverse. A counterparty with a large derivatives book that holds no euro or Polish zloty interest rate exposure of the relevant kind is not inside Article 7a at all, however busy its clearing looks elsewhere. Equity, credit, FX and commodity derivatives do not count toward this threshold. The requirement is deliberately surgical, and the notification form measures activity only against those two categories.

Three status questions, and the carve-outs behind them

Section 3 of the template is where the substance sits. It poses three yes or no questions, and each one connects to a specific piece of the requirement.

The first asks whether the counterparty is subject to the clearing obligation under Article 4a or 10 and exceeds the Article 7a(6) thresholds. A yes here is what brings the counterparty into scope in the first place.

The second asks whether the notional amount outstanding that the counterparty clears in Article 7a(6) contracts exceeds EUR 6 billion. This maps to the de minimis threshold that EMIR 3 applies to the representativeness obligation. A counterparty at or below EUR 6 billion is not asked to clear a representative spread of trades through the active account, because forcing diversity on a very small book would be disproportionate. Cross EUR 6 billion and the representativeness obligation bites: the account cannot be a dormant shell.

The third asks whether at least 85 per cent of the counterparty’s Article 7a(6) contracts are already cleared at an EU CCP authorised under Article 14. The 85 per cent threshold provides an exemption from certain Article 7a operational requirements, stress-testing requirements and Article 7b reporting requirements. It does not remove the active account obligation itself.

Two things are easy to misread here. The carve-outs do not switch off the notification. A counterparty that qualifies for either relief still declares its position on the form; the yes or no answers are how the CSSF and ESMA see who sits where. And the two thresholds do different jobs: EUR 6 billion governs the representativeness obligation, while the 85 per cent test governs the operational conditions. Reading either as a general exemption from the active account requirement is the wrong conclusion.

Completing the CSSF template, field by field

The workbook has a declaration sheet, an instructions sheet, a table for the notification and a worked example. Only the yellow cells need populating. Section 1 captures counterparty information: the 20-character LEI of the notifying entity, its full legal name, its nature as either FC or NFC, its corporate sector, and its competent authority.

The corporate sector field is more particular than it looks. For a financial counterparty, the value has to come from Field 6 of Table 1 of Commission Implementing Regulation (EU) 2022/1860, the EMIR reporting standards, using the codes INVF, CDTI, INUN, UCIT, ORPI, AIFD or CSDS. For a non-financial counterparty, the value is one of the letters A to U from the same field. This is the same taxonomy that already sits behind trade reporting, so the code should match what the firm reports elsewhere rather than being invented for the notification.

The competent authority field is where a Luxembourg entity writes CSSF. EMIR defines the competent authority in Article 2(13): for financial counterparties it is the authority named in the sectoral legislation, and for non-financial counterparties it is the authority referred to in Article 10(5). For entities supervised in Luxembourg, both routes point to the CSSF, and the form expects the acronym.

Section 2 covers group information: whether the counterparty is part of a group under consolidated Union supervision, the LEI of that group, and its full name. Where the group has no LEI of its own, EMIR’s instructions ask the group to nominate one of its counterparties’ LEIs as an agreed group reference, so that all notifications from the same group link together. The same ultimate parent name is used across the group’s FC and NFC notifications. An entity that is not part of such a group repeats its own LEI and name in these cells.

ESMA’s file naming convention is fixed and unforgiving. The template is submitted as EMIR3_YYYYMMDD_[LEI of notifier]_AAN.xlsx, where the date is the submission date and AAN is the fixed suffix for active account notification. The email subject follows the same pattern and, as the instructions stress, keeps the colon after the words “Active Account notification.” These are small formatting rules, but a misnamed file is the kind of thing that stalls an intake queue before anyone reads the content.

Where filers get Article 7a(1) wrong

The notification date is the field I watch most closely when I prepare one of these. The instructions are explicit that the date entered in the declaration is the date from which the counterparty became subject to the active account requirement, not the date the spreadsheet happens to be filled in. Those two dates diverge whenever a firm crosses the threshold and then takes time to file, and because the six-month window to establish the account runs from the date of becoming subject, an inaccurate entry misstates the deadline the firm is actually working to.

A second recurring error is treating the notification as the monitoring report. They are governed by different articles, use different templates and answer to different rhythms. The notification is a one-off status message under Article 7a(1). The monitoring report is a six-monthly demonstration of compliance under Article 7b, built on the ESMA templates released on 13 April 2026 and detailed in the ESMA active account requirement reporting templates. A team that files the notification and assumes the obligation is discharged will miss the recurring cycle entirely.

A third mistake is reading the notification as a once-and-done event when status can change. A counterparty that was below the thresholds and later crosses them becomes subject and has to notify at that point. The form is built to be filed when the position changes, not only at the framework’s start date, which is one more reason the notification date matters.

Finally, do not conflate this with the daily and weekly EMIR flows that share the same regulation. Trade reporting to a repository under Article 9, and the position reporting that EMIR 3 introduced for non-financial counterparties, are separate obligations with their own mechanics. So is EMIR initial margin reporting. The active account notification touches none of those data streams; it is a governance flag, not a data feed.

After the notification: the six-month build and ongoing monitoring

Filing the notification starts a build. A counterparty that has declared itself subject has to establish the active account at an EU CCP within six months of becoming subject to the obligation. EMIR 3 sets operational conditions for that account: it has to be permanently functional, with legal documentation, IT connectivity and internal processes in place; the counterparty has to have the systems and resources to use it for large volumes at short notice; and all new trades in the relevant categories have to be capable of being cleared through it at all times. Where the representativeness obligation applies, the account also has to carry a representative spread of trades rather than sit idle. ESMA gives shape to that spread by identifying up to three derivative classes and up to five relevant subcategories per class, with counterparties clearing at least five trades per reference period in each, reduced to one trade per subcategory where clearing five trades would exceed half of the counterparty’s total trades for the preceding twelve months.

The monitoring layer then takes over. Under Article 7b, a counterparty subject to the requirement calculates its activity and risk exposures in the Article 7a(6) categories and reports every six months to its competent authority, which passes the information to ESMA without undue delay. The report includes a demonstration that the legal documentation, IT connectivity and internal processes behind the active account are in place. ESMA has said the first submission is expected on 31 July 2026, covering 25 June 2025 to 30 June 2026, with later reports due on 31 January and 31 July each year over a twelve-month reference period. Firms mapping their Luxembourg deadlines can slot that against the CSSF reporting calendar for Q3 2026.

The consequences of falling short are set out, not left to guesswork. Article 7a provides that where a counterparty is found in breach, its competent authority imposes administrative penalties or periodic penalty payments, or asks the courts to. The periodic penalty payment has to be effective and proportionate and cannot exceed 3 per cent of the counterparty’s average daily turnover in the preceding business year; it is imposed for each day of delay and for a maximum of six months, after which the authority reviews the measure. That is the mechanism the framework relies on to compel compliance rather than a prediction of how any supervisor will act.

Frequently Asked Questions

Is the active account notification the same as EMIR trade reporting?

No. Trade reporting under Article 9 sends contract-level details to a trade repository and applies broadly. The active account notification under Article 7a(1) is a one-off status declaration that a counterparty has come within the active account requirement. Filing one does not affect the other, and being outside the active account requirement does not exempt a firm from trade reporting.

Does a counterparty above the 85 per cent threshold still have to file?

The 85 per cent test relieves a counterparty of the operational conditions attached to the active account, because it already clears most of its relevant business at an EU CCP. It does not remove the notification. The form is designed to capture that position through its yes or no answers, so the CSSF and ESMA can see which counterparties rely on which relief.

What does EUR 6 billion actually switch on or off?

EUR 6 billion is the de minimis threshold for the representativeness obligation. A counterparty clearing at or below EUR 6 billion notional outstanding in Article 7a(6) contracts is not required to clear a representative spread of trades through its active account. Above EUR 6 billion, the representativeness obligation applies and the account has to carry a genuine, diverse set of trades.

Which date goes in the declaration?

The date from which the counterparty became subject to the active account requirement, not the date the form is completed. Because the six-month window to establish the account runs from that date, entering the completion date instead can misstate the deadline the firm is bound to.

Who is the competent authority for a Luxembourg fund or PFS?

The CSSF. EMIR defines the competent authority in Article 2(13), and for entities supervised in Luxembourg that leads to the CSSF for both financial and non-financial counterparties. The form asks for the acronym, so CSSF is what goes in the field.

How is the completed form named and submitted?

ESMA’s convention is EMIR3_YYYYMMDD_[LEI of notifier]_AAN.xlsx, with the submission date and the fixed AAN suffix, and a matching email subject that keeps the colon after “Active Account notification.” The template instructions describe an email-based submission process. The completed XLSX file is attached to an email sent to the dedicated email addresses provided by CSSF and ESMA; confirm those addresses directly before filing.

Where does the six-monthly monitoring report fit in?

It is a separate obligation under Article 7b, using ESMA’s reporting templates published on 13 April 2026. The first submission is expected on 31 July 2026, covering 25 June 2025 to 30 June 2026, and then twice a year. The notification switches the requirement on; the monitoring report proves the account is working.

Related Articles

• EMIR 3 Clearing Obligation Thresholds and the Active Account Requirement – How EMIR 3 reshaped the clearing thresholds and built the active account requirement that this notification triggers.
• ESMA Active Account Requirement Reporting Templates – The six-monthly Article 7b monitoring report, its templates and reference periods.
• EMIR Reporting Explained – The Article 9 trade reporting baseline that the active account notification is often confused with.
• EMIR Initial Margin Reporting – The separate EMIR margin reporting stream for counterparties with bilateral derivatives.
• ESMA 6th CCP Stress Test – The CCP resilience work that sits behind the EU push to keep systemic clearing in the Union.

Key Takeaways

• The EMIR active account notification under Article 7a(1) is a one-off status declaration to ESMA and the CSSF that a Luxembourg counterparty has come within the active account requirement.
• The CSSF published the notification form (an XLSX template) on 6 July 2026; the requirement itself became applicable on 25 June 2025.
• A counterparty is caught only if it is subject to the clearing obligation under Article 4a or 10 and exceeds the Article 7a(6) thresholds in euro or Polish zloty interest rate derivatives, or short-term euro interest rate derivatives.
• Group counterparties count all relevant derivatives cleared across the group under consolidated Union supervision, minus intragroup transactions, when testing whether they are in scope.
• EUR 6 billion is the de minimis for the representativeness obligation; at least 85 per cent EU-CCP clearing relieves the operational conditions. Neither removes the notification.
• The declaration date is the date the counterparty became subject, and the six-month window to establish the active account runs from it.
• The notification is distinct from Article 9 trade reporting and from the six-monthly Article 7b monitoring report, whose first submission is expected on 31 July 2026.
• Breach can draw administrative penalties or periodic penalty payments of up to 3 per cent of average daily turnover per day of delay, for a maximum of six months.

Sources and References

• Regulation (EU) 2024/2987 (EMIR 3), amending Regulation (EU) No 648/2012 as regards measures to mitigate excessive exposures to third-country CCPs, OJ L, 2024/2987, 4.12.2024: EUR-Lex
• Regulation (EU) No 648/2012 (EMIR), consolidated text: EUR-Lex
• ESMA Interactive Single Rulebook, EMIR Article 7a (Active account): ESMA
• CSSF, Active account notification under Article 7a(1) of EMIR (form, published 6 July 2026): CSSF
• Commission Implementing Regulation (EU) 2022/1860 (EMIR reporting standards, corporate sector codes): EUR-Lex
• Commission Delegated Regulation (EU) 2026/305, regulatory technical standards on the active account requirement (representativeness and thresholds): EUR-Lex
• ESMA, Final Report on the EMIR 3 Active Account Requirement (ESMA91-1505572268-4201): ESMA
• ESMA, reporting templates and instructions for the Active Account Requirement (published 13 April 2026): ESMA

The notification is the front door to your Article 7a obligations

It is tempting to see a single spreadsheet as a formality. The active account notification is closer to a switch. It tells ESMA and the CSSF that a Luxembourg counterparty has crossed into the active account requirement, it sets the date that governs the six-month build of a real clearing account, and it opens the six-monthly monitoring cycle that follows. The firms that treat it as a considered status call, checked against their euro and Polish zloty rates clearing and signed off by someone who owns the numbers, are the ones that never have to explain a wrong date later.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.