CSSF MMFR Handbook v1.4: Rechecking the Article 37 Filing Set-Up

RegReportingDesk card: CSSF, Commission de Surveillance du Secteur Financier, Luxembourg

The CSSF published version 1.4 of its MMFR Handbook on 16 November 2026. The CSSF MMFR Handbook tells Luxembourg money market fund managers, and the banks or PSFs that transmit for them as technical agents, how to deliver the report required by Article 37 of Regulation (EU) 2017/1131. Its change log describes version 1.4 as “Harmonisation, reformatting and review” plus the deletion of the “Reference documents” section.

The 20-page edition restates the set-up in force since MMF reporting moved to eDesk and the S3 API on 1 September 2025, which version 1.3 already recorded; the precise extent of the changes made in version 1.4 requires comparison with version 1.3. Older CSSF documents still online describe an earlier set-up, so the Q4 2026 cycle, due by 25 January 2027, is the point to check procedures and file generation against version 1.4.

Related reading: CSSF MMFR FAQ Update: What Version 5 Changes for Luxembourg MMF Managers

What the CSSF MMFR Handbook version 1.4 changes

Version Date Change recorded by the CSSF
1.0 16 June 2020 Initial version
1.1 15 July 2020 New layout, encryption information, chapter 1.3 added, feedback format information
1.2 28 January 2021 New dashboard for reporting status
1.3 1 July 2025 eDesk and API available from 1 September 2025; old external channels deactivated from that date
1.4 16 November 2026 Harmonisation, reformatting and review; “Reference documents” section deleted

The change log does not say which passages the review touched, and its document page lists version 1.4 as the only edition of the handbook, so a line-by-line comparison with 1.3 would need an archived copy. Section 1.2 still names the chain behind the report: Article 37, Commission Implementing Regulation (EU) 2018/708 with the template, the ESMA guidelines on Article 37 reporting (cited as ESMA34-49-168), ESMA’s technical instructions, validation rules and XSD (ESMA65-8-6480), and Circular CSSF 20/734.

Three dates frame the current cycle:

  • 1 September 2025: eDesk and the API became the only channels; E-file and SOFiE SORT-ATLAS were deactivated.
  • 25 January 2027: the CSSF’s point for Q4 2026 and full-year 2026 reports.
  • 30 January 2027: my calculation of the CSSF’s last day to pass Q4 data to ESMA under Article 37(5), which allows 30 days after the reporting quarter.

Day 25 in the handbook, day 30 in other texts

Section 1.4 requires the files to be submitted through a CSSF-accepted channel “until 25 days after the end of the corresponding quarter/year-end”. The CSSF’s User Guide on Article 37 reporting (version 2, August 2022) gives the same date, with 25 January as its Q4 example, and describes the 30th day as the CSSF’s own deadline to transmit to ESMA.

A calendar built from other texts would show day 30. Circular CSSF 20/734 of 28 January 2020 requires submission “until 30 days after the end of the corresponding quarter/year”, and paragraph 10 of the ESMA guidelines (final report ESMA34-49-168, appended to Circular CSSF 20/736) says managers could send the report until 30 days after the quarter or year. The CSSF’s page on reporting to be submitted by UCIs, last updated on 6 November 2026 and already listing eDesk and the API, still gives MMF reports a deadline “within 30 days of the end of the quarter or year”. On my reading, the handbook, updated on 16 November 2026, is the more specific text and puts the CSSF’s receipt point at day 25; a file submitted by day 25 meets both.

Point Circular CSSF 20/734 (2020) Handbook v1.4 (2026)
Submission point 30 days after quarter or year-end 25 days after quarter or year-end
Channels Those on the CSSF file-transport page eDesk or API under Circular CSSF 23/833
CSSF return files MMFFBR, MMFFDB (ZIP), MMFFBH (ZIP) MMFFDB (XML), MMFFBH (ZIP)

A report cannot go in before the quarter ends or, where relevant, before the liquidation, merger or withdrawal date. The handbook gives no weekend or holiday roll-forward; 25 January 2027 is a Monday.

eDesk, the S3 API and the technical agent

Section 2.1.1 lists the two channels under Circular CSSF 23/833. eDesk carries a dedicated MMF procedure for submissions and feedback, separate from other fund modules such as the CSSF LMT activation module. For the API, the sender’s “IT Expert” creates a bucket named “MMF Reporting” on the eDesk IT management console, following the CSSF’s S3 API technical guidance.

