Blog

---

1. What is the BCL S2.17 Report?

The S2.17 report, formally titled «Transactions of Financial Companies», is a quarterly statistical reporting obligation imposed by the Banque centrale du Luxembourg (BCL) under Regulation 2014/17. Where its companion report S2.16 captures a full balance sheet snapshot at the end of each quarter, S2.17 focuses exclusively on the financial flows — the net transactions that occurred during the reporting period for a specific, limited set of balance sheet items.

The rationale behind S2.17 is to give the BCL visibility into the changes in certain balance sheet categories that cannot be inferred from balance sheet positions alone. Price effects, exchange rate movements, and reclassifications can all cause balance sheet values to shift without any actual transaction taking place. S2.17 isolates the true transaction component, providing data that feeds directly into national financial accounts and European monetary statistics.

“The sole objective of data gathering on the basis of report S 2.17 is to provide information on transactions affecting some balance sheet items of financial companies.”

BCL Instructions S2.17, February 2026

Crucially, S2.17 is a conditional report. It is only required when one or more of the four in-scope items individually represents more than 5% of total assets. This makes it materially different from S2.16, which is always mandatory for qualifying entities regardless of the composition of the balance sheet.

---

2. Who Must Submit S2.17?

S2.17 is submitted by the same population as S2.16: resident financial companies established under BCL Regulation 2014/17 with total assets above the €500 million exemption threshold. A company qualifies as a financial company if its corporate object includes at least one of the following:

• Investing in any type of company or financial instrument (shares, bonds, receivables, certificates of deposit, etc.)
• Directly or indirectly acquiring and managing real estate, patents, or intellectual property rights
• Borrowing in any form
• Lending funds to shareholders, subsidiaries, affiliated companies, or any other entity

However, being subject to BCL reporting does not automatically mean S2.17 must be filed every quarter. The obligation is conditional on the materiality of specific balance sheet items — see Section 3.

---

3. The 5% Threshold Rule

S2.17 applies a materiality threshold: the report must only be submitted for items that, considered separately, represent more than 5% of total assets. The four items in scope are evaluated independently — crossing the threshold on one item triggers reporting for that item only, not for all four.

Consider the following example provided by the BCL:

This threshold must be assessed each quarter independently. An item that was above 5% in Q1 may fall below in Q2, removing the S2.17 obligation for that item in the subsequent period.

---

4. Reporting Frequency and Deadlines

S2.17 is a quarterly report, aligned with S2.16. The reference date is the last business day of each quarter. The file must be submitted to the BCL no later than 20 working days after the end of the reporting period — the same deadline as S2.16.

---

5. Financial Transactions: Definition and Scope

The BCL defines financial transactions as the net acquisition of financial assets or the net incurrence of liabilities for each type of financial instrument during the reporting period. In other words, S2.17 reports the algebraic sum of all purchases, sales, creations, and redemptions of the in-scope items that occurred during the quarter — not the end-of-period balance.

Financial transactions are recorded at transaction value — the value in the accounting currency at which the assets or liabilities involved were created, liquidated, exchanged, or assumed between institutional units on the basis of commercial considerations. This is distinct from market value or book value adjustments that may affect the balance sheet without involving an actual transaction.

---

6. The Four Reportable Items

S2.17 covers exactly four balance sheet items — two on the asset side and two on the liability side. No other items are in scope, regardless of their size.

Item Code	Description	Side	Definition
1-006010	Non-financial assets — Real estate	Asset	Residential, commercial, industrial, and office real estate; civil engineering works. Includes all acquisitions and disposals of real property during the quarter.
1-006999	Non-financial assets — Other	Asset	Machinery and equipment, virtual and crypto-assets, intellectual property (software, patents, licenses), valuables, and physical goods holdings. Excludes real estate.
1-007000	Financial derivatives (assets)	Asset	Net transactions on derivative contracts with positive market value: options, futures, forwards, swaps, credit derivatives, contracts for difference. Recorded at transaction value.
2-011000	Financial derivatives (liabilities)	Liability	Net transactions on derivative contracts with negative market value. Same instrument types as the asset-side derivatives item.

It is important to note that these are the same item codes used in the S2.16 balance sheet. The difference is that in S2.16 you report the end-of-period stock, while in S2.17 you report the quarterly flow (transactions) for the same items — but only when they are material.

---

7. Breakdowns Required

Unlike S2.16 — which requires full breakdowns by country, currency, economic sector, and original maturity — S2.17 requires no analytical breakdowns. All four items must be reported as a single aggregate figure using the following fixed codes for every dimension:

