Legal editorial illustration of a Romanian VAT decision file on a desk, titled VAT Registration Refused by ANAF and marked AI illustration

ANAF Refuses or Blocks VAT Registration in Romania: What Foreign-Owned Companies Should Review

Romanian VAT / ANAF decisions / foreign-owned companies

ANAF Refuses or Blocks VAT Registration in Romania: What Foreign-Owned Companies Should Review

A blocked VAT registration is a document problem before it is a strategy problem. Identify precisely what ANAF issued, when it was communicated, the legal route used for the application, and the facts stated in the decision.

This guide addresses a Romanian company with foreign owners whose VAT application has stalled, or whose finance team says that ANAF “refused the VAT number”. It also explains why a Romanian branch or an overseas business may need a different analysis. It is a framework for triage, not a conclusion about a particular company’s entitlement to register.

First, name the document you actually received

The phrase “ANAF refused VAT registration” can hide several distinct acts. For taxable persons with their place of business in Romania, ANAF Order 239/2021 governs the registration routes in Article 316(1)(a), (b) and (c) of the Fiscal Code. Under its special procedure for applications based on Article 316(1)(b) or (c), a VAT certificate may, in the specified cancellation situations, be communicated together with a cancellation decision. Read the ground and effective date in the decision. That is not the stated outcome for the Article 316(1)(a) route in this procedure. If ANAF has declined an initial filing, obtain its actual communication and identify the legal basis and remedy; neither a portal error nor an informal description proves that an appealable refusal decision has been issued. By contrast, Order 393/2021 expressly provides for a formal refusal decision in the separate Article 316(12)(e) re-registration route after specified cancellations under Article 316(11)(h). A request for information or a portal validation message is different again. ANAF Order 239/2021 procedure on the Romanian Legislative Portal and ANAF Order 393/2021 risk procedure on the Romanian Legislative Portal.

Select a situation below to add it to your review file, or combine several situations in the builder.

Ask the local finance team for the complete communication, including attachments and delivery record, rather than a screenshot of the taxpayer registry. A registry search is useful for checking current public status, but it cannot substitute for the legal grounds or the date on which an administrative act was communicated. The same word “rejection” in internal email may describe a technical filing error, a substantive decision or a missed request for information.

Build a review file from the facts you have

Select every situation that applies. The board combines the documents and questions to take into a review meeting. It makes no eligibility finding and calculates no deadline. The choices stay in your browser and are not sent to us.

VAT decision file builder

Your facts

No situations selected

Your review packet

Start with the core record below; select a situation to add focused items.

Documents to collect
  • The full ANAF communication and evidence of when and how it was received.
  • The filed VAT application, attachments and filing acknowledgement.
Questions for the review
  • Which entity applied, under which provision, and what administrative act exists?

Which legal route did the company use?

Article 316 of the Fiscal Code is the starting point, but the correct paragraph depends on the applicant and the registration history. Order 239/2021 covers certain applications by taxable persons with their place of business in Romania: registration around the start of operations, on crossing the small-business exemption threshold, or by opting for the normal VAT regime below that threshold. The current Article 3 differentiates the effective VAT registration date by the route used under Article 316. It was amended by ANAF Order 2633/2025, Article I, on the Romanian Legislative Portal, published on 16 December 2025. Do not assume that all applications take effect on the day ANAF finally communicates a certificate. ANAF Order 239/2021, Article 3, on the Romanian Legislative Portal.

Foreign ownership of a Romanian SRL does not, by itself, turn the SRL into a non-resident applicant. Examine the legal person that will make the supplies, its place of business, the Romanian branch if any, and the transaction flow. Point 1(2) of the risk-evaluation procedure in Annex 2 to Order 393/2021 excludes Romanian branches of taxpayers whose place of business is outside Romania and who must register under Article 316(2). This is an exclusion from that particular procedure, not a general exemption from Romanian VAT identification. A foreign parent’s VAT position, a Romanian subsidiary’s position and a branch’s position therefore should not be merged into one application narrative. Article 317 concerns a separate, limited VAT identification for specified intra-Community transactions or services; its code does not itself confer normal registration under Article 316. Test the transactions before assuming which route applies. ANAF procedure for Article 317 identification on the Romanian Legislative Portal. ANAF Order 393/2021, Annex 2, point 1(2), on the Romanian Legislative Portal.