E-file (Fundsquare) and SOFiE SORT-ATLAS (Cetrel Securities) were deactivated from 1 September 2025; feedback on reports sent through them before that date returns through the same channels. Any file sent since, including a correction for an earlier period, goes through eDesk or the API.

For administrators, the operative detail is the sender block in the file name, which identifies “the MMF manager or the technical agent” with the usual CSSF letters: B for a bank, P for a PSF, S for a management company, A for an AIFM. On the API, error FIL-001 rejects a file whose bucket participant differs from the participant in the file name, so, on my reading, a technical agent files under its own identifier from its own bucket. Error CME-019 rejects a sender not authorised to send MMFR reporting; the handbook does not describe how that authorisation is set up.

Identifiers and file names that trigger rejections

The CSSF uses its own version of the ISO 20022 message auth.093.001.01, with restrictions added to the ESMA schema, the first being one report per MMF and period in each file. Sections 2.2 and 2.3 set these formats:

Element Required format Check
File name MMFREP-[sender]-O[fund]-[sub-fund]-YYYY-[Q1/Q2/Q3/Q4/Y1]-[sequence].zip; one same-basename .xml file inside FIL-113; CSSF-001 against XML content
Sub-fund ID (FndNttyId/Id) OMMMMMMMM_CCCCCCCC, with an underscore CSSF schema
Manager ID (FndAuthrtyRegnNb/Id) S plus 8 digits (Chapter 15 or 16 management company) or A plus 8 digits (AIFM) CSSF schema
Depositary ID (DpstryId/Id) B plus 8 digits (credit institution) or P plus 8 digits (professional depositary of assets other than financial instruments) CSSF schema
Header sender and recipient From LU, To EU CSSF-004
Message definition auth.093.001.01 FIL-104, CSSF-003

The MMF national code joins the eight-digit fund and sub-fund identifiers with an underscore inside the XML. For a single, non-umbrella fund, the sub-fund component is 00000000 (Appendix 1 of Circular CSSF 20/734). In the file name, the fund and sub-fund components are separated by hyphens. Each ZIP holds exactly one XML (FIL-102) with a matching name (FIL-103), and archives above 20 MB are rejected (FIL-002). A file covering several quarters takes the last quarter in its name, according to the user guide.

Teams mapping error codes into tooling should note that the “MMFR Error codes” workbook still listed beside the handbook is dated 4 May 2021 and does not contain FIL-001 or FIL-002. The handbook’s tables are the fuller reference for file errors under the current channels.

Sequence numbers, corrections and the two dashboards

The sequence number is a sub-fund-level counter starting at 0001, with no reset at year-end. Order matters: section 1.3 warns that a report can pass CSSF validation and still not reach ESMA if a higher sequence for the same period has already gone there. A correction is resubmitted as “Upd” with a higher sequence. A cancellation (“Cxl”), used mainly for a wrong national code, invalidates the existing record.

The CSSF runs file checks and “a light content validation”, returning an MMFFDB file in XML; ESMA applies the business rules, and the CSSF relays its response as an MMFFBH ZIP. Each report ends as RJCT, ACPT or WARN, and a reused file name is rejected. The user guide treats a late report, or one that is incorrect, incomplete or outside the naming conventions or consistency checks, as an obligation not met. I read that as leaving a period open until a valid version goes through.

“Dashboard” means two things on the CSSF site. The handbook’s “MMF reporting dashboard” is an eDesk application consolidating CSSF and ESMA statuses for each manager’s expected reports, open to the MMF manager’s users holding the role of that name. The money market funds page separately lists PDF publications titled “MMF Reporting Dashboard”, the December 2025 edition dated 25 June 2026 and covering data from Q1 2020 onward.

What the handbook leaves to other documents

Version 1.4 covers how a report travels and is validated. Field content comes from the template in Implementing Regulation (EU) 2018/708 and the ESMA guidelines implemented by Circular CSSF 20/736. Stress-test fields take their parameters from ESMA’s stress test guidelines, whose 2025 update (ESMA50-481369926-30585) the CSSF integrated through Circular CSSF 26/911 of 19 May 2026.

