TPTBBL Reporting: The BCL Security-by-Security Return and TPTBBN

Every credit institution resident in Luxembourg owes the Banque centrale du Luxembourg (BCL) a monthly TPTBBL report, the BCL’s security by security report on balance sheet data for the Luxembourg entity, no later than 10 working days after month-end. TPTBBL reporting captures debt securities, shares and fund units held, debt securities issued and securities sold short at security level. Each reported position carries the applicable balance-sheet line and holding type and, for the relevant asset positions, the FINREP portfolio classification. Layout 5 of the report has been mandatory since the January 2022 reference period, and the BCL republished its instructions on 19 November 2025. Resident credit institutions with branches abroad also file TPTBBN, the same report for the head office and its branches together, each quarter within 20 calendar days.

Every security sits under one of four balance sheet lines, and the BCL checks that the security amounts add up exactly to the same lines in the statistical balance sheet: S 1.1 for TPTBBL, S 2.5-N for TPTBBN. Securities without an ISIN bring a block of issuer data, debt securities without an ISIN add maturity and coupon data, and the November 2025 revision rewrote how that issuer must be identified. A file that does not tie to the balance sheet, or that passes a pseudo-ISIN off as a real one, fails checks the BCL publishes in advance, and since 30 April 2024 the ECB’s infringement regulation for statistical reporting has applied to the collections listed in BCL circular letter ST.24-0013.

Related reading: BCL S 0.1 Report: Daily Deposit Reporting for Luxembourg Banks

Legal basis of TPTBBL reporting: ECB balance sheet statistics, BCL circulars and instructions

Article 32(1) of the Law of 23 December 1998 on the monetary status and the Banque centrale du Luxembourg authorises the BCL to collect the statistical information it needs for its missions, either from the competent national administrations or directly from economic agents, in conformity with EU law and the competences of the ESCB and the ECB. Article 34(1) gives the BCL power to adopt regulations within its competences.

The European layer is Regulation (EU) 2021/379 of the European Central Bank of 22 January 2021 on the balance sheet items of credit institutions and of the monetary financial institutions sector (recast) (ECB/2021/2). Circular BCL 2021/244 of 10 February 2021 explains how the BCL built its data collection for credit institutions on that regulation, and it names TPTBBL and TPTBBN among the reports affected by the updated “Definitions and concepts for the statistical reporting of credit institutions”. The circular’s stated aims include covering the ECB’s requirements and the statistical needs of BCL units and STATEC while keeping the reporting burden down. Recital 9 of the ECB regulation allows national central banks to collect the ECB’s data inside a broader national framework that also serves other statistical purposes.

The TPTBB instructions themselves cite no article of the ECB regulation. The security-level detail appears to be the BCL’s own design inside that national framework, anchored to ECB/2021/2 through the S 1.1 balance sheet it reconciles to; the documents do not state that mapping in so many words. The BCL’s TPTBB reporting instructions and verification compendia state that the French text prevails where the French and English versions differ.

The Layout 5 document set

The BCL publishes TPTBBL and TPTBBN as parallel document sets on one hub page, with these “last update” dates:

The instructions also import, by reference, the BCL document “Definitions and concepts for the statistical reporting of credit institutions”. Section 3 of the instructions adds that any change to the definitions used for the monthly and quarterly statistical reporting applies automatically to the security by security report, so a reclassification decided for S 1.1 travels into TPTBB without a separate notice.

Who must report TPTBBL and TPTBBN: resident banks, then the branch perimeter

Section 1.1 of the TPTBBL instructions is short: the report must be provided by all resident credit institutions regardless of their legal status. The instructions set no size threshold, no activity test and no exemption.