Document → review → next question

ANAF document response map

Select a row for the review focus ↓
Document in handReview firstDo not assume
Response channel, scope, deadline and evidence requested.A final appealable refusal already exists.
Cancellation ground, legal basis, effective date and communication.The certificate proves continuing active VAT status.
Prior cancellation and the applicable re-registration route.Every application follows the same procedure.
Filing history and complete SPV communications.A registry screenshot starts or settles a challenge period.
Review focusRespond to the request

Preserve the invitation and its delivery record. Answer the specific questions ANAF asked, using dated and consistent supporting documents.

Review the stated grounds, not a generic “ANAF risk” label

The grounds must be tied to the actual act. Under the consolidated Order 239 procedure, specified checks may include fiscal inactivity and the fiscal-record circumstances identified for the taxable person and relevant persons in the applicable provision. For applications under Article 316(1)(b) or (c), points 5–10 of the consolidated procedure address checks for fiscal inactivity and certain fiscal-record entries and, where the stated cancellation conditions apply, communication of the certificate together with a cancellation decision. These filters must be applied to the precise entity, persons and facts identified by the relevant provision. The checks relating to shareholders or administrators deserve their own evidence review: compare the persons, dates, fiscal-record entries and company-register data with the condition actually invoked, and document any correction rather than assuming that foreign ownership is itself an adverse finding. The dates and consequences must be read from the exact provision and documents; a generic assertion that ANAF can always refuse a new foreign-owned company for “lack of substance” is too broad. ANAF Order 239/2021 procedure, sections II–III, on the Romanian Legislative Portal.

Order 393/2021 addresses a narrower situation: particular Romanian companies seeking registration again after cancellation under Article 316(11)(h), including the prior intention-and-capacity or fiscal-risk circumstances specified in Annex 2, point 1(1). Other cancellation grounds can engage other re-registration rules under Article 316(12); do not apply the high-risk route to them by default. For the particular Article 316(12)(e) route covered by its risk-evaluation annex, the procedure sets out risk assessment and, before a proposed refusal in the specified high-risk scenario, an opportunity for the taxpayer to be heard and provide information and documents. The applicable criteria must be checked against the current legal text and the ground of the earlier cancellation. The decision is to state the concrete reasons of fact and law. That is a useful review lens for a decision under this route; it is not a universal promise of the same sequence for every VAT filing. ANAF Order 393/2021 risk-evaluation procedure, points 8–13, on the Romanian Legislative Portal.

For a foreign-owned group, evidence may include signed customer arrangements, the activities performed by the Romanian entity, premises or operating arrangements, personnel or service providers, purchasing and sales records, management roles and the origin of funds. Which items matter depends on ANAF’s stated objection. Submit accurate documents that address the question actually put, with a clear explanation of dates and entities. A stack of unrelated contracts can obscure a simple discrepancy between the application and the trade register.

Preserve the communication date and assess the challenge route

A formal fiscal administrative act may be challenged through the administrative objection mechanism in the Fiscal Procedure Code. Article 268 recognizes the objection, Article 269 sets its written content and provides for filing with the issuing tax body, and Article 270(1) sets a 45-day period from communication. Article 270(4) provides a three-month period if the act lacks the appeal information required by Article 46(2)(i). Whether a particular letter or portal event is an administrative act, and how it was communicated, must be examined before applying these rules. Romanian Fiscal Procedure Code, Articles 268–270, on the Legislative Portal.

