MiCA establishes a single legal framework across all EU member states, which is its main structural advantage over fragmented approaches. The UK’s FCA has its own crypto registration and regulatory regime. The US splits oversight between the SEC (securities) and CFTC (commodities), with no unified framework equivalent to MiCA. Companies operating in multiple jurisdictions must comply with each regime independently.

MiCA (Markets in Crypto-Assets Regulation) is the EU’s comprehensive regulatory framework for crypto-asset service providers, stablecoin issuers, and token issuers. Published as Regulation (EU) 2023/1114, it establishes licensing requirements, consumer protection rules, AML/KYC obligations, and reporting standards — including iXBRL format for white papers — across all EU member states. Stablecoin provisions applied from 30 June 2024; CASP and operational provisions from 30 December 2024. MiCA is fully in force.

MiCA applies to crypto-asset service providers (CASPs), crypto exchanges, digital wallet providers, stablecoin issuers, and asset-referenced and e-money token issuers that provide services to EU clients. It does not apply to fully decentralised DeFi protocols or NFTs unless these are classified as financial instruments. ESMA maintains an interim register of authorised CASPs.

MiCA requires that crypto-asset white papers be prepared in Inline XBRL (iXBRL) format. This makes disclosures machine-readable and comparable across the EU. Specialist iXBRL software is required to produce the tagged XHTML output.

MiCA compliance requires: regulatory authorisation from a national competent authority; publication of an iXBRL white paper before crypto-asset issuance; AML and KYC procedures; reserve maintenance (for stablecoin issuers); transparent disclosure of financial risks; and ongoing compliance and reporting obligations.

Non-compliant companies face significant fines and operational bans. Specific penalty amounts are set by national competent authorities in each EU member state. ESMA can withdraw authorisation and impose supervisory measures at the EU level. Operating without MiCA authorisation as a CASP since 30 December 2024 constitutes a breach.

Country by Country Reporting (CbCR) is a mandatory disclosure framework for multinational enterprises with consolidated revenues above €750m. Introduced under the OECD’s BEPS initiative, it requires MNEs to report income, taxes paid, employees, and other financial indicators on a jurisdiction-by-jurisdiction basis. From financial years starting 1 January 2025, EU submissions must use Inline XBRL format tagged to the EU-published taxonomy.

Compliance is required for MNEs with consolidated group revenues exceeding €750m in the previous fiscal year. The obligation typically falls on the ultimate parent entity in its home jurisdiction, with secondary filing required in other jurisdictions if automatic data exchange is not in place.

The report must include, by jurisdiction: revenue split between related and unrelated party transactions; profit or loss before tax; income tax paid and accrued; headcount; stated capital and retained earnings; and tangible assets excluding cash. The EU template is structured in three tables covering allocation data, entity lists, and additional explanatory information.

Penalties vary by jurisdiction. Belgium imposes fines of €1,250 to €25,000. Malta can fine up to €50,000 with daily penalties of €100 for ongoing violations. Germany’s penalties are generally more moderate but notification failures can still trigger sanctions. All jurisdictions treat repeated or wilful non-compliance more severely than procedural errors.

EU CbCR reports must be submitted in XHTML with Inline XBRL tagging, using the taxonomy published by the European Commission under Implementing Regulation (EU) 2024/2952. This requirement applies to financial years beginning on or after 1 January 2025. The XML schema for the required structure is published by the EU Publications Office.

Not currently. Country-specific sections for Czech Republic, Poland, and Slovakia are not included in this article. These jurisdictions implement CbCR under EU Directive 2016/881/EU and national legislation. Separate guidance covering these countries is planned. In the interim, consult the relevant national tax authority for local filing rules.

Successful ESEF iXBRL implementation is defined by a validation-clean tagged report, zero schema errors, produced by a repeatable internal process. The markers of success are: documented taxonomy mapping, a separated and quality-assured tagging workflow, and at least one dry run against a prior period report before the first live submission.

ESEF (European Single Electronic Format) applies specifically to the annual financial reports of listed companies under the Transparency Directive. CSRD (Corporate Sustainability Reporting Directive) has separate digital reporting requirements. However, CFOUR Comply supports both ESEF and CSRD reporting formats, so companies subject to both can manage them in a single platform.