TPTBBN has a narrower population. Its instructions require it from all resident credit institutions with branches abroad, and the report covers “the global business”: the Luxembourg head office and its branches abroad taken together. The BCL’s “Definitions and concepts” document supplies the version rule behind the pair. Credit institutions incorporated under Luxembourg law that have foreign branches report certain statistical reports in two versions: version L for the Luxembourg head office, where operations with its own branches are not eliminated, and version N for the whole entity, where transactions between the head office and its branches, and between branches, are eliminated. Luxembourg-incorporated banks without foreign branches, and Luxembourg branches of credit institutions governed by foreign law, report a single version L.

Two consequences follow from the version rule. A Luxembourg branch of an EU or third-country bank files TPTBBL and has no TPTBBN obligation, however many sister branches its parent runs elsewhere. A Luxembourg-incorporated bank with a branch in, say, Germany files both, and its N file cannot be built by appending the German branch’s rows to the L file, because intra-entity positions are eliminated. That elimination, as an inference from the general rule, removes a foreign branch’s holding of debt securities issued by its own Luxembourg head office from TPTBBN while leaving the head office’s L file untouched; this is worth confirming with the BCL for any material position. Subsidiaries appear in neither definition, so the perimeter stops at the legal entity and its branches.

What the report contains: four balance sheet lines and security-level classifications

Section 3 of the instructions limits TPTBB to securities reported in four lines of the statistical balance sheet. On the asset side, 1-003000 “Debt securities held” and 1-005000 “Equity”, which also carries shares and units of investment funds. On the liability side, 2-002050 for short sales of securities and 2-003000 “Debt securities issued”. Each security is attached to its line through an identifier built from the sub-table, the item, a country code, a currency code and an economic sector code, and the compendium authorises only the four lines in the aggregated form it lists, for example 1-003000-XX-XXX-90000.

The TPTBB instructions distinguish securities identified by an ISIN from securities without an ISIN. They also distinguish percentage-quoted from currency-quoted securities when determining the quantity to report.

Identifying the security

An ISIN (ISO 6166) has priority over any other code. The field codeType takes 1 for a security with an ISIN and 2 for any other code, internal or external, such as a CUSIP. Provisional and pseudo-ISINs are not valid ISINs under section 4.2: such a security goes in as codeType 2 and carries the full set of additional data required for securities without an ISIN. Internal codes built to look like ISINs do not count as ISINs either, the code must match its declared type, and an ISIN must pass the check-digit test.

Issuer data for securities without an ISIN

Issuer identification is required only for securities without an ISIN, and it is the part the November 2025 revision rewrote. The instructions list five elements: the LEI, the type of issuer identifier, the identifier itself, the issuer’s country and the issuer’s economic sector. The authoritative French instructions prescribe twenty zeros if the issuer has no LEI or the reporting bank cannot obtain its LEI. The parent’s LEI must not be substituted. A national identifier must be sent for each counterparty even where the LEI is filled in, using the identifier types in the ECB’s list of national identifiers.

The November 2025 TPTBB instructions prescribe the Luxembourg investment-fund issuer formats. Identifiers already maintained for AnaCredit or another reporting collection should be reused in TPTBB only after their issuer level, identifier type and format have been checked against the TPTBB instructions. The issuer’s country follows ISO 3166 plus the BCL’s own codes for international institutions, and “XX” (no breakdown) is barred. The sector comes from a closed list of twenty codes, from 11000 central government to 46000 pension funds, and 90000 (no breakdown) is barred too.

Holding type and portfolio type

The holding type exists to avoid double counting, and it applies the economic-holder concept. A bank that has lent securities, or sold them under a repurchase agreement, is still their holder; a bank that has borrowed securities or bought them under a reverse repo is not, and those securities stay out of the report because they are not on the balance sheet. The codes are 01 held and not affected by a temporary transfer, 02 lent, 03 sold in a repurchase agreement, 04 issued, 05 short sale and 06 otherwise encumbered. Code 06 is a residual category that includes securities in a covered bond cover pool and securities pledged as collateral in derivatives, securitisations or credit enhancements, so a bond out on repo still takes 03.