Article 278(1) says that lodging an administrative objection does not suspend enforcement of a fiscal administrative act. Article 278(2) preserves the possibility of seeking judicial suspension under Law 554/2004, subject to its conditions; an objection or a suspension request should not be treated as automatic restoration of VAT status. A subsequent court challenge may be available under the applicable fiscal and administrative litigation rules after the administrative objection is resolved. Fiscal Procedure Code, Article 278, on the Romanian Legislative Portal.

Save the SPV message, the complete PDF, transmission receipt and any postal proof. Record the date the document was legally communicated, not simply the date a manager first forwarded it to headquarters. Have local counsel or a tax specialist verify the applicable computation and any special provision in the decision. The file builder intentionally avoids a deadline calculator because it cannot determine the legally relevant communication event from a date typed into a webpage.

A corrected filing may be sensible where the problem is a missing item or a mistaken route. A formal objection may be necessary where a decision is legally or factually disputed. These are not interchangeable: filing a new application should not be assumed to preserve an objection period, and lodging an objection should not be assumed to activate VAT status. The decision should be based on the act, the current status and the costs of delay.

What should headquarters, finance and local management do now?

  1. Freeze the record. Export the full filing, SPV and correspondence trail. Do not overwrite the version originally filed; keep a separate corrected draft.
  2. Assign one owner for the timeline. List applications, ANAF requests, hearings, decisions, communication dates, registry changes and invoices issued. Include who received each notice and on whose behalf.
  3. Confirm the entity and its transactions. Identify the Romanian applicant, the foreign parent or branch, the intended supplies and the place-of-supply assumptions. Check whether the group’s commercial team used “VAT registration” to refer to a different identification or reporting obligation.
  4. Compare every reason in the act with evidence. Make a two-column matrix: ANAF’s finding and the dated document that confirms, corrects or disputes it. Identify gaps rather than inventing explanations.
  5. Choose a procedural response. Determine whether ANAF is asking for more information, has cancelled a registration or has issued a formal refusal decision under the applicable route, including whether an initial application is actually at issue. Verify the decision’s appeal instructions and the available remedy before sending a letter labelled “appeal”.
  6. Control the commercial consequences. Ask finance to assess invoicing, VAT treatment, input VAT and contractual promises during any period of cancellation or pending registration. Consult the current ANAF’s public VAT registry for status, while preserving the underlying decisions as the legal record.

Illustrative case: a Romanian subsidiary with a cancelled VAT registration

What the document review can reveal

Illustrative scenario, not a client testimonial: A foreign-owned Romanian subsidiary prepares its first invoices. Its finance team reports that “ANAF refused the VAT number”, but the file contains a VAT certificate and a separate cancellation decision. The lawyers first identify the application route, compare the two acts and their communication dates, and ask the tax adviser to map invoices against the effective cancellation date.

The legal review then tests the actual cancellation ground against the company and relevant persons, preserves any objection period and sets out the evidence needed for a response or challenge. The next step depends on the documents and the tax position; this example makes no claim about an actual Atrium mandate or a guaranteed result.

How a focused legal review can help

A scoped review can examine the ANAF act, the submitted application, the communications trail and the relevant corporate documents; identify the registration route and procedural clock; and provide a reasoned choice between responding to a request, correcting the record and challenging a decision. For a one-off VAT decision review, the scope and fee are quoted after examining the act and the filing record, and agreed in writing before work begins. For companies needing recurring authority-facing legal support, Atrium publishes an Exclusive subscription from €1,800 per month plus applicable taxes; the hours and exact services are agreed for that mandate. This subscription price is not a quoted fee for a standalone VAT objection. Tax computations, accounting corrections and filings can be coordinated with the company’s tax adviser. No professional can guarantee an ANAF outcome on an unseen record.

If a transaction depends on the VAT position, send the decision and communication evidence before asking for a fixed commercial timetable. The team can then separate the legal dispute from accounting implementation and give headquarters a list of assumptions that require confirmation.

Request a review of the ANAF decision   Discuss the file online

Frequently asked questions

Can a foreign-owned Romanian company register for VAT?

Foreign ownership alone is not the deciding criterion. Examine the Romanian company’s activities, Article 316 route and any applicable cancellation conditions. A non-resident entity or branch needs its own analysis.