The ESEF taxonomy defines the iXBRL tags that listed companies must use when tagging their financial statements. ESMA publishes a new taxonomy version each year. For FY2025 annual reports, the applicable version is ESEF Taxonomy 2025, published 21 April 2026, which incorporates IFRS 18 entry points. Companies must confirm they are tagging against the taxonomy version that corresponds to their reporting period.

An ESEF-compliant report requires six steps: prepare accurate financial statements under IFRS; convert them to XHTML format; apply iXBRL tags from the ESEF taxonomy to primary financial statement elements and notes; validate the tagged document against the taxonomy; compile all parts into a single XHTML document; and submit to the relevant regulatory authority by the required deadline.

The most common issues are: selecting incorrect taxonomy tags for financial line items; creating extensions without proper anchoring to standard tags; and applying incorrect context, units, or sign logic. These errors often go undetected without dedicated validation tooling. Validation against the ESEF taxonomy schema before submission is a required step, not an optional check.

ESEF applies to annual financial reports of listed companies and requires iXBRL-tagged XHTML format for financial data. CSRD (Corporate Sustainability Reporting Directive) covers sustainability reporting for qualifying companies — after Omnibus I (in force March 2026), this means companies with over 1,000 employees and over €450m turnover. The two frameworks are separate but complementary. CFOUR Comply supports both.

ESEF applies to all companies with securities listed on EU or EEA regulated markets. It covers equities and bonds. Companies with cross-border listings across EU/EEA and non-EU markets must meet ESEF standards for their EU/EEA filings. Newly listed companies must produce ESEF-compliant reports from their first annual filing.

XBRL (eXtensible Business Reporting Language) is the underlying data language. iXBRL (Inline XBRL) embeds XBRL tags directly within an XHTML document, so the same file is both machine-readable (for automated processing) and human-readable (viewable in a web browser as a standard financial report). ESEF requires iXBRL, not standalone XBRL, so that the report functions as both a structured data file and a readable document.

The most common challenges are: selecting the correct ESEF taxonomy tag for each financial line item; managing custom extensions (anchoring them correctly to standard tags); and applying accurate context, units, and sign logic within iXBRL properties. Validation against the ESEF taxonomy schema before submission is the key control step to catch tagging errors before they reach the regulator.

ESEF (European Single Electronic Format) reporting is the requirement for companies listed on EU and EEA regulated markets to file annual financial reports in XHTML format with iXBRL tagging applied using the ESEF taxonomy. Introduced under the EU Transparency Directive (Directive 2004/109/EC) and implemented by ESMA, ESEF has been in effect for financial years starting on or after 1 January 2020. The goal is standardisation: machine-readable reports that regulators and investors can process and compare without manual data extraction.

The ESEF taxonomy is the structured set of iXBRL tags that listed companies must use when marking up their financial statements. It is based on the IFRS taxonomy and is published by ESMA. The current version is ESEF Taxonomy 2025, published 21 April 2026, which supports FY2026 consolidated financial statements. It includes two entry points: one under IAS 1 (current standard) and one under IFRS 18 (for early adopters). IFRS 18 becomes mandatory from 1 January 2027. ESMA has confirmed it will not issue a 2026 taxonomy update, so the 2025 taxonomy remains applicable for both FY2025 and FY2026 reporting periods.

Initial implementations require more time for taxonomy mapping, staff training, and process adjustments. Once established, subsequent filings are considerably faster than manual form completion. Many organisations find that well-designed iXBRL tools reduce overall preparation time compared to traditional methods. 

Some XBRL platforms support multiple taxonomies within a single application. If subject to both SBR and ESEF requirements, selecting software that handles both simplifies training and may offer cost efficiencies. Verify your chosen software explicitly supports both the Dutch Taxonomy and the ESEF Taxonomy. 

SBR stands for Standard Business Reporting. It is a government-initiated framework that standardises how businesses submit financial and regulatory information to public sector agencies using structured digital formats, primarily iXBRL. The initiative reduces administrative burden by enabling companies to prepare financial data once and submit to multiple government bodies without re-entering information. 

From 1 January 2026, SBR is mandatory for annual accounts filed with the Dutch Chamber of Commerce. All limited companies (BVs and NVs) and foreign legal entities with a Dutch branch must file in iXBRL format using the Dutch Taxonomy. For tax returns, SBR remains optional. 

SBR and ESEF are both iXBRL-based frameworks but serve different purposes. SBR is a Dutch national initiative for filing statutory accounts with the Chamber of Commerce using the Dutch Taxonomy. ESEF is an EU-wide regulation requiring listed companies to prepare consolidated annual reports using the ESEF Taxonomy based on IFRS. Dutch listed companies may need to comply with both. 