The portfolio type identifies the FINREP portfolio in which the security is classified: 11 held for trading, 12 non-trading mandatorily at fair value through profit or loss, 13 designated at fair value through profit or loss, 14 fair value through other comprehensive income, 15 amortised cost and 16 investments in subsidiaries, joint ventures and associates. The compendium narrows this by line: debt securities may use 11 to 15, equity only 11, 12, 14 and 16. Sections 5.2.3 and 5.2.4 of the TPTBB instructions do not prescribe a portfolio-type field for short sales or issued securities. Our FINREP reporting guide covers the accounting classification the code mirrors.

Quantity, amount and valuation

Quantity depends on how the security is quoted. A percentage-quoted security is reported as nominal capital with the currency of the nominal, and the pool factor is ignored when measuring that nominal. A currency-quoted security is reported as a number of units, with no nominal and no nominal currency, and trading lots are irrelevant because the instructions ask for the number of individual securities.

The amount is expressed in the accounting currency of the balance sheet, with enough decimals that the line totals equal the exact sum of the security amounts; the BCL’s statistical reporting definitions permit amounts with up to five decimal places, and the compendium requires every security amount to be zero or positive, liabilities included. As a rule, quoted securities are valued at the exchange price at the end of the reporting date. The instructions require debt securities to be valued at dirty price, accrued interest included. A total, totalReportedAmount, closes each balance sheet line and must equal the sum of its security amounts.

One tension deserves a decision before the first run. The “as a rule” market-price sentence sits next to a hard check that each line total must equal the corresponding S 1.1 or S 2.5-N amount, and the BCL’s definitions document lets statistical reporting follow the valuation of supervisory reporting. That equality check does not, by itself, prescribe the valuation basis of every individual amortised-cost security. The TPTBB valuation instructions must be read together with the BCL’s general statistical valuation rules, and any unresolved treatment should be confirmed with the BCL before implementation.

Supplementary data for securities without an ISIN

Debt securities without an ISIN carry security type F.3, the issue date, the final maturity date (01.01.2999 for a perpetual), the pool factor (default 1 where the concept does not fit the security, and possibly above 1 where it includes accrued interest), the coupon type (01 fixed, 02 progressive, 03 floating, 04 zero coupon, 05 index linked, 99 other), the coupon frequency (00 zero coupon, 01 annual, 02 semi-annual, 04 quarterly, 06 bi-monthly, 12 monthly, 24 fortnightly, 99 other), the date of the last coupon payment and the coupon rate. If no coupon has been paid, the last coupon date is the issue date. The coupon rate is annualised and expressed in percent, so a 5.5% coupon is reported as 5.5.

In the supplementary block, equity without an ISIN needs only a security type: F.511 quoted shares, F.512 unquoted shares, F.519 other equity and F.52 shares or units of investment funds. For debt a bank has issued without an ISIN, TPTBBL fixes the issuer country at LU and the sector at 32100, while TPTBBN uses the country of residence of the issuing branch where a branch issued it, for instance DE for a German branch.

Reference dates, frequency and deadlines for TPTBBL and TPTBBN

TPTBBL is monthly. In principle the reference date is the last day of each month, and the file is due no later than 10 working days after the end of the reference period. TPTBBN is quarterly and due no later than 20 calendar days after the end of the reference period. Both instruction sets add that the BCL publishes a calendar of remittance dates on its website, and footnote 1 of that calendar explains the count: the deadlines are based on the working days the ECB defines for national central banks’ transmission of statistics. That footnote is the reason to work from the published table and not from a Luxembourg holiday list.

The TPTBBN instructions contain a drafting trap. Section 1.2 says quarterly, but section 2.2 still says the last day of each month should be the reference date, and section 5 speaks of “a monthly file”, wording carried over from TPTBBL. The BCL calendar resolves it: TPTBBN appears among the quarterly reports, with reference periods March, June, September and December.

The 2026 BCL calendar

The BCL publishes one calendar per year; the 2026 edition is dated December 2025. Its TPTBBL L5 dates match the S 1.1 L6 dates in every month, and its TPTBBN L5 dates match S 2.5-N.