Is an ANAF information request a refusal?

Not necessarily. Read the communication and preserve its response instructions. A request, a refusal decision and a cancellation decision have different procedural implications.

How long is there to challenge a VAT decision?

For an applicable fiscal administrative act, the general objection period in Article 270(1) of the Fiscal Procedure Code is 45 days from communication. Article 270(4) addresses an act missing the required appeal information. Verify the act and legally relevant communication date for the case.

Does a challenge reactivate a cancelled VAT code?

Do not assume so. Check the registry and the effective terms of the cancellation and seek specific tax advice for transactions during the affected period.

Should the company apply again or object?

That depends on whether there is a final act, its grounds, the filing record and the available time. A new filing should not be treated as a substitute for preserving an objection period.

Disclaimer: This page provides general information only and does not constitute legal advice, a legal opinion or the creation of a lawyer-client relationship. Legal solutions depend on the specific facts and documents involved.

AI-assisted content.

Finance team reviewing a Romanian RO e-Factura electronic invoice workflow

RO e-Factura Romania 2026: Foreign Company Guide

RO e-Factura in Romania is no longer only a local accounting issue. A foreign company may be affected because it has a Romanian subsidiary, a fixed establishment, a Romanian VAT registration, domestic transactions or Romanian customers. The correct result depends on the company’s VAT status and the transaction—not simply on the country in which the parent company is incorporated.

Key points for 2026:

  • From 1 January 2026, the statutory transmission deadline is generally five working days, subject to the separate legal deadline for issuing the invoice.
  • A Romanian VAT number alone does not necessarily mean that a foreign company is established in Romania.
  • Domestic B2B clearance, reporting by a non-established supplier and invoices to a foreign Romanian-VAT-registered customer must be classified separately.
  • When RO e-Factura is mandatory, a PDF is not a substitute for the validated structured electronic invoice.
  • The operational record should preserve the XML, the Ministry of Finance electronic seal or validation response, submission evidence and any corrected invoice.

This guide updates the existing Atrium article for the 2026 rules and is intended for foreign investors, finance teams, Romanian subsidiaries and non-resident businesses with Romanian VAT exposure. It should be read together with advice on Romanian tax law and, where a foreign entity needs a local fiscal identifier, the guide to obtaining a Romanian NIF tax identification number.

RO e-Factura compliance in Romania for foreign companies
RO e-Factura compliance workflow for companies operating in Romania. AI-generated illustration.

What changed for RO e-Factura in 2026?

The most important operational change is the move from five calendar days to five working days. The change was introduced through Government Emergency Ordinance no. 89/2025, which amended OUG no. 120/2021 and replaced the previous five-calendar-day transmission deadline with a five-working-day deadline effective from 1 January 2026. See also the explanatory summaries published by Contabilul and VATupdate. The deadline runs from the invoice issue date, but it cannot extend beyond five working days calculated from the statutory deadline for issuing that invoice under the Romanian Fiscal Code. Public holidays and the precise date from which the period is calculated should therefore be built into the company’s controls.

2026 pointPractical meaningControl to implement
Five working daysThe transmission period is counted in working days from 1 January 2026, subject to the invoice-issuance backstop.Use a Romanian working-day calendar and escalate before the final day.
Foreign VAT customersA Romanian-established supplier may have reporting duties for domestic invoices issued to a non-established customer registered for VAT in Romania.Separate establishment, VAT registration and invoice-delivery status in customer master data.
Special B2C exceptionsFrom 1 June 2026, Law 88/2026 introduced optional treatment for certain natural persons and specifically listed categories.Do not treat every individual customer record as identical.
Older guidanceMaterials referring to the calendar-day deadline, future 2025 B2C implementation or obsolete registration forms may be outdated.Version-control procedures and use current ANAF forms and legislation.
Scope selector
Which foreign-company profile are you assessing?

Select the closest profile. The explanation below is a screening result, not a substitute for transaction-level VAT analysis.