You need specialised iXBRL software supporting the Dutch Taxonomy. Options include dedicated iXBRL tagging tools, integrated accounting systems with built-in iXBRL export, or outsourcing to a service provider. Key features include taxonomy support, validation functionality, and ease of use. 

SBR (Standard Business Reporting) software enables companies to produce annual reports in iXBRL format for filing with the Kamer van Koophandel (KVK). From 2026, this is mandatory for all large and medium-sized Dutch companies. The software handles conversion of financial documents into structured iXBRL packages and validates them against the SBR taxonomy before submission. 

All large and medium-sized companies registered in the Netherlands must file their annual reports in iXBRL format from the 2026 reporting year onwards. This affects an estimated 8,000+ businesses – a significant expansion from the approximately 168 listed companies previously required to file under ESEF. 

ESEF (European Single Electronic Format) applies to listed companies filing with securities regulators across the EU. SBR is the Dutch national standard and applies to a much broader group of companies – including non-listed large and medium-sized entities – filing their annual accounts with the KVK. For more background, see: What is ESEF?

iXBRL (Inline XBRL) is the technical format used for structured financial reporting. Tagging is the process of marking up financial statements with accounting definitions from a taxonomy – a structured dictionary of financial concepts. The result is a document that is both human-readable and machine-processable. For a plain-language explanation, see: What is XBRL?

Yes – and many are already preparing to do so. Firms that already provide ESEF tagging services are well-positioned to extend this to SBR. For firms new to iXBRL tagging, platforms like CFOUR Comply are designed to make this commercially viable, with per-client pricing and short onboarding times. 

With CFOUR Comply, most first-time users complete tagging within one day for a standard annual report. For repeat clients using roll-forward functionality, the time is even shorter. 

All large and medium-sized companies registered in the Netherlands must file their annual reports in iXBRL format from the 2026 reporting year onwards. This affects an estimated 8,000+ businesses – a significant expansion from the approximately 168 listed companies previously required to file under ESEF. 

XBRL filing refers to the process of submitting financial or other business-related data in the XBRL format. It’s a digital filing system where companies tag their financial reports (such as balance sheets, income statements, etc.) with predefined XBRL tags. These tags define the meaning of the data and allow it to be easily processed, analysed, and compared by computers, regulators, and investors. 

Companies that are publicly listed or subject to regulatory reporting requirements often need to use XBRL for filing their financial reports. In the EU, publicly listed companies are required to file their annual financial reports in iXBRL (an inline version of XBRL) under the ESEF regulation. Large or public companies in also need to report on ESG data in iXBRL as part of the CSRD regulations. 

Reporting in XBRL is required from companies under ESEF and CSRD regulations. Specifically, publicly listed companies in the EU must submit their annual financial statements in iXBRL format under the ESEF regulation. The CSRD regulation extends this requirement to large companies, mandating the disclosure of ESG data in a structured format, often using XBRL/iXBRL. Both regulations aim to standardise reporting and make financial and non-financial data more accessible and comparable across the EU. 

XBRL reporting involves using the XBRL format to create and submit structured financial reports. These reports are machine-readable, making it easier to automate analysis and ensure consistency across financial data. 

Yes, you can open XBRL files with Excel, but it requires an XBRL add-in or specialised software to interpret and display the data in a usable format. 

Yes, all publicly listed companies in the European Economic Area (EEA) must comply with ESEF regulations when submitting their annual financial reports. 

XBRL (eXtensible Business Reporting Language) is a digital format used to structure financial data, making it easier for regulators, investors, and analysts to process and compare reports. 

ESEF (European Single Electronic Format) is a reporting standard introduced by ESMA that requires listed companies to submit their financial statements in a machine-readable format, ensuring accuracy and transparency. 

ESEF primarily applies to financial statements, but some companies must also report on sustainability metrics and other non-financial data under the Corporate Sustainability Reporting Directive (CSRD). 

ESEF improves transparency, ensures financial data is easily accessible, and helps investors compare company reports across different markets. 

XBRL (Extensible Business Reporting Language) software is a tool used to prepare, validate, and file financial and sustainability reports in structured format. It automates the tagging of financial and ESG data, ensuring reports comply with regulations such as ESEF and CSRD. Most modern tools produce iXBRL output, which is both machine-readable and human-readable.

