Print Invoice for Romania

Romania has progressively implemented mandatory e-invoicing, transitioning from a voluntary system to a comprehensive clearance model across various transaction types. The journey began with Business-to-Government (B2G) e-invoicing becoming mandatory on July 1, 2022, for transactions with public institutions. This was followed by a significant shift for Business-to-Business (B2B) transactions, where e-invoicing became mandatory for Romanian-established businesses and VAT-registered non-established taxpayers for domestic supplies from January 1, 2024. A grace period for penalties for B2B transactions was initially in place until May 31, 2024, allowing businesses to adapt. From July 1, 2024, B2B e-invoicing became fully mandatory for Romanian-established taxpayers, requiring both issuance and receipt of invoices exclusively through the RO e-Factura system.

The scope further expanded to include Business-to-Consumer (B2C) transactions, with mandatory e-reporting for domestic B2C supplies by Romanian-established taxpayers taking effect from January 1, 2025. While B2C e-reporting was voluntarily available from July 1, 2024, penalties for non-compliance for B2C transactions began on July 1, 2025. As of January 1, 2026, all B2B, B2C, and B2G invoices must be transmitted through the RO e-Factura system. The deadline for transmitting B2B and B2C invoices is generally within five working days from the invoice issue date, or five working days from the legal invoice issuance deadline.

Romanian e-invoices must adhere to a specific structured XML format, primarily based on the Universal Business Language (UBL 2.1) and compliant with the European e-invoicing standard EN 16931. Beyond the general European standard, Romania implements its own Core Invoice Usage Specifications (RO_CIUS), which define national rules and a standardized structure for invoice data.

A detailed breakdown of essential invoice elements in the XML format includes:

• Supplier and Buyer Identifiers: This encompasses crucial information such as the tax identification code (CUI/CIF), legal name, address, and VAT registration status for both the issuer and the recipient.
• Invoice Number and Date: Standard invoice numbering and dating conventions are required.
• Line Item Details: Each item on the invoice must be clearly described, including the quantity, unit of measure (using UBL unit codes), unit price, and total amount. For certain high-risk goods, specific tariff codes are also mandatory.
• Taxation Details: This involves clearly stating the applicable VAT rates, VAT amounts, and the total VAT payable.
• Totals: The invoice must include subtotals, any discounts or charges, and the final total amount due.
• Digital Sealing: After submission and validation on the RO e-Factura platform, the Romanian Ministry of Finance applies an electronic seal to the invoice. This seal guarantees the integrity and authenticity of the document, certifying that its content has not been altered since validation. The digitally sealed XML file is considered the original legal invoice for VAT deduction purposes.
• Real-time Reporting: The RO e-Factura system operates on a clearance model, meaning invoices are sent to the tax authority for validation before the recipient uses them for tax purposes, allowing for near real-time access to invoicing information.

Integrating your accounting software with Romania's RO e-Factura system is a critical step for compliance. The RO e-Factura platform, managed by the National Agency for Fiscal Administration (ANAF), serves as the central hub for all e-invoicing processes.

Here are the practical steps for ensuring seamless data transfer:

• Registration in SPV: Economic operators must first register in the Virtual Private Space (SPV) of ANAF. This is where businesses connect to the e-invoicing system. Access to SPV typically requires a digital signature and a confirmation certificate for ANAF.
• API or Web Loading: Invoices in XML format can be issued and transmitted using either web services (API integration) or by manually uploading them via the web portal, depending on whether a company has its own application for generating electronic invoices. For automated solutions, API integration is generally preferred.
• OAuth2 Authentication: When integrating via API, completing the OAuth2 authorization flow with ANAF is a prerequisite.
• XML Generation: Your accounting software must be capable of generating invoices in the RO_CIUS compliant UBL 2.1 XML format.
• Submission and Validation: Once generated, the XML invoice is submitted to the RO e-Factura system. The system performs syntactic and semantic validations. If compliant, it applies an electronic seal, and the invoice is then considered legally issued.
• Recipient Notification and Retrieval: The recipient is notified of the incoming e-invoice and can download it from the SPV within a 60-day period.

Common challenges include ensuring the accuracy and alignment of master data with ANAF's specific requirements, as incorrect data can lead to rejected invoices. Robust error handling and a retry mechanism for failed submissions are crucial for smooth operations.