Romanian subsidiary

A Romanian company making domestic B2B supplies is ordinarily within the mandatory domestic system. Map invoice types, credentials, software and recipient status before go-live.

Does RO e-Factura apply to a foreign company?

There is no reliable yes-or-no answer based only on the existence of a Romanian VAT number. The analysis should identify the supplier, customer, place of supply, establishment used for the transaction, VAT-registration status and invoice category.

A Romanian subsidiary is a Romanian-established taxable person. A foreign company may also have a Romanian fixed establishment if the relevant VAT tests concerning sufficient permanence and human and technical resources are met. By contrast, a foreign company can be registered for Romanian VAT without being established in Romania.

Particular care is required where a foreign company is not established in Romania but holds a Romanian VAT registration. Such businesses should not automatically be analysed under the same mandatory domestic B2B clearance rules that apply to taxable persons established in Romania. Their obligations must be verified separately under the specific provisions applicable to non-established VAT-registered persons and any optional RO e-Factura registration route.

Business situationLikely RO e-Factura treatmentQuestion requiring verification
Romanian subsidiary invoices a Romanian businessDomestic B2B clearance is generally mandatory.Are any statutory exclusions or special invoice rules relevant?
Foreign company supplies through a Romanian fixed establishmentThe entity may be treated as established for the relevant transaction.Is the Romanian establishment actually involved in the supply?
Foreign company has only a Romanian VAT registrationVAT registration alone does not create a Romanian establishment. Any reporting obligations should be assessed separately from the mandatory domestic B2B clearance regime applicable to established taxable persons.What is the place of supply and has the company opted into the system?
Romanian supplier invoices a non-established customer registered for Romanian VATReporting obligations should be analysed under the specific rules applicable from 1 January 2026. Additional commercial transmission arrangements may still be required depending on the recipient’s status and access to the system.Is the recipient participating in RO e-Factura or only VAT-registered?
Export, intra-Community supply or service with place of supply abroadGenerally outside the domestic B2B exchange rule, subject to transaction-specific reporting.Is the VAT classification and evidence supporting the cross-border treatment correct?

Important distinction: an obligation to report invoice data is not always identical to full platform exchange between supplier and recipient. A non-established business should confirm whether it is reporting a domestic transaction, voluntarily registered in RO e-Factura or subject to the domestic clearance route because of a Romanian establishment.

How does the electronic invoice flow work?

The invoice is prepared as structured data compliant with the Romanian semantic model, based on the European e-invoicing standard. It is transmitted through the Ministry of Finance infrastructure, commonly through SPV-integrated software or an authorised technical solution. The system validates the file. If validation succeeds, the electronic seal is applied and the validated file becomes the system invoice. If it fails, the issuer receives an error response and must correct and resubmit it.

Invoice flow
From accounting data to defensible archive

Select a control point to see what the finance or IT team should retain.

Create structured XML

Generate the invoice from accurate supplier, customer, VAT and line-item data using the current RO_CIUS technical rules.

The official platform makes files available for download for a limited operational period. This is not a substitute for the company’s own legally compliant archive. The archive should allow the original XML, seal or validation status, readable representation, correction trail and accounting entry to be matched.

Technical specifications, validators and official web applications are published through the Ministry of Finance technical information page and the RO e-Factura web applications page.

Which transactions are in scope?

The Romanian rules cover several legally distinct streams: B2B, B2G and B2C reporting, as well as particular reporting obligations for non-established persons. Companies should not use a single ERP flag called “Romanian customer” as a substitute for the legal analysis.

The B2C reporting regime introduced for suppliers established in Romania should not automatically be assumed to apply to every non-resident supplier. For foreign businesses without a Romanian establishment, the legal position should be verified separately based on the applicable provisions and transaction structure.