The first reference date under Layout 5 was the end of January 2022: Circular BCL 2021/244 made the new collection mandatory from the January 2022 deadline, with the first reports relating to end-January 2022. Going forward, the month now closing is due on the date the BCL calendar lists for it, and in the 2026 table each quarter-end TPTBBN falls on the 20th of the following month.

Submission of the TPTBB file: XML schema, file name and secure channels

TPTBB is filed as XML; there is no XBRL taxonomy. The BCL publishes separate Layout 5 XML schema packages for TPTBBL and TPTBBN on its TPTBB reporting hub. Section 5.1 of the instructions requires the month-end reference date, closing date, reporter and declarant identifiers and reporting currency. The precise XML element names, namespaces, schema version and header structure must be taken from the BCL’s published schemas and example files.

The BCL’s “Manual of electronic transmission for statistical reports of credit institutions” (February 2021) fixes the file names:

• TPTBBL_L5_yyyymm_Rrrrrrrrrr_Dddddddddd_yyyymmdd_nnn
• TPTBBN_L5_yyyymm_Rrrrrrrrrr_Dddddddddd_yyyymmdd_nnn

The first date is the reference month. R and D are placeholders for the reporter’s and declarant’s identification-type letters, not literal characters in the submitted filename. A bank uses B followed by its nine-digit, zero-padded CSSF identification number. A PFS reporter uses P for its own identification type, while the bank whose data are reported remains the B declarant. The second date is the file’s creation date, and nnn is a sequence number that restarts at 001 each day; 000 must not be used.

The manual names two channels, Sofie and e-file, and says the BCL is willing to accept any new secure channel that both the BCL and the reporting agent accept. Circular BCL 2007/216 set up that model of BCL-approved secure channels and opened security-by-security reporting over Sofie and e-file from 1 January 2009. Circular letter ST.24-0013 closed the informal route: the BCL no longer accepts statistical reports by e-mail.

Feedback files and resubmission

The BCL’s April 2025 note on feedbacks names TPTBBL and TPTBBN among the collections that can receive up to three feedback types: FL-OK or FL-NOK on the technical status of the file, DQ-FDB on data points that need correction or confirmation, and ADHC-FDB for ad hoc requests outside the production cycle. The note moves these feedbacks from e-mail to Sofie and e-file in stages, under names starting FDBBUSI_, and each feedback states its own response deadline, which the note places inside the ECB’s non-compliance framework.

The TPTBB documents say nothing on how a corrected file replaces an earlier one. The general rules fill part of the gap: the definitions document requires reporting agents to follow the BCL’s revisions policy and to attach explanatory notes to revisions outside the regular cycle, and the sequence number in the file name separates files created on the same day for the same report.

Validation rules in the TPTBB compendium and where a file fails

The compendium of verification rules (February 2021) splits the checks into permanent and temporary rules. The BCL invites software providers to build the permanent rules into reporting tools; the temporary rules check data quality characteristics that can change over time and are addressed to reporting agents. The TPTBBN compendium mirrors TPTBBL, except that its cross-check runs against S 2.5-N and its own-issue rule accepts a branch’s country code. The single temporary rule allows sector 12100 (state government) only for countries with a federal structure.

The coupon rules turn on data a securities master may not hold for securities without an ISIN. Rule 19 pairs coupon type 04 with frequency 00 in both directions. Rule 21 tests the gap between the closing date and the last coupon date against twice the coupon period: under 720 days for annual, 360 for semi-annual, 180 for quarterly, 124 for bi-monthly, 62 for monthly and 31 for fortnightly, the doubling being there to absorb a long first coupon. A last coupon date that is never updated fails as soon as that window is passed. Rules 23 and 24 reject a zero coupon rate on a fixed-rate security with a non-zero frequency, and on any security whose last coupon date falls strictly between its issue and maturity dates.

