Home ArticlesCSSF U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission Guide

guide

Last updated June 25, 2026

CSSF U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission Guide

Direct answer

Use CSSF U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission Guide when a CSSF-facing question needs a structured file rather than a loose policy summary. It explains understanding the Luxembourg regulatory obligation, supervisory evidence, internal ownership, and escalation points in CSSF U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission 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 what changed, checklist before filing, and next steps for the reporting team 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.

What changed

The CSSF's January 2026 U1.1 communication identifies the new reporting format and the available submission routes. The CSSF's September 2025 XSD communication states that the new XML schema is available, that the new format applies from the 12/2025 reference period, and that the schema is backward compatible. It also warns that fields added as optional in the XSD may be subject to checks depending on the reporting period. The CSSF's December 2025 delegation communication states that, starting 31 December 2025, U1.1 reporting changes and transmission may be delegated through the delegation module in the dedicated eDesk procedure.

The operational decision is therefore practical: confirm whether the report has a December 2025 or later reference date, decide whether the entity will submit through eDesk or S3 XML, confirm who may transmit, and retain proof that the submitted data can be reproduced from source records.

Decision matrix

Situation	Source/evidence	Operational action	Supervisory risk	Fallback
Reference date is December 2025 or later	CSSF 5 January 2026 communication and CSSF 25 September 2025 XSD communication	Use the new U1.1 format and document the period assessment.	Wrong format or period treatment may delay filing or create correction work.	Recheck the eDesk procedure and XSD notes before transmission.
Manual or procedural submission is preferred	CSSF 5 January 2026 communication and eDesk user guide inside the dedicated procedure	Confirm eDesk access, submitter role, maker-checker review, and acknowledgement storage.	Access gaps or unclear roles can make submission dependent on one user.	Assign an alternate authorised user and keep screenshots or acknowledgements as evidence.
Automated XML submission is preferred	CSSF 5 January 2026 communication and CSSF 25 September 2025 XSD communication	Validate XML generation, S3 routing, schema version, file naming, and error handling.	A technically valid file may still fail period-specific checks.	Run pre-submission validation against the current XSD and review business-field checks.
Transmission is delegated	CSSF 17 December 2025 delegation-module communication	Use the delegation module in the dedicated eDesk procedure and record the delegation scope.	Unclear submitter designation can weaken accountability for filing evidence.	Keep an internal approval note and revoke or amend delegation when roles change.
Optional XSD fields appear irrelevant	CSSF 25 September 2025 XSD communication	Map added fields to reporting periods and document whether each field is used, checked, or not applicable.	Assuming optional means unnecessary may create rejection or query risk.	Ask the reporting owner to review the eDesk guide and contact [email protected] where the official procedure remains unclear.

Checklist before filing

Artifacts: current eDesk procedure notes, U1.1 user guide from eDesk, XML schema, field map, source-data extract, validation results, delegation approval, submission acknowledgement, and rejection or correction log.
Internal owner: reporting owner for content, IT or data owner for XML and S3, compliance owner for regulatory evidence, and an approved submitter or delegate for transmission.
Evidence to keep: reference-period assessment, channel decision, access review, schema version, reconciliation to source records, maker-checker sign-off, and proof of final submission.
Official source to check: the CSSF U1.1 new-format page, the CSSF XSD page, the CSSF delegation-module page, and the user guide available in the dedicated eDesk procedure.
Escalation point: escalate to compliance or a legal adviser if the entity scope, delegation authority, reporting period, field interpretation, or correction approach is not clear from the official procedure.

Next steps for the reporting team

First, inventory all U1.1 reports with reference dates from December 2025 onward. Second, decide whether each report will use the eDesk procedure or XML via S3. Third, test access and delegation before the filing window becomes operationally tight. Fourth, map every material field to source data and mark any field that is optional in the XSD but may be checked for the reporting period. Fifth, keep a file that shows who prepared, reviewed, approved, transmitted, and monitored the report.

If a submission fails, classify the issue before resubmitting: schema issue, source-data issue, period mismatch, delegation problem, transmission problem, or unclear official instruction. That classification helps the team correct the cause rather than only resending a file.

Official sources

CSSF: U1.1 Reporting - New format and new features, published 5 January 2026.
CSSF: Reporting U1.1 - Availability of the new XSD schema, published 25 September 2025.
CSSF: Reporting U1.1 - Delegation module available as of 17 December 2025, published 17 December 2025.

Regulatory note

This guide is general regulatory information. It does not replace CSSF instructions, the eDesk user guide, XML schema materials, or entity-specific professional advice. Confirm the live CSSF procedure before filing.

Official source and decision check

Use this section as the practical checkpoint for CSSF U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission 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 CSSF or reporting portal 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

Decision point	What to check	Reader action
Cssf u1.1 reporting format transition	Confirm that the case is really about CSSF U1.1 reporting format transition, 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 CSSF or reporting portal source	Keep the template, submission and deadline 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 U1.1 Reporting New Format, eDesk and S3: Practical 2026 Submission 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

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.