Regulatory watch: Luxembourg regulatory e-file reporting is changing, Are you ready for 2027?

Regulatory reporting in Luxembourg is about to get more complex. By February 2027, financial institutions transmitting data through the Banque Centrale du Luxembourg and Administration des Contributions Directes e-file channels must contend with five separate regulatory changes, some of them running simultaneously with existing reporting obligations. 

For operations and compliance teams, that means more formats to manage, more validation rules to satisfy and less margin for error. The firms that start preparing now will navigate this smoothly. Those that leave it late will feel the pressure. 

Here is what is changing, why it matters, and how FE fundinfo helps you stay ahead. 

Five changes, one tight deadline 

The BCL is introducing new Layout 2 versions for three of its core statistical reports: S2.16, S2.17, and TPTIBS. All effective February 2027. The ACD is upgrading its NCD/DAC2 (Common Reporting Standard) channel to a new schema version under the EU's DAC8 directive, effective January 2027. And the BCL has updated its AnaCredit technical specifications, effective August 2026. 

That is not a simple cutover. It is a meaningful operational uplift that requires updated systems, new validation logic and thorough testing before go-live. 

What is actually changing? 

BCL reports S2.16, S2.17, and TPTIBS 

S2.16 covers the quarterly statistical balance sheet of financial companies. S2.17 covers transactions of financial companies. TPTIBS is the security-by-security report. All three are moving to a new Layout 2 structure by February 2027. 

The changes across all three reports follow a common pattern. Non-financial asset lines are restructured. The affiliated link field replaces the older relationship link field, with updated code values. Holding type code 06 is retired.  

TPTIBS goes further. It also introduces three new issuer identification fields for non-ISIN securities — covering LEI code, national identifier type and national identifier code — tightens issuer country and sector validation rules and removes dividend fields and custodian bank country. Country and sector code lists are extended and relabelled to align with ECB standards. It is the most structurally significant of the three changes. 

ACD NCD/DAC2: new CRS schema under DAC8 

The ACD's NCD/DAC2 domestic channel is upgrading to CRS XSD version 3.0, driven by EU Directive 2023/2226 (DAC8) and the OECD's Crypto-Asset Reporting Framework (CARF). From January 2027, amended declarations — initial, corrected or cancelled — must use the new schema. 

The new schema adds a meaningful set of new data elements: account type, due diligence procedure, equity interest type, self-certification status and joint account indicators. It also introduces 12 new cross-field validation rules with new error codes. Some trigger resubmission requirements; others generate warnings. Getting the cross-field logic right before go-live is critical. 

BCL AnaCredit: updated specifications effective August 2026 

The BCL published updated AnaCredit technical specifications in May 2026 (version 1.0.14), effective August 2026. The change is primarily a schema versioning update across all four survey types. If your transmission pipeline references XSD files by version number, you need to update those references before the August deadline. 

Why this matters for your operations 

Managing regulatory reporting across multiple formats, channels and regulators is already demanding. These five changes add real complexity: 

Your validation logic needs to reflect new field structures, updated code lists and new cross-field rules. Your testing cycles need to complete before go-live. 

Firms managing this manually or through fragmented systems face the greatest risk. A missed validation rule or an incorrect file format does not just create a compliance exposure — it creates rework, delays and operational cost that accumulates across every submission cycle. 

That is the problem FE fundinfo solves. 

How FE fundinfo supports your reporting obligations 

FE fundinfo's [regulatory filing service] is the authorised e-file transmission channel connecting Luxembourg financial institutions to the BCL, ACD, CAA and CSSF. 

When regulation changes, we change with it. Our platform absorbs the technical complexity — new XSD schemas, updated validation logic, revised file naming conventions, parallel layout support — so your operations team does not have to. 

For the 2027 BCL and ACD changes, we are building support for all five updates as part of our standard release cycle. That means Layout 2 transmission and form support for S2.16, S2.17 and TPTIBS. It means CRS XSD 3.0 validation for NCD/DAC2 with the full updated cross-field rule set. And it means AnaCredit schema alignment already in place. 

You get a single dashboard showing the status of every transmission, regulator feedback and audit trail — across every channel, every report, every submission. No chasing regulators. No manual reconciliation. No compliance gaps. 

Start preparing now 

If you currently use the BCL or ACD e-file channel directly or through a third-party provider, the right time to review your setup is now — before testing windows open. The firms that use this period to confirm their provider's roadmap, review their current configurations and plan testing will be in a far stronger position than those reacting to change at the last minute.

Frequently asked questions 

Q: Does FE fundinfo's platform handle all five of these changes? 
A: Yes. All five updates — S2.16 L2, S2.17 L2, TPTIBS L2, NCD/DAC2 CRS XSD 3.0 and AnaCredit v1.0.14 — are supported by our platform as part of our standard regulatory release cycle.  

Q: What is the risk of not being ready in time? 
A: Files that do not conform to the new layout or schema requirements will fail validation at the regulator. For NCD/DAC2, certain validation failures require full resubmission. For the BCL reports, transmission failures create compliance gaps and operational rework. The earlier you begin preparation, the more time you have to test and resolve issues before the deadline.