The February 2021 verification compendium does not publish rejection rates by rule. It therefore cannot support a ranked list of common TPTBB filing errors. And the compendium still carries its February 2021 date: it lists no dedicated rules for checking the LEI or the issuer-identifier formats specified in November 2025. This does not establish whether XML schema constraints or other BCL controls can reject incorrect values. The November 2025 instructions remain applicable regardless of the checks enumerated in the compendium.

Behind the rules sits the ECB’s enforcement framework. Regulation (EU) 2022/1917 (ECB/2022/31) has applied since 30 April 2024, and circular letter ST.24-0013 told reporters that the ECB and the BCL would monitor compliance from the April 2024 reference period against minimum standards for transmission, accuracy and conceptual compliance. Article 8 of the regulation bars an infringement procedure where the potential fine is unlikely to exceed EUR 10,000 for a late report or EUR 20,000 for incorrect, incomplete or non-compliant data, and it states that technical difficulties, or difficulties maintaining and upgrading IT infrastructure, outsourced IT included, are not circumstances beyond the reporting agent’s control. The circular letter lists legal bases, not report codes, so it does not say in terms which TPTBB fields sit inside the monitored scope.

Caveats for TPTBB: S 1.1 tie-outs, TPTBH boundaries and FINREP codes

The TPTBB documents contain no proportionality regime, no waiver, no national option and no transitional provision for Layout 5.

The tie-out to S 1.1 or S 2.5-N is the interaction with the widest reach. Any revision to lines 1-003000, 1-005000, 2-002050 or 2-003000 of the statistical balance sheet breaks the cross-check until the TPTBB file is revised as well. The compendium establishes an equality requirement but does not prescribe simultaneous resubmission. Corrections should follow the BCL’s reporting-revision policy, with the affected TPTBB and statistical balance-sheet amounts kept consistent.

Customer holdings belong in separate off-balance-sheet security-by-security returns. The current BCL TPTBH reporting hub, electronic-transmission manual and 2026 remittance calendar identify TPTBHR L2 for resident customers and TPTBHN L2 for non-resident customers. Circular BCL 2021/244 uses TPTBNR for the latter, but TPTBHN is the current operational report code; on the current TPTBH hub, TPTBNR denotes a separate annual questionnaire on assets held on behalf of non-resident third parties. A bank that runs both custody and treasury books needs one documented rule for which position feeds which report.

The portfolio code ties TPTBB to FINREP classification. When the FINREP update of 1 January 2018 left the old codes unable to record the portfolio correctly, circular letter ST.17-0644 realigned the TPTBB portfolio codes to FINREP and added holding type 06 to improve the BCL’s liquidity analysis of credit institutions. A FINREP reclassification therefore changes the TPTBB code in the same month, and an equity position cannot move to code 13 or 15 because the compendium does not allow it. The definitions document also requires monthly and quarterly statistical reports and related documents to be kept for twenty-four months.

Changes to TPTBB: from Layout 3 to Layout 5, the November 2025 issuer rules and IReF

Layout 3 applied until the reference period of May 2018. Layout 4 was optional from January 2018 and mandatory from June 2018 to December 2021; circular letter ST.17-0644 of 19 December 2017 brought its FINREP-aligned portfolio codes into force from 1 January 2018 (reports at 31 January 2018), with the old portfolio codes still accepted until 30 June 2018. Layout 5 has been mandatory since the January 2022 reference period, following Circular BCL 2021/244 and the recast ECB regulation; that circular also added country codes for the EFSF and the Single Resolution Mechanism and changed the sector classification of supranational institutions, and it says those changes carry into TPTBBL and TPTBBN.

