Newsletter: monthly mandate & ERP support changes

Home › Guides

Romania playbook: RO e-Factura, the D300, D394 and D390 returns and the D406 SAF-T

A Romanian entity reports the same transactions several times: as structured invoices through RO e-Factura, in the D300 VAT return, in the D394 informative return, in the D390 recapitulative statement when there is intra-EU trade, and in the D406 SAF-T file. Each has its own deadline and validation. The work is to make them agree with one another and with the ledger, every period.

Data for Romania on this site: Romania country page · Romania × ERP e-invoicing support · Romania e-invoicing status

This playbook uses the same structure as the other country playbooks. Facts come from the Romania page and the official sources it cites. ERP support is on the Romania e-invoicing matrix.

What applies

VAT returns and audit files for this country, from this site's data
RequirementTypeFrequency (from the country page)Status on this site
VAT returnordinary returnRegistered fiscal period: month, quarter, half-year or year (a quarterly filer making a taxable intra-EU acquisition can have to switch to monthly)verified
EU recapitulative statementEU sales list / recapitulative statementMonthly, for months with reportable intra-EU supplies, acquisitions, services or call-off stock movementsverified
Informative return of domestic supplies and acquisitionsinformation return (annual summary or third-party transactions)Same reporting period as the D300 VAT returnverified
Standard audit file for taxaudit file – periodic submissionRegular file monthly or quarterly, following the VAT period (quarterly for half-yearly/annual VAT filers and non-VAT-registered taxpayers); annual assets file; stocks on requestverified

The rows give the deadlines: the D300 by the 25th of the month after the period; the D394 by the 30th; the D390 by the 25th of the month after the month in which VAT became chargeable; and the regular D406 file by the last calendar day of the month after the reporting period. Non-working days move some of them. Check the rows and their sources each cycle.

Operating model

  1. The ERP creates the invoice and the RO_CIUS XML.
  2. The XML is submitted within the working-day limit; the ERP records the submission and ANAF's validation result.
  3. Rejected submissions are corrected and resubmitted without creating a new accounting invoice.
  4. Supplier invoices are downloaded from the authority and matched once.
  5. At period end, the D300, D394, D390 and D406 are prepared from the same closed ledger.

ERP set-up checklist

Worked example: one month, four outputs that must agree

The 21% standard rate is from the Romania page (source: the EU's Your Europe VAT rates page). Amounts are illustrative round numbers in RON. In March a monthly filer issues one domestic invoice and books one domestic purchase.

Example entries: March sale, purchase and VAT settlement (RON, illustrative)
StepAccountDebitCreditNote
Domestic sale, submitted to RO e-FacturaTrade receivables12,100.00
Sales revenue10,000.00
Output VAT2,100.0021%
Domestic purchase, received through RO e-FacturaPurchases4,000.00
Input VAT840.0021%
Trade payables4,840.00
Settle March VATOutput VAT2,100.00
Input VAT840.00
VAT payable1,260.00

The cross-check for March:

OutputWhat it should showAgrees with
RO e-Factura1 issued invoice, 10,000 net; 1 received invoice, 4,000 netSales and purchase ledgers
D300Output VAT 2,100; input VAT 840; payable 1,260VAT accounts before settlement
D394The same sale and purchase, by counterpartyD300 for the same period
D390Nothing, because there was no intra-EU trade—
D406Opening balances, March entries, closing balancesTrial balance

If the D394 shows a purchase that the D300 does not, the most likely cause is a supplier invoice received through RO e-Factura but not yet posted. Post it in the right period or document why not before filing either return.

Exceptions to plan for

Worksheet

Use the Romania operating checklist.

Worksheet: Romania operating checklist

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use with the Romania playbook.

Scope

e-Factura

Each period

OutputDeadline (from the row, checked on)Agrees withDone
D300VAT accounts
D394D300
D390 (if intra-EU trade)Intra-EU sales and acquisitions
D406Trial balance

Differences

OutputDifferenceCauseFixOwner

Sources checked: 27 October 2026, through this site's Romania page (e-invoicing section checked 17 October 2026). Detailed exclusions, working-day computation and correction procedures need the current legislation and ANAF technical rules.

Data on this site: Romania country page · Romania × ERP e-invoicing support · Romania e-invoicing status · E-invoicing country × ERP matrix · VAT reporting requirements by country · SAF-T and audit files by country

In Country playbooks: previous Saudi Arabia playbook: Fatoora clearance, simplified-invoice reporting and VAT returns · next Hungary playbook: online invoice-data reporting, the 65 VAT return and the A60 statement · Guides by task · All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-27.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version · Suggest a correction

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.