- Product Explore >
- Pricing
-
Insights
Insights
Explore >
Up to top (this text gets replaced by JS) Up a level (this text gets replaced by JS)
- Discover
- Press Centre
- Articles
- Research and Guides
- Events
- FAQs
- A strategic guide for navigating legal entity compliance in 2025 and beyond
- Remain Legally Compliant in 2025
- Industry Focus Explore >
- Contact Us
Denmark has entered a new phase of statistical classification. Starting 1 January 2025, all Danish companies have received updated DB25 branch codes, which align with the European framework NACE Rev. 2.1 under Commission Delegated Regulation (EU) 2023/137. Although this reform is mainly statistical, it directly influences compliance, tax reporting, and data management across many sectors.
How does the EU regulation set the framework?
The European Commission adopted the delegated regulation on 10 October 2022, amending Regulation (EC) No 1893/2006 and creating NACE Rev. 2.1. From 2025 onward, all Member States must send official statistics to Eurostat using this new classification. The reform aims to reflect Europe’s economic evolution, incorporating digital services, green industries, and technological advances. Therefore, it improves comparability across Member States while allowing each country to tailor local details through national systems.
How is Denmark applying the change through DB25?
Denmark implements this reform through Dansk Branchekode 2025 (DB25). On 1 January 2025, the Danish Business Authority (Erhvervsstyrelsen) updated every company’s branch code in the Central Business Register (CVR). Consequently, all active enterprises now carry a DB25 code that mirrors their main activity under the new framework.
The first four digits correspond to the NACE class level, while the last two digits provide Danish-specific detail. During 2025, the authorities publish statistics using both DB07 and DB25, ensuring smoother comparisons and avoiding data gaps. The complete transition for statistical reporting will occur in 2026.
Companies that received new codes were notified through eBoks at the beginning of 2025. Those whose DB25 code does not represent their activity correctly can make corrections via Virk.dk or contact Statistics Denmark. To enable this update, the Business Authority briefly closed self-service registration tools between 28 December 2024 and 1 January 2025.
What impact does DB25 have on companies?
Even though DB25 primarily affects statistical registers, it still brings several practical implications. Because branch codes feed into internal systems, risk models, and compliance checks, businesses must adapt quickly. Data teams should manage dual coding during 2025 and label reports clearly with the correct code version. Furthermore, analysts will need to bridge time-series data to prevent breaks. Some institutions, such as Jobindsats, continue using DB07 temporarily, which means companies must remain alert to mixed references across datasets.
Although this reclassification modifies how companies are grouped, it does not alter their legal status or require amendments to corporate documents. The reform concerns administrative and statistical processes only.
How should companies prepare?
Compliance and reporting teams should review where branch codes appear in their workflows—such as financial statements, ESG reports, or internal dashboards. They should ensure that all databases can handle DB25 and maintain DB07 in parallel during 2025. In addition, businesses should build or update mapping tables to match old and new codes, train staff on changes, and verify that each system uses the right classification version. Acting early helps prevent inconsistencies in audits, tax submissions, or external disclosures.
Why does it matter for compliance?
Branch codes may seem administrative, but they influence sectoral analysis, risk assessments, and regulatory oversight. A mismatch can distort how activities appear in reports or supervisory databases. Therefore, compliance teams must align their systems with DB25 to safeguard accuracy and maintain transparency.
What’s next?
Managing a classification transition requires careful coordination and constant attention to detail. For insights into similar reforms across Europe, explore our feature on France’s NAF 2025 article.
Klea transforms entity management by offering centralised governance, automated compliance, and secure collaboration tools. For this reason, businesses seeking an efficient, scalable solution can take the following actions:
- Request a Demo – See Klea in action for your organisation.
- Start a Trial – Experience firsthand how automation reduces workload and improves efficiency.
- Talk to Our Experts – Get tailored recommendations based on your entity management needs.
Company secretarial software solutions play a vital role in ensuring structured governance, consistent compliance, and precise legal entity management. With Klea, organisations can maintain corporate governance that is efficient, transparent, and risk-free.
Legal Disclaimer
The information provided on Klea’s website is made available “as is” for informational purposes only. Klea does not provide legal, tax, or financial advice and is not responsible for any actions taken or not taken based on the content found on this website. In no event shall Klea be liable for any loss or damages arising from reliance on the information contained herein.
For specific legal or compliance support tailored to your business needs, please contact Klea directly. Our team provides personalised guidance and expert solutions. Any reliance on general content without direct consultation does not establish any legal responsibility or liability on Klea’s part.