The November 2025 revision is the one that matters for a current build. The revision-marked TPTBBL instructions confine the changes to section 4.3 on issuer identification. The new text adds the LEI rule with its twenty-zero value and the ban on a parent’s LEI, a national identifier for every counterparty, Peppol guidance for public entities, LU-prefixed CSSF fund identifiers in place of a struck-out instruction that the LU prefix must not be filled in, RCS-based identifiers for AIFs not authorised by the CSSF and as the fallback where the ECB list lacks a fund, the XX_NOTAP type with code XX as the default where the reporter has no issuer identifier, together with a statement that the BCL will monitor its use, and the list of authorised sector codes. The TPTBBN instructions carry the same text. The template, compendium and XML schema were not reissued, the instructions state no separate application date, and the BCL’s list of circular letters shows no letter announcing the revision.

The longer horizon is the ECB’s Integrated Reporting Framework. On 8 June 2026 the ECB announced a public consultation on the draft IReF Regulation planned for the second half of 2027, a one-year pilot starting in the second quarter of 2030 and first official IReF reporting from the second quarter of 2031, followed by a one-year parallel phase in which existing statistical reporting within IReF’s scope continues. The ECB made those timelines subject to adoption of the IReF Regulation. The press release names no existing collection and says an implementation plan will set out how national collection frameworks evolve, so neither source says whether TPTBB will be absorbed. The ECB release places IReF within the wider integration of statistical, prudential and resolution reporting coordinated by the Joint Bank Reporting Committee, covered in our note on the JBRC Reporting Contact Group.

Frequently Asked Questions

Part of a bond position is in a securities lending programme with a custodian, and the quantity lent at month-end is unknown. Which holding type applies?

The instructions answer this case directly: where securities are entrusted to another custodian for lending and the precise quantity lent is not available, the whole position is reported with holding type 02, securities lent.

Does a zero-coupon note without an ISIN need a coupon rate?

It takes coupon type 04 with frequency 00, and the last coupon date equals the issue date because no coupon has been paid. Rule 23 only bites on fixed-rate securities with a non-zero frequency, and rule 24 only where the last coupon date sits strictly between issue and maturity, so neither forces a non-zero rate on a true zero. The instructions still list the coupon rate field for every debt security without an ISIN, so the field is completed rather than left out.

A service provider files the statistical reports. Whose number goes in the file name and the header?

The manual separates the two roles: the reporter submits the file and the declarant is the entity whose data are reported. It lists type 23 (letter B) for numbers the CSSF allocates to banks and type 32 (letter P) for professionals of the financial sector, so on its own definitions a PFS submitting for a bank appears as reporter with its own number while the bank remains the B declarant.

Is TPTBB the BCL’s implementation of the ECB regulation on statistics on holdings of securities?

The TPTBB documents do not say so. Circular letter ST.24-0013 lists Regulation (EU) No 1011/2012 (ECB/2012/24) among the legal bases of BCL collections, applying to all reporters, but it maps legal bases to reporter types and names no report codes. The documented link for TPTBB runs through ECB/2021/2 and the S 1.1 balance sheet.

Our reference data still hold a CSSF fund number without the LU prefix. Will the file still go through?

The February 2021 verification compendium does not list a specific rule for the LU-prefixed CSSF issuer identifiers introduced in the November 2025 instructions. That does not establish whether an old-format identifier would pass XML schema validation or other BCL data-quality controls. The old value no longer matches the November 2025 instructions, which removed the instruction to omit the LU prefix. The BCL’s published feedback guidance addresses data-quality errors generally but does not specify how this particular identifier error would be processed.

Related Articles

• BCL S 0.1 Report: Daily Deposit Reporting for Luxembourg Banks: the BCL’s twice-monthly deposit report, its template, verification rules and filing workflow.
• AnaCredit v1.0.15: BCL Swaps the NUTS 3 Code List for January 2027: the BCL’s AnaCredit schema change and the counterparty codes it invalidates.
• FINREP Reporting Explained: What You Actually Need to Know: the FINREP framework and the accounting classification behind the TPTBB portfolio code.
• JBRC Reporting Contact Group: What the Call for Members Means: the EBA and ECB committee coordinating statistical, prudential and resolution reporting integration.

Key Takeaways