The handbook is silent on the CSSF’s final guidance on MMF weekly liquid asset levels of 30 October 2026, which runs on a separate notification track. Changes to the template itself would need EU-level instruments, the track covered in our note on the European Commission’s MMF Regulation review. Section 4.2 points to the Swift MyStandards Readiness Portal for testing, and section 4.1 gives opc@cssf.lu for questions.

Frequently Asked Questions

Our MMF is below EUR 100 million and reports annually. Does day 25 apply?

Yes. Article 37(1) allows annual reporting where assets under management in total do not exceed EUR 100 000 000, and section 1.4 applies the 25-day point to the “quarter/year-end”. The user guide adds that an authorised MMF still unlaunched at 31 December files a static-data report flagged “NOTX” in field 57, annually and on the same deadline.

We changed technical agent mid-year. Does the new agent restart at 0001?

No. Section 3.1.1 ties the sequence to the sub-fund, and its third example shows a new agent filing Q2 as 0003 after the previous agent’s Q1 file (0001) and correction (0002). The incoming agent needs each sub-fund’s last sequence at handover.

A sub-fund merged mid-quarter. What dates go into the last report?

Submission waits until the merger date, and rule CME-061 requires the merger date to equal the reporting end date. The user guide puts that date in the “To Date” field and shows the last stress test results without a new pre-event test. Paragraph 37 of the ESMA Article 37 reporting guidelines provides for the final report of a merged MMF to be sent within 30 days after the end of the quarter of merger. The CSSF handbook separately specifies a general Luxembourg submission point of 25 days after the relevant quarter or year-end. For the Luxembourg filing calendar, apply the earlier CSSF operational point unless the CSSF confirms a different treatment for the final merger report.

Key Takeaways

  • Leave room inside the 25 days for a rejection; the corrected file needs a higher sequence and fresh CSSF and ESMA validation.
  • Re-point procedures, calendars and vendor settings that cite E-file, SOFiE or a 30-day CSSF deadline to version 1.4.
  • API filers: confirm the “MMF Reporting” bucket and the file-name sender belong to the same participant.
  • Build file-error mapping from the handbook’s tables, since the 2021 workbook lacks FIL-001 and FIL-002.
  • Ensure that the MMF manager’s users responsible for reconciling CSSF and ESMA statuses have the eDesk “MMF reporting dashboard” role. Confirm any technical-agent access separately.

Sources and References

  • CSSF, MMFR Handbook, Version 1.4, 16 November 2026: page and PDF
  • Regulation (EU) 2017/1131, Article 37: EUR-Lex
  • Commission Implementing Regulation (EU) 2018/708: EUR-Lex
  • ESMA, Guidelines on reporting under Article 37 of the MMF Regulation (ESMA34-49-173 on the ESMA page; final report ESMA34-49-168): ESMA
  • ESMA, MMF Reporting Technical Reporting Instructions (ESMA65-8-6480): ESMA
  • CSSF, User Guide: Reporting under Article 37 of the MMFR, Version 2: CSSF
  • CSSF, MMFR Error codes (4 May 2021): CSSF
  • Circular CSSF 20/734 (28 January 2020): CSSF
  • Circular CSSF 20/736 (28 January 2020): CSSF (PDF)
  • Circular CSSF 23/833 (16 May 2023): CSSF
  • Circular CSSF 26/911 (19 May 2026): CSSF (PDF)
  • CSSF, S3 Application Programming Interface technical guidance: CSSF
  • CSSF, New transmission method for MMF reporting, 16 April 2025: CSSF
  • CSSF, Money market funds page: CSSF
  • CSSF, Reporting to be submitted by UCIs (MMF Reporting): CSSF
  • CSSF, Final Guidance on MMF Weekly Liquid Asset Levels, 30 October 2026: CSSF

Before the Q4 2026 MMF files go in on 25 January 2027

The Q4 2026 cycle is a practical opportunity to check whether the MMFR submission set-up follows the CSSF’s documented filing requirements: each sub-fund’s file named to the convention, an underscore-joined national code inside the XML, the next sequence number in that sub-fund’s series, and a route through the participant’s own bucket or the eDesk procedure. By 25 January 2027, each expected Q4 2026 or annual 2026 report should have been submitted through an accepted CSSF channel. Teams should then reconcile CSSF and ESMA feedback until the reports achieve ACPT or WARN, correcting and resubmitting any rejected reports.

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

Similar Posts