Last updated
CSSF Short Selling Net Short Position Notification in Luxembourg: SSR Control Guide
Direct answer
Use CSSF Short Selling Net Short Position Notification in Luxembourg: SSR Control Guide when a short report, activist campaign, or squeeze narrative needs to be separated from the underlying market evidence. It explains understanding public short theses, activist reports, market reaction, disclosure rules, squeeze risk, and how investors should read the evidence, then shows how to separate the short thesis, public evidence, disclosure context, price reaction, squeeze risk, and limits of any market claim. The later sections connect official sources used, start with ssr scope by instrument, and determine whether cssf is the relevant competent authority so the next step is easier to judge. Read it before treating a short report as either proof or noise, because incentives, evidence, timing, and market mechanics all matter.
The CSSF short selling page states that Regulation (EU) No 236/2012 applies to short selling of shares, sovereign debt, sovereign CDS and related instruments admitted to trading or traded on an EEA trading venue, unless primarily traded on a third-country venue. It also states that the SSR requires holders of net short positions in shares or sovereign debt to make notifications once certain thresholds have been breached.
This guide is for investment managers, hedge funds, trading desks, compliance teams, sovereign-debt traders, brokers, legal teams and operations teams. It is not legal advice. Source check date: 20 May 2026.
| Control point | Why it matters | Evidence |
|---|---|---|
| SSR scope | Determines whether net short position controls apply | Instrument list, trading venue, issuer/sovereign competent authority |
| Threshold monitoring | Notifications are triggered when thresholds are breached | Daily calculation, prior position and crossing log |
| CSSF platform | CSSF platform is the notification channel where CSSF is relevant competent authority | Platform user, submission receipt and published-position check |
| Evidence | Trading and compliance need a defensible audit trail | Position file, calculations, approvals and corrections |
Official sources used
This guide uses the CSSF short selling page, CSSF Short Selling Platform materials and related CSSF/ESMA references. Readers should verify current SSR thresholds, ESMA guidance and CSSF platform manuals before acting.
- CSSF: Short Selling (SSR)
- CSSF Short Selling Platform user manual
- CSSF short selling issuers list
- CSSF short selling existing guide
- CSSF administrative sanctions guide
Start with SSR scope by instrument
Short selling controls should begin with instrument classification. Shares, sovereign debt, sovereign CDS and related instruments can be in scope, but the details matter. A fund trading equity swaps, contracts for difference, listed shares and sovereign bonds needs a broader inventory than a simple equity desk.
The CSSF page summarizes the SSR perimeter and notes the EEA trading venue and third-country primary-trading caveat. The instrument master should therefore record issuer, ISIN, venue, competent authority, sovereign issuer, exempted share status where relevant and related-instrument mapping.
A position cannot be monitored properly if the instrument is not identified correctly. The first control is therefore static-data quality.
Static-data exceptions should be escalated before trading volume grows.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Start with SSR scope by instrument starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Determine whether CSSF is the relevant competent authority
Notification to the CSSF depends on the CSSF being the relevant competent authority for the share or sovereign debt. The CSSF page provides lists and platform access where the CSSF is relevant competent authority.
Firms should not assume Luxembourg trading activity automatically means CSSF notification. Competent authority analysis should use the relevant issuer or sovereign list and current SSR rules.
The evidence file should include the authority determination for each issuer or sovereign debt class monitored.
Wrong authority analysis can mean missed or misdirected notifications.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Determine whether CSSF is the relevant competent authority starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Build a daily net short calculation process
Net short position controls need daily calculation. The calculation should aggregate short and long exposures, related instruments and group or fund-level positions according to applicable SSR rules.
Trading systems may show gross shorts, but notification depends on net short position. Operations and compliance should reconcile positions, deltas, corporate actions, derivatives and settlement differences.
The calculation file should preserve inputs, methodology, thresholds and reviewer sign-off.
A daily file is more reliable than reconstructing positions after a regulator asks.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Build a daily net short calculation process starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Monitor threshold crossings and direction
The notification control should detect when a net short position reaches, exceeds or falls below a threshold. This requires prior-day and current-day comparison, not only current exposure.
A downward crossing can be as relevant as an upward crossing for notification. The system should record threshold, direction, position date, prior notification date and deadline.
Manual checks are risky for active trading strategies. Even if the final filing is manual, the alert should be systematic.
Crossing logs are key evidence.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Monitor threshold crossings and direction starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Control CSSF platform access
The CSSF Short Selling Platform is the operational notification channel where CSSF is relevant competent authority. Access should not depend on one employee, one device or one undocumented credential.
Firms should maintain authorized users, backups, role reviews, onboarding and offboarding controls. Platform login issues should be tested before a deadline.
Submission evidence should include platform confirmation, position date, notification type, issuer or sovereign, net short percentage and timestamp.
Access control is a filing control.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Control CSSF platform access starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Use the platform manual as an operating source
The CSSF platform user manual is practical evidence because it describes how users select notification type, search issuers or sovereign debt issuers and enter required fields. Compliance procedures should reflect the actual platform workflow rather than abstract legal steps.
The procedure should identify required fields, document source for each field, screenshot policy where allowed and post-submission verification.
If the platform changes, update the procedure. Do not rely on old screenshots indefinitely.
Operating procedures should follow the tool that actually files the notification.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Use the platform manual as an operating source starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Reconcile trading and compliance data
Trading desks see strategy and execution. Compliance sees thresholds and filings. Operations sees positions and corporate actions. A good short-selling control reconciles all three.
Daily breaks should be investigated. If trading records and custody records differ, the notification calculation should not simply pick one without explanation.
The reconciliation log should identify data source, break, resolution and sign-off.
This is especially important around corporate actions and derivative resets.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Reconcile trading and compliance data starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Handle derivatives and related instruments carefully
Net short positions can include exposures from related instruments. Equity swaps, options, futures, CFDs and other derivatives can create economic short exposure even when no physical share short sale exists.
The calculation methodology should identify which instruments are included, how delta or notional exposure is measured, and where data comes from.
Complex products may require legal and quantitative input. The file should preserve assumptions.
Derivative omission is a common source of underreporting risk.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Handle derivatives and related instruments carefully starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Monitor sovereign debt and sovereign CDS separately
Sovereign debt and sovereign CDS have their own SSR considerations. A desk trading Luxembourg sovereign debt or other sovereign instruments should not use an equity-only control.
The instrument inventory should distinguish issuer type, debt instrument, CDS reference entity, uncovered position analysis and competent authority.
Sovereign positions may involve macro hedges and cross-instrument exposure. The calculation memo should explain methodology.
Separate controls prevent equity assumptions from leaking into sovereign analysis.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Monitor sovereign debt and sovereign CDS separately starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Build a publication monitoring step
The CSSF platform allows publication and consultation of certain significant net short positions in accordance with the SSR. Firms should monitor whether positions expected to be public appear correctly and whether published data matches submission evidence.
Publication monitoring is not a substitute for filing, but it can catch errors quickly. It can also help investor-relations or communications teams understand public visibility.
If a published position is wrong, escalate immediately and preserve evidence.
Publication checks close the loop.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Build a publication monitoring step starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Create a correction and cancellation procedure
Filing errors can occur: wrong issuer, wrong percentage, wrong date, duplicate notification or missed downward crossing. The firm should have a correction procedure before it needs one.
The procedure should identify who assesses the error, who contacts CSSF if needed, how platform corrections are made, and how the internal event log is updated.
A correction should include root-cause analysis, not just a fixed filing.
Recurring corrections indicate control weakness.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Create a correction and cancellation procedure starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Control delegation to administrators or managers
Some funds or managers may rely on administrators, delegates or group compliance teams for position monitoring and filings. Delegation does not remove the need for oversight.
The arrangement should define who calculates, who reviews, who files, who receives alerts, who covers absences and who owns regulatory responsibility.
Service-level expectations should include short-selling deadlines and evidence delivery.
Delegated filing without evidence is weak governance.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Control delegation to administrators or managers starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Integrate trading pre-clearance for sensitive positions
Where strategies may approach thresholds, pre-trade or intraday alerts can prevent surprise crossings. This is especially useful for concentrated positions and active short strategies.
Pre-clearance does not mean trading is prohibited. It means compliance can prepare for possible notification and verify data before deadline pressure.
The alert should identify current net short, proposed change, estimated post-trade position and threshold proximity.
Pre-clearance turns filing into planned workflow.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Integrate trading pre-clearance for sensitive positions starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Manage exempted shares and third-country primary trading
The CSSF page references exempted shares under the short selling legal framework and the SSR caveat for instruments primarily traded on a third-country venue. Firms should maintain current static data on exemptions and primary trading status.
An outdated exemption file can cause over-reporting or under-reporting. Data should be refreshed from official or reliable sources and dated.
When an exemption is relied upon, preserve evidence. Do not rely on informal market assumptions.
Static-data governance is part of regulatory reporting.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Manage exempted shares and third-country primary trading starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Prepare evidence for supervisory questions
A regulator may ask how a position was calculated, why a threshold was not notified, or why a filing was late. The firm should be able to produce the instrument scope, position inputs, calculation method, threshold log, platform receipt and reviewer sign-off.
The response should not require rebuilding data from trading systems weeks later. Store daily files and event packs according to retention policy.
If the position was not reportable, keep the rationale. No-filing decisions can be as important as filings.
Evidence readiness reduces supervisory stress.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Prepare evidence for supervisory questions starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Train traders on notification impact
Traders do not need to become lawyers, but they should know that net short thresholds create reporting obligations. Training should cover threshold proximity, derivatives, sovereign positions, pre-trade alerts and who to contact.
Training should use real strategy examples rather than generic compliance slides. A trader should understand how a hedge can affect net short calculation.
Training records should be maintained, especially for desks that trade in-scope instruments.
Good training reduces surprise and friction.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Train traders on notification impact starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Review thresholds after regulatory changes
Short selling thresholds and related requirements can change through EU or ESMA measures. Firms should monitor CSSF and ESMA updates and update procedures promptly.
Temporary measures, such as the 2020 lower reporting threshold, illustrate why static procedures can become stale. The team should record source check dates.
Change management should include system thresholds, procedure text, training and communication to trading desks.
Regulatory change control is essential.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Review thresholds after regulatory changes starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Coordinate short selling with market abuse surveillance
Short positions can coexist with market abuse risk, especially around rumors, disclosure events, research publication or coordinated trading. Short-selling notification compliance does not by itself solve market abuse risk.
Firms should coordinate short-selling controls with surveillance for insider dealing, unlawful disclosure and market manipulation. Research, trading and communications teams should observe information barriers.
If a short position is connected to issuer-specific confidential information, escalate to legal and compliance immediately.
Regulatory controls should reinforce each other.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Coordinate short selling with market abuse surveillance starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Run periodic file testing
Compliance should periodically test filed and non-filed events. Select days with high short activity, corporate actions or threshold proximity and verify calculations, alerts, filings and evidence.
Testing should identify whether the process caught downward crossings, derivative exposures, sovereign positions and data breaks.
Findings should lead to fixes in static data, reconciliation, training or platform access.
Testing keeps the process alive.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Run periodic file testing starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Use a concise event pack
For each threshold event, keep an event pack: instrument, competent authority, prior position, current position, threshold, position date, notification deadline, platform submission, confirmation and publication check where relevant.
The event pack should be understandable without opening the entire trading database. It should include enough data to defend the filing.
If no notification was made after an alert, include the reason.
A concise pack is the strongest practical evidence.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Use a concise event pack starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Control beneficial-owner and fund aggregation
Short-selling calculations may need aggregation across funds, desks or legal entities depending on control, management and applicable SSR interpretation. The firm should not assume each account is isolated without analysis.
A fund manager should map which portfolios are aggregated, which are separate, who controls investment decisions and how data is consolidated. Group-level arrangements can complicate the file.
The aggregation memo should be reviewed when funds launch, mandates change or investment discretion moves.
Aggregation errors can produce systematic underreporting.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Control beneficial-owner and fund aggregation starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Address intraday threshold pressure
Some desks may cross thresholds intraday and close below them by end of day. The firm should understand the relevant position date and notification rules and configure monitoring accordingly.
A procedure should define whether intraday alerts are informational, when end-of-day calculations are final, and who reviews large temporary exposures.
This reduces confusion between trading-risk alerts and regulatory filing triggers.
Intraday controls are useful even where final notification depends on end-of-day or position-date rules.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Address intraday threshold pressure starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Prepare for corporate actions in short positions
Corporate actions can affect share counts, derivatives, settlement, borrow availability and net short percentages. A split, rights issue, merger or delisting can create calculation complexity.
The short-selling control should receive corporate-action feeds and review affected positions manually where necessary. Static data should be updated before the next calculation cycle.
Event packs should preserve adjustment factors and issuer denominator changes.
Corporate actions are common sources of reporting breaks.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Prepare for corporate actions in short positions starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Track borrow and locate evidence separately
Short selling controls should not confuse net short notification with borrow, locate or settlement controls. A trade can create notification questions and separate settlement or uncovered short-selling questions.
The file should preserve borrow availability, locate records or settlement controls where relevant, while still maintaining a separate net short position calculation.
Separating these controls helps explain what the firm did for reporting versus trading settlement discipline.
This is important where a regulator asks about uncovered positions.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Track borrow and locate evidence separately starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Review public positions for communications risk
When a net short position becomes public, investor-relations, legal or client teams may receive questions. The trading firm should have a communications protocol that avoids disclosing strategy or confidential information improperly.
The protocol should identify who can respond, what can be said, and how to handle media or issuer contact. It should not interfere with required regulatory publication.
Public visibility can affect reputation and client relations, so communications should be coordinated.
A protocol reduces ad hoc responses.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Review public positions for communications risk starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Use scenario testing before active campaigns
Before launching an active short strategy in a relevant issuer or sovereign, run scenario tests. Estimate position changes, threshold crossings, filing deadlines, platform readiness, borrow constraints and public visibility.
Scenario testing lets trading and compliance plan before market speed creates pressure. It can also identify whether derivatives or related instruments create exposure not visible in ordinary share reports.
The scenario should not become a trading recommendation record; it is a compliance readiness tool.
Planning is especially important for concentrated positions.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Use scenario testing before active campaigns starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Maintain regulator contact details and escalation routes
The CSSF short selling page lists a short selling contact address. Firms should maintain current regulator contact details, internal escalation contacts and platform-support procedures.
If a platform issue or filing error occurs close to a deadline, the team should know whom to contact and what evidence to preserve.
Contact records should be verified periodically because webpages and processes can change.
Operational readiness includes knowing how to escalate.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Maintain regulator contact details and escalation routes starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Reconcile published lists and internal static data
The CSSF page links to lists of issuers of shares and issuers of sovereign debt for which the CSSF is the relevant competent authority. Internal static data should be reconciled against current official lists.
If an issuer appears or disappears, the instrument master and notification procedures should update. A stale issuer list can cause wrong filing behavior.
Reconciliation should be dated and archived.
Official-list reconciliation is a low-cost control.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Reconcile published lists and internal static data starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Document no-filing decisions
A short-selling alert does not necessarily result in a notification. The position may be outside scope, below threshold after final calculation, covered by an exemption, linked to a non-CSSF competent authority or generated by stale data. The no-filing decision should still be documented when the alert was material.
A no-filing memo should state the alert, calculation, reason no notification was made, reviewer and evidence. This protects the firm if the same event is questioned later.
No-filing records also help tune alerts. If many alerts are false because of one data source, fix the source rather than accepting review fatigue.
Silence is weak evidence; a concise no-filing note is stronger.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Document no-filing decisions starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Separate public disclosure from internal risk limits
A net short notification threshold is a regulatory reporting concept. It is not the same as the firm's internal trading limit, risk appetite or stop-loss framework. Both can apply at the same time.
Risk teams may impose lower internal alert levels than SSR notification thresholds. Compliance should understand those alerts but not confuse them with filings.
The event file should identify whether an alert is regulatory, internal-risk, borrow, settlement or strategy-related.
This separation prevents unnecessary filings and missed filings.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Separate public disclosure from internal risk limits starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Include corporate actions in daily position governance
Corporate actions can affect net short percentages by changing issued share capital, instrument terms or derivative adjustments. If the calculation uses stale issued share capital, the reported percentage can be wrong.
The short-selling control should receive corporate-action feeds and compare them with official issuer or market data where relevant. The position file should preserve the denominator source.
A corporate-action review is especially important around rights issues, share consolidations, cancellations, mergers and delistings.
Daily governance should include denominator quality.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Include corporate actions in daily position governance starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Review external administrators and prime broker data
Funds often receive position and exposure data from administrators, prime brokers, swap counterparties and internal systems. These sources may not agree. A reporting control should define which source is authoritative and how breaks are resolved.
Prime broker data may be timely but incomplete for derivatives held elsewhere. Administrator data may be official but too slow for notification deadlines. Internal order systems may capture strategy but not settlement adjustments.
The reconciliation model should fit the trading strategy and deadline.
External data reliance requires oversight.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Review external administrators and prime broker data starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Create backup filing scenarios
Platform access, staff absence, connectivity problems or unexpected validation errors can threaten timely notification. The firm should have backup filing scenarios before an event occurs.
Backups can include secondary platform users, alternate network access, pre-saved issuer information, escalation contacts and documented manual evidence if platform issues arise.
A backup test should be run periodically. It should not expose confidential strategy unnecessarily.
Operational resilience applies to regulatory filing too.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Create backup filing scenarios starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Monitor threshold proximity bands
A good control does not only alert after a threshold is crossed. It also monitors proximity bands, such as positions approaching a reporting threshold. This gives trading and compliance time to prepare.
Proximity alerts should be calibrated to strategy volatility. A highly active strategy may need tighter intraday visibility than a slow-moving position.
The alert should not stop trading automatically unless the firm's policy says so. It should prompt awareness and evidence preparation.
Proximity monitoring reduces last-minute filings.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Monitor threshold proximity bands starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Use independent review for high-impact positions
Large or public net short positions can attract market attention. High-impact positions should receive independent review of calculation, competent authority, platform filing and publication expectations.
Independent review can come from compliance, operations or a second reporting specialist. The reviewer should not be the trader who owns the strategy.
The review should be completed before deadline and preserved with the event pack.
Four-eyes review lowers error risk.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Use independent review for high-impact positions starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Align retention with regulatory and audit needs
Short-selling evidence should be retained long enough to answer supervisory questions, audit testing and internal reviews. Retention should cover daily files, event packs, platform confirmations, no-filing memos, correction logs and methodology documents.
The retention policy should specify storage location, access rights and format. Files should be searchable by issuer, ISIN, position date and threshold event.
If data is stored only in trading systems that overwrite history, the evidence file may be incomplete.
Retention is part of control design.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Align retention with regulatory and audit needs starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Coordinate with client and fund disclosures
Investment managers may have client reporting, fund board reporting or offering-document commitments that interact with short positions. SSR notification is separate, but material short exposure may also matter for governance and investor communication.
The firm should know who receives internal reports about public short positions, how client confidentiality is protected and whether any fund documentation imposes additional limits.
Do not disclose strategy details beyond what is required without appropriate approval.
Coordination avoids conflicting messages.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Coordinate with client and fund disclosures starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Build annual methodology certification
At least annually, the firm should certify or review its SSR methodology: instrument scope, competent authority data, thresholds, aggregation, derivatives, sovereign debt, platform access, evidence retention and testing results.
This review should be approved by compliance and challenged by operations or internal audit where possible. Changes should be communicated to trading desks.
A methodology certification helps show that the process is current and not just inherited from an old procedure.
Annual review is especially important when ESMA or CSSF guidance changes.
| Control point | Why it matters | Evidence |
|---|---|---|
| Scope | Build annual methodology certification starts with instrument and competent-authority analysis | Issuer/sovereign list, venue and exemption evidence |
| Calculation | Net short reporting depends on correct aggregation | Daily position file and methodology |
| Filing | Threshold events need timely platform action | CSSF platform confirmation and event pack |
Short selling control checklist
Use this checklist before relying on a short-selling process.
| Control point | Why it matters | Evidence |
|---|---|---|
| Instrument master | Defines in-scope instruments | ISIN, venue, issuer, competent authority |
| Daily calculation | Detects threshold crossings | Net short position file and reviewer sign-off |
| Platform access | Enables timely filing | User list and backup access |
| Threshold log | Tracks upward and downward events | Crossing date, position date and prior notification |
| Correction procedure | Handles filing errors | Error log and root cause |
| Periodic testing | Confirms control effectiveness | Sample tests and remediation |
FAQ
What is the CSSF Short Selling Platform? The CSSF page states that the platform allows notification of significant net short or uncovered positions where CSSF is relevant competent authority, and publication and consultation of certain significant positions.
Does SSR only cover shares? No. The CSSF page refers to shares, sovereign debt, sovereign CDS and related instruments admitted to trading or traded on an EEA trading venue, subject to stated conditions.
Why does competent authority matter? Notifications should be made to the relevant competent authority. The CSSF provides lists for shares and sovereign debt for which it is relevant competent authority.
Can derivatives create reportable short exposure? Related instruments can matter, so firms should include derivative mapping in their methodology.
Is this legal advice? No. It is operational guidance and firms should verify current SSR rules, ESMA guidance and CSSF platform requirements.
Source risk and update note
SSR requirements, thresholds, ESMA measures, CSSF lists and platform procedures can change. This guide was checked against CSSF official sources on 20 May 2026.
Official source and decision check
Use this section as the practical checkpoint for CSSF Short Selling Net Short Position Notification in Luxembourg: SSR Control Guide. The reader decision is whether the available evidence is strong enough to act now, or whether the file should first be confirmed with the financial regulator or exchange source. Rules can change by country, status and date, so treat this guide as orientation for the file and recheck the current rule before relying on a filing obligation, governance deadline, supervisory scope or reporting workflow.
For expats, foreigners, students, workers, founders, families and other mobile readers, record the reader category, country, residence status and deadline before comparing the official source with the article checklist.
Official sources to verify first
- CSSF official website
- CSSF documentation portal
- CSSF laws and regulations
- EUR-Lex EU law access
- ESMA official website
| Decision point | What to check | Reader action |
|---|---|---|
| Short-selling risk and mechanics | Confirm that the case is really about short-selling risk and mechanics, not a different category that follows another rule. | Write down the country, authority, dates, status and document number before asking for a decision. |
| File for financial regulator or exchange source | Keep the borrow, margin, disclosure and risk evidence in one dated file, with originals, translations where required and proof of submission. | Save receipts, emails, appointment confirmations, payment records and authority replies in the same order as the checklist. |
| CSSF Short Selling Net Short Position Notification in Luxembourg: SSR Control Guide fallback | If the answer is refused, delayed or unclear, identify the competent authority, review window, complaint route or regulated provider escalation path. | Ask for the reason in writing and compare it with the official source before paying again, travelling, closing an account or resubmitting. |
| When the answer is unclear | What to do next |
|---|---|
| The authority, bank, insurer, employer or provider gives a verbal answer only. | Ask for the answer in writing, save the name of the office or provider, and compare it with the official source before changing travel, payroll, residence or payment plans. |
| The file depends on a deadline, appointment, payment, address or status change. | Keep the dated receipt, note the next deadline, and avoid closing the old route until the replacement document, account, policy or registration is confirmed. |
Related guides to cross-check
- First month in Europe checklist
- Living in one European country and working in another
- EU remote working guide
- Cross-border worker benefits in the EU
- Private health insurance documents in Europe
For legal, tax, medical, immigration or financial consequences, confirm the position with the competent authority or a qualified adviser. This page is designed to organize the decision, source checks and next steps; it is not a substitute for case-specific professional advice.