Last updated
CSSF T+1 Settlement Readiness Survey 2026: Practical Luxembourg Preparation Guide
Direct answer
CSSF T+1 Settlement Readiness Survey 2026: Practical Luxembourg Preparation Guide helps compliance teams, directors, risk owners, and advisers translate a Luxembourg supervisory topic into owners, evidence, and escalation points. It explains understanding the Luxembourg regulatory obligation, supervisory evidence, internal ownership, and escalation points in CSSF T+1 Settlement Readiness Survey 2026: Practical Luxembourg Preparation Guide, then shows how to map the controlling rule, prepare board or compliance evidence, and know when a CSSF-facing specialist should review the file. The later sections connect official sources used, why the survey matters, and t+1 changes the whole chain so the next step is easier to judge. Read it before assigning owners or responding to a supervisory request, so the evidence file matches the regulatory question.
For Luxembourg banks, investment firms, fund managers, central administrators, depositaries, custodians, brokers, transfer agents, settlement internalisers, issuers, treasury teams, and outsourced service providers, the practical message is straightforward: T+1 is not a late-2027 project. It is a 2026 discovery, dependency, testing, and remediation project. The entities that wait until the final year may discover that trade allocation, confirmation, FX funding, securities lending, corporate actions, NAV timing, custody cut-offs, static data, and exception handling cannot be compressed by policy alone.
Official sources used
- CSSF: Reminder of the importance of participating in T+1 initiatives, 2 June 2026
- CSSF: T+1 readiness complementary survey, 12 May 2026
- CSSF: T+1 Settlement: Preparing for the future of European financial markets
- CSSF: Countdown to halving settlement times on financial markets
- CSSF: High-level Roadmap to T+1 Securities Settlement in the EU
- CSSF: Prudential reporting for investment firms
Official CSSF, ESMA, EUIC, CSDR, and market infrastructure materials can change. Verify the current survey links, deadlines, implementation roadmap, legal text, and sector-specific guidance before acting.
Decision matrix
Use this matrix to turn the CSSF survey into an operational readiness decision rather than a one-off questionnaire.
| Readiness question | Decision support | Evidence to keep |
|---|---|---|
| Should the firm answer the survey? | The CSSF strongly urged broad and timely participation before the 9 June 2026 deadline, so Luxembourg market participants should treat response ownership as a governance task. | Survey owner, submitted response, management note. |
| What is the implementation date? | The CSSF's 2 June 2026 reminder states that the T+1 settlement cycle under CSDR is effective from 11 October 2027. | CSSF reminder, legal-text reference, project milestone plan. |
| Is this only a settlement function issue? | No. Map trade capture, allocation, confirmation, matching, custody, funding, FX, static data, NAV timing and exception handling. | End-to-end process map, impacted-system list, exception history. |
| Which flows are highest risk? | Prioritise cross-border, high-value, high-volume, manually corrected and historically late-settling flows. | Flow inventory, fail data, market and custodian dependency register. |
| Are providers ready? | Internal readiness is incomplete until brokers, custodians, administrators, transfer agents and vendors confirm cut-offs, formats and testing windows. | Provider attestations, SLA change log, testing calendar. |
| Can exceptions be fixed within T+1 timing? | If today's exception queue depends on spare T+2 time, remediation must begin before late 2027. | Root-cause analysis, target metrics, owner and remediation date. |
Why the survey matters
Surveys are sometimes dismissed as optional administration. In this case, the survey is also a discovery tool. The CSSF states that it wants better visibility on the situation within Luxembourg, including potential points of attention. Broad participation across financial sectors and Member States is described as crucial to obtain an accurate overview of preparation status and identify areas needing further attention. That means a thoughtful response can help the supervisor and industry understand where risks are concentrated.
For the firm itself, the survey forces the first useful inventory. Which activities settle on a T+2 timeline today? Which systems assume T+2? Which providers need to adapt? Which deadlines move? Which manual steps cannot survive compression? Which exceptions are already frequent? Which markets, clients, products, and operating models are most exposed? A firm that answers these questions honestly gains a practical roadmap, not just a submitted survey.
T+1 changes the whole chain
The CSSF says the move requires review across the entire trading and post-trading chain, not just the settlement layer. This point should shape every internal project plan. Settlement is the visible deadline, but settlement depends on trade capture, allocation, confirmation, matching, funding, FX, securities availability, custody instructions, standing settlement instructions, corporate action data, cash forecasting, margin, collateral, lending and borrowing, reconciliation, exception management, and communication.
If one link remains on a T+2 operating rhythm, the chain may fail. A trade may be executed correctly but allocated too late. It may be allocated but not matched. It may be matched but not funded. It may be funded but not instructed. It may be instructed but rejected because static data is stale. A T+1 project should therefore map the chain from trade decision to final settlement and exception closure.
Fund operations need special attention
Luxembourg's fund ecosystem creates additional complexity. Management companies, AIFMs, UCITS, AIFs, central administrators, depositaries, transfer agents, distributors, portfolio managers, and custodians may all sit in different entities and countries. NAV timing, order cut-offs, subscriptions, redemptions, portfolio trades, swing pricing, liquidity management, custody reconciliation, and cash management may need review. A fund that invests in markets moving to T+1 while its own subscription and redemption cycle remains different needs to understand the liquidity effect.
Fund boards should ask whether T+1 affects dealing cut-offs, portfolio funding, settlement fails, cash buffers, overdrafts, FX execution, collateral, liquidity risk management, and investor communications. The answer may differ by strategy, asset class, market, share class, and service-provider model.
Custody and broker dependencies
T+1 readiness depends heavily on brokers, custodians, CSDs, settlement systems, and service providers. A firm cannot solve the entire chain internally. It needs evidence from its counterparties. Which cut-offs will change? Which instruction formats change? Which matching tools are available? Which markets are covered? Which exception reports will arrive earlier? Which SLAs need amendment? Which escalation contacts apply during transition? Which testing windows exist?
A mature firm maintains a dependency register. The register should name the provider, affected process, required change, provider readiness status, evidence received, open issue, owner, and deadline. Without this register, the firm may believe it is ready because its internal project plan is green while a critical provider remains unresolved.
Funding and FX compression
Moving from T+2 to T+1 compresses cash and FX processes. Treasury teams may have less time to forecast, fund, convert currency, manage overdrafts, and respond to failed trades. Cross-border activity adds time-zone and currency complexity. A portfolio manager may execute a trade in one market while funding depends on cash flows elsewhere. If FX instructions, cash forecasting, and custody cut-offs are not aligned, settlement risk increases.
The practical control is a funding scenario analysis. Identify trades, markets, currencies, funds, and clients where cash must move faster. Test whether data arrives early enough to make funding decisions. Check whether FX providers and custodians can support the required cut-offs. Define what happens if funding fails.
Static data and standing settlement instructions
Standing settlement instructions are a classic source of settlement defects. T+1 gives less time to fix them. Firms should review client static data, counterparty data, custodian accounts, settlement locations, market identifiers, instrument identifiers, broker instructions, and escalation contacts. The review should not be a spreadsheet clean-up exercise only. It should test whether trade systems, middle-office tools, custody portals, and outsourced providers all use the same current data.
A useful static-data exercise focuses on high-volume, high-value, cross-border, and historically problematic flows first. It also identifies who can change data, who approves changes, and how changes are tested before live use.
Exception management becomes the project
In a T+2 world, some exceptions can be handled with extra time. In a T+1 world, exception capacity becomes a key control. Firms should analyse current exception volumes, root causes, resolution times, late confirmations, unmatched trades, rejected instructions, missing SSIs, funding breaks, and custody breaks. Then ask which exceptions would fail under T+1 timing.
The project should reduce avoidable exceptions before implementation. Automation helps, but root-cause reduction matters more. A faster exception queue still fails if the same avoidable errors keep entering it.
What market participants should do before the 9 June 2026 survey deadline
Before responding, firms should hold a short cross-functional readiness session. Include front office, middle office, operations, treasury, compliance, risk, IT, legal, vendor management, and key outsourced providers where possible. Map affected activities. Identify known gaps. Record dependencies. Decide who owns the response. Submit a factual answer, not an aspirational one. Then turn the response into a project backlog.
The survey deadline should be treated as the first governance milestone. After submission, the firm should produce a management note summarising readiness status, major risks, provider dependencies, testing needs, and next decisions.
Customer and investor communication
Clients may need to understand new cut-offs, funding expectations, document timelines, or settlement-fail consequences. Institutional clients may need to align their own operations. Fund investors may need clearer communication if subscription, redemption, or cash management processes are indirectly affected. A firm should not wait until operational friction appears before explaining changes.
Communication should be accurate and limited to what is known. It should avoid promising no impact before testing is complete. It should also explain practical actions: update SSIs, respond to confirmations faster, pre-fund where required, review cut-offs, and maintain current identifiers.
Board-level reporting
Boards and authorised management need concise readiness reporting: affected business lines, critical dependencies, provider readiness, system changes, testing status, exception reduction, funding risks, client communication, budget, and unresolved decisions. The report should distinguish current readiness from projected readiness. A project that depends on future vendor delivery is not fully ready.
Good reporting also identifies cross-border dependencies. Luxembourg market participants often rely on international managers, custodians, brokers, administrators, and infrastructure. T+1 readiness should be coordinated across those relationships.
Editorial risk note
This guide is not legal advice, regulatory advice, or a substitute for CSSF, ESMA, EUIC, CSDR, or infrastructure guidance. T+1 effects are activity-specific. Use this article as a practical control framework and verify the current official materials, timelines, and provider requirements before acting.
Readiness Checklist
- Submit or evidence the decision on the CSSF national competent authorities' survey before the 9 June 2026 deadline if in scope.
- Confirm impacted legal entities, desks, funds, instruments, markets, custodians, brokers and outsourced providers.
- Map the current trade-to-settlement timeline and mark every step that depends on T+2 timing.
- Review allocation, confirmation, SSI, custody, funding, FX, NAV, cash forecasting and exception queues together.
- Collect provider cut-offs, format changes, testing windows, escalation contacts and service-level changes.
- Report readiness to authorised management with open dependencies, funding risks, client impacts and remediation dates.
Next Steps
- Turn the survey response into a project backlog within one week of submission.
- Run a first exception root-cause review using recent failed or late-settling trades.
- Ask each critical provider for T+1 cut-offs, testing plans and evidence of readiness.
- Prepare client or investor communication only after process impacts are confirmed.
- Schedule board-level updates around dependency closure, testing completion and residual-risk decisions.
Readiness playbook
Readiness control 1: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 2: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 3: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 4: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 5: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 6: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 7: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 8: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 9: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 10: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 11: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 12: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 13: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 14: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 15: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 16: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 17: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 18: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 19: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 20: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 21: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 22: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 23: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 24: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 25: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 26: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 27: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 28: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 29: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 30: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 31: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 32: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 33: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 34: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 35: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 36: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 37: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 38: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 39: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 40: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 41: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 42: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 43: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 44: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 45: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 46: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 47: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 48: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 49: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 50: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 51: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 52: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 53: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 54: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 55: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 56: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 57: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 58: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 59: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 60: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 61: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 62: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 63: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 64: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 65: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 66: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 67: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 68: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 69: exceptions
For CSSF T+1 settlement readiness and the 2026 survey process, test what happens when evidence is missing, a provider is late, data is inconsistent, or a rule is not yet fully implemented. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 70: remediation
For CSSF T+1 settlement readiness and the 2026 survey process, test what can be fixed this month, what needs a project, and what must be disclosed as residual risk to management. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 71: scope map
For CSSF T+1 settlement readiness and the 2026 survey process, test which legal entity, branch, desk, fund, custodian, market infrastructure, outsourced provider, or business process is actually affected. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 72: deadline control
For CSSF T+1 settlement readiness and the 2026 survey process, test which official date, consultation window, survey deadline, implementation milestone, or transitional rule creates the critical path. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 73: process owner
For CSSF T+1 settlement readiness and the 2026 survey process, test who owns the process, who approves the design, who can stop go-live, and who receives exceptions. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 74: source evidence
For CSSF T+1 settlement readiness and the 2026 survey process, test which file, register, system report, contract, board paper, procedure, or regulatory text proves the answer. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 75: operational dependency
For CSSF T+1 settlement readiness and the 2026 survey process, test which counterparty, custodian, broker, CSD, platform, service provider, data vendor, or group function must change at the same time. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 76: senior governance
For CSSF T+1 settlement readiness and the 2026 survey process, test which board or authorised management metric would show readiness, delay, concentration, or unaccepted risk. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 77: customer consequence
For CSSF T+1 settlement readiness and the 2026 survey process, test how the rule affects investors, clients, issuers, counterparties, complaints, communications, onboarding, or service continuity. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
Readiness control 78: testing
For CSSF T+1 settlement readiness and the 2026 survey process, test which dry run, reconciliation, scenario test, sample review, legal analysis, or control test proves the process can work. The move to T+1 compresses time, so weak dependencies become visible faster. A useful answer names the owner, source evidence, review date, dependency, exception route, and next action. If the answer is only a project slogan or a compliance assertion, it is not strong enough for board review, supervisory dialogue, or client-facing confidence.
FAQ
What is the EU T+1 implementation date referenced by CSSF?
The CSSF states that from 11 October 2027, CSDR as amended introduces migration from T+2 to T+1.
Is T+1 only a settlement department project?
No. CSSF says the change requires review across the entire trading and post-trading chain, not just the settlement layer.
Why should firms answer a voluntary survey?
The CSSF says the survey helps monitor preparedness in Luxembourg and identify points needing attention.
What should be reviewed first?
Start with affected flows, provider dependencies, settlement instructions, funding and FX timing, current exception volumes, and testing windows.