What RO e-Factura is
RO e-Factura is Romania's national electronic invoicing system, operated by the Ministry of Finance through ANAF. It is not an invoicing app and not a portal for prettier PDFs. It is a clearance system: every in-scope invoice must be submitted to the state platform in a structured XML format, validated by ANAF, stamped with a ministry seal, and only then treated as a legally issued invoice. The PDF a customer sees is a downstream artefact; the XML lodged with ANAF is the invoice of record.
The legal foundation is OUG 120/2021 on the administration and implementation of the RO e-Factura system, since amended repeatedly as the rollout expanded. The structured format follows the European standard EN in the Romanian CIUS-RO implementation, which is why an invoice that renders correctly as a document can still be rejected for a structural error the human eye never sees.
The invoice of record is the XML lodged with ANAF, not the PDF the customer files. Treat the platform, not the document, as the source of truth.
For a founder used to issuing invoices from accounting software and emailing a PDF, this is a genuine shift in what "issuing an invoice" means. The obligation is procedural and unforgiving: an invoice not lodged in the system, or lodged late, is treated as defective regardless of its commercial validity. The material sits at mfinante.gov.ro/web/efactura, the official reference for the system.
The system is bidirectional. It is not only a channel for issuing — every in-scope invoice a company receives also arrives through RO e-Factura, deposited in its SPV inbox rather than by email. A buyer accounts for and reclaims input VAT from the lodged XML, so a supplier's failure to submit correctly becomes the buyer's problem too: the paper or PDF copy carries no independent standing. This mutual dependence is why the system works as a fiscal cross-check — ANAF holds both sides of every BB transaction and can reconcile them automatically.
SPV enrolment: the precondition
Access to RO e-Factura runs through the Spațiul Privat Virtual (SPV) — ANAF's secure electronic communication channel. Enrolment in SPV has been mandatory for legal entities since March , under the amendments to the Codul de procedură fiscală. Since that date, ANAF disregards documents submitted on paper by companies and treats electronic transmission through SPV as the only valid channel. A newly formed SRL that has not completed SPV enrolment cannot lodge, receive, or download e-invoices — it is, operationally, unable to invoice.
Enrolment requires a qualified electronic signature (a certificat digital calificat) tied to the company's legal representative or an authorised agent. This is the same certificate infrastructure used across ANAF filings, so for most SRLs the accountant already holds or arranges it. The practical sequence for a new company is: incorporate at ONRC, obtain the qualified certificate, enrol in SPV, then connect to RO e-Factura. Skipping the certificate step is the most common reason a founder finds they cannot issue their first compliant invoice on schedule.
Enrolment is a one-time step per company, but the certificate has a validity period and must be renewed. Build the renewal date into the compliance calendar — an expired certificate silently blocks every electronic filing, not only e-invoicing. The mechanics of running this through an external accountant are covered in our guide to SRL accounting obligations.
The rollout: BG, then BB, then BC
The scope of RO e-Factura widened in phases, and the dates shifted more than once. The confirmed sequence is worth stating precisely, because older guidance describes a narrower system than the one now in force.
- BG — mandatory from July . Suppliers to public authorities were the first cohort brought into the system.
- BB — mandatory reporting from January , with a transitional period in which invoices could also travel by conventional means. From July , resident taxable persons must issue and receive BB invoices exclusively through RO e-Factura; an invoice outside the system is not a valid invoice.
- BC — mandatory from January . Invoices to non-taxable final consumers were optional from July and became compulsory at the turn of the year. Simplified invoices below the relevant limit are exempt from transmission.
As at mid-, the system is in full effect across BG, BB, and BC for resident taxable persons. The BB and BC obligations rest on the issuing company for its own invoices. What remains genuinely fluid is the treatment of specific edge cases — simplified invoices, certain exempt sectors, and non-resident scenarios — where I would verify the current position against ANAF at the point of setup rather than rely on any general statement, including this one.
The five-working-day submission rule
Every in-scope invoice must be submitted to RO e-Factura within a fixed window of its issue date. That window changed at the start of . In the period July to December the deadline was five calendar days. From January , under OUG /, it became five working days from the issue date — a modest relaxation, since weekends and public holidays no longer count against the clock. ANAF's guidance is that the issue day itself is not counted; the five working days run from the following day.
Late submission is a standalone breach. The invoice can be entirely correct and the penalty still applies.
This is a recurring transmission obligation, not a one-off registration. For a company issuing dozens of invoices a month, it means a disciplined submission rhythm — most SRLs meet it by having their accounting software submit automatically, or by handing the batch to an accountant who lodges on a fixed schedule. Missing the window is a breach in its own right, independent of whether the invoice is otherwise accurate. This is the compliance point founders most often underestimate, because it converts invoicing from a monthly bookkeeping task into a near-continuous one.
Penalties for non-submission
Two distinct penalty regimes apply, and they stack conceptually. The first targets late or missing transmission. Fines are graduated by taxpayer size:
- RON ,–, for large taxpayers.
- RON ,–, for medium taxpayers.
- RON ,–, for other legal persons and self-employed persons — the band most foreign-owned SRLs fall into.
The second regime is more serious. In defined BB situations — issuing an invoice outside the system, or accounting for one received outside the proper flow — the sanction is % of the invoice value. On a single large invoice this dwarfs the fixed fines and is the real deterrent behind the system. The distinction matters: a late submission draws a fixed administrative fine, but a supply invoiced entirely outside RO e-Factura draws the percentage penalty.
Neither penalty relieves the underlying VAT or accounting obligation. A company that pays the fine still has to lodge the invoice. For a founder budgeting compliance risk, the exposure is not theoretical — ANAF has the data to detect gaps automatically, because it holds the counterparty's side of every BB transaction.
Corrections run through the system too. A credit note (storno) or amended invoice is itself an e-Factura submission referencing the original, not a document exchanged privately with the customer. This matters for a foreign owner: there is no off-platform route to fix an error quietly. Every adjustment is visible to ANAF, so the discipline that governs issuing also governs correcting. Treat the platform as the ledger of record for the entire invoice lifecycle, from first issue to final credit note.
Running it as a foreign-owned SRL
For a non-resident owner operating through an external Romanian accountant, RO e-Factura is manageable but demands a clear division of responsibility. The practical model most foreign-owned SRLs run:
- Certificate and access — the accountant typically holds a qualified certificate under a power of attorney (împuternicire) registered with ANAF, letting them lodge and retrieve invoices on the company's behalf.
- Issuing — invoices are raised in the company's own software, exported to the CIUS-RO XML, and submitted to the platform, either directly by the software's integration or by the accountant on a fixed schedule inside the five-working-day window.
- Receiving — inbound supplier invoices arrive in the company's SPV inbox and must be downloaded and booked. Someone has to monitor that inbox; invoices do not arrive by email.
The failure mode to guard against is a gap between who issues and who monitors. If the founder raises invoices in their own tool but assumes the accountant is submitting them, and the accountant assumes the tool submits automatically, invoices fall through the five-working-day window unnoticed. Agree explicitly, in writing, which party lodges each invoice and who checks the SPV inbox. A foreign owner running a lean structure should treat this as a defined process, not an assumption. Our guidance on remote SRL formation covers the operating setup for owners who never relocate.
Where RO e-Transport fits
RO e-Factura has a sibling for the physical movement of goods: RO e-Transport, established by OUG / and administered by ANAF. It requires certain road movements of goods to be declared in advance, generating a -character UIT code that must accompany the transport. It is a separate obligation from e-invoicing and catches a narrower set of businesses — but a foreign-owned SRL that trades in physical goods needs to know whether it is in scope.
Reporting applies to monitored road vehicles with a maximum authorised mass of at least . tonnes where a goods consignment exceeds kg or RON , in value, and to intra-community and high-fiscal-risk movements. The obligation to declare generally sits with the beneficiary, consignor, or supplier rather than the haulier, though the driver must be able to present the UIT code on demand. From January , real-time GPS position transmission became mandatory for high-fiscal-risk goods. Penalties are substantial — fines commonly cited in the RON ,–, range, with confiscation risk in serious cases.
A services-only SRL — consulting, software, digital products — is generally outside RO e-Transport entirely. A company moving physical stock across the border or domestically should confirm its position against ANAF guidance before its first shipment, because the thresholds and the high-risk goods list are revised periodically. Treat e-Transport scope as a fact to verify at setup, not to assume.
Frequently asked questions
What is RO e-Factura?
RO e-Factura is Romania’s national electronic invoicing system, run by the Ministry of Finance through ANAF under OUG /. In-scope invoices must be submitted to the state platform in a structured XML format, validated, and sealed. The XML lodged with ANAF is the legal invoice of record — the PDF a customer receives is a downstream document, not the invoice itself.
Do I need to enrol in SPV to use e-Factura?
Yes. Access runs through the Spațiul Privat Virtual, ANAF’s electronic communication channel, which has been mandatory for legal entities since March . Enrolment needs a qualified electronic signature tied to the legal representative or an authorised agent. Without SPV enrolment a company cannot lodge, receive, or download e-invoices, so it is a precondition for issuing any compliant invoice.
What is the deadline for submitting an invoice to e-Factura?
From January the deadline is five working days from the invoice issue date, under OUG /. Between July and December it was five calendar days. ANAF’s guidance is that the issue day itself does not count; the five working days run from the following day. Late submission is a breach in its own right, separate from the invoice being otherwise correct.
What are the penalties for not using e-Factura?
Late or missing transmission draws graduated fines: RON ,–, for large taxpayers, RON ,–, for medium taxpayers, and RON ,–, for other legal and self-employed persons. Separately, in defined BB situations, issuing or booking an invoice outside the proper flow can attract a penalty of % of the invoice value, which is the more serious exposure.
How does a foreign owner run e-Factura through an external accountant?
The accountant usually holds a qualified certificate under a registered power of attorney, letting them lodge and retrieve invoices for the company. Invoices are raised in the company’s software, exported to CIUS-RO XML, and submitted within the five-working-day window; inbound invoices arrive in the SPV inbox and must be downloaded and booked. Agree in writing who lodges and who monitors the inbox.
Is my company in scope for RO e-Transport?
RO e-Transport is a separate obligation for road movements of goods, generating a -character UIT code. It applies to vehicles of at least . tonnes where a consignment exceeds kg or RON ,, plus intra-community and high-fiscal-risk movements. A services-only SRL is generally outside it; a company moving physical goods should confirm its position with ANAF before its first shipment.
Talk to us
RO e-Factura and RO e-Transport are operational obligations that quietly determine whether your invoices are valid and your goods can move. We set foreign-owned SRLs up with SPV enrolment, a qualified certificate, a working submission rhythm, and a clear split of duties with the accountant. Talk to us about getting the invoicing chain right from day one, or see our pricing for formation and ongoing compliance.
Related guides
- Romanian VAT registration in 2026 — why every VAT-registered SRL is in scope for e-Factura
- SRL accounting obligations and the filing calendar — how e-Factura fits the wider compliance year
- Remote SRL formation from abroad — setting up SPV and invoicing without relocating
- Romanian SRL formation: the complete 2026 guide — the pillar that frames incorporation and setup
- The 1% microenterprise rate — the CIT regime that runs alongside these duties