Non-compliance with Romania's e-invoicing regulations can result in significant financial penalties, which vary based on the size of the taxpayer and the nature of the infraction. The enforcement of penalties began on June 1, 2024, following a grace period.

Here's a breakdown of potential penalties:

• Late Submission Fines: For delays in transmitting invoices to the RO e-Factura system, fines are tiered by business size:
• Large taxpayers: 5,000 lei to 10,000 lei (approximately €1,000 to €2,000).
• Medium taxpayers: 2,500 lei to 5,000 lei (approximately €500 to €1,000).
• Small taxpayers and individuals: 1,000 lei to 2,500 lei (approximately €200 to €500).
• For B2C transactions, only one fine per month is applied, regardless of the number of non-compliant invoices.
• Non-E-Invoice Penalties for B2B: In B2B transactions, if an issuer fails to send an invoice via RO e-Factura, a penalty of 15% of the invoice value can be imposed. The same 15% penalty applies to the recipient if they receive and record a non-e-invoice. This underscores that compliance is a shared responsibility.
• B2G Payment Restrictions: For B2G transactions, public authorities are only permitted to pay invoices that have been submitted via RO e-Factura. If a public authority makes a payment without an e-invoice, they can face a fine of 500 lei to 1,000 lei, and any illegal payment must be recovered with interest and late-payment penalties.

Hypothetical Scenario: Imagine a medium-sized manufacturing company that, due to an oversight, fails to submit 10 B2B invoices totaling 50,000 lei through RO e-Factura within the five-working-day deadline. Beyond the late submission fine of 2,500 lei to 5,000 lei, the company could face an additional penalty of 15% of the invoice value (7,500 lei) for each non-compliant invoice, potentially leading to substantial cumulative fines. Furthermore, their business partners receiving these non-compliant invoices could also incur a 15% penalty, jeopardizing business relationships.

Mitigation strategies include implementing robust automated systems for timely submission, conducting regular internal audits, and ensuring all staff involved in invoicing are thoroughly trained on the RO e-Factura requirements.

Maintaining continuous compliance with Romania's e-invoicing regulations requires a proactive approach and robust internal processes. The goal is not just to avoid penalties but to leverage the efficiency benefits of digital invoicing.

Here are some best practices for e-invoicing in Romania:

• Prioritize SPV Registration and Access: Ensure your company, or your authorized representative (like an accountant), has a fully functional account in the Virtual Private Space (SPV) and understands the process for authorizing applications to send invoices on your behalf.
• Automate XML Generation: Invest in accounting or ERP software that can automatically generate invoices in the RO_CIUS compliant UBL 2.1 XML format. Manual creation is prone to errors and inefficiencies.
• Implement Robust Integration: If using an API, ensure your integration with RO e-Factura is stable, includes proper error handling, and has retry mechanisms for failed submissions. Regularly monitor the status of your submissions.
• Validate Data Rigorously: Before submission, implement internal validation checks to ensure all mandatory fields are correctly populated and that master data (e.g., buyer/seller details, VAT codes, tariff codes) is accurate and aligned with ANAF's requirements.
• Adhere to Submission Deadlines: Always submit invoices within the five-working-day deadline from the invoice issue date. Consider submitting earlier to allow for potential corrections.
• Establish Clear Internal Workflows: Define clear responsibilities and procedures for invoice creation, submission, error resolution, and archiving.
• Ensure Secure Archiving: While RO e-Factura temporarily stores invoices for 60 days, both the issuer and recipient are legally obliged to retain electronic invoices for at least 10 years. Implement a secure digital archiving solution.
• Regular Audits and Updates: Periodically audit your e-invoicing processes to ensure ongoing compliance. Stay informed about any legislative changes or updates to the RO e-Factura system.
• Staff Training: Provide comprehensive and ongoing training to all staff involved in invoicing, including accounting, sales, and IT teams, on the latest e-invoicing regulations, system usage, and best practices.

Compliance Readiness Checklist:

• Is your company registered in the SPV with active access?
• Can your accounting system generate RO_CIUS compliant UBL 2.1 XML invoices?
• Do you have an automated process for submitting invoices to RO e-Factura?
• Are your internal data validation rules aligned with ANAF's requirements?
• Do you have a system to track submission statuses and handle rejections promptly?
• Is your archiving solution compliant with the 10-year retention period?
• Are your staff regularly trained on e-invoicing procedures and updates?
• Do you have a process for monitoring legislative changes related to e-invoicing?