Opening an XBRL file requires dedicated XBRL software. Standard applications such as Excel cannot handle XBRL’s tagging and validation structure. Certified XBRL tools and platforms designed for ESEF or CSRD reporting allow you to view, validate, and edit the tagged content in a compliant environment.

XBRL itself is an open standard, but the software required to generate, tag, and validate XBRL reports is not typically free. Most solutions are sold on a subscription or licence basis, with pricing based on features, user count, and reporting volume.

Cost varies by provider and scope. Entry-level solutions may start from a few hundred euros per month for small reporting entities, while enterprise platforms with ERP integration, unlimited users, or multi-jurisdiction support cost substantially more annually. Contact vendors directly for pricing based on your entity count and filing volume.

Yes. Most regulatory frameworks now specify Inline XBRL (iXBRL) as the required format. iXBRL integrates XBRL tags directly into an HTML document, making reports accessible to both people and automated processing systems. It is the mandated format for ESEF and the expected format for CSRD digital tagging.

XBRL produces a machine-readable data file only. iXBRL embeds the same structured tags into a human-readable HTML document. Most regulators now require iXBRL because it eliminates the need to produce a separate document for humans and a separate data file for machines.

A taxonomy is a structured dictionary that defines and standardises financial and ESG concepts. The ESEF taxonomy (currently ESEF 2025, published April 2026) defines the financial concepts that listed companies must tag in their IFRS annual reports. The CSRD/ESRS taxonomy defines the sustainability disclosure concepts required for CSRD report tagging. Software maps your report’s line items to these taxonomy concepts, producing a validated, regulatorily compliant output.

The CSRD timeline has been revised by Omnibus I (in force March 2026). Wave 1 companies (NFRD reporters) submitted their first CSRD reports in 2025 covering 2024 data but may skip 2025–2026 filings under a transition exemption. The next mandatory wave falls in 2028, covering 2027 fiscal data, for large companies with more than 1,000 employees and more than €450m in turnover. Non-EU companies must report from 2029 for 2028 data if the relevant EU-group thresholds are met.

The CSRD came into force on 5 January 2023. Wave 1 reporting (for 2024 fiscal data) began in 2025, covering companies previously subject to the NFRD. Omnibus I (March 2026) introduced a transition exemption allowing Wave 1 companies to skip 2025 and 2026 filings.

Wave 1 in 2025 covered companies previously reporting under the NFRD. These include companies with over 500 employees, net turnover exceeding €50m, and assets above €25m. Omnibus I introduced a transition exemption allowing these companies to skip filings in 2025 and 2026.

Non-compliance can result in financial penalties and reputational harm. Investors, customers, and other stakeholders assess ESG disclosure quality, and a gap in reporting can affect access to capital and commercial relationships.

Under Omnibus I, listed SMEs are excluded from mandatory CSRD reporting. They may choose to report voluntarily under the VSME standard based on EFRAG’s framework. Mandatory SME reporting may be introduced in future regulatory cycles.

Omnibus I (Directive (EU) 2026/470, in force March 2026) made six significant changes. It narrowed scope to companies with more than 1,000 employees and more than €450m turnover; introduced a Wave 1 transition exemption for 2025–2026; postponed the Wave 2 deadline from 2026 to 2028; removed sector-specific ESG standards; narrowed supply chain data requirements to direct partners only; and replaced reasonable assurance with limited assurance.

Yes, most of the solutions listed offer integration with ERP system, but this should be checked individually with your provider before implementation. CFOUR is agnostic to any data source, making it the best solution for companies seeking a flexible tool.  

Automated consolidation drastically reduces errors and can cut down processing time by over 50%. With CFOUR, companies report that consolidation time was reduced from 2-5 days to less than 8 hours. If you’re looking for a solution with advanced automation and user-friendly design, CFOUR is your go-to choice.  

Yes, consolidation software can integrate with multiple ERP systems, allowing data consolidation from various sources to create unified financial statements. 

For example, CFOUR provides APIs and pre-built connectors to facilitate seamless data transfer from any data source, with no limit on the number of sources it can integrate. This flexibility enables companies to consolidate financial data across multiple ERPs and other systems, ensuring efficient, accurate, and up-to-date reporting without manual data handling. 

This feature is not always available with any consolidation software provider; however, consolidated software can offer this possibility for smooth integration.  

Simple FAQ Content

Simple FAQ Content – 2

Your relevent FAQ answer.