Transaction2026 starting positionOperational note
Domestic B2B between persons established in RomaniaMandatory platform exchange, unless a statutory exclusion applies.The validated XML is the legally relevant electronic invoice.
B2G invoice within the statutory regimeMandatory according to the public-procurement and e-invoicing rules.Check public authority identifiers and contract references.
B2C invoice issued by an established supplierReporting is generally mandatory, with specific 2026 exceptions.The consumer does not need SPV access for the commercial invoice.
Domestic transaction by a non-established VAT-registered supplierA reporting obligation may apply; optional system registration changes the mechanics.Confirm current registration form and recipient-delivery channel.
Export or intra-Community supplyGenerally outside the domestic B2B exchange obligation.Retain evidence supporting the VAT treatment and destination.
Simplified invoice or other statutory exceptionTreatment depends on the specific legal exception.Do not infer exclusion merely because the amount is small.

How is the five-working-day deadline calculated?

From 1 January 2026, the invoice must generally be transmitted within five working days from the issue date, but no later than five working days after the last legal date on which the invoice should have been issued. The day of the triggering event, weekends and Romanian public holidays can affect the calculation under the applicable time-computation rules.

A delayed invoice issue date does not automatically postpone the transmission deadline. Where the invoice is issued after the statutory issuance deadline under Article 319 of the Romanian Fiscal Code, the five-working-day transmission period must be assessed by reference to the legal issuance deadline rather than the late issuance date. This backstop is also explained in the 2026 deadline summary.

Deadline control
A working-day clock needs four checks

Select a card to see the control that prevents a false deadline.

Confirm issue date

Use the date actually stated on the invoice and reconcile it with the accounting event. Backdating or delayed batch creation can create an immediate compliance risk.

For example, if an invoice is issued on a Monday and there is no public holiday, Tuesday is ordinarily the first working day and the following Monday is the fifth. This is only an illustration: the statutory invoice-issuance deadline and Romanian public holidays must also be checked.

What happens if an invoice fails validation?

A technically rejected file has not completed the required process. The response should be triaged immediately: identify whether the problem concerns syntax, master data, tax codes, totals or a business-rule conflict; correct the source data; regenerate the XML; resubmit it; and preserve both the failed and successful responses.

A successfully communicated invoice cannot simply be “returned” inside the system. Commercial objections should be handled separately, and corrections should follow Article 330 of the Romanian Fiscal Code. The corrective document must itself be transmitted when the RO e-Factura obligation applies.

What penalties and audit risks should foreign companies consider?

The penalty analysis depends on the legal obligation that has been breached. Late reporting can attract fixed fines by taxpayer category. For mandatory domestic B2B exchange, issuing or accepting an invoice outside the system can trigger a percentage-based sanction. The 15% sanction should not be applied mechanically to every cross-border or non-resident scenario without first confirming that the relevant statutory route covers the transaction and party.

The applicability of the 15% sanction should always be assessed by reference to the specific statutory obligation governing the transaction, including the supplier’s establishment status and the legal route under which the invoice was required to be transmitted.

RiskPossible consequencePreventive evidence
One or more late invoices in a calendar monthGenerally RON 5,000–10,000 for large taxpayers; RON 2,500–5,000 for medium taxpayers; RON 1,000–2,500 for other legal persons and individuals.Deadline dashboard, submission timestamps and exception log.
Mandatory domestic B2B invoice issued outside the systemA sanction equal to 15% of the total invoice value may apply to the issuer under the relevant rule.ERP block preventing off-system finalisation of in-scope invoices.
Recipient records an in-scope domestic B2B invoice received outside the systemA corresponding 15% sanction may apply to the recipient, subject to the statutory conditions.Accounts-payable validation against the system record.
Validation failure left unresolvedThe invoice may remain untransmitted and become late.Error queue, named owner, retry log and successful response.
Wrong establishment or customer classificationIncorrect platform route, missing report or duplicate delivery.Documented VAT and establishment decision tree.
Control map
Where implementation most often fails

Select a risk to see the corresponding control.

Wrong customer status

Maintain separate fields for country, Romanian VAT number, establishment status, customer type and participation in RO e-Factura. One “foreign” flag is not enough.

