16 / 20 Transition timetable by domain and country
When is NACE Rev 2.1 used in bank reporting?
Published Updated
Statistical classification only
Statistical classification only. This guide does not determine any reader's code. Confirm a code with the national statistical institute or the business register that holds the record. This is general information, not advice on any reader's registration.
Eurostat records that, in collaboration with the European Central Bank and the European Banking Authority, the Joint Banking Reporting Committee recommends that NACE Rev. 2.1 is implemented in a harmonised manner across bank reporting frameworks from 1 January 2026 onwards (FIXED, as recorded by Eurostat). That is a recommendation for reporting frameworks, not a statement in the NACE regulations themselves, and it must be read as such. The general data transmission range still runs from 1 January 2025 to 1 January 2031 (FIXED range), depending on the statistical domain.
What is the Joint Banking Reporting Committee recommendation?
The Joint Banking Reporting Committee brings together reporting work across banking frameworks, and Eurostat states that it worked with the European Central Bank and the European Banking Authority on this recommendation. The recommendation is for harmonised implementation across bank reporting frameworks, so that the same classification version is used in the same way in different frameworks. Harmonised implementation matters because a bank report that uses one version in one framework and another version in a second framework cannot be compared cleanly, and the same activity could be counted in different places. The recommendation addresses that risk by naming a single start point for harmonised use. It does not amend the NACE regulations, and it does not set the timetable for European statistics in general. It is recorded here because Eurostat records it on the transition page, and because a reader of bank reporting data needs to know that the date comes from a recommendation, not from the delegated regulation.
How does a recommendation differ from a regulation date?
A regulation date is fixed in an instrument, with an entry into force date and an application schedule. Commission Delegated Regulation (EU) 2023/137 entered into force on 9 February 2023 (FIXED), and the EUR-Lex summary states its incremental application to data transmission. A recommendation is a statement of what a committee recommends, and its force depends on the frameworks that adopt it. Eurostat cites a European Banking Authority press release dated 30 June 2025 (FIXED) for the recommendation. A reader should therefore cite the recommendation as a recommendation, with the committee and the press release named, and should check the reporting framework in use to confirm whether it adopted the recommended start point. A reader who cites the recommendation as if it were a regulation date will overstate its status.
| Element | Record |
|---|---|
| Recommending body | Joint Banking Reporting Committee, with the European Central Bank and the European Banking Authority |
| Recommended start | From 1 January 2026 onwards (FIXED, as recorded by Eurostat) |
| Press release cited by Eurostat | European Banking Authority, 30 June 2025 (FIXED) |
| Status | Recommendation for harmonised implementation, not a NACE regulation date |
| General range | From 1 January 2025 to 1 January 2031 (FIXED range) |
The table keeps the status visible. The status is part of the fact, and a record that drops it misstates the fact.
What should a reader of bank reporting data check?
A reader should check the reporting framework first, then the classification version, then the reference period. The framework is the set of reporting requirements under which the data were collected. The version is the NACE version stated in the framework documentation or the dataset metadata for that framework. The reference period is the period the data describe. If the framework adopted the recommendation, the version from 1 January 2026 onwards (FIXED, as recorded by Eurostat) will be NACE Rev. 2.1. If the framework did not adopt it, or adopted it later, the metadata will show the version actually used. The correspondence table and the explanatory notes remain the record of meaning and movement for any class that split or moved, and a one to many mapping in the table does not by itself pick the new class for a specific unit.
What does bank reporting use of a code not prove?
A NACE code in a bank report is a statistical breakdown in a reporting framework. It does not prove that a borrower carries on a particular activity, it does not prove that a loan was made for a particular purpose, and it does not decide any question about credit, licensing, or supervision. The code describes an activity category for statistical and reporting purposes. The underlying facts about a business, its activities, and its obligations are recorded in the registers and documents that govern those facts, and the entry for a specific business is confirmed with the national statistical institute or the business register that holds the record. A reporting code should never be quoted as if it were a finding about a specific business.
Where is the recommendation confirmed?
The recommendation is confirmed on the Eurostat transition page, which records the collaboration, the committee, the harmonised implementation aim, and the start point, and cites the European Banking Authority press release dated 30 June 2025 (FIXED). For a single framework, check the framework documentation and the dataset metadata for the version used. For a single business entry, confirm with the institute or register that holds the record.
Check the framework documentation for the version adopted, check the metadata for version and reference period, and confirm a business entry with the institute or register that holds it.