Skip to content
CSSF · Luxembourg

The Luxembourg reporting calendar for a payment firm

Fintech Passport
August 20, 2026 · 10-min read
The Luxembourg reporting calendar for a payment firm

Luxembourg’s calendar is dominated by one supervisor, which makes it simpler to map and easier to under-estimate. The CSSF collects most of it; the CRF, the BCL, the AED and the beneficial-ownership register take the rest. A high share of the obligations are notifications, registers and attestations rather than returns, and those are the ones that fail quietly. The calendar is also about to change channel: from 1 April 2027 the CSSF’s periodic reporting for payment and e-money institutions moves to eDesk.

1. Who collects what

CounterpartyWhat it collectsRhythm
CSSFPeriodic financial tables, annual audit and control documents, outsourcing notifications, governance certificate, complaints table, ICT incident notifications and the DORA register of information, the AML/CFT data collectionMonthly, quarterly, annual and event-driven
CRFSuspicious transaction reports through goAMLEvent-driven, without delay
BCLStatistics on payment instruments and operations, including the PSD2 fraud dataPeriodic, on the BCL’s remittance calendar
AEDCESOP cross-border payment data via MyGuichet.luQuarterly
RBEThe beneficial-ownership registerKept current when ownership changes

2. The periodic CSSF tables: the 20th of the month

The CSSF legal reporting for payment and e-money institutions rests on Circular CSSF 10/462 together with Circular CSSF 11/511 for payment institutions and Circular CSSF 11/522 for e-money institutions. Payment institution tables are coded Z, e-money tables W. The deadline is the same across the set: the 20th of the month after the period ends.

TablePIEMIDue
Balance sheetZ 1.1, monthlyW 1.1, monthly20th of the following month
Third-party funds heldZ 1.2, monthlyW 1.2, monthly20th of the following month
Authorised reinvestmentsn/aW 1.3, quarterly20th of the month after quarter-end
Capital adequacyZ 1.4, quarterlyW 1.4, quarterly20th of the month after quarter-end
Profit and loss accountZ 2.1, quarterlyW 2.1, quarterly20th of the month after quarter-end
Analysis of shareholdingsn/aW 4.5, yearly20th of the month after year-end

Today the tables travel as the CSSF’s Excel templates, in .xls or .xlsx, through the external transmission channels governed by Circular CSSF 23/833. The template structure must not be altered, and tables an entity does not need must not be deleted. An e-money institution with branches abroad also files branch and whole-institution versions under Circular 11/522.

3. The 2027 switch to eDesk

In September 2026 the CSSF announced that the Excel route will be replaced by a reporting module inside eDesk. Its timetable has three parts:

  • 1 January to 31 March 2027: a testing phase open to all concerned entities. Test submissions are not official regulatory submissions.
  • Until 31 March 2027: every report due on or before that date is still filed through the current channel, whatever testing is under way.
  • From 1 April 2027: eDesk becomes the sole official channel and the old process stops. That covers every report due on or after that date, including reports for periods that ended before it, such as the March 2027 monthly report and the Q1 2027 quarterly report.

The content changes too. A new circular, not yet published at the time of writing, will replace Circulars 11/511 and 11/522 and add obligations for crypto-asset service providers authorised under Article 63 of MiCAR. The announcement describes quarterly financial and human-resources data (including control-function staffing), monthly reporting limited to the segregation of funds, and an annual return on shareholding, branches, agents and distributors, previously requested ad hoc. Submission will be manual in eDesk or a JSON file over S3. An annex lists the data points, which may still change slightly.

4. The annual pack