Dimension	Required code	Meaning
Country	XX	No breakdown — report as a single total
Geographical area of final beneficiary	XX	No breakdown
Currency	XXX	No breakdown — report all currencies combined
Economic sector	90000	No breakdown
Original maturity	I999-999	No breakdown

---

8. Technical Constraints and XML Transmission

S2.17 must be transmitted to the BCL as a structured XML file conforming to the BCL’s published Layout 2 schema. The same general XML principles that apply to S2.16 apply here: the file must be schema-valid, pass all internal verification rules, and follow the strict file naming convention.

8.1 File Naming Convention

The naming convention for S2.17 follows the same structure as all BCL statistical reports:

# File name structure for S2.17
S0217_L2_yyyymm_Rrrrrrrrrr_Dddddddddd_yyyymmdd_nnn.xml

# Where:
S0217      = Report code for S2.17
L2         = Layout version 2
yyyymm     = Year and month the data refers to (e.g. 202503 = Q1 2025 end)
R + code   = Reporter type + 9-digit reporter ID (BCL/CSSF number)
D + code   = Declarant type (DSE for financial companies) + 9-digit RCS number
yyyymmdd   = File creation date
nnn        = Sequential number (starts at 001 each day — 000 is not valid)

# Example:
S0217_L2_202503_DSE000001234_DSE0240150_20250420_001.xml

8.2 Reporter and Declarant Identification

As with S2.16, each file contains a reporter ID and a declarant ID. Financial companies use identification type 35 (filename prefix: DSE) allocated by the BCL. The declarant code is the numerical part of the RCS registration number (letter + up to 7 digits, left-padded with zeros to reach 9 characters total).

8.3 Permanent Verification Rules

The BCL’s Compendium of Verification Rules for S2.17 currently contains only permanent rules (no temporary rules). The following internal checks must be applied for all four items (1-006010, 1-006999, 1-007000, and 2-011000):

• Country code must be XX
• Geographical area of the final beneficiary must be XX
• Currency code must be XXX
• Sector code must be 90000
• Original maturity code must be I999-999
• The amount can be positive or negative

These rules must be implemented by software providers and validated before submission. Any deviation will result in a rejection by the BCL’s processing system.

8.4 Approved Transmission Channels

• Sofie — SIX Payment Services (Europe) S.A. / CETREL Securities
• e-file — Bourse de Luxembourg / Fundsquare

Any new secure transmission channel requires mutual agreement between the BCL and the reporting agent prior to use.

---

9. Link with S2.16 and TPTIBS

S2.17 sits within a wider ecosystem of three complementary BCL reports. Understanding how they relate to each other is key to managing the reporting process efficiently:

Report	Full name	Frequency	What it reports	Conditional?
S2.16	Quarterly Statistical Balance Sheet	Quarterly	End-of-period stocks — full balance sheet with all breakdowns	No — always required
S2.17	Transactions of Financial Companies	Quarterly	Quarterly flows — net transactions for 4 specific items only	Yes — only when items >5% of total assets
TPTIBS	Security-by-Security Report	Monthly	ISIN-level details of all security holdings and issuances	No — always required

A key discipline in managing S2.17 is tracking the relationship between the S2.16 closing balance, the S2.17 transactions, and the opening balance of the following quarter. The equation Opening stock + Transactions + Other changes = Closing stock must hold for each in-scope item. “Other changes” captures revaluations, exchange rate effects, and reclassifications that are explicitly excluded from S2.17.

---

10. How Fund XP’s Solution Simplifies S2.17 Reporting

---

11. Conclusion

The BCL S2.17 report is a targeted but technically precise obligation. Its conditional nature — triggered only when specific balance sheet items exceed 5% of total assets — means that many financial companies will not need to file it every quarter. But when the threshold is crossed, the report must be produced correctly: transaction values accurately isolated, “no breakdown” codes explicitly declared in the XML, and the file submitted within the same 20 working-day window as S2.16.

Managing this alongside S2.16 and TPTIBS within a tight reporting calendar calls for an integrated approach. Tracking the threshold manually, maintaining separate XML generation workflows, and verifying compliance with BCL rules across three reports is a process that benefits enormously from automation.

Fund XP’s XLSM reporting template was built to handle exactly this — embedding the 5% threshold logic, the verification rules, and the XML generation for all three BCL reports into a single, audit-ready workbook that your team can rely on every quarter.

---