Implementation checklist for a foreign company

  1. Map the Romanian footprint. Identify subsidiaries, branches, fixed establishments, VAT registrations and fiscal representatives.
  2. Classify transaction flows. Separate domestic B2B, B2G, B2C, exports, intra-Community supplies, local reverse-charge cases and other cross-border services.
  3. Confirm access and authority. Verify SPV access, qualified certificates, mandates and the persons authorised to submit or retrieve files.
  4. Update master data. Record establishment status, Romanian VAT identifiers, customer type and system-participation status separately.
  5. Test XML generation. Validate tax codes, units, discounts, advance invoices, credit notes, currency and rounding rules.
  6. Build deadline monitoring. Use Romanian working days, identify the statutory issue-date backstop and prevent submission only on the final day.
  7. Create an error workflow. Route rejected files to a named owner and require documented resubmission.
  8. Control incoming invoices. Reconcile accounts payable with RO e-Factura where domestic B2B exchange is mandatory.
  9. Archive the evidence. Preserve XML, seal or response, readable copy, corrections and submission logs under the applicable accounting and tax-retention rules.
  10. Review changes. Monitor the official Ministry of Finance RO e-Factura hub, current legislation and ANAF technical announcements.

Official registration and verification resources

At the time of publication, ANAF documentation refers to Form 081 for the optional register, Form 082 for the mandatory register and Form 083 for certain non-resident operators. Companies should verify the current ANAF form catalogue before implementation, as registration procedures and form numbering may change over time.

At the time of publication, Form 083 is generally used by certain non-established operators wishing to opt into RO e-Factura. Companies should verify the current ANAF requirements before filing because registration procedures may change.

Use the official ANAF forms catalogue and the ANAF online registers. For the governing framework, consult the current consolidated text of Government Emergency Ordinance no. 120/2021, together with subsequent amendments including Law no. 88/2026.

Need a transaction-specific RO e-Factura review?

A focused review can determine whether a foreign company is established, merely VAT-registered or subject to a separate domestic reporting route, and translate that conclusion into an implementable invoice workflow.

Book a Consultation

Frequently asked questions

Does a Romanian VAT number make a foreign company established in Romania?

No. VAT registration and establishment are separate concepts. A fixed-establishment analysis considers permanence and appropriate human and technical resources, as well as whether that establishment is involved in the transaction. A Romanian VAT registration obtained through direct registration or fiscal representation does not in itself create a Romanian fixed establishment for VAT purposes.

Are all invoices involving a foreign company reported through RO e-Factura?

No. The result depends on the supplier, customer, place of supply, establishment status, Romanian VAT registration and invoice category. Exports and intra-Community supplies are generally outside the domestic B2B exchange rule, although other reporting obligations may apply.

What is the RO e-Factura deadline in 2026?

From 1 January 2026, the general transmission deadline is five working days from issue, but no later than five working days calculated from the statutory deadline for issuing the invoice. Romanian public holidays and the applicable time-computation rules must be included.

Is a PDF invoice sufficient?

Not where mandatory RO e-Factura exchange applies. The structured XML validated through the system and accompanied by the Ministry of Finance electronic seal is the legally relevant electronic invoice. A PDF may remain useful as a readable copy.

Can a recipient reject an invoice in RO e-Factura?

The system invoice cannot simply be returned. The recipient may communicate objections, while any correction should follow Article 330 of the Fiscal Code and be transmitted through RO e-Factura when the obligation applies.

What should a company do after a validation error or platform problem?

Preserve the response and technical logs, identify and correct the error, resubmit promptly and retain the successful confirmation. A company should not assume that a technical issue automatically extends the statutory deadline; any official unavailability procedure should be checked on the facts.

This article provides general information on Romanian electronic invoicing and tax compliance. The result depends on the transaction, place of supply, establishment, VAT status, invoice type, technical implementation and legislation in force. It does not replace legal or tax advice on a specific invoice flow.

AI Notice: AI-assisted content, reviewed and approved by a qualified Romanian lawyer.