The annual documents are governed mainly by Circular CSSF 15/614, plus the governance circular and the conduct rules. Several of them have deadlines set relative to the ordinary general meeting rather than to a calendar date, so they move with the firm’s own AGM date:

  • Short form report on the annual accounts: as soon as possible, and at the latest two weeks before the ordinary general meeting.
  • Long form audit report: as soon as possible, and at the latest one month after the ordinary general meeting (the content is set by Circular CSSF 12/550 for payment institutions and 13/569 for e-money institutions).
  • Summary report of the internal auditor: at the latest on the last day of the third month after the closing date, so 31 March for a calendar-year firm.
  • Table of complaints with a summary report: by 1 March each year, under Circular CSSF 17/671. See conduct and complaints.
  • Annual certificate of compliance with Circular CSSF 26/906 on internal governance, the compliance officer’s annual report, the PSP ICT and security risk assessment (Circular CSSF 25/880), the proposed allocation of results, the final versions of the periodic tables, and the minutes and attendance list of the general meeting.

5. Event-driven and annual exercises outside the pack

  • Suspicion reporting to the CRF through goAML, with the abstention and blocking powers attached.
  • Outsourcing notifications and the register under Circular CSSF 22/806, an advance-notification regime with a maintained register.
  • The DORA register of information, submitted through its own eDesk procedure (the window for the 31 December 2025 reference date ran from 11 February to 31 March 2026), and major ICT incident reporting under Circular CSSF 25/893.
  • The CSSF AML/CFT data collection. For 2026 the CSSF used AMLA-developed templates instead of its own financial-crime questionnaire for payment and e-money institutions, launched on eDesk on 2 March 2026 with a 22 May 2026 deadline for entities outside the calibration sample.
  • BCL payment statistics (collection CDDP6, based on BCL Regulation 2021/N°30 of 12 July 2021 and applicable since 1 January 2022). Payment and e-money institutions are in the reporting population, and the collection includes the PSD2 fraud tables, which the CSSF directs to the BCL rather than to itself under Circular CSSF 19/712. Exemptions are case by case and last at most one year. A payment or e-money institution is not a reporting agent for the BCL’s BOP 1.2 cross-border payments return, which is limited to credit institutions and the postal financial services. See also the ECB payment statistics regulation and PSD2 fraud reporting.
  • CESOP to the AED through a certified MyGuichet.lu business eSpace, due by the end of the month after each quarter: 30 April, 31 July, 31 October and 31 January.

6. The year at a glance

For a calendar-year e-money institution, the fixed dates fall like this. Dates tied to the general meeting, and the BCL statistics, which follow the BCL’s published remittance calendar, have to be added from the firm’s own diary.

WhenWhat
20th of every monthBalance sheet and third-party funds tables for the previous month
20 JanuaryQ4 quarterly tables; annual shareholdings table (W 4.5)
31 JanuaryCESOP Q4 file to the AED
1 MarchComplaints table and summary report
31 MarchInternal auditor’s summary report; end of the DORA register of information window for the 2025 reference date
20 April, 20 July, 20 OctoberQuarterly tables for Q1, Q2 and Q3
30 April, 31 July, 31 OctoberCESOP files for Q1, Q2 and Q3
Spring (per circular letter)AML/CFT data collection on eDesk
Relative to the AGMShort form report (two weeks before), long form report (one month after)

7. Registers are the Luxembourg specialty

The outsourcing register, the DORA register of information and the beneficial-ownership filing are maintained artefacts, not transmissions. Their control is a periodic completeness reconciliation against an independent source (the contract record for outsourcing, the ICT service inventory for DORA), plus a change trigger between reconciliations. The advance-notification side needs its own control, because it applies before an arrangement starts.

8. Three worked scenarios

The quarter the channel changes. Facts: an e-money institution tests the eDesk module in February 2027 and files its February monthly tables on 18 March 2027 through the existing channel. Its finance team plans to send the March tables and the Q1 quarterly tables the same way. Rule: reports due on or before 31 March 2027 go through the current channel, test submissions do not count, and every report due from 1 April 2027 goes through eDesk only, even when the period ended earlier. What the practitioner does: treats the 18 March file as the last legacy submission, makes sure the eDesk roles and the S3 credentials (if the JSON route is used) are live before 1 April, and plans the March monthly and Q1 quarterly reports, both due 20 April 2027, as eDesk submissions. Outcome: no report goes down a channel that has been switched off.