• Scope test: every resident credit institution files TPTBBL; only Luxembourg-incorporated banks with branches abroad add TPTBBN, and a Luxembourg branch of a foreign bank files TPTBBL alone.
• Generate the four line totals from the same data run as S 1.1 (monthly) and S 2.5-N (quarterly); the compendium tolerates no difference.
• Take remittance dates from the BCL’s annual calendar, which counts ECB working days.
• For Luxembourg investment-fund issuers without an ISIN, use the LU-prefixed CSSF identifier or the prescribed RCS-based identifier, as applicable. For issuers resident elsewhere, apply the appropriate national issuer identifier rather than a Luxembourg-specific format. A national identifier is required even where an LEI is provided.
• Keep lent and repo’d-out securities in the file as 02 and 03; drop borrowed and reverse-repo securities entirely.
• Refresh last-coupon dates on bonds without an ISIN before month-end, since rule 21 rejects a date older than twice the coupon period.
• Send files named TPTBBL_L5 or TPTBBN_L5 with CSSF-allocated reporter and declarant numbers over Sofie or e-file.

Sources and References

• BCL, TPTBB security by security report (balance sheet data) hub page: bcl.lu
• BCL, Report TPTBBL L5 reporting instructions (November 2025): PDF
• BCL, Report TPTBBL L5 reporting instructions, version with revision marks: PDF
• BCL, Report TPTBBN L5 reporting instructions (November 2025): PDF
• BCL, Report TPTBBL L5 template: XLS
• BCL, Report TPTBBN L5 template: XLS
• BCL, Report TPTBBL L5 compendium of verification rules (February 2021): PDF
• BCL, Report TPTBBN L5 compendium of verification rules (February 2021): PDF
• BCL, TPTBBL L5 XML schema package: ZIP
• BCL, TPTBBN L5 XML schema package: ZIP
• BCL, Definitions and concepts for the statistical reporting of credit institutions (2024): PDF
• BCL, Manual of electronic transmission for statistical reports of credit institutions (February 2021): PDF
• BCL, Feedbacks for the statistical reports (April 2025): PDF
• BCL, Calendar of remittance dates for the statistical reporting of credit institutions in 2026 (December 2025): PDF
• Circular BCL 2021/244, Modification of the statistical reporting from credit institutions (10 February 2021): PDF
• Circular BCL 2007/216, Remote transmission of statistical data (28 December 2007): PDF
• BCL circular letter ST.17-0644, Update of reporting instructions (19 December 2017): PDF
• BCL circular letter ST.24-0013, Monitoring compliance with statistical reporting (15 January 2024): PDF
• Law of 23 December 1998 on the monetary status and the Banque centrale du Luxembourg, consolidated French version of 30 July 2021, Articles 32 and 34: PDF
• Regulation (EU) 2021/379 of the European Central Bank of 22 January 2021 (ECB/2021/2), OJ L 73, 3.3.2021: EUR-Lex
• Regulation (EU) 2022/1917 of the European Central Bank of 29 September 2022 (ECB/2022/31), OJ L 263, 10.10.2022: EUR-Lex
• Regulation (EU) No 1011/2012 of the European Central Bank of 17 October 2012 concerning statistics on holdings of securities (ECB/2012/24): EUR-Lex
• ECB, List of national identifiers (referenced in the TPTBB instructions): XLSX
• ECB press release, ECB announces main milestones for roll-out of Integrated Reporting Framework (8 June 2026): ecb.europa.eu

Running the TPTBBL file at each month-end

At month-end, freeze the four S 1.1 lines, generate the security-level records from the same positions, apply the Luxembourg-specific November 2025 issuer formats only to relevant Luxembourg issuers and use the appropriate national identifier types for issuers resident elsewhere, run the published validation rules and S 1.1 reconciliation, and submit TPTBBL L5 over Sofie or e-file. Banks with branches abroad repeat the exercise each quarter on the N perimeter against S 2.5-N. The next deadline is the date the BCL’s annual calendar gives for the month now closing, 10 ECB working days after month-end for TPTBBL.

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.