- Created by Romain Ducenne, last modified yesterday at 5:11 pm
Responsible authority Refers to the government department or agency responsible for overseeing and implementing eInvoicing regulations in the country. Ministry of Transport, Information Technology and Communications Business-to-Government (B2G) mandate Refers to whether or not businesses are legally required to send electronic invoices for the contracts in public procurement. NO Business-to-Business (B2B) mandate Indicates if businesses are required to use electronic invoices when dealing with other businesses, including when dealing with Public Authorities in the country. NO Business-to-Consumers (B2C) mandate Indicates if businesses are required to use electronic invoices when dealing with consumers. NO European Standard for eInvoicing EN 16931 The European Standard (EN 16931) on eInvoicing defines a common format and data model for electronic invoices, ensuring they are structured, machine-readable, and compatible across EU systems. YES All public contracting authorities are required to accept and process electronic invoices that comply with the European Standard for eInvoicing for all public procurement contracts above EU Public Procurement thresholds [1]. Operating model for B2G eInvoicing Refers to whether there’s a specific system or process for exchanging eInvoices with government entities, such as a central platform or outlined procedures to ensure compliance. NO Use of CIUS and Extensions for European Standard for eInvoicing EN 16931 Relates to whether the country uses any additional technical rules or extensions beyond the European eInvoicing Standard. NO VAT Real-time reporting system mandate The VAT real-time reporting system is a system for VAT reporting based on eInvoicing. NO Monitoring mechanism This reflects if the country has a mechanism to monitor eInvoicing developments in the country. YES Bulgaria is moving towards a comprehensive mandatory eInvoicing model and advanced digital reporting mechanisms, inspired by successful implementations in other European countries. No Business-to-Government (B2G) eInvoicing mandate exists, but since 1 November 2019, all public sector entities are required to receive and process structured eInvoices compliant with the European standard EN 16931[5], as mandated by Article 115a of the Public Procurement Act (SG 86/18), which transposes Directive 2014/55/EU. This rule applies when public authorities pay suppliers for goods or services provided through formal procurement contracts above the thresholds provided in the Public Procurement Directives[6]. There is no business-to-business (B2B) mandate. There is no business-to-consumer (B2C) mandate. The European standard EN 16931 has been adopted by contracting authorities. The most frequently syntax[7] used when exchanging eInvoicing is XML. Using compliant formats like UBL 2.1 or as Cross-Industry Invoice (CII)[8] ensures that invoices are machine-readable, interoperable, and accepted by public procurement platforms such as CAIS EPP. The Central Automated Information System for Electronic Public Procurement (CAIS EPP) serves as a central platform for eProcurement and tender-related eInvoicing. However, each public authority maintains its separate systems which connected to CAIS EPP. Suppliers register on CAIS EPP for tendering and document exchange but need to also interact with each public body separately for invoice processing and payment. This requires suppliers to monitor both their CAIS EPP profile and communications from individual public bodies, making invoice processing and payment decentralised. There is no national CIUS or additional extensions. Currently, there is no real-time reporting system in Bulgaria. Bulgaria’s eInvoicing monitoring system is centered around a centralized digital infrastructure managed by the National Revenue Agency (NRA), which enables real-time or near-real-time oversight of business transactions. Through the National Electronic Billing System (NEFS), all electronic invoices are submitted in standardized formats and digitally signed, allowing the NRA to instantly validate, archive, and cross-check invoice data. This system is complemented by the phased introduction of the Standard Audit File for Tax (SAF-T), which requires businesses to periodically submit structured financial data, including ledgers and transaction records. Together, these tools create a robust monitoring framework that enhances tax compliance by enabling automated data analysis, anomaly detection, and targeted audits based on real-time insights into business activities. Bulgaria has initiated a public consultation to implement a mandatory clearance model for eInvoicing for all contracting entities, following the example of other European nations such as Italy and France. [1] The European Standard on EU law sets minimum harmonised rules for tenders whose monetary value exceeds a certain amount and which are presumed to be of cross-border interest. More information can be found via: https://single-market-economy.ec.europa.eu/single-market/public-procurement/legal-rules-and-implementation/thresholds_en [2] The European Standard on eInvoicing (EN 16931) defines a common format and data model for electronic invoices, ensuring they are structured, machine-readable, and compatible across EU systems. [3] Ibid.2 [4] The European Standard on EU law sets minimum harmonised rules for tenders whose monetary value exceeds a certain amount and which are presumed to be of cross-border interest. More information can be found via: https://single-market-economy.ec.europa.eu/single-market/public-procurement/legal-rules-and-implementation/thresholds_en [5] The European Standard on eInvoicing (EN 16931) defines a common format and data model for electronic invoices, ensuring they are structured, machine-readable, and compatible across EU systems. [6] Ibid 1. [7] The information defined in the semantic data model of the eInvoicing standard, documented in the eInvoicing standard, must be carried in an electronic message that may be transferred from one computer to another. The semantic eInvoicing standard does not define the structure of the electronic message. The message structure is called syntax. [8] CII is a structured XML format developed by UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business). Last updated:
Aug 14, 2025 17:11Summary
Highlights
Legislation
B2G
B2B
B2C
Status on the implementation of the European eInvoicing standard
Operating model for B2G eInvoicing
Use of Core Invoicing Usage Specifications (CIUS) at national level
VAT Real-time reporting system
Monitoring mechanism
Next steps
Are you aware of further developments on eInvoicing B2G in this country? Contact us via email EC-DIGITAL-BUILDING-BLOCKS@ec.europa.eu.
You can also access the 2016, 2017, 2018, 2019, 2020, 2021, 2023 and 2024 eInvoicing Country Sheets via the eInvoicing User Community.
NO VERIFICATION
Status | NO VERIFICATION |
---|
How to comment
You can also use in-line comments to provide feedback.