The first annual pack. Facts: a payment institution authorised in its first year closes on 31 December and plans its AGM for late May. Rule: the complaints table is due by 1 March, the internal auditor’s summary by 31 March, the short form report two weeks before the AGM and the long form report within one month after it. What the practitioner does: fixes the AGM date early, works back from it for the auditor, and adds the 26/906 certificate to the same workplan. Outcome: one planned pack, not a run of surprises.

The outsourcing that started before the notification. Facts: an EMI engages a new ICT provider for a function it treats as important, and adds it to the registers at the next quarterly review. Rule: the outsourcing regime works on advance notification, so the question is when the notification was made relative to the start of the arrangement, and a register updated afterwards cannot answer it. What the practitioner does: puts the notification trigger in the contracting process as a procurement gate, and keeps the register reconciliation as a separate detective control. Outcome: the notification and the register entry are evidenced separately, each with its own date.

9. The certificate, and what it commits

The annual certificate of compliance with Circular 26/906 deserves separate attention because it is the one item on this list that puts named individuals behind the rest. A certificate from the management body is a statement about the state of the firm’s arrangements. Every register, notification and reconciliation described above becomes evidence for a signature rather than a task in a workflow.

So collect the evidence throughout the year. A firm that reconstructs a year of registers in the weeks before signing must fix or disclose every gap under time pressure. A smaller point: the CSSF publishes circulars and templates in English as well as French, but some documents, such as the schedule of conditions, are French only.

10. FAQ

When are the CSSF periodic tables due?

On the 20th of the month after the period ends: monthly for the balance sheet and third-party funds, quarterly for capital adequacy and the profit and loss account (and for authorised reinvestments at an e-money institution), and yearly for the e-money shareholdings table.

When does eDesk become mandatory for these reports?

From 1 April 2027 eDesk is the sole official channel, for every report due on or after that date, including the March 2027 monthly and Q1 2027 quarterly reports. The testing phase from 1 January to 31 March 2027 does not replace official filing through the current channel.

Do Circulars 11/511 and 11/522 still apply?

For now, yes. The CSSF has announced a new circular to replace them, which had not been published when this article was written. Watch the CSSF publications for its date and content.

Does a payment or e-money institution report to the BCL?

Yes, payment statistics and fraud data under BCL Regulation 2021/N°30, unless it obtains a time-limited exemption. It does not file the BOP 1.2 cross-border payments return, which is limited to credit institutions and the postal financial services.

When must an outsourcing be notified?

Before the arrangement starts, so the trigger belongs in the contracting process.

11. What to do, today

  1. Build the calendar from the table in section 6, then add the AGM-relative dates and the BCL remittance calendar for the current year.
  2. Check eDesk readiness for April 2027 now: an endorsed Advanced User, LuxTrust authentication for at least two filers, and a decision between manual entry and the S3 JSON route.
  3. Book the January to March 2027 test window and run at least one full test cycle on real data.
  4. Map the CSSF annex data points to your ledger and HR systems, and put CESOP, BCL and CRF duties in the same calendar with named owners.
  5. Run a completeness reconciliation of the outsourcing register and the DORA register of information before the 26/906 certificate is signed.
  6. Watch CSSF publications for the circular replacing 11/511 and 11/522, and for each year’s AML/CFT data-collection dates.

Related: CSSF legal reporting · CSSF eDesk and the S3 API · CSSF outsourcing · BOP 1.2 and the BCL · The Dutch reporting calendar · The CSSF AML/CFT data collection · CSSF Regulation 12-02 — the Luxembourg AML rulebook · CRBA — Luxembourg’s central register of bank accounts · RBE — the beneficial owners register · CESOP in Luxembourg — AED filing via MyGuichet.lu · CRS reporting to the ACD in Luxembourg · BCL payment statistics (CDDP6) for Luxembourg PIs and EMIs

Related reads.