Romania's SAF-T Pilot Program: Lessons for European Businesses

Romania’s National Agency for Fiscal Administration (ANAF) launched a 12-month SAF-T pilot program running from September 2025 through August 2026, marking a critical phase in the country’s digital tax transformation. The pilot centers on the D406 declaration, Romania’s SAF-T filing form, and introduces automatic cross-validation between SAF-T submissions and existing VAT returns (D300). For European businesses watching the continent’s SAF-T expansion, Romania’s experience offers valuable lessons in data quality, ERP readiness, and phased implementation strategy.

The D406 Declaration: Romania’s SAF-T Filing

Romania adopted the OECD SAF-T standard and implemented it through the D406 informative declaration. This XML-based filing encompasses the full range of SAF-T data sections:

• •General Ledger: Chart of accounts and journal entries for the reporting period
• •Accounts Receivable and Payable: Customer and supplier master data with transaction details
• •Tax Table: VAT codes, rates, and tax treatment classifications
• •Source Documents: Sales invoices, purchase invoices, payments, and goods movements
• •Fixed Assets: Asset register with acquisition, depreciation, and disposal data

The D406 is submitted electronically through ANAF’s e-filing portal. Filing frequency is monthly for most data sections, with fixed assets reported annually. The XML must conform to ANAF’s published format specification, which includes Romania-specific requirements to the base OECD SAF-T structure.

Automatic Cross-Validation: D406 vs D300

One of the most significant aspects of Romania’s pilot is the automated reconciliation between SAF-T data (D406) and VAT returns (D300). ANAF’s systems automatically compare:

• •Total taxable amounts reported in the SAF-T file against corresponding figures in the VAT return
• •VAT amounts by rate category to detect misclassifications or calculation errors
• •Transaction counts and document references for consistency between the two filings
• •Intra-community supply and acquisition data for cross-border transaction accuracy

Romania’s Phased Rollout History

Romania’s SAF-T journey has been gradual, reflecting the complexity of implementing digital tax reporting at national scale:

• •2022: ANAF published the initial SAF-T technical specifications and format requirements
• •January 2022: First group of large taxpayers (annual turnover above RON 500 million) required to begin D406 submissions, with a second group joining in July 2022
• •January 2023: Obligation extended to medium taxpayers (turnover between RON 100 to 500 million)
• •January 2025: Small taxpayers brought into scope, completing the main rollout
• •September 2025: Pilot program launched for automated D406/D300 cross-validation

This phased approach gave large enterprises roughly a year of lead time before the next tier joined, creating a cascade of practical experience that benefited subsequent groups.Bulgaria is following a similar phased model for its own SAF-T rollout. However, each phase also revealed new categories of issues, particularly around data quality and ERP compatibility.

Common Pitfalls During SAF-T Implementation

Romania’s multi-year rollout has surfaced recurring challenges that are relevant to any country implementing SAF-T. These pitfalls include:

1. Inconsistent Master Data

The most common source of D406 validation failures is inconsistent master data. Customer and supplier records with missing tax identification numbers, incorrect addresses, or duplicate entries cause reference integrity errors when cross-linked with transaction data. Businesses that invested in master data cleanup before their first filing had significantly fewer rejection cycles.

2. ERP Mapping Gaps

Many accounting systems store data in structures that do not map cleanly to the SAF-T format. Common gaps include missing fields for ANAF-specific code lists, incorrect account type classifications, and transaction categories that do not align with SAF-T coding standards. Companies relying on legacy or heavily customised accounting systems faced the steepest adaptation curves.

3. VAT Return Reconciliation Failures

With automated D406/D300 cross-validation, even small discrepancies between SAF-T data and VAT returns trigger flags. Common causes include timing differences (transactions recorded in different periods across systems), rounding variations, and manual adjustments made to VAT returns that are not reflected in the underlying accounting data.

4. Large File Handling

Companies with high transaction volumes generate SAF-T files that can exceed hundreds of megabytes. File generation times, upload failures, and portal timeout issues have been reported, particularly during peak filing periods. Compression, file splitting (where permitted), and off-peak submission help mitigate these issues.

5. Insufficient Testing

Businesses that treated the first live filing as their first real test consistently encountered more issues than those who ran multiple rounds of test generation and validation beforehand. Pre-submission validation using local tools catches the majority of schema and business rule errors before they reach the tax authority portal.

Lessons for Other European Countries

Romania’s experience offers several transferable lessons for businesses in countries that are implementing or expanding SAF-T requirements across Europe:

• •Start with data quality. The SAF-T file is only as good as the underlying data. Clean, consistent master data is the foundation of successful compliance.
• •Treat SAF-T as a process, not a project. Ongoing monthly filings require embedded workflows, not one-time implementation efforts.
• •Expect cross-validation. Tax authorities are increasingly comparing SAF-T data against other filings. Ensure your data is consistent across all submissions.
• •Engage ERP vendors early. SAF-T export capability varies dramatically across ERP platforms. Verify support and plan for any required configuration or development work.
• •Validate before submitting. Local validation tools catch errors faster and more privately than discovering them through portal rejection.
• •Learn from early adopters. Countries and companies that have gone through SAF-T implementation publish lessons learned. Use these experiences to avoid repeating common mistakes.

The Importance of ERP Readiness

Romania’s rollout has underscored that ERP readiness is the single largest determinant of SAF-T compliance success. Key aspects of ERP readiness include:

• •Native SAF-T export: The ERP should generate compliant XML without requiring external transformation tools
• •Country-specific code lists: Tax codes, account types, and document classifications must match the tax authority’s official nomenclatures
• •Performance at scale: File generation must handle large data volumes without timeouts or memory issues
• •Incremental updates: The ability to regenerate files for corrected periods without full system reprocessing

For businesses operating in multiple European jurisdictions, the ideal scenario is an ERP platform that supports SAF-T generation for multiple country schemas from a single data source. This approach reduces duplication of effort and ensures data consistency across all filings, whether Romania’s D406, Luxembourg’s FAIA, Poland’s JPK, or any future SAF-T mandate.